Skip to content

Commit 99c0e1c

Browse files
Merge pull request #51284 from staleycyn/patch-4
Update 2-design-for-governance.md
2 parents 20e302e + 652880f commit 99c0e1c

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

learn-pr/wwl-azure/design-governance/includes/2-design-for-governance.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,7 @@
11
[Governance](/azure/cloud-adoption-framework/govern/guides/) provides mechanisms and processes to maintain control over your applications and resources in Azure. Governance involves determining your requirements, planning your initiatives, and setting strategic priorities.
22

3+
> [!VIDEO https://learn-video.azurefd.net/vod/player?id=e01e84ad-b8e8-4bdf-bee9-77935d19814a]
4+
35
To effectively apply your governance strategies, you must first create a hierarchical structure for your organizational environment. This structure lets you apply governance strategies exactly where they're needed. The governance strategies we cover in this module are Azure policy and resource tags.
46

57
:::image type="content" source="../media/governance-strategies.png" alt-text="Diagram of the Azure hierarchy that shows the tenant root group, management groups, subscriptions, resource groups, and resources." border="false":::
@@ -15,4 +17,4 @@ A typical Azure hierarchy has four levels: management groups, subscriptions, res
1517
- **Resources** are instances of services that you create. For example, virtual machines, storage, and SQL databases.
1618

1719
> [!NOTE]
18-
> The **tenant root group** contains all the management groups and subscriptions. This group allows global policies and Azure role assignments to be applied at the directory level.
20+
> The **tenant root group** contains all the management groups and subscriptions. This group allows global policies and Azure role assignments to be applied at the directory level.

0 commit comments

Comments
 (0)