Accounts, subscriptions, and environments
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
structure accounts or subscriptions for isolation and blast-radius control.
Planned topics
- An account (or subscription) is a hard boundary for identity, billing, and quota.
- One account per environment (dev, test, prod) limits mistakes; separate accounts for security logging and shared networking.
- Blast radius: how far a mistake or compromise spreads; smaller boundaries mean smaller radius.
- Too many accounts without automation becomes burden; start with a small, clear split.
- Organization-level policies apply across all accounts (detail in ARC-020).
Draft outline details
Demonstration
a tree: organization, then folders for workloads, with accounts prod, non-prod, shared-network, security-logging, and a sandbox.
Check your understanding
Why separate prod from non-prod accounts?
Show answer
A mistake or leaked credential in test cannot touch production.
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.