<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
0D5KZ000019sMzU0AUOkta Classic EngineAuthenticationAnswered2025-07-31T15:19:51.000Z2025-07-23T19:36:24.000Z2025-07-31T15:19:51.000Z

ShezK.21748 (Customer) asked a question.

July 23, 2025 at 7:36 PM
Okta Office 365 WS-Federation Error: Sorry, but we’re having trouble signing you in. AADSTS90019: No tenant-identifying information found in either the request or implied by any provided credentials.

I am trying to connect our Office 365 portal to Sign On with Okta via WS-Federation. I first got the error Office 365 Error "Your account has not been configured for this application" seen resolved in this support thread https://support.okta.com/help/s/article/Office-365-Error-Your-Account-Has-Not-Been-Configured-For-This-Application?language=en_US

 

But since making that profile change I now get the error AADSTS90019: No tenant-identifying information found in either the request or implied by any provided credentials.

 

 

  • 2 answers
  • 418 views

  • ShezK.21748 (Customer)

    The reason I was getting this error was that Microsoft 365 Apps for Business does not support federated authentication, including WS-Federation, which is required for SSO integration with identity providers like Okta.Federation capabilities are only available with enterprise-level Microsoft 365 plans, such as:

    Microsoft 365 E3 or E5

    Office 365 E1, E3, or E5

    Expand Post
    Selected as Best

  • paul.stiniguta1.508386743840768E12 (Okta, Inc.)

    Hello @ShezK.21748 (Customer)​ Thank you for posting on our Community page!

     

    This issue could be caused by the domain used when assigning the user to the application. If your domain is different then the one used to assign the user in Okta, this could cause this issue.

    Please also see this article that might help you in this case:

    https://learn.microsoft.com/en-us/answers/questions/5425430/what-is-the-resolve-to-the-below-error-code-aadsts?forum=msoffice-all&referrer=answers

     

    Thank you for reaching out to our Community and have a great day!

    --

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

    Expand Post

  • ShezK.21748 (Customer)

    The reason I was getting this error was that Microsoft 365 Apps for Business does not support federated authentication, including WS-Federation, which is required for SSO integration with identity providers like Okta.Federation capabilities are only available with enterprise-level Microsoft 365 plans, such as:

    Microsoft 365 E3 or E5

    Office 365 E1, E3, or E5

    Expand Post
    Selected as Best
This question is closed.
Loading
Okta Office 365 WS-Federation Error: Sorry, but we’re having trouble signing you in. AADSTS90019: No tenant-identifying information found in either the request or implied by any provided credentials.