Reading device compliance from Intune, Jamf, or Apple Business Manager

If your company already manages devices through Intune, Jamf Pro, or Apple Business Manager, MiraShield can read compliance state directly from it — a stronger signal than a script on the device, because it comes from the MDM's own attestation rather than from something a local admin could disable.

Honest state, not optimistic marketing: as of writing, none of the three has been run against a real tenant and read on screen, which is the bar every connector here has to clear before it's offered. They show as "Built, and not yet run against a real account of this kind" in the connector picker — visible, and correctly not yet connectable.

What each will read

• Microsoft Intune — disk encryption, the compliance policy Intune itself enforces, OS version, jailbreak/root state, and check-in freshness. Rides the same Microsoft 365 consent Azure uses.
• Jamf Pro — FileVault encryption, whether the MDM management profile is still active, OS version, and check-in freshness. Connects with a Jamf Pro API client you generate yourself; the client secret is encrypted at rest and used only to call your own Jamf server.
• Apple Business Manager — narrower on purpose: it has no compliance signal to offer, only device inventory and MDM assignment. It reports exactly one thing — a device your company owns that isn't assigned to any MDM server at all, which is a real blind spot worth knowing about even without a compliance reading.

Once one of these has been verified against a real tenant, it moves from greyed-out to connectable in the same picker used for cloud accounts — no separate screen to learn.