Skip to main content
INTEGRATION · MICROSOFT INTUNE

The certificate authority Intune talks to directly.

Intune hands SCEP requests to a third-party CA and asks it to confirm each one. SCEPman is that CA, running in your Azure tenant. No NDES server, no Certificate Connector, and every certificate stays tied to its Intune and Entra ID object for as long as it lives.

  • Windows, macOS, iOS, iPadOS, Android, Linux
  • Revoked on delete, disable, wipe
  • Community Edition free

Your devices

Windows, macOS, iOS, iPadOS, Android, Linux

Microsoft Intune

Delivers the root and the SCEP profile

SCEPman in your Azure tenant

Issues the certificate and answers every check

What Intune, the device and SCEPman each do

Intune's certificate report lists every SCEPman certificate like one from any other CA.
  • Intune
    Intune
    Intune sends the device a trusted root profile and a SCEP profile with SCEPman's URL.
  • The device
    The device
    The device creates its key and sends a certificate request to SCEPman, with a challenge from Intune.
  • SCEPman
    SCEPman
    SCEPman sends the request to Intune, which checks the challenge and whether the subject, alternative names, key usage, key length and extended key usage match the SCEP profile assigned to the device. Only then does SCEPman issue the certificate, with the device or user ID in it, and report the result back to Intune.
  • Every check
    Every check
    Every check of the certificate later asks SCEPman, and SCEPman asks Entra ID and Intune.
REVOCATION

What revokes an Intune certificate

Both are off by default; the user-risk check is marked experimental in the documentation.

  • Device deleted

    Gone from Intune and Entra ID: revoked for good.

  • Device disabled

    Disabled in Entra ID: on hold, valid again when you enable it.

  • Wipe or retire

    Issued, pending or failed: on hold at once, even while the device is offline. On by default; needs the Intune device ID in the certificate.

  • Optional

    Revoked in Intune

    Optional: SCEPman also reads Intune's list of issued certificates, so a revocation you trigger in Intune counts.

  • Enterprise Edition

    Not compliant

    Optional, Enterprise Edition: on hold while the device is out of compliance, with a grace period after enrollment so Autopilot can finish.

  • Enterprise Edition

    User risk

    Optional, Enterprise Edition: user certificates on hold while Microsoft Entra ID Protection rates the user above your limit.

TRY IT

How long an Intune certificate lives

Three limits meet: the profile in Intune, SCEPman's Intune endpoint and SCEPman's global maximum. The shortest wins, except on Apple platforms.

Platform

Effective validity

365 days

Limited by: the Intune profile

  • the Intune profile365 days
  • SCEPman's Intune maximum365 days
  • SCEPman's global maximum730 days

Issued at: backdated 24 hours for clients with a wrong clock

ACTIVE DIRECTORY

Strong certificate mapping for on-premises sign-in

Since Microsoft's KB5014754 changes, domain controllers expect certificates used for on-premises authentication to name the account's SID. SCEPman can add the SID extension to the certificates it issues, the way ADCS does, or you add the SID as a URI in the Intune profile. You only need either if your Intune certificates sign in to on-premises resources, for example through NPS or RDP.
LINUX

Linux devices in Intune

SCEP profiles don't reach Linux. Intune-managed Linux devices get their certificate through SCEPman's self-service enrollment instead: an Intune script calls SCEPman's REST API, and the certificate is tied to the device's Intune or Entra object like every other Intune certificate.
COMPARE

Every MDM we document

How certificates issued through each MDM are delivered, renewed and revoked.

MDMs documented for SCEPman, with platforms, renewal and revocation
MDMPlatformsIssuance and renewalAutomatic revocationManual revocation
Microsoft IntuneWindows, macOS, iOS, iPadOS, Android, LinuxYesYesYes
Jamf PromacOS, iOS, iPadOSYesYesYes
Google WorkspaceChromeOS, AndroidYesUser certificates synced from Entra IDYes
Iru (formerly Kandji)macOS, iOS, iPadOSYesUser certificates synced from Entra IDYes
AddigymacOS, iOS, iPadOSYesUser certificates synced from Entra IDYes
MosylemacOS, iOS, iPadOSYesNoYes
SOTI MobiControlWindows, macOS, iOS, iPadOS, Android, UbuntuYesNoYes
Active Directory (group policy)WindowsYesNo—

Automatic revocation for "user certificates synced from Entra ID" works for user certificates whose users come from Microsoft Entra ID.

Questions about SCEPman and Microsoft Intune

01Does Intune Cloud PKI make SCEPman unnecessary?

That depends on what else needs certificates. SCEPman also covers servers, domain-joined Windows, Jamf and other MDMs, code signing and sub CAs, and runs in your own tenant with your own key, or, with RADIUSaaS, as a service we run.

02Which device ID goes into the certificate?

The Entra device ID or the Intune device ID; SCEPman can check both. Wipe detection needs the Intune device ID.

03What happens during Autopilot when compliance checks are on?

Either SCEPman issues a short-lived bootstrap certificate that is replaced once the device is compliant, or you set a grace period after enrollment.

04Can we see SCEPman certificates in Intune?

Yes. SCEPman reports each issued certificate back to Intune, and Intune's certificate report shows it.

Every Microsoft Intune certificate issued is validated against the tenant.

Deploy SCEPman, connect it to Microsoft Intune, assign one profile.