Let's see how as your bills you for your use and how you can restrict the access to azure resources.
We'll use the example from our previous video, where you have different subscriptions for each department. In your enterprise,
a bill is generated for each subscription on a monthly basis.
The charge shows up on the associated credit card 10 days after the billing period ends.
All those subscriptions are built independently. The account owner is responsible for payment.
In our example, the marketing, finance and HR departments will have separate bills that you can apply towards the budgets of each department.
This way, you can keep track of each department spending and better control their individual costs.
You can also use different payment methods for each subscription,
different credit cards for each department.
And last but not least, you can create budgets for each subscription and get notified if one of the departments exceeds their budget.
If you need a more detailed analysis of your spending
as your offers additional tools like the cost management and billing service that you can use to query billing data and get a better picture of your spending,
you can drill down to granular levels like resource groups or even individual resources.
Restricting access to resources and services is crucial for security in the cloud
authentication for users. And Azure is performed by Azure Active Directory or a D.
Azure. Active Directory is a cloud based identity provider that supports multiple authentication protocols, including modern standards like Open it and show Off.
You can use azure active directory to register users applications, create groups and other entities, which makes it a complete directory service.
Entities registered with a D are not handled by a single instance of the service.
Instead, as your active directory is partitioned into tenants,
a tenant is an isolated, dedicated instance of aid that is managed by a single organization.
Azure Active Directory is used by other cloud services from Microsoft, including Office 3 65. Microsoft in Tune and Dynamics 3 65.
When you sign up for any Microsoft Cloud Service, an instance of a D is automatically created for you.
Keep in mind that there is no 1 to 1 relationship between azure active directory tenants and your organization.
For example, you could have multiple A D tenants under your account for testing or other purposes,
and each one of those tenants can have multiple subscriptions associated with them.
Thus, each tenant has a single account owner but can have multiple subscriptions associated with it.
Also, a subscription can be associated with the single tenant.
You can migrate subscriptions between tenants if you need to.
Using Azure active Directory,
you can manage the access to each subscription in every resource underneath individually.
This gives you a lot of flexibility to model your organizational access within azure.