Account and subscription hierarchies
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
design the hierarchy that policy and billing follow.
Planned topics
- Group accounts into folders or management groups by purpose (workloads, shared, security, sandbox).
- Policies and permissions inherit down the tree; design the tree for the policy you need.
- Dedicated accounts for central logging, security tooling, and shared network.
- Separate prod from non-prod; give each team a boundary with a budget.
- Keep the tree shallow; deep hierarchies are hard to reason about.
Draft outline details
Demonstration
a tree diagram: root, Security, Shared services, Workloads (Prod, Non-prod), Sandbox, with policies noted at each level.
Check your understanding
Why design the hierarchy around policy?
Show answer
Policies inherit down the tree, so structure decides where they apply.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.