Forum Discussion
Multiple Azure tenants > best practice (one microsoft account or more?)
Then I think you should go with one Tenant (yours) and different (isolate) subscriptions. You can transfer subscriptions to other owners, but you keep your unique tenant and admin account:
https://docs.microsoft.com/en-us/azure/billing/billing-subscription-transfer
https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits
if you are looking for Multitenant applications, you can start here:
https://docs.microsoft.com/en-us/azure/active-directory/application-dev-setup-multi-tenant-app
I'm afraid that is not what I mean. Or I don't understand it yet ;-)
What I want is that each customer has it's own dedicated Azure tenant. So, suppose, the do not want to use our application anymore, I can hand over the tenant to the customer so that they still will be the owner of their own data. The tenants are separate and do not have to share any data. I, as a developer, need to log in to the tenants obviously to do my development. Do I need to create different Microsoft accounts to register those different tenants?
I hope I made myself clear.
Why not use B2B so they can give you access to their resource and you can help develop what you need to develop?
Then I think you should go with one Tenant (yours) and different (isolate) subscriptions. You can transfer subscriptions to other owners, but you keep your unique tenant and admin account:
https://docs.microsoft.com/en-us/azure/billing/billing-subscription-transfer
https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits
