Managing Azure Subscriptions
Managing Resource Groups
The course is part of these learning paths
As an IT professional tasked with managing resources in Azure, it’s important to understand key administrative roles and permissions within a subscription and within a resource group. It’s also important to know how to leverage Role Based Access Control (RBAC) for managing such administrative roles and permissions.
In the first part of this course, you will learn about Azure subscriptions. You will learn about key roles within a subscription, including the owner role, account administrator role, service administrator role, and the co-administrator role. You’ll also learn how to manage these roles by using RBAC. We’ll also cover subscription policies and the role they play in the management of an Azure subscription.
In the second part of the course, we’ll talk about resource groups in Azure. We’ll touch on what they do and how they are managed. You will learn how to secure resources within a resource group via resource policies and resource locks. You’ll also learn about resource tagging and how it can be used to manage and group Azure resources.
Rounding out this course, we’ll cover the process of moving resources from one resource group to another, as well as the deletion of resource groups altogether.
- Understand the Owner Role
- Understand the Account Administrator Role
- Understand the Co-Administrator Role
- Understand the Service Administrator Role
- How to Manage Roles and Permissions with RBAC
- Understand Subscription Policies
- Understanding the Purpose of Resource Groups
- How to Leverage Resource Group Policies
- How to Use Resource Locks to Protect Resources
- How to Leverage Resource Tags
- Moving Resources Between Resource Groups
- Removing Resource Groups
- IT Professionals interested in becoming Azure cloud architects
- IT Professionals preparing for Microsoft’s Azure certification exams
- General knowledge of IT infrastructure
- General knowledge of the Azure environment
Understanding compliance in Microsoft Azure requires the ability to identify the status of resources in a subscription. In this demonstration, we'll walk through the process of creating a policy assignment, to identify virtual machines that are not using managed disks. To get started, let's create a policy assignment, and assign the audit virtual machines without managed disks policy definition. To do this, browse to the Azure Portal, and then click all services. From here, search for policy, and then select it from the results list. Click assignments in the left pane. An assignment is a policy that's been assigned to take place within a specific scope. Next, click assign policy from the top of the policy assignments page. From the assigned policy page, select a scope by clicking the ellipsis and then choosing either a management group or a subscription. The scope determines which resources the policy assignment gets applied to. Click select at the bottom of the scope page. Exclusions are optional, so we'll leave this option blank since we aren't excluding anything. Click the policy definition ellipsis to open the list of available definitions.
By default, as your policy offers built-in policy definitions that you can use. For this exercise, we can search through the list of policy definitions to find the audit VMs that do not use managed disks definition. Click on that policy and then click select. The assignment name is automatically populated with the policy name, but that can be changed. For this exercise, we just going to leave audit VMs that do not use managed disks. Adding a description is optional. The description, if used, should provide details about the policy assignment itself. Assigned by is filled in automatically, based on who is logged in. This field is also optional, and as such, custom information can be entered here as well. For this exercise, I'm going to leave create a managed identity unchecked. This option must be checked if the policy being assigned includes a policy with the deploy if not exist effect. Since the policy we are working with in this exercise does not, we can leave it blank. Click assign to assign the policy. With the policy assigned, we can identify non-compliant resources. To do so, click compliance in the left side of the page, and then find the audit VMs that do not use managed disks policy assignment that was created. Resources that are not compliant with this new assignment will appear under non-compliant resources. When conditions are evaluated against resources, and are found to be true, those resources are marked as non-compliant with the assigned policy. Compliance state results are either compliant or non-compliant. So as you can see from this demonstration, policies are extremely helpful when trying to ensure resource compliance with pre-defined standards.
About the Author
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.