A My Neoma Agora login screen that loops back on itself or returns a 403 error rarely indicates a password issue. The cause is almost always within the Microsoft 365 authentication layer, at the SharePoint tenant level that hosts the NEOMA student space. Identifying the exact mechanism of the blockage prevents wasting time on an unnecessary reset.
Corporate Proxy and Microsoft Tenant Imposed on an Internship Computer
Students in work-study or internships encounter a specific blockage that usual guides do not address. On a professional workstation, the employer’s proxy or firewall intercepts the request to the NEOMA tenant even before the SharePoint page loads.
The mechanism is simple: the company configures its machines to force authentication to its own Microsoft 365 tenant. When the student tries to access neoma.sharepoint.com, Windows automatically redirects to the professional account already registered in the session. The identifier [email protected] is never offered.
Two options work in this case:
- Use a personal device connected via 4G or on a home Wi-Fi network, outside the employer’s network perimeter.
- Open a private browsing window on the professional workstation, which bypasses the Windows session cache in most proxy configurations (except those that also block private mode).
- Request the company’s IT department to whitelist *.sharepoint.com and login.microsoftonline.com in the proxy if access to My Neoma Agora is necessary for the mission.
If none of these solutions unlock access, the issue lies with the corporate firewall and not with NEOMA. We then recommend contacting the employer’s IT department with the exact error message.
Targeted Purge of Microsoft Cookies to Restore SharePoint Access
The classic reflex is to clear the entire browser cache. This approach works, but it also disconnects all other services (email, banking, social networks). A targeted purge of Microsoft cookies is sufficient in most cases and preserves the rest of the sessions.
When the connection to My Neoma Agora fails after a normal attempt, the browser retains an expired authentication token or one linked to the wrong account. Deleting only the cookies associated with the domains microsoft.com, live.com, office.com, and sharepoint.com forces the browser to initiate a clean authentication.
Procedure on Chrome and Edge
In the browser settings, go to the Cookies and site data section. Use the search bar to filter each of the four mentioned domains. Delete them one by one, then completely close the browser before reopening it.
On Firefox, the process goes through Preferences, then Privacy & Security, then Manage Data. The principle remains the same: filter by domain and delete only the Microsoft entries.
Restarting the browser without completely closing it is not enough. On macOS, quit using Cmd+Q. On Windows, ensure no Chrome or Edge processes are still running in the task manager.
Conflict of Multiple Microsoft Accounts in the Browser
The most common blockage on My Neoma Agora has nothing to do with a forgotten password. It stems from a session conflict between multiple Microsoft accounts active simultaneously in the same browser.
A NEOMA student often has a personal Outlook account, sometimes an old university account, and their school identifier in the format [email protected]. When SharePoint detects multiple active tokens, it tries to switch to the last authenticated account, which has no rights on the NEOMA tenant.
The typical symptom: the page displays “You do not have permission to access this resource” or redirects in a loop to the account selection page without ever succeeding.
Resolution by Browser Profile Isolation
Private browsing temporarily resolves the issue. For a lasting solution, we recommend creating a dedicated browser profile for NEOMA. Chrome, Edge, and Firefox all allow managing multiple independent profiles, each with its own cookies and sessions.
In this dedicated profile, connect only the account [email protected]. No other Microsoft account should be active in this profile. This isolation permanently prevents tenant conflicts.
SharePoint Online Outage and Microsoft 365 Status Check
Before any technical manipulation, one must rule out an outage on Microsoft’s side. SharePoint Online experiences service degradations that render My Neoma Agora inaccessible regardless of local configuration.
The official Microsoft 365 status page (status.office.com) provides real-time information on the status of each service, including SharePoint Online. If a degradation is reported, no user-side action will change anything.
Another useful reflex: test the connection on another device (smartphone on 4G, tablet). If My Neoma Agora does not load on any device, the problem lies with the service and not with your configuration. In this case, monitoring the Microsoft status page and NEOMA communication channels (institutional email, school social media) remains the only option.
Local Wi-Fi Connection and False Diagnosis of My Neoma Agora
A growing share of My Neoma Agora outage reports actually stems from a local Internet connection issue. The Wi-Fi shows “connected” but the actual bandwidth is insufficient to load a SharePoint page, which requires multiple parallel requests to Microsoft servers.
The quickest test: open a lightweight site (google.fr) and a heavy site (youtube.com). If Google loads but YouTube remains slow, the bandwidth is too low for SharePoint. Restarting the router or switching to 4G immediately clarifies the issue.
On the NEOMA campus Wi-Fi network (network named “Neoma BS”), the connection requires the @first identifier. An @neoma-bs.com identifier will not work for Wi-Fi, even if it is valid for My Neoma Agora. This confusion between the two identifier formats regularly generates blockages at the beginning of the school year.
The diagnosis of My Neoma Agora outages thus follows a strict logical order: first check the Internet connection, then the Microsoft 365 status, then session conflicts, then cookies, and only as a last resort consider a password reset via account.neoma-bs.fr. Following this order prevents modifying a perfectly functional password and creating a new synchronization issue between NEOMA services.