A company plans to migrate a legacy payroll application currently running on on-premises physical servers to Azure. The application consists of several web and application servers, along with a Microsoft SQL Server database that utilizes SQL Server Agent jobs and cross-database queries. The network connections between the application servers and external systems are undocumented. The company wants to minimize deployment complexity and administrative overhead for the migration and the final hybrid identity solution. Which migration assessment, database tier, and identity synchronization strategy should you recommend?
- Perform agent-based dependency analysis using Azure Migrate, select Azure SQL Managed Instance for the database tier, and implement Microsoft Entra Connect with Password Hash Synchronization (PHS).Answer
- BPerform agentless dependency analysis using Azure Migrate, select Azure SQL Managed Instance for the database tier, and implement Microsoft Entra Connect with Password Hash Synchronization (PHS).
- CPerform agent-based dependency analysis using Azure Migrate, select Azure SQL Database for the database tier, and implement Microsoft Entra Connect with Password Hash Synchronization (PHS).
- DPerform agent-based dependency analysis using Azure Migrate, select Azure SQL Managed Instance for the database tier, and implement Active Directory Federation Services (AD FS).
Answer
Perform agent-based dependency analysis using Azure Migrate, select Azure SQL Managed Instance for the database tier, and implement Microsoft Entra Connect with Password Hash Synchronization (PHS).
The correct strategy involves using agent-based dependency analysis because Azure Migrate only supports agent-based dependency mapping for physical servers (unlike VMware or Hyper-V, which support agentless analysis). Azure SQL Managed Instance is required because the database tier relies on SQL Server Agent jobs and cross-database queries, which are not natively supported in Azure SQL Database. Password Hash Synchronization (PHS) with Microsoft Entra Connect is the simplest hybrid identity solution that minimizes administrative overhead and deployment complexity while meeting standard authentication requirements, unlike Active Directory Federation Services (AD FS), which requires significant on-premises infrastructure.
Step-by-Step Solution
Key Concept
Selecting migration assessment methods, database tiers, and hybrid identity architectures based on server types, application feature requirements, and operational overhead.