Forum Discussion
Plan to Test ADFS SSO with Production O365 and to enable Federation in Production Azure Portal
Hi Manmeet,
If you have your public domain in production please follow the steps in the following article to enable ADFS to Office 365 https://blogs.technet.microsoft.com/canitpro/2015/09/11/step-by-step-setting-up-ad-fs-and-enabling-single-sign-on-to-office-365/
For testing you will need to create a separate environment to other Office 365 Tenant.
The downtime is almost 0 because after you enable it it's seconds.
You can follow this article also https://blogs.technet.microsoft.com/rmilne/2017/05/14/how-to-install-ad-fs-2016-for-office-365-part-3/
Thanks Nuno for quick reply.
Right now I have 2 domains added in Azure Portal.
Assume
abc.com ======= is Primary =====Not Federated
xyz.com ======= is verified =====Not Federated
abc.com is in Production Use.
My goal is to federate xyz.com
While installing AAD Connect, if i choose xyz.com for federation, will it become Primary also?
Please clarify. Thanks.
Hi Manmeet,
If you need more than one domain you will need "SupportMultipleDomain" parameter. Please see the following article https://blogs.technet.microsoft.com/abizerh/2013/02/05/supportmultipledomain-switch-when-managing-sso-to-office-365/
If you want the xyz.com domain as primary you will need to change on Office 365 Portal.
Thanks Nuno for your help. I will come back to you.
I am collecting requirements for all the things which need to be federated before running AAD Connector. To minimize the risk, I am using pilot group of few users. I will federate this pilot group and move on with other users after success of Pilot Federation.
