The questions admins ask about SCEPman
The answers from every page of this site, grouped by topic. Setup steps and settings are in the documentation.
Questions admins ask first
01Is there a free edition?
Yes. Community Edition is free and uses the same binaries as Enterprise Edition. It covers device and user certificates for Intune and Jamf Pro, without support. Active Directory enrollment, Certificate Master, domain controller certificates, geo-redundancy, the intermediate CA and the compliance check need Enterprise Edition; a licence key switches over.
02How does SCEPman compare to Microsoft Cloud PKI?
03Can glueckkanja reach into our tenant?
No. SCEPman runs in your subscription with managed identities you grant. It sends a small amount of non-personal, non-secret data to us for licensing and quality assurance. More detail goes out only if you switch on remote debugging for a support case, and that switches itself off at the date you set. If we run SCEPman for you as a service with RADIUSaaS, it reads your tenant through the connection you grant: admin consent or an app registration of your own.
04Do we still need NDES or the Intune Certificate Connector?
No. Intune talks SCEP to SCEPman directly and confirms each request through its challenge.
05Can glueckkanja host it for us?
Together with RADIUSaaS, yes: in the SaaS Bundle we run SCEPman for you as a service. Geo-redundancy, Active Directory enrollment, the Enrollment REST API and Kerberos certificates are available soon.
06How many users do we license?
Everyone who has a SCEPman certificate on themselves or their devices, plus everyone who relies on SCEPman's domain controller, server or code signing certificates. In many Microsoft 365 setups that equals your Intune licences. The minimum is 50 users.
07Do we need a CRL?
Usually not. OCSP covers Wi-Fi, VPN and Windows. Some systems, Entra certificate-based authentication among them, check a CRL; SCEPman can publish one, and it lists the certificates you revoke in Certificate Master. Automatic revocations reach OCSP clients only.
08What happens to a device that is offline when we delete it?
Nothing has to happen on the device. The next time anything checks its certificate, SCEPman answers "revoked". That works for wipe and retire too, even while the device is switched off.
09Why are the certificates on our iPhones valid for 365 days?
iOS, iPadOS and macOS ignore the validity set in the Intune profile. They get SCEPman's Intune maximum, 365 days by default, or SCEPman's global maximum where that is lower. You can raise or lower both.
Wi-Fi, LAN and VPN
01Does the laptop need a user logged on to join the Wi-Fi?
No. A device certificate is available to Windows before logon, so the network is there for the logon itself.
02How fast does a deleted device lose access?
Immediately: SCEPman answers "revoked" from the moment the device is gone. A RADIUS server that caches OCSP answers may keep the last "good" for up to 10 minutes by default; you can shorten that.
03What if SCEPman is unreachable?
04Can we use user certificates instead of device certificates?
Partly. SCEPman checks the user in Entra ID: disabled means on hold, deleted means revoked. A user certificate is only there once someone has signed in, so a Windows PC with nothing but a user certificate stays off the network at the sign-in screen, and signing in may need that network. On Windows, use device certificates, or chain the two: the device authenticates first, and once the user has signed in, it authenticates again with the user certificate. Chaining doesn't work on shared devices.
05Does SCEPman fit a Zero Trust design?
Yes. A certificate proves the device or user at every connection, and the answer to the revocation check comes from Entra ID, Intune or Jamf, so access follows the state of the device rather than its place on the network. With the compliance check of Enterprise Edition, it also follows Intune compliance.
Servers and Linux
01Are these certificates trusted by browsers on the internet?
No. SCEPman is your private CA, so its certificates are trusted where you deploy the root: your managed devices and servers. For a public website, use a public CA.
02Can a server renew forever without a person?
Yes, with EST. Each renewal proves itself with the current certificate. If a certificate expires before it is renewed, the next one needs an authenticated request again.
03Which key sizes are possible?
Through a CSR, whatever the requester generated. In the Certificate Master form, RSA 2048 or 4096 bits.
04Who sees what in Certificate Master?
Roles in the Certificate Master app registration decide it, per certificate type and per method. A helpdesk group can be allowed server certificates by CSR and nothing else.
05Do server certificates count as licensed users?
Users who connect to services secured with SCEPman server certificates count. In practice that is often everyone who has the SCEPman root on a device.
06Can SCEPman issue the certificates for Remote Desktop?
Yes. Domain-joined servers can get an RDP certificate through group policy autoenrollment from the Active Directory endpoint of Enterprise Edition, and other servers request one in Certificate Master or over the REST API. Remote Desktop clients then trust the server through your root instead of the self-signed certificate Windows creates.
07Can SCEPman issue certificates for routers, switches and access points?
Yes. Request a device certificate in Certificate Master, either with a key Certificate Master creates (RSA 2048 or 4096 bits, as PKCS#12 and PEM) or from a CSR the device generated, and install it on the device. A role decides who may request one.
Phishing-resistant MFA
01Does this replace Windows Hello for Business?
No, it sits next to it. Many organizations use Windows Hello on their own devices and certificates on YubiKeys for admin accounts or shared workstations. SCEPman also issues the domain controller certificates some Windows Hello setups need.
02Is the private key on the YubiKey generated there?
In the documented flow, Certificate Master generates the key and you import the PKCS#12 file into the YubiKey. Delete the file after the import.
03Can we block users with a high risk level?
Enterprise Edition can treat user certificates as on hold while Microsoft Entra ID Protection rates the user above a level you choose. The setting is off by default and marked experimental. It acts on OCSP checks, so Wi-Fi and VPN follow it; Entra CBA checks the CRL instead.
04Do certificates for MFA cost extra?
No. They count like any other SCEPman certificate: per user.
Code signing
01Which edition do we need?
Enterprise Edition. Code signing certificates come from Certificate Master.
02How long is a code signing certificate valid?
As long as you choose when you request it, up to the maximum you configure for code signing certificates.
03What happens to signed scripts when the certificate expires?
That depends on whether the signature carries a timestamp from a timestamp service. Without one, signatures are treated as invalid once the certificate expires; plan renewals and re-signing accordingly.
04How is code signing licensed?
Per user who runs or validates the signed code. In practice that is usually everyone with the SCEPman root on a device.
IoT devices
01Can a device renew its own certificate?
Yes, over EST with the certificate it has, if it speaks EST and the endpoint allows renewals.
02Do IoT devices need Entra ID?
No. The line station or backend that requests the certificates authenticates with Entra ID; the device itself only holds its key and certificate.
03Can we use a separate CA for IoT?
Yes. Run a second SCEPman instance with its own root, so the IoT trust chain stays apart from the laptops.
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.
Jamf Pro
01Do we need Intune for Jamf?
No. SCEPman runs in an Azure subscription of yours, or as a service we run with RADIUSaaS, and Jamf certificates are checked against Jamf.
02Which permissions does SCEPman get in Jamf?
Read access to computers, mobile devices and users. Nothing it could change.
03Can Intune and Jamf share one SCEPman?
Yes. Each MDM has its own endpoint, and both issue under the same root.
Other MDMs
01Which edition do we need?
Enterprise Edition. Both endpoints belong to it, and Static-AAD refuses requests without it.
02Is the challenge a secret?
Yes, treat it like one. Anyone who has it can request certificates from that endpoint, so give it only to your MDM. SCEPman can keep it in Azure Key Vault.
03There's no setup guide for our MDM. Will it work?
Yes, if it can send a fixed SCEP challenge. The endpoints have no logic specific to an MDM; the MDMs under setup guides are simply the ones we have written guides for.
05Can we run another MDM and Intune side by side?
Yes. Intune has its own endpoint, and every certificate comes from the same root.
Replacing ADCS
01Can SCEPman and ADCS run in parallel?
Yes. They are separate CAs; devices can hold certificates from both while you move.
02Do we need Enterprise Edition for this?
For the Active Directory endpoint, domain controller certificates, Certificate Master and the intermediate CA, yes.
03What about certificates for users who never touch your MDM?
Domain-joined users get theirs through the Active Directory endpoint; everyone else through Certificate Master or self-service enrollment.
04Does SCEPman need to be in our network?
No. Clients reach it over HTTPS; the Active Directory endpoint authenticates them with Kerberos through the service principal you register.
Secure Network Access Bundle
01Can I get SCEPman SaaS without RADIUSaaS?
No. SCEPman as a service is an add-on to RADIUSaaS and comes only in the SaaS Bundle. On its own, SCEPman runs in your Azure tenant, as Community Edition or Enterprise Edition.
02I already use RADIUSaaS with another CA. Can I switch?
Yes. RADIUSaaS can trust SCEPman's root next to the CA you use today, so devices move over one MDM profile at a time. RADIUSaaS then takes its own server certificate from SCEPman and renews it by itself.
03Can the CA key stay in my own Key Vault?
Yes. In the Enterprise Bundle SCEPman runs in your tenant and creates the key in your Key Vault. In the SaaS Bundle you can give SCEPman an Azure Key Vault of your own for the CA key (RSA 4096-bit); you choose that before the first certificate, because it can't be changed later.
04Does it work for VPN and wired LAN as well as Wi-Fi?
Yes. RADIUSaaS has rules for Wi-Fi, wired 802.1X and VPN, and checks the certificate the same way for all three.
05Which access points work with RADIUSaaS?
Any access point, switch or VPN gateway that speaks RADIUS or RadSec with EAP. The RADIUSaaS documentation has setup guides for Aruba, Fortinet, Juniper Mist, Meraki, MikroTik, Ruckus and UniFi over RadSec, and for ExtremeCloud IQ, Meraki, Sophos UTM and UniFi through a proxy.