<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
0D54z0000AH8iTrCQJOkta Classic EngineIntegrationsAnswered2024-11-28T09:53:49.000Z2024-11-01T13:12:32.000Z2024-11-28T09:53:49.000Z

RobJ.66541 (Customer) asked a question.

Microsoft 365 Application - WS Federation - Auto - Issue

Hi Everyone

 

I have done this previously, with no issues in the past, however ive been trying to add MS 365 as an application for the past few days, and keep getting a failed message when trying to Auto federate.

 

Please review the form to correct the following error(s):

  • Could not setup the domain federation with Office 365; please retry setting up the federation for this domain after a few hours.

 

Logs say the following:

 

Unable to setup the domain federation, received error: Received response with HTTP status code 400. httpStatusCode=400 errorCode=Request_BadRequest errorMessage="Invalid value specified for property 'issuerUri' of resource 'InternalDomainFederation'." client-request-id=dbdd5617-b6a2-4fcc-8f75-3ca438c7d5d7 request-id=93c77387-dcb3-47b7-9df4-683c1947e75a timestamp='Fri, 01 Nov 2024 13:07:15 GMT' method=POST url=https://graph.microsoft.com/v1.0/domains/<My Domain>/federationConfiguration

 

However - i just cant seem to get past this - any one get any helpful ideas?


  • Mihai N. (Okta, Inc.)

    Hi @RobJ.66541 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

     

    It could be related to the requirements for Microsoft Graph.  

      

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

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

    Expand Post
    • RobJ.66541 (Customer)

      No - the domain starts with a "J"

       

      If i set this up manually - it works fine - it just wont work if i set it to Auto.

      • SachinP.28093 (Customer)

        We ran into the same problem, our domain starts with a number and Okta Support confirmed it's a bug on their side with numbers in the domain (so may be just Auto sets in general).

         

        However we maybe found a potential workaround via the manual setup that kind-of works (just unconfirmed at this point) but:

         

        • Set the federation manually as per the Okta Powershell commands
          • Note the https://xxxxx from the Powershell command, the XXX value
        • Set-MsolDomainFederationSettings -DomainName [DOMAIN] -IssuerUri [DOMAIN}:[XXXValueFromOktaPS]
        • Get-MsolDomainFederationSettings -DomainName [DOMAIN] and verify the IssuerURI = [DOMAIN]:[XXXXX]
        • Go back to Okta - set it to Automatic, Fetch and Select your domain + Save

         

        This worked for us.

        Expand Post
This question is closed.
Loading
Microsoft 365 Application - WS Federation - Auto - Issue