A company plans to migrate an on-premises payroll application running on physical servers to Azure. The application relies on a local Microsoft SQL Server database that utilizes SQL Server Agent jobs for nightly processing and performs cross-database queries. The company also needs to synchronize their on-premises Active Directory Domain Services (AD DS) identities to Microsoft Entra ID. The migration strategy must minimize administrative and infrastructure overhead, maintain application compatibility, and ensure that all server connections are identified before migration.
Which migration and identity synchronization strategy should you recommend?
- Migrate the database to Azure SQL Managed Instance, perform an agentless dependency analysis using Azure Migrate, and configure Microsoft Entra Connect with Password Hash Synchronization.Answer
- BMigrate the database to an Azure SQL Database single database, perform an agentless dependency analysis using Azure Migrate, and configure Microsoft Entra Connect with Password Hash Synchronization.
- CMigrate the database to Azure SQL Managed Instance, perform an agentless dependency analysis using Azure Migrate, and deploy Active Directory Federation Services (AD FS) to federate identities.
- DMigrate the database to Azure SQL Managed Instance, migrate the application servers immediately without performing a dependency analysis to minimize assessment time, and configure Microsoft Entra Connect with Password Hash Synchronization.
Answer
Migrate the database to Azure SQL Managed Instance, perform an agentless dependency analysis using Azure Migrate, and configure Microsoft Entra Connect with Password Hash Synchronization.
The correct strategy migrates the database to Azure SQL Managed Instance because it supports instance-level features like SQL Server Agent and cross-database queries. It uses Azure Migrate dependency analysis to ensure all connection vectors are verified before server migration. It utilizes Password Hash Synchronization (PHS) to sync identities with the least administrative and on-premises infrastructure overhead.
Step-by-Step Solution
Key Concept
Selecting SQL database deployment tiers, dependency assessment methods, and hybrid identity architectures based on legacy application requirements and operational constraints.
Estimated Time:1m 30s