This is a continuation of a series of articles on hosting solutions and services on Azure public cloud with the most recent discussion on Multitenancy here This article continues to discuss Azure Arc enabled servers, their sizing guidance, operational considerations when increasing the numbers and the overall planning required for Azure arc enabled data services deployment. It discusses specifically the migration of on-premises or other cloud based Azure arc enabled server to cloud.

The transitioning must be managed for both Azure Arc enabled servers based on the supported VM extensions and the Azure services based on its Arc server resource identity.  Azure Migrate can help with understanding requirements for on-premises machines to be migrated to Azure.

The tasks to be undertaken include the following: 1. Inventory and remove VM extensions, 2. Review access rights, 3. Uninstall the Azure Connected Machine agent, 4. Install the Azure Guest Agent, 5. Migrate server machine to Azure, 6. Deploy Azure VM extensions.

Step 1 can be done with the listing from Azure CLI or with  Azure PowerShell,  The VM extensions can be identified with using the az connectedmachine extension list command. After identifying these extensions, they can be removed using the Azure Portal. If the extensions were installed with Azure Policy and the VM Insights initiative, it is necessary to create an exclusion to prevent the re-evaluation and deployment of the extensions on the Azure Arc enabled server before the migration is complete.

Step 2 can be done by reviewing the access rights. The role assignments for the Azure Arc enabled servers must be done using the PowerShell or with other PowerShell code and the results can be exported to CSV or other format.

Step 3 can be done by following the guidance to uninstall the agent from the server. The extensions must be checked that they are removed by disconnecting the agent.

Step 4 can be done by installing the Azure Guest agent. Migrated VMs do not have guest agents installed. Manually installing them is required.

Step 5. Servers and machines can be migrated to Azure in this step.  The migration options based on the environment must be carefully reviewed prior to the migration.

Step 6: The migration and completion of all post-migration configuration steps can be done by deploying the Azure VM extensions based on the VM extensions originally installed on the Azure Arc enabled server.

Finally, the audit settings inside a machine must be resumed with guest configuration policy definitions.

 
Reference: Multitenancy: https://1drv.ms/w/s!Ashlm-Nw-wnWhLMfc6pdJbQZ6XiPWA?e=fBoKcN