Skip to main content
Checks that all Azure infrastructure entities are classified by criticality.

​
About

When you connect Microsoft Azure to DSALTA, the platform pulls your resources into Inventory using read-only API access. DSALTA activates this check until every resource is classified by criticality.

​
Why This Matters

You cannot apply the right level of protection to a resource you have not classified. Rating resources by criticality ensures the most important systems get the strongest controls and is required by ISO 27001 asset-management controls.

​
How to Fix

Before you begin
  • Ensure the Microsoft Azure integration is connected so resources appear in your inventory.
Classify each resource by criticality
  1. In DSALTA, go to Data Library → Inventory.
  2. For each Microsoft Azure resource, set a criticality classification — Critical, High, Medium, or Low — based on the data and workload it supports.
  3. In Microsoft Azure, apply matching tags or labels so classification stays consistent, and use a policy to enforce tagging on new resources.
Once all entities are classified, DSALTA sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Microsoft Azure integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Microsoft Azure.