<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
0D51Y00006EmtNBSAZOkta Classic EngineOkta Integration NetworkAnswered2024-04-15T13:28:26.000Z2019-05-08T14:20:12.000Z2019-05-13T14:36:32.000Z

ikwub (ikwub) asked a question.

Concerns about Federating with Azure AD?

I am trying to federate to Azure AD as part of SSO for O365. My current default domain is the vanity/company domain. Okta documentation states that you cannot federate to the default domain by design. My concern is that if I change the default domain to the onmicrosoft.com that end users will have issues accessing email and one drive folders and logging into the O365 Portal. I opened a ticket with Microsoft and the tech I spoke with stated that changing the default domain would cause issues. I want to know if there is anyone out there that has attempted to do this and if so did the end users have any issues?


  • Taylor Higley (Customer)

    I had this exact scenario several implementations. Changing the default domain from the Vanity/Company domain to the onmicrosoft.com domain had zero negative impact on existing Office 365 users. Once the default domain was changed, I proceeded to federate with OKTA for SSO without issue.

This question is closed.
Loading
Concerns about Federating with Azure AD?