<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
0D51Y00008vc5XMSAYOkta Classic EngineAdministrationAnswered2026-04-01T09:00:20.000Z2020-07-07T12:31:33.000Z2020-07-08T12:32:52.000Z

p0xb3 (p0xb3) asked a question.

Federation with o365 and on-prem AD

When you attemps to configure the federation with Office 365 you are warned that this federation will overwrite any existing federation. We have a federation between our on-prem AD and o365. Will that be overwritten or can they coexist?


  • sandeepk.84743 (Wipro Technologies)

    Hi Neil,

     

    I don't think OKTA will change your On-Premise AD federation. however Enabling SSO with Office 365 does a couple of things: 

    • Modifies the settings of your verified Office 365 domain to point to your Okta Tenant (or overwrites the Federation Settings if they are already configured)
    • Changes the behaviour of the Office 365 login page to redirect you to the configured IDP when the email suffix matches that of a Federated domain

     There's also a couple of things to be aware of: 

    • Ensure that a non-federated (ideally the onmicrosoft.com) domain is set as the default domain ahead of time (federated domains cannot be default and will give an error)
    • Ensure that the account you are using for AADConnect and your admin account are using a non-federated domain (also, ideally onmicrosoft.com)

     In regards to on-premises impact, we would not expect anything to change at all. Commonly, customers ask about mail flow and DNS impact, however neither of these will be modified as a result of setting the domain as federated.  The Set-MSOLDomainAuthentication cmdlet in Powershell (https://msdn.microsoft.com/en-us/library/dn194112.aspx) can also be used to revert the domain to Managed rather than Authenticated if you did want to test toggling Federation settings.

     

    Expand Post
    • p0xb3 (p0xb3)

      Thanks Sandeep. Could you expand on the SSO caveat because it seems that this would overwrite our existing federation with AD? The reason that we want the Okta federation is so that we can use SSO with Office 365.

  • k5fuw (k5fuw)

    Each domain that you register in O365 can only point to a single identity provider at a time. If your domain is currently federated with your on-premises environment (using ADFS?), then federating that same domain in Okta will cause that domain's federation settings in O365 to be overwritten, which will break the federation with your on-premises environment. If your goal is to switch identity providers, that's the way to go, just be certain that all of your AD users have been assigned to the O365 integration in Okta so they can continue to authenticate.

    Expand Post
    • p0xb3 (p0xb3)

      Mike

      Thanks for this explanation. We manage our users on-prem and ADSync syncs changes to o365, but the users authenticate against o365. For instance we need to input a password in Outlook. If we switch to Okta as our IDP will ADSync continue to work for provisioning and changes?

      Neil
      Expand Post
  • feok4 (feok4)

    Neil, we used Okta to replace the AADC, not work in combination with it. I would read the articles on the support site as they go into detail re Okta and AADC (I assume you mean AADC when you refer to ADSync). The biggest caveat we've seen with Okta is you need to enable universal sync to pull in groups, etc. The issue with this is you can't pick and choose which group types, contacts, etc you want to pull in. IMO, this is major drawback on using universal sync.

     

    From the O365 provisioning tab in Okta for Universal Sync:

    Synchronize all directory objects. 

    Administer in source directory.

    Cannot be used with DirSync, AADSync, or AADConnect.

     

    Expand Post
    • p0xb3 (p0xb3)

      Thanks Jeff

      I do mean AD Connect rather than ADSync and I have read the docs but will go through them again. Thanks for the tip about the universal sync. This would be an issue for us.

      Neil
      Expand Post
This question is closed.
Loading
Federation with o365 and on-prem AD