All Checks

all-checks

all-checks is the broad grouped sweep command for repeatable first-pass AzureFox coverage.

Use it when you want one dependable artifact set quickly, especially in unfamiliar environments or handoff-heavy workflows.

What This Command Answers

• Can AzureFox give you one repeatable first sweep?
• Can you start reviewing while the rest of the coverage finishes?
• Can you hand off a broad artifact set without rebuilding the command list from memory?

Run It

For a broad run:

azurefox all-checks --output table

For a narrower section run:

azurefox all-checks --section identity --output table

When To Use It

• when the tenant is unfamiliar and you want broad first-pass coverage fast
• when time is short and predictable output matters more than hand-picking commands
• when another analyst may need the artifact set later

What To Look For

• session and estate truth early in the run
• config, secret, and identity-heavy context before deeper service-family review
• failures, partial reads, or summaries that show where the artifact set is incomplete
• the sections that tell you where to pivot next

Why It Matters

Skipped coverage is a real failure mode in first-pass cloud review.

all-checks lowers that risk by making the normal AzureFox sweep predictable, repeatable, and easier to hand off. Its value is consistency and coverage, not new analysis logic.

What Should Stand Out First

• session and estate truth first
• config, secret, and identity-heavy context early
• deeper compute, network, and resource triage after the shared context is visible
• failures, partial reads, and final summary impossible to miss

What To Do Next

• Start reading the early sections before diving into narrower service detail.
• Use grouped output to decide which command family deserves focused follow-up.
• Prefer Chains when you want a targeted path story instead of a broad transitional sweep.

Boundary

all-checks is a routing and orchestration command.

It should provide predictable grouped coverage and organized output. It is not a different analysis model, hidden extra collection path, or replacement for focused flat-command review.

Transitional Note

all-checks is still useful, but it is a transitional surface.

The replacement direction is Chains plus direct flat-command execution when the operator needs a narrower, path-oriented workflow instead of a broad grouped sweep.