A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Hi @Jan-Dirk Schuitemaker Thank you for reaching out to Q&A. Your @live.com sign‑in is a personal Microsoft account, while the account created when you bought Microsoft 365 for Business is a work/school identity in a Microsoft Entra tenant. These are two separate identity systems and there's no way to combine them — that's by design. What is possible is moving the subscription (the container your VMs, disks, NICs and public IPs live in) so your work account can manage and/or pay for it.
Option A -You just want to manage the VMs with your work account:
Invite the work account as a guest in the current tenant and give it Owner or Contributor on the subscription via Access control (IAM). Takes a few minutes, nothing is deleted, no downtime. If your goal is simply "log in with my business account and see my VMs," this is usually enough.
Option B - Change the directory only, keep billing where it is:
You can associate the subscription with your business Entra tenant while leaving the payment method untouched. Steps are in Transfer an Azure subscription to a different Microsoft Entra directory. Azure Lighthouse is also called out there as an alternative if you'd rather leave the subscription in place and delegate access instead.
Option C: Move billing and the tenant (full transfer)
From the Azure portal, signed in as an administrator of the billing account: Subscriptions → select the subscription → Transfer billing ownership → enter the email of a billing administrator on the business account → tick Move subscription tenant → Send transfer request.
- Leave the checkbox unticked and only the invoice moves resources and all existing role assignments stay as they are.
- Tick it and the resources land in the business tenant, but every role assignment and custom role is permanently deleted and can't be restored.
The recipient gets an email and must accept; the request is valid for 15 days, and only one can be active at a time. Full portal walkthrough: Transfer billing ownership of an MOSP Azure subscription.
If you go with Option C, please export this first it's the only recovery path:
az role assignment list --all --include-inherited --output json > roleassignments.json
az role definition list --custom-role-only true --output json --query '[].{roleName:roleName, roleType:roleType}'
az ad sp list --all --filter "servicePrincipalType eq 'ManagedIdentity'"
And please confirm none of these are in the subscription, as they either can't move or need work first AKS clusters, Azure Databricks, Microsoft Dev Box, Deployment Environments, Service Fabric, Entra Domain Services, and SQL/MySQL/PostgreSQL servers with Microsoft Entra authentication enabled. Azure Policy objects and Microsoft Sentinel workspaces are also affected (Sentinel can be re‑onboarded in the new tenant within 90 days), storage/Azure Files ACLs must be re‑applied, and resource locks and Disk Encryption Sets need re‑creating.
One important warning: if a key vault in this subscription holds customer‑managed keys encrypting a storage account or database, moving it can leave you in an unrecoverable state. Switch to a different vault or temporarily disable CMK before transferring. Also worth planning for Microsoft notes that in some scenarios a tenant transfer can require downtime.
If both subscriptions already share the same tenant:
Then skip all of the above and just move the resources: Resource group → select resources → Move → to another subscription. Both source and destination resource groups are locked for up to four hours, but your VMs keep running with no downtime.
A VM move has to include all its dependents in a single operation virtualMachines, disks, networkInterfaces, publicIPAddresses, networkSecurityGroups, virtualNetworks and storageAccounts otherwise you'll hit MissingMoveDependentResources. Also make sure the destination subscription is active and registered for the relevant resource providers, and remember that resource IDs change, so any scripts, dashboards or templates referencing them need updating.
Reference: Move Azure resources to a new resource group or subscription.
If you have further questions regarding this answer, feel free to click "Comment". If you find the answer helpful, please click "upvote". This helps the community by allowing others with similar queries to easily find the solution.