Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Inspect the Zero Trust Assessment configuration and change settings when you identify a bottleneck. Lower concurrency to reduce memory pressure and throttling. Increasing a timeout doesn't fix missing access.
Start with an imported module and diagnostic files for the bottleneck. The following settings and defaults describe the development source. Check the configuration available in your installed package before changing it.
Prerequisites
- An installed assessment module, imported into your PowerShell session.
- The collector and test diagnostics for the bottleneck you want to investigate.
Inspect configuration settings
Review current values before deciding what to change.
Import the assessment module if it isn't already loaded.
Inspect its configuration:
Get-PSFConfig -Module ZeroTrustAssessmentCompare the relevant values with the available settings and the affected collector and test diagnostics.
Change settings for the current session
Set values before invoking the assessment.
Select a setting that addresses the identified bottleneck.
Set the value. For example, reduce test concurrency in the current session:
Set-PSFConfig -Module ZeroTrustAssessment -Name 'ThrottleLimit.Tests' -Value 3Run the assessment and review the affected collector or test diagnostics.
The -ConfigurationFile parameter accepts JSON for supported settings. Explicit command-line values override configuration-file values. Not every run parameter is a configuration-file setting.
Persist a setting
Set the value, then register that configuration entry for future sessions.
Set and register the entry. For example:
Set-PSFConfig -FullName 'ZeroTrustAssessment.Graph.CacheMaxItems' -Value 10000 Register-PSFConfig -FullName 'ZeroTrustAssessment.Graph.CacheMaxItems'Use the configuration inspection command in future sessions to review the registered value.
Register-PSFConfig defaults to the current user's settings. Set-PSFConfig doesn't have a -Register switch.
Duration settings accept standard time spans and PSFramework notation such as 30m, 2h, or 2h 30m. See the PSFramework documentation and assessment configuration definitions.
Available configuration settings
All names in this table use the prefix ZeroTrustAssessment.. Defaults describe the development source.
| Setting | Default | Purpose |
|---|---|---|
Export.DependencyWaitLimit |
1d |
Maximum wait for another export that a collector depends on. |
Export.SignInLog.MaxSizeBytes |
1073741824 (1 GB) |
Sign-in export size cap; collection stops at the cap. |
ThrottleLimit.Export |
5 |
Maximum parallel collectors. |
ThrottleLimit.Tests |
5 |
Maximum parallel tests. |
Tests.Timeout |
1h |
Per-test timeout; 0 disables it. |
Tests.TimeoutType |
Idle |
Idle measures time since last activity; Start measures time since execution began. |
Tests.RetryCount |
0 |
Reattempts for failed executions. |
Tests.RetryTimeout |
$false |
Include timed-out executions in retries. |
Tests.Statistics.MessageCountSoftCap |
1024 |
Threshold for simplifying stored per-test message objects. |
Azure.DisableCache / Graph.DisableCache |
$false |
Disable the respective in-memory request cache. |
Azure.CacheMaxItems / Graph.CacheMaxItems |
50000 |
Maximum items in each request cache. |
Azure.CacheLifetime / Graph.CacheLifetime |
30m |
Expiration of cached entries. |
Logging.Database.IncludeQueryResults |
$false |
Include database row values in logs. Leave disabled normally: it increases volume and exposes tenant data. |
Logging.InMemoryLog.MinSize |
51200 |
Minimum PSFramework in-memory message capacity enforced at import. Larger values consume more memory. |
Debug.KeepWorkflows |
$false |
Keep background workflows for debugging instead of normal cleanup. Avoid for routine runs. |
TabExpansion.TestLimit |
10 |
Maximum test IDs offered by tab completion at a time. |
Tune a large-tenant run
Review related limits together rather than increasing every value.
- Inspect collector and test logs to identify slow collection, throttling, timeouts, or memory pressure.
- Consider lowering both throttle limits and bounding caches.
- Review sign-in lookback, the collection time budget, the sign-in export size cap, and test and export timeouts together. See run parameters.
- Review retry settings only for failed or timed-out executions. They don't turn a failed security recommendation into a pass.
- Leave database row-value logging and retained workflows disabled for routine runs.