Microsoft localise cause error to see form in Edge browser

Wendy McBride 0 Reputation points
2026-09-15T17:53:38.12+00:00

I have been receiving this error message 'Unable to execute OIDC flow: Received invalid status code 400' on a website when I am trying to complete a form online. I have contacted the IT support of this website and they advised that this happened for a few of the customers and it appears to do with our Microsoft local settings causing the form not able to upload on the site. Can someone help?

Microsoft Edge | Website issues | Windows 11
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Vikki-T 10,575 Reputation points Microsoft External Staff Moderator
    2026-09-16T06:58:32.8133333+00:00

    Hi Wendy McBride,

    I understand how disruptive this is when the form cannot be completed, especially after the website’s support team suggested that the regional settings may be involved.

    The browser checks already provided are useful for ruling out local session or extension issues. In addition, please compare your Windows regional format with the display language used in Microsoft Edge:

    • In Windows 11, open Settings > Time & language > Language & region and note the Regional format.
    • In Edge, open Settings > Languages and check the current display language.
    • If the language and regional format are different, temporarily set them to the same region, restart Edge, and test the form again.

    Please also check whether the same message appears in another browser. If it does, this would point more strongly to the website’s authentication or form-processing configuration rather than an Edge-specific setting.

    Since the message reports an OIDC status code 400 and the website’s IT team has seen the same behavior for multiple customers, please ask them to review the failed authentication request in their server logs. Providing them with the exact time of the attempt, the affected page, and any correlation or request ID shown on the page would help them identify which request parameter was rejected.

    Please note that this is a user-to-user support forum. Contributors cannot access the website’s authentication logs or modify its OIDC configuration directly. I hope these checks help determine whether the regional settings are involved or whether the website needs to correct the authentication flow. Thank you so much for your understanding.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

  2. AI answer

    2026-09-15T17:53:56.2433333+00:00

    Try these browser-side checks in Microsoft Edge on Windows 11:

    1. Clear cookies and cached data for the site Corrupted or excessive cookies can break sign-in and form flows. Microsoft documents cases where too many cookies cause request/header problems and clearing cookies resolves it.
    2. Test in an InPrivate window This helps confirm whether the issue is caused by cached session data, cookies, or an extension.
    3. Disable Edge extensions temporarily Extensions can modify requests or interfere with sign-in and form submission flows. If the form works after disabling them, re-enable extensions one at a time to find the cause.
    4. Check Edge privacy/cookie settings Authentication flows can fail when required cookies are blocked. In Edge, go to Settings > Privacy, search, and services and review cookie-related settings. If third-party cookies are blocked, turn that off and test again.
    5. Avoid InPrivate for sign-in testing if the site uses Microsoft authentication Microsoft documents known authentication issues in some Edge scenarios where storage is cleared across security zones, which can break sign-in flows and cause redirect or token problems.
    6. Make sure modern TLS is enabled in Windows Internet settings On Windows:
      • Press Win + R
      • Run inetcpl.cpl
      • Open the Advanced tab
      • Verify:
        • Use TLS 1.0 = unchecked
        • Use TLS 1.1 = unchecked
        • Use TLS 1.2 = checked
        • Use TLS 1.3 = checked
      • Select OK
    7. Try Microsoft Edge with the latest updates, or test another modern browser Microsoft recommends using a modern, up-to-date browser because older browser behavior can cause compatibility and authentication issues.
    8. If this only happens on a work or restricted network, ask the site’s IT team to check blocked Microsoft endpoints Microsoft documents that web sign-in failures such as 503 errors can be caused by local or corporate network restrictions blocking required Microsoft URLs.

    If the form works in InPrivate or after clearing cookies, the most likely cause is browser session data or an extension. If it fails only on one network, the likely cause is network filtering. If it fails in all browsers, the website owner likely needs to fix the site’s OIDC implementation.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    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.