Intune Documentation and Purview Compliance Manager

How Microsoft Purview Compliance Manager and Intune Documentation fit together, what each one checks, and how to attach device evidence to improvement actions.

Microsoft Purview Compliance Manager and Intune Documentation do different jobs. They work well together. Compliance Manager is the register for a regulation, with controls, owners and workflow. Intune Documentation produces the device configuration evidence that Compliance Manager asks for but cannot collect itself.

This page explains the difference in plain terms, with links to Microsoft Learn so you can check every claim about Purview.

Evidence, not certification

Intune Documentation produces evidence about how devices are configured. It does not certify your organisation and it does not make any control pass. A person still reviews the evidence in Compliance Manager and decides what it means for the assessment.

Two different meanings of compliance policy

Microsoft uses similar names for two unrelated things.

  • In Microsoft Purview, a compliance policy usually means a data policy, such as data loss prevention, retention, sensitivity labels, Insider Risk Management, Communication Compliance or eDiscovery. These policies govern data in Microsoft 365 and connected services.
  • In Microsoft Intune, a device compliance policy checks device state, for example whether a disk is encrypted. Intune configuration profiles, Settings Catalog policies and endpoint security policies configure the device itself.

Microsoft Purview Compliance Manager belongs to the first world. It helps you work through a regulation with templates, improvement actions and a compliance score that Microsoft calculates from the tests and records held in Compliance Manager. Evidence for many controls is uploaded by hand.

Intune Documentation belongs to the second world. It reads the Intune configuration itself.

What Compliance Manager checks automatically

Compliance Manager can test some improvement actions automatically. Microsoft lists the sources for that automated testing as other Purview solutions, Microsoft Secure Score, Microsoft Defender for Cloud, and connectors, including connectors for Salesforce, Zoom and Corporate Sustainability. See Improvement actions in Microsoft Purview Compliance Manager, Connectors in Microsoft Purview Compliance Manager and Microsoft Secure Score.

There is no Intune connector in that list. Secure Score lists its own contributing products, and Intune is not one of them.

That means Compliance Manager does not read:

  • Intune configuration profiles
  • Settings Catalog policies
  • Intune device compliance policies
  • Endpoint security policies

It also does not show which Intune policy or which setting value supports a device control, because it never looks at that configuration.

What happens to device controls instead

Controls that depend on device configuration are handled as customer managed work in Compliance Manager. Someone opens the improvement action, marks the status, and uploads evidence on the Evidence tab. Accepted evidence file types include .pdf and .zip. See Storing evidence on Microsoft Learn.

In practice, an admin has to find the right Intune settings, show their configured values, check that the policy is assigned, and package all of that as a file. Intune Documentation does that collection and packaging step.

What Purview does better

Use Compliance Manager for the parts it was built for. In several areas it goes far beyond anything an Intune documentation tool should try to do.

  • Regulation coverage. Microsoft offers more than 360 regulatory templates, far more than the frameworks Intune Documentation maps Intune settings to. Premium templates are licensed per regulation family. Microsoft 365 E5, A5 and G5 plans include three premium templates. For current licensing, check Microsoft's licensing guidance rather than relying on a page like this one.
  • Organisational and nontechnical controls. Policies, training, supplier management and other measures outside Intune still need a home. Compliance Manager covers the whole regulation, not only device settings. Intune Documentation covers only the controls that Intune and Conditional Access configuration can evidence, and marks the rest clearly. See Compliance evidence.
  • Workflow. Improvement actions have owners, due dates and status tracking across a team.
  • Continuous testing for data controls. For supported Microsoft 365 data controls, Compliance Manager retests automatically, typically every 24 hours, and updates the result without anyone uploading a file.

If your organisation tracks a regulation in Compliance Manager, keep doing that. Intune Documentation feeds device evidence into that process. It does not replace it.

What Intune Documentation adds

Intune Documentation reads the actual Intune settings in your tenant, with exact setting ids and configured values, and it is assignment aware. A setting in a policy that is assigned to nobody does not count as evidence.

For each mapped control, you can see and export:

  • the Intune policy behind the evidence, and whether it is assigned
  • the exact setting, with its expected value and its actual value
  • whether the value matches, differs, or is missing

