<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z0000AFqv6MCQROkta Classic EngineAuthenticationAnswered2025-10-26T09:01:37.000Z2024-09-21T20:17:44.000Z2024-11-19T19:28:44.000Z

urn4s (urn4s) asked a question.

September 21, 2024 at 8:17 PM
Office 365 Federation - 400 Bad Request

Hi All

 

I have federation a domain from Entra ID to Okta using the WS federation Automatic setup with the Office 365 App within the Okta portal and I can login to Okta and click through to Office 365 and login all ok, However if I try and go to office.com, enter my email thus then forwarded to Okta I get an error 400 Bad request from Okta, So can only login to office 365 via the Okta portal direct, which does not seem correct?

 

Thanks

  • 4 answers
  • 498 views
PatrickG.00794 likes this.

  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hi @urn4s (urn4s)​ , thank you for contacting Okta Community.

     

    At 14:53pm PT on September 23th, Okta's Engineering Team team became aware of an O365 federation issue affecting customers on all cells. During this time, you may experience a "400 Bad Request" error when federating new domains. Okta is documenting a workaround and developing a fix release to mitigate the issue. Keep an eye on our Status page for updates.

     

    UPDATE: workaround article published.

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

     

     

    Expand Post
    Selected as Best

  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hi @urn4s (urn4s)​ , thank you for contacting Okta Community.

     

    At 14:53pm PT on September 23th, Okta's Engineering Team team became aware of an O365 federation issue affecting customers on all cells. During this time, you may experience a "400 Bad Request" error when federating new domains. Okta is documenting a workaround and developing a fix release to mitigate the issue. Keep an eye on our Status page for updates.

     

    UPDATE: workaround article published.

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

     

     

    Expand Post
    Selected as Best

  • urn4s (urn4s)

    Hi

     

    Thats done it! Thanks very much

  • RichardL.50159 (Customer)

    This article is no longer available. I am experiencing the same issue and need a workaround. Diana can you repost the article and confirm that the link works?

    • User17157611498146715886 (Customer Support Online Community and Social Care)

      Hello @RichardL.50159 (Customer)​ , thank you for contacting Okta Community. The article is no longer available because this was an issue related to a federation issue that has since been resolved.

       

      I would suggest reviewing the documentation we have available on EntraID:

      Microsoft Entra ID integration - check if the integration was done according to this guide

      Configure Single Sign-On for Microsoft Entra ID

       

      If you still need assistance and have a paid account, you can open a ticket here. Please contact your Account Executive if you have a paid account and encounter trouble opening a ticket.

      If you do not have a paid account but would be interested in one, you can contact our Sales team here.

       

      Otherwise, we encourage everyone to take advantage of our public library and community forum. You can also check the Roadmap for upcoming features or the status page for recent service history.

       

      Regards. 

      --

      Help others in the community by liking or hitting Select as Best if this response helped you.

       

      Expand Post
This question is closed.
Loading
Office 365 Federation - 400 Bad Request