Sending, receiving, and organizing email in Outlook on the web for business
Check Microsoft 365 admin center → Health → Service health → Exchange Online first, because this Outlook on the web 401 occurs while loading StartupData, and the error alone cannot distinguish a Microsoft service incident from a tenant, account, session, or network problem.
1. Check Exchange Online service health
A Microsoft 365 administrator should:
- Sign in to the Microsoft 365 admin center.
- Open Health → Service health.
- Review:
- Active issues Microsoft is working on
- Issues for your organization to act on
- Issue history, using the failure time 2026-11-18 07:19 UTC
- If an Exchange Online or Outlook on the web incident is listed, follow that incident’s updates rather than changing the user or tenant configuration.
- If nothing is listed, select Report an issue on the Service health page. Service health is available to Global, Service Support, and Helpdesk administrators; the public service-status page can be used when the admin center itself is unavailable.^1^
No publicly readable incident for that exact timestamp is established here.
2. Determine whether the failure follows the account, browser, or network
Perform these tests once and record the result:
- Open an InPrivate/Incognito window and sign in using only the affected work account.
- If that works, clear cookies and cached site data for Microsoft sign-in and Outlook sites in the normal browser, close every browser window, and retry. This has resolved closely matching Outlook web failures containing
BootResult: fail,StartupData, JSON-response errors, and HTTP401.^2^ - Test the same account from another device and another network—for example, a mobile hotspot rather than the corporate network.
- Test another licensed user in the same tenant:
- Only one account fails everywhere: investigate that user’s authentication and mailbox state.
- Multiple users fail: prioritize service health and tenant/network checks.
- It fails only on one browser/device: remove browser extensions and site data.
- It fails only on one network: inspect its proxy, VPN, firewall, TLS inspection, or content filtering.
Do not repeatedly reset the password unless Entra reports invalid credentials; this error does not by itself establish a password problem.
3. Correlate the attempt in Microsoft Entra
An administrator with at least the Reports Reader role should open:
Microsoft Entra admin center → Entra ID → Monitoring & health → Sign-in logs
Filter by:
- The affected user
- Status: Failure
- Time around 2026-11-18 07:19 UTC
- The Outlook/Office application, if available
Open the matching event and review Failure reason, Additional Details, Authentication Details, and Conditional Access. Capture the Entra correlation ID and sign-in error code.^3^
The Client Id, Session Id, reqid, and cv displayed by Outlook are useful support evidence, but they might not equal the Entra event’s correlation ID. Match primarily by user and UTC time.
If the event is present, select Launch the Sign-in diagnostic. Alternatively, use Diagnose & solve problems → Sign-in Diagnostic → Troubleshoot and search within 48 hours using the user, application, request/correlation ID, and timestamp.^4^
Apply only the remediation reported there—for example, completing MFA or correcting the particular Conditional Access policy. If the event succeeded but Outlook subsequently returned StartupData 401, authentication reached Entra and the investigation should move to Exchange Online/mailbox or service-side processing.
4. Check the network only if the failure is network-specific
Ensure the proxy or firewall is not blocking, rewriting, or requiring additional authentication for Microsoft 365 endpoints. Relevant required destinations include:
-
outlook.office.com,outlook.office365.com, andoutlook.cloud.microsoft -
*.outlook.com - Microsoft identity endpoints such as
login.microsoftonline.com -
*.cloud.microsoft,*.static.microsoft, and*.usercontent.microsoft
The official endpoint list specifies the applicable TCP/UDP ports and should be used rather than maintaining an improvised static list.^5^
5. Escalate if no local cause appears
Open a Microsoft 365 support request if:
- No relevant Entra failure or Conditional Access explanation exists;
- The issue follows the user across browsers, devices, and networks;
- Service health shows no incident; and
- Other Microsoft 365 applications work but Outlook on the web still fails.
Include the UTC timestamp, affected user UPN, tenant ID, browser/version, whether other users are affected, Entra sign-in details, and the displayed Client Id, Session Id, reqid, cv, and front-end server value. Avoid posting tenant and account identifiers publicly.
References