comp9
comp9
In this task, you will create and configure management groups. Management groups
are used to logically organize and segment subscriptions. They allow for RBAC and
Azure Policy to be assigned and inherited to other management groups and
subscriptions. For example, if your organization has a dedicated support team for
Europe, you can organize European subscriptions into a management group to provide
the support staff access to those subscriptions (without providing individual
access to all subscriptions). In our scenario everyone at the Help Desk will need
to create a support request across all subscriptions.
Review the Access management for Azure resources area. Ensure you can manage access
to all Azure subscriptions and management groups in the tenant.
Create a management group with the following settings. Select Submit when you are
done.
Setting Value
Management group ID az104-mg1 (must be unique in the directory)
Management group display name az104-mg1
Refresh the management group page to ensure your new management group displays.
This may take a minute.
Note: Did you notice the root management group? The root management group is built
into the hierarchy to have all management groups and subscriptions fold up to it.
This root management group allows for global policies and Azure role assignments to
be applied at the directory level. After creating a management group, you would add
any subscriptions that should be included in the group.
Select the Access control (IAM) blade, and then the Roles tab.
Scroll through the built-in role definitions that are available. View a role to get
detailed information about the Permissions, JSON, and Assignments. You will often
use owner, contributor, and reader.
Select + Add, from the drop-down menu, select Add role assignment.
On the Add role assignment blade, search for and select the Virtual Machine
Contributor. The Virtual machine contributor role lets you manage virtual machines,
but not access their operating system or manage the virtual network and storage
account they are connected to. This is a good role for the Help Desk. Select Next.
Did you know? Azure originally provided only the Classic deployment model. This has
been replaced by the Azure Resource Manager deployment model. As a best practice,
do not use classic resources.
Note: The next step assigns the role to the helpdesk group. If you do not have a
Help Desk group, take a minute to create it.
Continue on the Access control (IAM) blade. On the Role assignments tab, confirm
the helpdesk group has the Virtual Machine Contributor role.
Did you know? This assignment might not actually grant you any additional
privileges. If you already have the Owner role, that role includes all permissions
associated with the VM Contributor role.