Azure AD Sync for On-Premises AD Migration
Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements. Your company's Active Directory forest includes thousands of user accounts. You have been informed that all network resources will be migrated to Azure. Thereafter, the on-premises data center will be retired. You are required to employ a strategy that reduces the effect on users, once the planned migration has been completed. Solution: You plan to sync all the Active Directory user accounts to Azure Active Directory (Azure AD). Does the solution meet the goal?
Community Insight
The exam tests whether identity synchronization is the correct strategy to minimize user disruption when retiring on-premises servers in favor of cloud-only resources.
This question evaluates the use of Azure AD Connect to synchronize on-premises Active Directory identities to Azure AD, ensuring a seamless user experience during infrastructure migration. The solution meets the goal by allowing users to retain their existing credentials and access patterns.
Candidates often select 'No' because they associate identity sync with a hybrid model that requires keeping on-premises servers running. They fail to recognize that sync can be used as a migration tool before the on-premises environment is fully retired.
Community Discussion (44 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Syncing Active Directory accounts to Azure AD (typically via Azure AD Connect) creates synchronized identities in the cloud. This allows users to continue using their familiar on-premises usernames and passwords to access cloud resources immediately after the migration. By maintaining the same authentication mechanism, the impact on users is minimized, fulfilling the requirement to reduce disruption.Why the Other Options Are Wrong
Selecting 'No' implies that syncing causes significant user impact or is technically invalid for this scenario. However, without sync (or password hash sync), users would need to change their login methods, causing high friction. The option assumes a strict separation between cloud and on-premises that contradicts the goal of a smooth transition.Community Comment Notes
Community consensus strongly supports 'Yes'. As Rohitbmenon noted, "Azure AD is correct" for minimizing impact. AntonioTech explained that this approach ensures users "can continue using their existing... credentials." While some users like emptyH questioned if this constitutes a hybrid state, the key is that the sync enables the transition regardless of the final long-term architecture.Exam Strategy
When asked about migrating from on-premises AD to Azure while minimizing user impact, prioritize solutions that preserve existing credentials and identity management practices, such as Azure AD Connect sync.
Frequently Asked Questions
Does syncing AD to Azure AD require keeping on-premises servers?
Not necessarily for the sync process itself, but Azure AD Connect typically runs on a server connected to the on-premises AD. You can sync accounts and then retire the on-premises infrastructure once the migration is complete.
Why is Azure AD Connect better than creating new accounts manually?
Manual creation leads to errors and forces users to learn new credentials. Sync ensures consistency, automation, and immediate access for thousands of users without disruption.
Related Analysis
Practice All AZ-900 Questions
Access 90 questions with complete answers and detailed explanations.
View Full AZ-900 Practice Test →