Recheck discovered resources before running a preview Chaos Studio Scenario

Workspace discovery follows its selected scope as resources change; the planned test population needs a fresh review before execution.

Resilient network core with engineered blue and gold data paths.
DSE visual intelligenceNetworks & infrastructureGuide · 2 min read
Executive summary

What you need to know

Workspace discovery follows its selected scope as resources change; the planned test population needs a fresh review before execution.

Potentially affected

Nonproduction Azure Chaos Studio Workspaces and Scenarios in public preview.

DSE recommendation

Review the current discovered targets and execution identity before each approved nonproduction resilience test.

Source facts

Chaos Studio Workspaces and Scenarios are in public preview and are not intended for production use. A Workspace discovers resources within its subscription, resource-group or service-group scope and automatically picks up later additions and removals.

Actions run under the Workspace’s managed identity, not the operator’s personal credentials. Execution requires both permission to trigger the Scenario and the identity’s required target permissions. Reports identify which actions succeeded, failed or were skipped. Microsoft Learn.

Applicability

Limit this review to an authorized nonproduction preview evaluation. Identify the scope, Scenario configuration and current target population rather than relying on an old test plan.

DSE recommendation

DSE recommends comparing newly discovered resources with the intended failure exercise before allowing a run. Review identity grants against those exact targets and remove unexplained scope expansion from the proposed test. Assign stop conditions and application-health observations before execution. A saved Scenario should not silently authorize disruption of a resource that joined the scope after the original approval.

Verification

For an approved preview test, retain the reviewed target list, identity assignments and run identifier. Compare the action report with the intended resource set and investigate skipped or unexpected actions. Pair the report with the application’s own observations; a completed Scenario is not by itself evidence that the application recovered correctly. Reconcile any scope changes before the next run.

Official references

Microsoft Learn: Chaos Studio Workspaces overview. Source retrieved September 9, 2026.

Primary reference

Review the official source

Chaos Studio Workspaces overview - Azure Chaos Studio | Microsoft Learn · Verified September 9, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE