Forum Discussion
Multiple Azure tenants > best practice (one microsoft account or more?)
We deliver an web application (SQL database and webserver). We host this application from an Azure tenant. No we are setting up an (separate) Azure tenant for a customer. In the future this will be the way we will deliver our application to our customers. So we might end up with (for example) 20 Azure tenants.
What will be the best practice for setting up these tenants. Shall I use my Microsoft account I use for my first Azure account (someaccount@outlook.com) for all the tenants or shall I create a new microsoft account for all tenants (tenant1@outlook.com, tenant2@outlook.com, etc)?
Or is there a better way to do this?
Thanks, Mike
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.
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
Its better you setup the Customers tenants for the customer with the customers domain or use their existing tenant (if they have one). Then register your microsoft account or company account with their Azure AD as B2B this will enable them give you access to their resource to develop what you need to develop.
If you are delivering software as a service to the customer and you will be maintaining the application after handover then you can develop the application/software on your tenant and give your customer access to the application via B2B.