That evidence supports several outputs:

  • As built documentation. A readable Word or PDF document of your policies, settings and assignments. See Select and export.
  • Framework evidence reports. A PDF evidence report per framework for an auditor, an insurer or a customer questionnaire. See Compliance evidence.
  • Purview evidence pack (desktop app). One ZIP file with the framework evidence PDF, the JSON evidence record, an index that lists every assessed control with the matching Purview template name and where to find it in the PDF, and upload instructions for Compliance Manager. Where no matching Purview template exists, the index says so. There are no per-control PDFs. You attach the ZIP, or the framework PDF from it, to the related improvement action.
  • Evidence register (desktop app). The same assessment as an Excel workbook and as CSV, one row per technical check, for review, tracking or import into your own tooling.
  • Local snapshot history and change tracking (desktop app). Collections you choose to keep, encrypted on your computer and off by default, so you can show what changed between two points in time and which policy or setting caused a control result to change. Collection can also run on a schedule while the app is open.
  • Draft fix pack (desktop app). For safeguards with no evidence at all, draft, unassigned Windows Settings Catalog policies as JSON. A draft has no effect until you review it, import it and assign it yourself.
  • Entra tenant policy and device status context. The tenant authentication methods policy and security defaults are read with the Policy.Read.All permission already used for Conditional Access, with no new permissions. Screen lock after inactivity counts as supporting evidence. Intune's per-policy device status counts are shown next to the evidence and never change a status.
  • Reference comparison (desktop app). Compare one tenant or snapshot against a reference tenant or snapshot, setting by setting.
  • MSP portfolio overview (desktop app). Several tenants side by side, with framework coverage and snapshot age, for teams that manage many customers. See Work with multiple tenants.

In the desktop app, collection and report generation happen on your computer, and tenant data stays on your machine. See Security and privacy. If a report flags a value as different, Search settings shows every policy that sets it. The management report summarises safeguard coverage for leadership.

At a glance

QuestionPurview Compliance ManagerIntune Documentation
Main jobTrack a regulation end to end, with templates, owners and workflowDocument Intune configuration and map exact settings to framework controls
Reads Intune configurationNo. No Intune connector and no reading of profiles, Settings Catalog, device compliance policies or endpoint security policiesYes. Exact setting ids and values, with assignment for each policy
Automated testingOther Purview solutions, Secure Score, Defender for Cloud and connectors such as Salesforce, Zoom and Corporate SustainabilityChecks collected Intune and Conditional Access configuration against expected values each time you collect and assess
Evidence for device controlsCustomer managed. Someone marks the improvement action and uploads a file, for example a PDF, on the Evidence tabBuilds the file for you: one framework evidence PDF (alone or in the ZIP evidence pack), with policy, setting, expected value, actual value and assignment per control
Framework coverageMore than 360 templates, including premium templates licensed per regulation familyThe frameworks listed in Compliance evidence, mapped to device configuration evidence
Organisational controlsYes, as part of the full assessmentNo. Controls that Intune cannot evidence stay clearly marked for separate assessment
Workflow and ownersImprovement actions with owners, due dates and statusNo task workflow. Outputs are documents, an evidence pack and a register
Output for an auditorThe assessment, its records and the evidence you attachedAs built Word and PDF documentation, framework evidence PDFs, a Purview evidence pack, and an Excel and CSV register in the desktop app
Where tenant data is processedIn your Microsoft 365 tenantDesktop app: on your computer. Web app: in memory only, never stored. See Security and privacy

How they work together

Use Compliance Manager as the control register and Intune Documentation as the evidence source for device controls.

Assess your configuration in Intune Documentation

Collect your tenant, open Compliance evidence, choose the framework that matches your Compliance Manager assessment, and set the scope to the platforms and levels in that assessment. Review controls with missing, different or mixed evidence before you export anything.

Save the Purview evidence pack in the desktop app

Export the Purview evidence pack for that framework. The ZIP file contains the framework evidence PDF, the JSON evidence record, an index that lists every assessed control with its Purview template name and where to find it in the PDF, and a short set of upload instructions. Save the Excel or CSV evidence register alongside it if your team tracks checks in a spreadsheet.

Before you upload, check each control id in the index against the template version in your tenant. Template contents can differ between versions, so treat the index as a map you verify, not as a promise that every id will match.

Attach the pack to improvement actions in Compliance Manager

In Compliance Manager, open the assessment, then open the improvement action for the device control. On the Evidence tab, use Add evidence and upload the evidence pack ZIP, or the framework PDF from it. The index in the pack says where each control is covered in the PDF. Repeat for each improvement action you are evidencing, then record the status your team decides on.

Keep the pack, including its index, and the register saved alongside it with your assessment records. When the configuration changes, collect again, export a fresh pack, and replace or add the affected evidence. Local snapshot history in the desktop app helps you show what changed between the two packs.

Uploading a PDF does not change a test result on its own. Your team reviews the evidence and updates the improvement action in Compliance Manager. Intune Documentation shortens the step before that: finding, checking and packaging the device configuration evidence.

Microsoft also offers configuration management in Microsoft Entra Tenant Governance, sometimes called Unified Tenant Configuration Management. It can capture Intune configuration snapshots and monitor them for drift. Its output is JSON based and aimed at comparison and backup workflows, and it carries no framework mapping. See Intune resources in Microsoft Entra Tenant Governance on Microsoft Learn.

That capability and Intune Documentation answer different questions. Tenant Governance answers whether configuration drifted from a snapshot. Intune Documentation answers what the configuration says in readable form, which framework controls it evidences, and what has changed over a local history that you keep and control on your own machine in the desktop app. Teams can use both: one for drift snapshots in Microsoft's service, the other for readable documentation and framework evidence.

Questions

Sources and further reading

Microsoft Learn is the source for every Purview claim on this page.

On this page