Skip to main content
Azure - FinOps Platform

Governance & Policy Compliance

Policy compliance rate

Share of the latest Azure Policy evaluation states that are Compliant, across every policy assignment applied to this subscription.8 state(s) evaluated
Why this matters

A rate below 100% doesn't automatically mean risk — check the detail table below to see which specific assignments are driving the gap before treating it as urgent.

Target is 100% compliant across every evaluated policy state.

Compliance state

Azure Policy's latest evaluation state per resource/assignment pair — Non-compliant is an Azure Policy evaluation state, not an AFP opinion.8 state(s)
Why this matters

Non-compliant is Azure Policy's own evaluation state, not a security incident — cross-check the category breakdown and detail table below to see which policy definitions are driving the non-compliant count.

  • Good (8)
Policy state detail Traces a compliance result to its exact policy assignment, definition, and resource. Filter by state, category, or resource group to narrow this list.
State Assignment Definition Category Resource group
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant allowed-locations-assignment Allowed locations General rg-blue-harbor-prod-app
Compliant storage-geo-redundancy-assignment Storage accounts should use geo-redundant storage Storage rg-blue-harbor-prod-app