Inventory
Collect and normalise the Azure estate, then return Excel reports, machine-readable data and clear collection-health records.
Azure inventory, reporting and insights
CloudState inventories Microsoft Azure inside your automation, then returns structured data and reports that platform teams can review and act on.
In development. Inventory and Insights are being validated; collection, findings and delivery scope are agreed during the pilot.
Azure pilots from £2,500–£4,000 plus VAT.
Excel inventory and a separate evidence ZIP.
Three service levels
Collect and normalise the Azure estate, then return Excel reports, machine-readable data and clear collection-health records.
Analyse the collected evidence and produce a separate findings workbook and JSON output. The current Azure checks cover selected disk, VM, storage, network and tagging conditions; they remain under validation.
Add experienced Cygnus review, recommendations and implementation guidance while the inventory and reports remain under your control.
How it works
Your configured automation obtains short-lived Azure tokens through a customer-controlled identity for inventory collection. Report delivery uses separately agreed credentials and write permissions.
CloudState inventories the configured estate and records both successful coverage and material collection gaps.
Human-readable reports, machine-readable resources and relationships, run health and delivery records are produced together.
Where Insights is included, checks run locally against the collected inventory. Customer data does not need to be sent to Cygnus.
Reports and data go to your chosen destination for technical review, management reporting and action.
Reports and data
A formatted workbook covering the configured subscriptions and the resource types collected during the run.
Versioned, machine-readable resource and relationship data for repeatable downstream analysis.
Clear records of what was collected, where access or queries failed and which areas need further attention.
Traceable run and delivery information, including output integrity and the outcome of the configured destination.
Conditions worth reviewing, with severity, supporting data and validation guidance when CloudState Insights is included.
A concise view of material themes, priorities and agreed next actions at the Insights and Advisory levels.
Data control
You manage the Azure identity, run the automation and choose where CloudState stores its reports and data.
A customer-managed identity provides access to the subscriptions and resource types included in the inventory.
Inventory and optional analysis are designed to run in your configured automation environment, including a customer-managed GitHub workflow.
The pilot validates the selected destination, such as GitHub artefacts, SharePoint or Azure Storage, and its authentication and write permissions.
You choose what to share with Cygnus when Advisory review is included.
Subscription levels
Azure inventory workbook, machine-readable resource and relationship data, collection coverage, run health and delivery records.
Everything in Inventory, plus prioritised findings, governance checks and management reporting. The pilot confirms which history and trend outputs your team needs.
Everything in Insights, plus up to six hours of Cygnus technical review, recommendations and consultancy each month.
Indicative subscription guide
Level 1 — Inventory
£750/month
£7,200 annually. Inventory, machine-readable data and run-health reporting for the agreed Azure scope.
Level 2 — Insights
£1,500/month
£14,400 annually. Inventory plus prioritised findings, governance checks and management reporting.
Level 3 — Advisory
£3,000/month
£28,800 annually. Insights plus up to six hours of Cygnus review and consultancy each month.
Onboarding
From approximately £2,500, depending on subscription count, identity and permissions, delivery integration and reporting requirements.
Larger estates are priced according to subscription count, access model, delivery integration and reporting requirements.
Discuss scope and pricingStart with a pilot
Choose the scope. Agree the subscriptions, identity, inventory coverage, report destination and questions the pilot needs to answer.
Run the pilot. A pilot is typically £2,500–£4,000 plus VAT, with some or all of the fee available as credit against an annual subscription.
Review the result. Confirm collection coverage, report usefulness, data control and operational ownership in your environment.
Choose the next step. Continue with Inventory, Insights or Advisory only if the pilot delivers what your team needs.
Excel inventory and a separate evidence ZIP.
Example output
Generated by the current Inventory code using synthetic Azure records. Download the Excel workbook and its machine-readable evidence separately.
Frequently asked
CloudState is a customer-side Azure inventory and reporting service. It collects a structured view of the configured estate, produces human-readable and machine-readable outputs, and records collection coverage and run health. Higher service levels add prioritised insights and Cygnus advisory support.
Collection and optional analysis are designed to run in your configured automation environment. The pilot validates the deployment and report destination. You share information with Cygnus only when you want advisory support.
Inventory collection is designed to use a customer-controlled identity with read-only access to the agreed Azure scope. Report delivery requires separate authentication and write permissions, agreed during the pilot.
Insights flags conditions worth reviewing across security, operations, governance and optimisation. Each item includes supporting data and validation guidance so your team can decide what action is warranted.
CloudState begins with a paid Azure pilot. After the pilot, you can choose Inventory, Insights or Advisory as a recurring service, with the final scope and price based on the Azure estate and reporting requirements.
The pilot establishes suitable scope and operating limits. Larger environments need validation of subscription count, access model, runtime and delivery integration.
Start with a pilot
Tell us how many subscriptions are involved, where the reports should go and what your team needs to learn from them. We will outline a practical pilot.