So the last slide we saw that we had a connection with the Resource Manager, PowerShell, Azure portal, and Azure CLI. Well, what is right underneath the resource manager is our providers. The providers are the actual connections that we give to Azure. If we look at this through PowerShell, we have the command which is Get-AzResourceProvider, and you saw so many examples on the slide. But these are the resource providers, and so they provide us with the access. We go up here and see there's a lot of different ones. So you have Microsoft.SiteRecovery, Container Registry, Migrate, DevOps, signal services, we have PolicyInsights, advisor, the DomainRegistration, logic, ServiceBus, going back over here, Microsoft.Compute, Microsoft.Storage, Microsoft.keyvalult. So these are all of the resources that we have in the resource group, and the providers provide the connection to the resources underneath the Azure Resource Manager, and we have the tools that connect through the Azure Resource Manager, through the providers, through the Azure subscription, through the Azure Resource Group to the resources and that's how we're able to manage those resources. So let's put it all together. So we have a PowerShell Azure portal, the Azure CLI, which has connection and a resource manager. The resource manager pass the resource providers that connects to the Azure subscription, the resource group. Then we have the resource itself. So you have Azure Active Directory. Azure Active Directory is going to be our identity. So this is going to provide us with the accounts, this is going to provide us with the identities that are going to have access and be able to have permissions. So we have roles that are associated with it. So there's trust between the Resource Manager and the Azure Active Directory. Now, you have the Tenant. The tenant is actually where the Azure Active Directory resides. Now, the thing is, we can have multiple connections to Azure Active Directory. So those are based on the tenant. The tenant creates the connection if we were doing Azure Active Directory connector, which we'll talk about when we get into Azure AD. What it does is allows us to be able to take our On-Premises Active Directory and filter into Azure Active Directory. So that way we have a common identity, while the tenant would be associated with it. So that way we'll be able to do filtering by OUs for example. So subscription is connected with the Azure Active Directory and the tenant, then you have RBAC, Role-Based Access Control. What this does is this provides us with the permissions saying what we can do within our resource group to our resources within our Azure subscription. So RBAC is role-based access control. So you have the resource policies, and now what the policies do, is these control what we can do with those resources. Then we have resource limits. It says these are the maximum amount. For example, we can only have 60 public IP addresses within Azure subscription. We can only have up to 10,000 NIC cards within the Azure subscription. Maybe that's one of the resource limits. When you think about managed disks, we can have up to 10,000 of those. These are the limits that we cannot go pass. Now, they can be updated. That's why when you have multiple subscriptions, the multiple subscriptions had a tenant associated with it, and it's going to have an Azure Active Directory. The Azure Active Directory provides identities. You have the resource policies that say that I can't create certain types of VMs, or I can't create them in a different region. Then you have the resource limits that says these are the maximum amount of resources I can put into that resource group. Then you have the finance limits. These are where we actually have a billing alerts. So that way when we get to a certain level or certain department, we can block them from being able to create additional resources. So when you look at it, you have PowerShell, there's the Azure Resource Manager. The resource manager connects to the Azure Resource Provider, and then the Azure Resource Provider gives us access through the resource group, through the subscription, to the Azure resource. That way we'll be able to go and manage our resources. So going back into PowerShell, if I do Get-azresourcegroup, I'm bringing back those and that's going through the resource provider. If I could do Get-azVirtualNetwork, that gives me a listing of my virtual networks that I have available, and it comes back with a JSON. So it shows me the virtual network. But how is that able to do that, is through the resource provider. Then I could do AzVm, now will give me a listing of my virtual machines. Again, what it's doing is providing the resource provider gives me the connection through the resource manager to be able to do this.
