Example workbook · Microsoft Azure
CloudState Example Inventory Workbook
Explore the current CloudState Excel inventory format using synthetic Azure records, with a separate machine-readable evidence download.
Development example. Synthetic data and simulated collection; no sign-up required.
CloudState is in development. This Excel workbook was generated by the current Inventory code using synthetic Azure records. It shows the workbook format, rather than a separate PDF presentation. No customer data or live Azure queries were used.
Inside the workbook
- 39 worksheets covering Overview, Run Health, subscriptions and resource inventory;
- three invented subscriptions, six virtual machines and linked disk, network, storage and platform records;
- resource attributes and ownership tags; and
- a Run Health worksheet showing simulated collector and coverage outcomes.
The demonstration warning gives this sample a degraded run status. It makes clear that collection was simulated; it is not evidence that a live Azure estate was successfully inventoried. The empty DeletedDisks worksheet illustrates a capability marked not applicable; it does not establish production coverage.
Machine-readable Inventory data
Download the example evidence bundle (ZIP).
The bundle contains the same workbook, resource and relationship records in NDJSON (one JSON record per line), run health, a redacted example configuration, a run log and a manifest for checking file integrity. The sample does not demonstrate delivery to an external customer destination. Separate execution and delivery sidecars are produced during a normal Inventory run.
The CloudState Showcase on GitHub carries the same workbook, evidence bundle and previews. All example records are synthetic.
Inventory and Insights are separate outputs
Inventory supplies the Excel workbook and machine-readable evidence. Optional Insights analyses that evidence and produces a separate findings workbook and JSON output. This Inventory download contains no Insights findings or advisory assessment.
Both products are still being validated. Supported collection, findings and delivery scope will be agreed during the pilot; this example is not a promise of complete estate coverage.
Discussing your Azure scope
Tell us which subscriptions matter, where the automation would run and where the outputs should be stored. Inventory collection is intended to use customer-controlled read-only Azure access; the selected report destination requires its own agreed authentication and write permissions.