Скачать с ютуб Azure Resource Manager Terminology benefits and scope Explained with DEMO в хорошем качестве

Azure Resource Manager Terminology benefits and scope Explained with DEMO

Terminology benefits and scope Explained with DEMO Azure Resource Manager is the deployment and management service for Azure. It provides a management layer that enables you to create, update, and delete resources in your Azure account. You use management features, like access control, locks, and tags, to secure and organize your resources after deployment. Terminology Resource - A manageable item that is available through Azure. Virtual machines, storage accounts, web apps, databases, and virtual networks are examples of resources. Resource groups, subscriptions, management groups, and tags are also examples of resources. Resource Group - A container that holds related resources for an Azure solution. The resource group includes those resources that you want to manage as a group. You decide which resources belong in a resource group based on what makes the most sense for your organization. Resource Provider - A service that supplies Azure resources. For example, a common resource provider is Microsoft. Compute, which supplies the virtual machine resource. Microsoft.Storage is another common resource provider. See Resource providers and types. Resource Manager template - A JavaScript Object Notation (JSON) file that defines one or more resources to deploy to a resource group, subscription, management group, or tenant. The template can be used to deploy the resources consistently and repeatedly. Declarative Syntax - Syntax that lets you state "Here is what I intend to create" without having to write the sequence of programming commands to create it. The Resource Manager template is an example of the declarative syntax. In the file, you define the properties for the infrastructure to deploy to Azure. Benefits of using ARM Manage your infrastructure through declarative templates rather than scripts. Deploy, manage, and monitor all the resources for your solution as a group, rather than handling these resources individually. Redeploy your solution throughout the development lifecycle and have confidence your resources are deployed in a consistent state. Define the dependencies between resources so they're deployed in the correct order. Apply access control to all services because Azure role-based access control (Azure RBAC) is natively integrated into the management platform. Apply tags to resources to logically organize all the resources in your subscription. Clarify your organization's billing by viewing costs for a group of resources sharing the same tag. Understand scope Azure provides four levels of scope: management groups, subscriptions, resource groups, and resources. You apply management settings at any of these levels of scope. Lower levels inherit settings from higher levels. You can deploy templates to tenants, management groups, subscriptions, or resource groups. Resource groups There are some important factors to consider when defining your resource group: All the resources in your resource group should share the same lifecycle. You deploy, update, and delete them together. If one resource, such as a server, needs to exist on a different deployment cycle it should be in another resource group. Each resource can exist in only one resource group. You can add or remove a resource to a resource group at any time. You can move a resource from one resource group to another group The resources in a resource group can be located in different regions than the resource group. When creating a resource group, you need to provide a location for that resource group. You may be wondering, "Why does a resource group need a location? And, if the resources can have different locations than the resource group, why does the resource group location matter at all?" The resource group stores metadata about the resources. When you specify a location for the resource group, you're specifying where that metadata is stored. For compliance reasons, you may need to ensure that your data is stored in a particular region. If the resource group's region is temporarily unavailable, you can't update resources in the resource group because the metadata is unavailable. The resources in other regions will still function as expected, but you can't update them A resource group can be used to scope access control for administrative actions. To manage a resource group, you can assign Azure Policies, Azure roles, or resource locks. To create a resource group, you can use the portal, PowerShell, Azure CLI, or an ARM template. Resiliency of Azure Resource Manager Distributed across regions. Some services are regional. Distributed across Availability Zones (as well regions) in locations that have multiple Availability Zones. Not dependent on a single logical data center. Never taken down for maintenance activities. This resiliency applies to services that receive requests through the Resource Manager. For example, Key Vault benefits from this resiliency. #PaddyMaddy #cloudComputing #azuretutorial