The login page keeps looping, the password seems correct, and yet nothing happens. This scenario recurs every new school year for NEOMA students trying to access MyNeomagora on SharePoint. The blockage rarely comes from a forgotten password. In most cases, it is an invisible conflict between multiple Microsoft accounts that prevents authentication from succeeding.
Microsoft Tenant Conflict: The Hidden Cause of Neomagora Blockages
You may have a personal Microsoft account for Outlook or Xbox. Perhaps also an old work account linked to an internship. And now, your NEOMA identifier in the format [email protected]. Each of these accounts belongs to what Microsoft calls a “tenant,” a distinct organizational space.
Related reading : How much can you save with Armor Lux offers at Intermarché?
When you open your browser to access Neomagora, the browser automatically selects one of these accounts. If it’s not the right one, SharePoint redirects you to an error page or asks for a password that doesn’t match anything. The problem is not your password: it’s the active Microsoft identity in your session.
This conflict is even harder to spot because Windows can itself register a work account in its system settings. On a shared computer in a library or residence, the operating system intercepts the authentication before the browser even intervenes. Nothing in the usual help pages indicates this scenario.
Read also : What to do if food gets stuck in your throat: practical guide and tips
A detailed guide explains how to access Neomagora from Neoma by specifically bypassing this type of blockage related to multiple sessions.
Procedure for Cleaning Microsoft Cookies and Sessions
Deleting the browser history is not enough. You need to target the cookies related to Microsoft domains that maintain an invalid session. Three domains are responsible for most blockages:
- login.microsoftonline.com: this is the centralized authentication portal. An expired cookie on this domain systematically redirects to the wrong tenant.
- office.com: Office 365 sessions remain active for several days, even after closing the browser. They can interfere with the SharePoint connection.
- sharepoint.com: Neomagora operates on SharePoint. An expired session token on this domain causes a login loop without an explicit error message.
In your browser settings, look for the “Cookies and site data” section and then delete only the entries related to these three domains. On Chrome, type chrome://settings/siteData in the address bar and filter by “microsoft” then “sharepoint”.
After this cleanup, open a private browsing window to test the connection. This mode ignores all existing cookies and forces you to manually enter the NEOMA identifier. If the connection works in private mode but not in normal mode, you have confirmation that the problem comes from a session residue.
NEOMA Password Reset: The Correct Process
Be careful not to confuse two different procedures. The “Forgot Password” link displayed on the Neomagora SharePoint page redirects to the standard Microsoft reset. This process does not always resolve the access blockage to the NEOMA portal itself.
The reliable procedure goes through the dedicated page account.neoma-bs.fr. You enter your identifier in the format [email protected] and your personal email address (the one provided during administrative registration). A reset link will arrive at your personal email, not at your NEOMA address.
This detail is important. If your NEOMA access is blocked, you obviously cannot check your inbox [email protected]. Everything goes through the Gmail, Outlook, or other address you provided upon arrival.
Once the password is changed, wait a few minutes before trying to log in again. The propagation between the NEOMA system and Microsoft servers can sometimes take a short delay.
Neomagora Connection on Mobile and App
On both Android and iOS, Microsoft applications (Teams, Outlook, OneDrive) share the same authentication token. If you are logged into Teams with a personal account, opening Neomagora via the mobile browser may inherit this session.
The most direct solution: log out of all Microsoft applications on your mobile before attempting access. Go into the settings of each application, section “Accounts,” and remove accounts that are not your NEOMA identifier.
Then use the mobile browser in private browsing to open neoma.sharepoint.com/sites/myneomagora/FR. Enter your identifier @neoma-bs.com and the freshly reset password if necessary.
One point to keep in mind: Neomagora does not require a VPN to function off-campus. SharePoint services are hosted in the Microsoft cloud. If someone advises you to install a VPN to access Neomagora, the problem lies elsewhere, likely in a conflict of accounts or an outdated shortcut.
When to Contact the IT Service Center
If after cleaning cookies, using private browsing, and resetting the password via account.neoma-bs.fr the blockage persists, the problem may be on the server side. The NEOMA IT Service Center can be reached via a ticket form on hotlinesi.neoma-bs.fr. Describe precisely the steps already attempted to avoid being redirected to the standard procedure.
The majority of connection issues with Neomagora are resolved by identifying which Microsoft account the browser or system is using by default. Cleaning the cookies from the three Microsoft domains, testing in private browsing, and then resetting via account.neoma-bs.fr covers almost all cases. The reflex to change the password repeatedly without clearing existing sessions is the reason why the blockage seems to persist even though the credentials are correct.