Audit run and export states

Task and prerequisites

Use this guide to monitor an audit or set a recurring review. You need normal access to the workspace and an included, validated cloud connection.

Starting or changing a schedule also needs the relevant administrative permission and an active Growth or Enterprise entitlement. Free evaluation and Starter audits are manual.

A provider connection being valid does not establish that billing and every optional source are ready.

States users should trust

Read the audit result before the export status. A completed audit with an unavailable PDF still has an audit result; a running audit has not yet produced a final result.

A partial result needs its coverage limitations reviewed before you use its findings.

• Use the audit outcome for collection/detection success.
• Use report state for report aggregation availability.
• Use the export control's status for file availability. A disabled export cannot be fixed by repeatedly requesting it.

• Available reports and exports
• Troubleshoot missing results

Report and export availability

Report preparation and file export have separate outcomes from collection. A report or export problem does not automatically invalidate a completed audit.

General audit PDF is unavailable during the controlled launch; use the authorized CSV option shown in the audit or Findings view. Repeated PDF requests will not remove that launch restriction.

Dedicated Azure Virtual Desktop reports and internal statements have separate scope and access requirements, so their formats do not establish general audit PDF availability.

Choose the next step

For a failed audit, correct the customer-safe connection or collection issue before starting another run. For a partial audit, identify which decisions can use the collected evidence and which need another source.

For an export failure, check the selected format and follow its retry guidance without rerunning a successful audit solely to recreate a file. Before sharing a CSV, confirm the selected population, native currency, and any resource names or account identifiers it contains.

Monitoring and schedules

Open Connections, select the intended connection and inspect its current schedule before changing it. Growth and Enterprise support daily, weekly and monthly audit frequencies; Off disables the recurring audit schedule.

Save only through the authorized control, then check the saved frequency and the next run shown by the application. Review Audits for the resulting run and its coverage.

Cost synchronization and price-catalog refresh are separate jobs, so an audit schedule does not promise an immediate billing refresh or an emailed report.

• Confirm the selected connection, workspace and permitted plan.
• Check the run reference and collection time, not just the notification count.
• After a failure, resolve the safe cause before retrying; avoid creating repeated runs while one is still active.

Expected result and troubleshooting

A usable result identifies the run, included scope, evidence time, outcome and missing sources. If no scheduled run appears, check whether the schedule is Off, entitlement is inactive or the connection is unavailable.

A queued run can wait for background capacity. A failed collection must not be reported as a clean audit.

Contact support with the run reference, time and safe failure category if recovery does not help. Do not share credentials or raw exception output.