My Office 365 client is unable to sign into https://outlook.office.com

2026-11-18T09:35:33.3466667+00:00

The error comes up as follows:

UTC Date: 2026-11-18T07:19:12.292Z

Client Id: [Moderator note: Personally Identifiable Information removed] 

Session Id: [Moderator note: Personally Identifiable Information removed] 

Client Version: 20261112073.05

BootResult: fail

Back Filled Errors: Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined|Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|Unhandled Rejection: SyntaxError: Failed to execute 'json' on 'Response': Unexpected end of JSON input:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined|undefined:undefined

err: Error: 401

esrc: StartupData

et: ServerError

estack: Error: 401

at Object.b [as createStatusErrorMessage] (https://res.public.onecdn.static.microsoft/owamail/hashed-v1/react19/scripts/owa.mailindex.a3392149.js:1:1036)

at https://res.public.onecdn.static.microsoft/owamail/hashed-v1/react19/scripts/owa.mailindex.a3392149.js:1:195164
```st: 401

efe: JN3P275CA0160

reqid: [Moderator note: Personally Identifiable Information removed] 

cv: rN2F67hxKKikapQnXHB5sK.3.1

Outlook | Web | Outlook on the web for business | Email
0 comments No comments

3 answers

Sort by: Oldest
  1. AI answer

    2026-11-18T09:37:04.51+00:00

    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:

    1. Sign in to the Microsoft 365 admin center.
    2. Open Health → Service health.
    3. 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
    4. 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.
    5. 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:

    1. Open an InPrivate/Incognito window and sign in using only the affected work account.
    2. 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 HTTP 401.^2^
    3. Test the same account from another device and another network—for example, a mobile hotspot rather than the corporate network.
    4. 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, and outlook.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

    1. How to check Microsoft 365 service health
    2. I get this error message when I try to launch Microsoft outlook cloud. How can I fix this? - Microsoft Q&A
    3. How to troubleshoot Microsoft Entra sign-in errors
    4. What is the Sign-in diagnostic in Microsoft Entra ID?
    5. Microsoft 365 URLs and IP address ranges
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Airfire solutions Airfire solutions 0 Reputation points
    2026-11-18T09:43:01.5166667+00:00

    Please explain how I escalate - with the correct URL.

    This did not solve my problem, the issue does not follow the network the browser or even the device. I have the same issue if I make the attempt from 4 different browsers located on a machine on a different network 10 km's away.

    Was this answer helpful?

    0 comments No comments

  3. Helen Luu 3,845 Reputation points Independent Advisor
    2026-11-18T10:24:45.69+00:00

    Hello @Airfire solutions Airfire solutions

    I understand you are receiving a 401 Unauthorized error when trying to access the resource. This error generally means that the request could not be authenticated or authorized successfully. In some cases, it may be related to the account, sign-in configuration, access policies, or the network from which the resource is being accessed.

    In this situation, I would recommend contacting your IT administrator so they can investigate this from the organization side. Since they have access to the relevant administrative portals and tenant configuration, they can review the following areas:

    • Check the Microsoft Entra ID sign-in logs for your account around the time the error occurs. The logs may provide additional details, such as a failure reason, error code, Conditional Access result, or authentication requirement.
    • Review any Conditional Access policies or other access restrictions that may be preventing access, particularly policies based on network location, device compliance, authentication method, application, or user/group membership.
    • Confirm whether the resource is restricted to the organization's trusted or corporate network, and whether access from an external network, home network, VPN, or another location is permitted.
    • If the organization uses named locations or IP-based restrictions, verify that your current public IP address or network range has been configured correctly. If an IP address needs to be allowlisted, the IT administrator should also confirm that the appropriate range has been added completely.
    • Check whether your account has the necessary permissions, role, or license to access the affected resource.

    Please also provide your IT administrator with the approximate time when the issue occurred, the resource or service you were trying to access, the network you were connected to, and a screenshot of the error message with any personal or sensitive information removed. These details can help them correlate the issue with the sign-in logs and narrow down the cause more efficiently.

    If the IT administrator confirms that the account, authentication, Conditional Access policies, network restrictions, permissions, and IP configuration are all correct but the 401 error continues, further investigation with the appropriate service administrator or Microsoft Support may be necessary.

    I hope this helps clarify the error and the recommended next steps. Please feel free to share any updates or additional details if the issue continues.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.