-
Notifications
You must be signed in to change notification settings - Fork 0
Running Against The Proof Lab
Colby Farley edited this page Apr 4, 2026
·
1 revision
If you do not already have a safe Azure environment for demos or testing, use the companion proof lab:
Use a disposable subscription you control. The lab is intentionally insecure and is meant for practice, validation, and walkthroughs.
- Build the lab by following the proof-lab repo instructions.
- Authenticate to Azure.
- Point Azure CLI at the lab subscription.
- Run a small command first, then a grouped pass.
Authenticate and select the subscription:
az login
az account set --subscription <lab-subscription-id>Confirm identity and visible subscription context:
azurefox --outdir ./azurefox-lab whoami --output tableRun an initial census:
azurefox --outdir ./azurefox-lab inventory --output tableRun a grouped sweep once the basics look right:
azurefox --outdir ./azurefox-lab all-checks --output tableIf you want a narrower pass first:
azurefox --outdir ./azurefox-lab all-checks --section identity --output table- It gives you a known environment to validate command behavior.
- It makes screenshots and walkthroughs easier to reproduce.
- It reduces the temptation to learn AzureFox for the first time in a production tenant.
Use a dedicated --outdir like ./azurefox-lab so the resulting artifacts stay grouped
together while you compare runs.
- Home
- Getting Started
- Platform Notes
- Running Against The Proof Lab
- Understanding Output
- Command Guides
Core
Identity
Config
Secrets
Storage
Resource
Compute
Orchestration
Chain Families
Grouped Sweeps
Investigations
- Axios - Post Exposure Azure Triage
- From EvilTokens to AzureFox: Why Token Theft Can Become Azure Control
- FAQ / Known Limits (coming soon)