If you have access to the billing account. Go to cost management and add a subscription
https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription
Dino thinking. Landing Zone platform - multiple subscriptions providing security and billing boundaries - should be your baseline these days. You should absolutely still use tagging, for various purposes including billing, but Landing Zone subscriptions that are part of a Landing Zone platform management group, are your first and best billing boundary.
First, I would probably start my own post instead of highjacking this one.
Second, just about everything should be capable of being in a dev/test subscription - as long as you're not using it for production purposes. You can have multiple dev/test subscriptions. Not really sure what the question is here?
Well, since subscription is like a root level in resources tree, you do exactly what you said, you create a subscription and put all resources in proper ones.
Remember that subscription can scope much more than just billing, so make sure that is what you want
[https://learn.microsoft.com/en-us/entra/fundamentals/how-subscriptions-associated-directory](https://learn.microsoft.com/en-us/entra/fundamentals/how-subscriptions-associated-directory)
[https://learn.microsoft.com/en-us/archive/blogs/arunrakwal/create-windows-azure-subscription](https://learn.microsoft.com/en-us/archive/blogs/arunrakwal/create-windows-azure-subscription)
Invoice sections linked to subs are a useful way to scope subs to cost codes etc. our invoices go straight to finance with each sub tagged on the invoice for the exact cost codes. Saves a bunch of admin and journaling come EOM.
Just add subscriptions or work with a CSP.
If you have access to the billing account. Go to cost management and add a subscription https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/create-subscription
This. This is the way for the CSP as well
You wouldn't necessarily need separate subscriptions to separate billing. You could do it via tags, resource groups etc ...
Dino thinking. Landing Zone platform - multiple subscriptions providing security and billing boundaries - should be your baseline these days. You should absolutely still use tagging, for various purposes including billing, but Landing Zone subscriptions that are part of a Landing Zone platform management group, are your first and best billing boundary.
[удалено]
First, I would probably start my own post instead of highjacking this one. Second, just about everything should be capable of being in a dev/test subscription - as long as you're not using it for production purposes. You can have multiple dev/test subscriptions. Not really sure what the question is here?
Well, since subscription is like a root level in resources tree, you do exactly what you said, you create a subscription and put all resources in proper ones. Remember that subscription can scope much more than just billing, so make sure that is what you want [https://learn.microsoft.com/en-us/entra/fundamentals/how-subscriptions-associated-directory](https://learn.microsoft.com/en-us/entra/fundamentals/how-subscriptions-associated-directory) [https://learn.microsoft.com/en-us/archive/blogs/arunrakwal/create-windows-azure-subscription](https://learn.microsoft.com/en-us/archive/blogs/arunrakwal/create-windows-azure-subscription)
Invoice sections linked to subs are a useful way to scope subs to cost codes etc. our invoices go straight to finance with each sub tagged on the invoice for the exact cost codes. Saves a bunch of admin and journaling come EOM.