--- title: "Security compliance" slug: "security-compliance" updated: 2026-09-02T06:32:10Z published: 2026-09-02T06:32:10Z canonical: "docs.turbo360.com/security-compliance" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.turbo360.com/llms.txt > Use this file to discover all available pages before exploring further. # Security compliance ## Overview **Security compliance** is a document type in Azure Documenter that provides a detailed status report on policy assignments across your subscriptions and resources. ### Business value - Get a consolidated view of policy adherence across subscriptions without switching between the Azure portal and multiple compliance dashboards - Filter the report by specific policy states to focus on non-compliant or conflicting resources ahead of audits or governance reviews - Share a structured, exportable compliance snapshot with security and audit teams on demand ## Prerequisites ### Required permissions | Role | Permission level | Access | | --- | --- | --- | | Account owner, Owner, Contributor | - | Full access to the Documentation section | | Custom role | Read | View documents generated under Documentation | | Custom role | Manage | View, generate, and manage documents under Documentation | ## How it works The Security compliance document reports on the status of Azure Policy assignments across your subscriptions and resources. ### Document structure The document is organized per subscription. For each subscription, the report includes: - **Assignments:** a table listing all policy assignments with counts for Compliant, Non Compliant, Exempt, and Conflict resources per assignment - **Per initiative:** for each initiative assignment, a list of the policies it contains or "No data available" if the initiative has no policy details - **Policy groups:** policies not grouped under an initiative appear under "Not grouped policies" with their compliance state - **Per policy:** a detailed resource-level table listing every resource evaluated under the policy The per-policy resource table columns are: | Column | Description | | --- | --- | | Resource | The name of the Azure resource | | Resource type | The Azure resource type (e.g., Virtual Machines, SQL Databases, App Services) | | Compliance state | Compliant or Non compliant | If a subscription has no policy assignments configured, the document shows **No initiatives available** for that subscription. Policy states: - **All:** Includes Not Compliant, Compliant, Conflict, and Exempt states. - **Compliant:** Includes policies with the state Compliant. - **Non compliant:** Includes policies with the state Non-Compliant. - **Conflict:** Includes policies with the state Conflict. - **Exempt:** Includes policies with the state Exempt. Learn more about how compliance and policy states work in the [Azure Policy documentation](https://learn.microsoft.com/en-us/azure/governance/policy/how-to/get-compliance-data#how-compliance-works). ## Steps Use the following steps to generate a Security compliance document. Navigate to **Azure Documenter** to get started. 1. Click **New configuration**. The **Configure your document** wizard opens. 2. In **Step 1: Basics**, enter a configuration name. Under **Choose document type**, select **Security compliance**. Choose the **Policy states** to include: All, Compliant, Non compliant, Conflict, or Exempt. Click **Next**. 3. In **Step 2: Service principal**, select the service principal and configure the subscription scope. Click **Next**. 4. Complete **Steps 3–6** (Branding, Publish settings, Schedule, Notifications) as required. Click **Next** after each step. 5. In **Step 7: Review**, confirm your configuration and click **Finish**. Once generation is complete, a **URL** is created for the document, and you can download it using the **Download** link. ## Example scenario A cloud governance team needs to confirm whether all production subscriptions comply with the organization's tagging and encryption policies before a quarterly audit. They generate a Security compliance document scoped to those subscriptions, filtering for **Non compliant** and **Conflict** states, and share the generated URL with the audit team. ## Troubleshooting 1. **Security compliance document returns no data for a subscription** Cause: no policy assignments are configured for the selected subscriptions in Azure Policy. Fix: verify that policy assignments exist for the subscriptions and that the service principal has permissions to read compliance data. 2. **Document generation fails or returns incomplete data** Cause: the service principal lacks the required permissions to read Azure Policy compliance data for the selected subscriptions. Fix: verify the service principal has at least Reader access on all selected subscriptions, then regenerate. 3. **Per-policy resource table is empty for a compliant policy** Cause: the selected Policy states filter excludes Compliant resources from the output. Fix: set Policy states to **All** in Step 1: Basics to include resources across all compliance states. ## FAQs 1. **What subscriptions can I include in a Security compliance document?** You can choose any of the subscriptions available in your Azure Documenter document configuration when setting up the document. 2. **What do the policy states in the document mean?** Policies can appear as All, Compliant, Non compliant, Conflict, or Exempt. See the policy states callout above for what each state includes. 3. **Can I generate a Security compliance document without creating a new configuration?** Yes. Use the **Context menu ( ⋮ )** next to any existing document configuration in the tree view. ## Related articles - [Access details - By subscription](https://docs.turbo360.com/docs/access-details-by-subscription) - [Resource auditing](https://docs.turbo360.com/docs/resource-auditing) - [Managing document configurations](https://docs.turbo360.com/docs/managing-document-configurations)