Microsoft Intune
Connect Microsoft Intune to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Microsoft Intune to collect mdm evidence with automated compliance tests, switched on per workspace.
| Category | MDM |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Microsoft Intune's guide | learn.microsoft.com |
Connect with an API token
-
In Microsoft Intune:
- Sign in to the Microsoft Entra admin center (entra.microsoft.com) as at least a Cloud Application Administrator. If you have several tenants, use the Settings icon to switch to the right one.
- Browse to Entra ID › App registrations and select New registration. Enter a Name (for example Safeguard), under Supported account types choose Single tenant only - <your tenant>, and select Register.
- On the app's Overview page, record the Application (client) ID.
- Select Certificates & secrets › Client secrets › New client secret, add a description, select an expiration (24 months at most; Microsoft recommends less than 12), and select Add.
- Record the client secret Value now. It is never displayed again after you leave this page.
- Select API permissions › Add a permission › Microsoft Graph › Application permissions.
- Under Select permissions, select the permission or permissions Safeguard needs, then select Add permissions.
- Select Grant admin consent for <your tenant> and confirm. The button is disabled unless you are an admin.
Where to find the other values:
- Tenant ID: Entra ID › App registrations, select your application: the app's overview page shows the Directory (tenant) ID.
- Client ID: Application (client) ID on the app registration's Overview page.
Microsoft Intune shows the secret only once, so copy it before you leave the page.
Microsoft Intune's public documentation does not cover every step.
Source: learn.microsoft.com, learn.microsoft.com, learn.microsoft.com, learn.microsoft.com, checked 2026-10-07.
The permissions Safeguard needs:
DeviceManagementManagedDevices.Read.All,DeviceManagementConfiguration.Read.All. -
On Compliance › Connectors, open Microsoft Intune, click Connect, choose API token and fill in:
Field What to enter Tenant ID Required. Client ID Required. Client secret Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Microsoft Intune and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | C1.1, CC6.1, CC6.2, CC6.5, CC6.6, CC6.7, CC6.8, CC7.1 | 10 |
| ISO/IEC 27001 | Automated tests | A.5.9, A.5.11, A.6.5, A.8.1, A.8.7, A.8.8, A.8.9, A.8.20, A.8.24 | 10 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(5), 164.310(d)(1), 164.312(a)(1), 164.312(e)(1) | 10 |
| PCI DSS | Automated tests | 1.5.1, 3.5.1, 5.2.1, 6.3.3, 8.2.8, 12.5.1 | 8 |
| NIST CSF 2.0 | Automated tests | DE.CM-09, ID.AM-01, PR.AA-03, PR.AA-05, PR.DS-01, PR.IR-01, PR.PS-01, PR.PS-02 | 10 |
These tests are switched on per workspace by the Safeguard team.
Related
- MDM connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks