An organization plans to migrate a legacy line-of-business (LOB) application currently running on on-premises physical bare-metal servers to Azure Virtual Machines. The application has multiple undocumented network connections to other local servers. The organization needs to map these dependencies before scheduling the migration. Additionally, you must design a hybrid identity solution to synchronize on-premises user accounts to Microsoft Entra ID while minimizing operational overhead and ensuring that user passwords can be managed on-premises. Which two actions should you include in the migration assessment and strategy? (Choose two.)
- Install the Azure Monitor agent and the Dependency agent on each physical server.Answer
- Configure Microsoft Entra Connect with Password Hash Synchronization (PHS).Answer
- CDeploy Active Directory Federation Services (AD FS) to establish federation with Microsoft Entra ID.
- DConfigure agentless dependency analysis on the physical servers using the Azure Migrate appliance.
- EDeploy Azure SQL Database single databases to host databases that require cross-database queries.
Answer
To successfully perform the migration assessment and design the identity solution, you must install the Azure Monitor agent and the Dependency agent on each physical server, and configure Microsoft Entra Connect with Password Hash Synchronization (PHS).
Installing the Azure Monitor agent and the Dependency agent is correct because physical bare-metal servers do not support agentless dependency analysis in Azure Migrate, making the agent-based approach necessary. Configuring Microsoft Entra Connect with Password Hash Synchronization (PHS) is correct because it synchronizes user accounts and passwords to the cloud with the least operational overhead, avoiding the maintenance costs of dedicated federation infrastructure.
Step-by-Step Solution
Key Concept
Azure Migrate dependency analysis methods vary by platform; physical servers require agent-based mapping, while hybrid identity designs should prioritize Password Hash Synchronization (PHS) over AD FS for lower operational overhead unless federation is explicitly required.