We currently have Office 365 and our Azure Directory sync is managed by a a third party service who do not use AD Connect but their own API. Once we configure ADFS our end and setup AD Connect will this break all the accounts on Azure since they have already been populated from our AD or will this re-enable the sync again once we come away from third party and allow SSO?

Also, would there be an issue with setting up AD Connect before we come away from our third party as Azure will be retrieving the same accounts from our ADFS and our third party identity provider?



  • 1
    Seems like this question is best suited for the third party service, as without any insight into the API in use, the community would be hard-pressed to provide any definitive information – Semicolon Jan 24 '19 at 15:24
  • Ask the vendor what will happen to the Office 365/Azure AD accounts if you disable/remove their product/solution/API. – joeqwerty Jan 24 '19 at 18:45
  • Hi the objects will continue to stay in Azure once third party has been decommissioned and they use objectGUID for stamping which I believe is the recommended way anyway. – phey Jan 31 '19 at 15:49

See there are 2 things to consider. AD Connect just sync the object to AzureAD. Your auth for the users is a whole different story.

What I am saying you can keep syncing your using your custom sync, and use ADFS for auth.

You can also break your current user sync and start sync users with AD Connect.

  • Hi our plan is to create our own ADFS infrastructure which we will do and test internally and externally prior to syncing with AD connect. It is looking likely that AD Connect will continue to sync from our network after third party decommissions. – phey Jan 31 '19 at 15:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.