Sometimes it may be necessary to convert back to a Standard domain from a federated domain. In this video, going back to a Standard Domain, the steps necessary to convert back are demonstrated. Sharon will discuss why reverting back to a Standard domain is required and demonstrate the PowerShell Cmdlets for this procedure.
- [Voiceover] There are several reasons…why a company may want to revert back to a standard domain.…These reasons may include cost, since ADFS…can be expensive to set up and manage,…or the company requirements may have changed,…such as a reduced number of seats.…Also, as your Azure directory connect may now be sufficient.…Other examples include the AD FS implementation…has failed and users need to be able…to access office 365 or for troubleshooting.…Reverting back removes the relying party trust setting…in the AD FS server and Office 365.…
Users who were configured for single sign-on…will be given a new temporary password…if the password hash sync was not set.…At this point I'm going to show you how we revert back.…I've already connected to the Microsoft online service.…All I have to do…is run through a couple power shell commandlets.…These will be convert to a standard domain…and we'll have some additional parameters…as well including skip user conversion.…If we answer true, users will not be converted at this time.…
Here, system admins will learn how to implement and manage federated identities for single sign-on in Office 365. Microsoft Certified Trainer Sharon Bennett shows how to plan for an Active Directory Federation Services (AD FS), install the AD FS role on Windows Server 2012 R2, and install and manage AD FS proxy servers.
Note: This training course maps to the Implement and Manage Federated Identities for SSO domain for Microsoft Certification exam 70-346.
- Planning for AD FS
- Sizing your infrastructure
- Configuring clients
- Installing the AD FS role
- Managing your servers
- Installing and configuring the AD FS proxy
- Tips for taking Microsoft Certification exam 70-346