Author: zeusexam

Assign administrator permissions Azure has many different roles for managing access to Azure resources. These include classic subscription administrative roles like Account Administrator, Service Administrator, or Co-Administrator, as well as Azure role-based access controls (RBAC) that are available in Azure Resource Manager (ARM). Note that classic roles and resources are scheduled to be deprecated in…

Remove resource groups In Azure, you can delete individual resources in a resource group, or you can delete a resource group and all its resources. Deleting a resource group also deletes all the resources contained within it in one operation. When deleting resource groups, exercise caution because the resource group might contain resources that other…

If you are moving resources between subscriptions, you must also be mindful of resource quotas. For example, if you are moving many virtual machines, you will need to make sure that the target subscription has enough vCPUs available, or the move operation will fail. Make sure you validate any quotas prior to moving a resource….

Manage resource groups When creating resource groups, it is important that you consider factors for your resource group design: region or location details along with a valid resource group name (see Figure 1-42). FIGURE 1-42 Create A Resource Group blade Move resources across resource groups Some resources in Azure can be moved between resource groups…

Apply and manage tags on resources Resource tags allow you to apply custom metadata to your Azure resources to logically orga- nize them and to build out custom taxonomies. A tag is a name and a value pair. For example, suppose as you deploy resources in Azure, you want to track the environment the resource…

Configure resource locks Azure resource locks (sometimes called management locks) are used to prevent the accidental deletion or modification of resources. There are two types of locks: Note that both types of resource locks allow authorized users to read resources; resource locks apply across all users and roles, even custom and privileged roles. Resource locks,…

Controlling resource groups with Azure Policy is done by scoping the assignment of policy and initiatives. Recall that Azure Policy supports multiple scopes: When creating assignments, it is also possible to configure excluded scopes. You can always exclude a subscope. For example, when scoping an assignment to a management group, any subscriptions, resource groups, or…

Policy definitions can also be packaged using initiative definitions and applied to a scope using initiative assignments. Policy and initiative definitions both support parameter sets, which help simplify the reuse of a policy at multiple scopes. A policy definition describes your desired behavior for Azure resources at the time resources are created or updated. Through…