The My Neomagora login page spins endlessly, displays a cryptic error, or redirects you in a loop to a Microsoft login screen. Yet, you have entered the correct identifier, the one in [email protected]. The password also seems correct. The problem rarely comes from what you type: it comes from what your browser has already stored in memory.
Why the browser blocks access to My Neomagora even before the password
My Neomagora is hosted on a Microsoft 365 SharePoint tenant specific to NEOMA Business School. When you open the page, the browser automatically looks for an already active Microsoft account in the current session. If you are logged into a personal Outlook account, an old internship account, or another Microsoft 365 tenant, the browser tries to switch between two incompatible environments.
Further reading : What time to fully enjoy the paradise beaches of Guadeloupe?
The result: a redirection loop between two Microsoft tenants that never resolves. The screen remains stuck or returns a vague error message like “We couldn’t sign you in.”
Have you noticed that the problem sometimes disappears when switching devices? That’s because the second device doesn’t have a conflicting Microsoft session cached. The most direct solution exploits the same principle without changing machines: open a private browsing window. This mode starts without cookies or pre-existing sessions, allowing the browser to handle only the NEOMA identifier.
See also : Everything You Need to Know About the Tesla Charging Network: Operation, Benefits, and Coverage
Before resetting your password or contacting support, first try to log in to My Neomagora Neoma from a private window. In most cases, this is enough.
Private browsing and session cleanup: the concrete steps to follow
The private browsing test serves to confirm that the blockage indeed comes from a session conflict. If the login works in private, the session conflict is confirmed. Here’s how to proceed next to regain normal access in your usual browser.
Step 1: test in private window
Open a private browsing window (Ctrl + Shift + N on Chrome and Edge, Ctrl + Shift + P on Firefox). Go to the My Neomagora login page and enter your NEOMA identifier. If the page loads normally, the session conflict is confirmed.
Step 2: clear Microsoft cookies from the main browser
The private window resolves the symptom, not the cause. To regain stable access, you need to delete the cookies related to Microsoft domains in your main browser. No need to clear all history: target the cookies from the following domains.
- login.microsoftonline.com – manages Microsoft 365 authentication and retains active session tokens
- neoma.sharepoint.com – stores the session specific to the NEOMA tenant
- microsoft.com and live.com – related to personal Outlook or Hotmail accounts that conflict
On Chrome, go to settings, then Privacy and security, then Cookies and site data. Use the search bar to filter each domain and delete them one by one. Close all browser windows, reopen it, and then try logging in again.
Step 3: disconnect conflicting Microsoft accounts
If the problem returns after a few days, it means another Microsoft account is automatically reconnecting. Go to myaccount.microsoft.com with your personal account, then disconnect the active sessions. Only one active Microsoft account per browser avoids recurring conflicts.
Forgotten or expired NEOMA password: the account.neoma-bs.fr portal
When private browsing doesn’t resolve anything, the password itself may be the issue. NEOMA has centralized the management of identifiers on a dedicated portal accessible from the My Neomagora login page (link “Forgot your password?”).
This portal, hosted on account.neoma-bs.fr, allows you to reset the password associated with your identifier [email protected]. The password used for My Neomagora is the same as the one set during administrative registration. If you have changed it since, the latest version is what matters.
Here are a few points to check before initiating the reset:
- Your identifier includes the last two digits of your entry year at NEOMA, not your birth year
- The suffix is indeed @neoma-bs.com for SharePoint access (the @first identifier is for the Wi-Fi network on campuses)
- Accents and special characters in your name may differ from what you expect – check the registration confirmation email if in doubt
Network blocks and restrictions preventing access to NEOMA SharePoint
Some networks block or filter connections to Microsoft 365 servers. This is common on corporate networks, public hotel Wi-Fi, or municipal library Wi-Fi, and sometimes even on internet boxes configured with strict parental controls.
An active VPN can also cause a blockage. Microsoft 365 sometimes detects VPN connections as suspicious and refuses authentication or imposes additional verification. If you are using a VPN, temporarily disable it before attempting to log in.
Another scenario: an outage on Microsoft’s side. SharePoint occasionally experiences service incidents that affect specific tenants. The page status.office.com displays the real-time status of Microsoft 365 services. If SharePoint Online appears as having an incident there, all you can do is wait.
Contact NEOMA IT support when nothing else works
If private browsing, cookie clearing, password resetting, and network changing have yielded no results, the problem is likely on the server side or with your specific account. NEOMA provides a Service Center of the Information Systems Department accessible via an online ticket form.
From the My Neomagora login page, a “Need help?” link redirects to this form. Specify in your request the browser used, the network (campus Wi-Fi, home, 4G), the exact error message, and whether the private browsing test worked or not. These details allow support to diagnose without further exchanges.
Most blockages on My Neomagora can be resolved before reaching this point. The private browsing reflex alone eliminates the most common scenario. Keep it as your first systematic test, including for other Microsoft 365 services related to your NEOMA studies.