Max one cloud end point per sync group.
https://learn.microsoft.com/en-us/azure/storage/files/storage-files-scale- targets?toc=%2Fazure%2Fstorage%2Ffilesync%2Ftoc.json#azure-file-sync-scale-targets

You need the following to use Azure AD Connect cloud sync:
Domain Administrator or Enterprise Administrator credentials to create the Azure AD Connect Cloud Sync gMSA (group Managed Service Account) to run the agent service.
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/cloud-sync/how-to- prerequisites?tabs=public-cloud

Step 1: Sign in to the Azure portal.
Step 2: Search for and select Virtual machines. Select VM1 from the list..
Step 3: On the Virtual machine pane, select Disks.
Step 4: On the Disks pane, select Create and attach a new disk.
Step 5: In the drop-downs for the new disk, select attach c:\vhds\Disk1.vhdx Step 6: Specify that the disk is managed.
Step 7: Select Save to create and attach the new data disk to the VM.
Reference:
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/attach-managed-disk-portal

The Infrastructure Master role should be held by a Domain Controller that isn't a Global Catalog server (GC). If the IM role runs on a GC server it will halt updating object information because it doesn't have any references to objects that it doesn't hold.
Additionally, the Infrastructure master doesn't make changes often.
References:
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/fsmo-roles
https://docs.microsoft.com/en-us/troubleshoot/windows-server/identity/transfer-or-seize-fsmo- roles-in-ad-ds

First you need to move pagefile.sys and then change the drive letter.
https://learn.microsoft.com/en-us/azure/virtual-machines/windows/change-drive-letter