During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in
locally chaos directory
This page is part of the CLI Reference and is generated from the CLI's own help output, so it matches what locally chaos directory --help prints.
For more information see Chaos Engineering and Directory (Entra) Emulator.
locally chaos directory
Simulate Microsoft Graph (directory) failure modes.
Simulate Microsoft Graph (directory) failure modes. A fault command sets the fault's rate. With a scope flag (--name) it adds or edits a rule instead. Examples: locally chaos directory <fault> --percentage N locally chaos directory <fault> reset locally chaos directory show locally chaos directory reset
Usage
locally chaos directory [flags] locally chaos directory [command]
Flags
-h, --help[=true|false] help for directory
Subcommands
- locally chaos directory 403 - Answer requests with 403, as when a role assignment has not replicated yet.
- locally chaos directory 429 - Answer requests with 429 Too Many Requests and a retry hint.
- locally chaos directory 500 - Answer requests with 500 Internal Server Error.
- locally chaos directory disable - Turn chaos OFF for the directory and identity.
- locally chaos directory drop-connection - Close the connection without answering.
- locally chaos directory enable - Turn chaos ON for the directory and identity.
- locally chaos directory eventual-consistency - Return a not-yet-replicated view of what was just written.
- locally chaos directory incident - Take each resource down for a while, then bring it back.
- locally chaos directory latency - Hold requests for a random delay before they are handled.
- locally chaos directory outage - Fail requests for as long as the rule is armed, like a region or service that is down.
- locally chaos directory reset - Zero every Microsoft Graph (directory) fault and drop every rule.
- locally chaos directory show - Print the current Microsoft Graph (directory) chaos configuration.
- locally chaos directory stale-read - Serve stale reads after a write.
locally chaos directory 403
Answer requests with 403, as when a role assignment has not replicated yet.
Answer requests with 403, as when a role assignment has not replicated yet. On the control plane the error code is AuthorizationFailed; on a database the engine's own equivalent error is sent instead. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. Examples: locally chaos directory 403 --percentage 25 locally chaos directory 403 --percentage 100 --name my-app
Usage
locally chaos directory 403 [flags] locally chaos directory 403 [command]
Flags
-h, --help[=true|false] help for 403
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory 403 reset - Remove one 403 rule, or put the whole fault back to zero.
locally chaos directory 403 reset
Remove one 403 rule, or put the whole fault back to zero.
Reset the 403 fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory 403 reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory 429
Answer requests with 429 Too Many Requests and a retry hint.
Answer requests with 429 Too Many Requests and a retry hint. On a database the engine's own throttling error is sent instead. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --retry-after sets the Retry-After header the fault answers with, such as 5s. Without one the service's usual hint is sent. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos directory 429 --percentage 25 locally chaos directory 429 --percentage 25 --retry-after 5s locally chaos directory 429 --percentage 100 --name my-app
Usage
locally chaos directory 429 [flags] locally chaos directory 429 [command]
Flags
-h, --help[=true|false] help for 429
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--retry-after string Retry-After this fault answers with, e.g. 5s or 500ms (the service's usual hint when omitted)
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory 429 reset - Remove one 429 rule, or put the whole fault back to zero.
locally chaos directory 429 reset
Remove one 429 rule, or put the whole fault back to zero.
Reset the 429 fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory 429 reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory 500
Answer requests with 500 Internal Server Error.
Answer requests with 500 Internal Server Error. On a database the engine's own equivalent error is sent instead. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. Examples: locally chaos directory 500 --percentage 25 locally chaos directory 500 --percentage 100 --name my-app
Usage
locally chaos directory 500 [flags] locally chaos directory 500 [command]
Flags
-h, --help[=true|false] help for 500
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory 500 reset - Remove one 500 rule, or put the whole fault back to zero.
locally chaos directory 500 reset
Remove one 500 rule, or put the whole fault back to zero.
Reset the 500 fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory 500 reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory disable
Turn chaos OFF for the directory and identity.
Turn chaos OFF for the directory and identity. Disabling keeps every fault's configuration, so a later enable restores it. The directory and identity surfaces share one master switch: this is the same switch as 'locally chaos directory disable' and 'locally chaos identity disable'.
Usage
locally chaos directory disable [flags]
Flags
-h, --help[=true|false] help for disable
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory drop-connection
Close the connection without answering.
Close the connection without answering. The client sees the connection reset, with no status code or error body. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. Examples: locally chaos directory drop-connection --percentage 25 locally chaos directory drop-connection --percentage 100 --name my-app
Usage
locally chaos directory drop-connection [flags] locally chaos directory drop-connection [command]
Flags
-h, --help[=true|false] help for drop-connection
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory drop-connection reset - Remove one drop-connection rule, or put the whole fault back to zero.
locally chaos directory drop-connection reset
Remove one drop-connection rule, or put the whole fault back to zero.
Reset the drop-connection fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory drop-connection reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory enable
Turn chaos ON for the directory and identity.
Turn chaos ON for the directory and identity. Disabling keeps every fault's configuration, so a later enable restores it. The directory and identity surfaces share one master switch: this is the same switch as 'locally chaos directory enable' and 'locally chaos identity enable'.
Usage
locally chaos directory enable [flags]
Flags
-h, --help[=true|false] help for enable
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory eventual-consistency
Return a not-yet-replicated view of what was just written.
Return a not-yet-replicated view of what was just written. A read soon after a write can miss it, until the delay has passed. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. The value is a maximum: each firing picks 0 to N. A duration is required whenever the fault fires. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos directory eventual-consistency --percentage 25 --seconds 30 locally chaos directory eventual-consistency --percentage 100 --seconds 30 --name my-app
Usage
locally chaos directory eventual-consistency [flags] locally chaos directory eventual-consistency [command]
Flags
-h, --help[=true|false] help for eventual-consistency
--millis string Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory eventual-consistency reset - Remove one eventual-consistency rule, or put the whole fault back to zero.
locally chaos directory eventual-consistency reset
Remove one eventual-consistency rule, or put the whole fault back to zero.
Reset the eventual-consistency fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory eventual-consistency reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory incident
Take each resource down for a while, then bring it back.
Take each resource down for a while, then bring it back. Every interval each resource (or, on the directory and identity surfaces, the tenant) rolls against the percentage; on a hit every request to it fails for the rolled duration, answered as an outage would be, then it recovers on its own. Compare outage, which fails requests for as long as it is armed. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. One value N picks 0 to N each time; MIN-MAX, such as 30-120, picks within that range. A duration is required whenever the fault fires. --interval is how often the fault starts, such as 10m. It is required whenever the fault fires: nothing else sets it off. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos directory incident --percentage 25 --seconds 30-120 --interval 10m locally chaos directory incident --percentage 100 --seconds 30-120 --interval 10m --name my-app
Usage
locally chaos directory incident [flags] locally chaos directory incident [command]
Flags
-h, --help[=true|false] help for incident
--interval string How often this fault rolls for each resource, e.g. 10m; the first roll lands at a random point within the first interval (required when it fires)
--millis string Duration in milliseconds, e.g. 250; N for 0 to N, or MIN-MAX for a range
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; N for 0 to N, or MIN-MAX for a range
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory incident reset - Remove one incident rule, or put the whole fault back to zero.
locally chaos directory incident reset
Remove one incident rule, or put the whole fault back to zero.
Reset the incident fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory incident reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory latency
Hold requests for a random delay before they are handled.
Hold requests for a random delay before they are handled. The response is unchanged, just late. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. The value is a maximum: each firing picks 0 to N. A duration is required whenever the fault fires. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos directory latency --percentage 25 --seconds 30 locally chaos directory latency --percentage 100 --seconds 30 --name my-app
Usage
locally chaos directory latency [flags] locally chaos directory latency [command]
Flags
-h, --help[=true|false] help for latency
--millis string Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory latency reset - Remove one latency rule, or put the whole fault back to zero.
locally chaos directory latency reset
Remove one latency rule, or put the whole fault back to zero.
Reset the latency fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory latency reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory outage
Fail requests for as long as the rule is armed, like a region or service that is down.
Fail requests for as long as the rule is armed, like a region or service that is down. Each request rolls against the percentage, so at 100 every request fails until the fault is turned off. Each service answers in its own terms, usually 503 Service Unavailable, and a protocol with live connections also closes the ones open when the outage starts. For downtime that ends by itself, see incident. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --retry-after sets the Retry-After header the fault answers with, such as 5s. Without one the service's usual hint is sent. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos directory outage --percentage 25 locally chaos directory outage --percentage 25 --retry-after 5s locally chaos directory outage --percentage 100 --name my-app
Usage
locally chaos directory outage [flags] locally chaos directory outage [command]
Flags
-h, --help[=true|false] help for outage
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--retry-after string Retry-After this fault answers with, e.g. 5s or 500ms (the service's usual hint when omitted)
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory outage reset - Remove one outage rule, or put the whole fault back to zero.
locally chaos directory outage reset
Remove one outage rule, or put the whole fault back to zero.
Reset the outage fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory outage reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory reset
Zero every Microsoft Graph (directory) fault and drop every rule.
Zero every Microsoft Graph (directory) fault and drop every rule. Examples: locally chaos directory reset
Usage
locally chaos directory reset [flags]
Flags
-h, --help[=true|false] help for reset
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory show
Print the current Microsoft Graph (directory) chaos configuration.
Print the current Microsoft Graph (directory) chaos configuration. Examples: locally chaos directory show
Usage
locally chaos directory show [flags]
Flags
-h, --help[=true|false] help for show
--tenant string Tenant UUID (defaults to the configured default)
locally chaos directory stale-read
Serve stale reads after a write.
Serve stale reads after a write. Each write opens a window on what it wrote, and reads inside the window see it as it was before the write. Without scope flags this sets the fault's rate on Microsoft Graph (directory). With --name it adds or edits one rule, leaving the rate and other rules alone. A rule can be lower than the rate: "everywhere except one place" is a rate of 100 plus a rule at 0. --seconds and --millis set the duration. A bare number is in the flag's unit; one with its own suffix, such as 250ms or 1.5s, means what it says. The value is a maximum: each firing picks 0 to N. A duration is required whenever the fault fires. A value flag left out keeps what the row already has; a new rule starts with none. 'reset' clears a row. Examples: locally chaos directory stale-read --percentage 25 --seconds 30 locally chaos directory stale-read --percentage 100 --seconds 30 --name my-app
Usage
locally chaos directory stale-read [flags] locally chaos directory stale-read [command]
Flags
-h, --help[=true|false] help for stale-read
--millis string Duration in milliseconds, e.g. 250; the maximum: each firing picks 0 to N
--name string Scope this rule to one user or application, by name
--percentage int How often this fault fires, 0-100 (required)
--seconds string Duration in seconds, e.g. 30 or 1.5; the maximum: each firing picks 0 to N
--tenant string Tenant UUID (defaults to the configured default)
Subcommands
- locally chaos directory stale-read reset - Remove one stale-read rule, or put the whole fault back to zero.
locally chaos directory stale-read reset
Remove one stale-read rule, or put the whole fault back to zero.
Reset the stale-read fault. With a scope flag, removes that rule so those requests use the fault's rate. Without one, removes every rule and sets the rate to 0. 'reset --location X' removes the rule; '--percentage 0 --location X' keeps a rule that never fires, which is how to say "everywhere except X".
Usage
locally chaos directory stale-read reset [flags]
Flags
-h, --help[=true|false] help for reset
--name string Scope this rule to one user or application, by name
--tenant string Tenant UUID (defaults to the configured default)
During Public Preview you can use the Team plan for free, and get an early-adopter discount at GA. Sign in