<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
0D51Y00009QZoPiSALOkta Classic EngineOkta Integration NetworkAnswered2025-10-09T20:48:44.000Z2020-09-16T19:56:42.000Z2021-01-08T20:37:28.000Z
  • rohern (Okta)

    Hi Jeff,

    I've went through rolling back on O365 federation a couple weeks ago. MS states up to 24 hours, but in my experience it's near immediate.

    To manage objects as cloud objects you would need to remove the linked directory, if I recall.

    O365 federation requires the account be linked to a directory (AD or Okta)

    The directory sync is what removes the ability to edit the accounts as cloud accounts.

     

    Hope that makes sense

    Expand Post
  • rohern (Okta)

    As a side note, you can get a free 30day trial of O365 E3. It's fully featured with federation and provisioning. You would need your own domain name to setup, but is a very quick way to get some solid testing done

  • feok4 (feok4)

    Thanks Rus. We were able to solve it with the help of Okta PS and things went smoothly. Here were steps we followed (hopefully this will help others):

    * 4-5 days before migration, disable dirsync in the tenant via PS and remove the API config for the O365 app in Okta

    * Verify the above is complete by running the following commands. NOTES - it must return disabled, not pending disabled

    (Get-MSOLCompanyInformation).DirectorySynchronizationStatus

    (Get-MsolCompanyInformation | select DisplayName,DirectorySynchronizationEnabled,DirSyncServiceAccount,LastDirSyncTime)

    * Once the above is verified, test that you can manually change objects in the O365 tenant.

    Expand Post
  • rohern (Okta)

    Apologies Jeff, I just realized this was a question from back in Sept. Glad you were able to get it going. Okta PS is the bee's knees!

This question is closed.
Loading
O365 Federation with Okta