PKI-as-a-Service

PKI-as-a-Service

    Integrations Overview

    PKI-as-a-Service issues certificates to many kinds of devices, not only Windows computers joined to the domain. Each kind of device uses the enrollment method that suits it best.

    • Domain-joined Windows computers and users: Auto-enrollment through CEP and the Enrollment Gateway. Typical certificate use: Wi-Fi, VPN, device authentication, smart card logon.
    • Mobile devices managed by Microsoft Intune: SCEP through Microsoft NDES. Typical certificate use: Wi-Fi, VPN, email signing.
    • Apple devices managed by Jamf Pro: SCEP through Microsoft NDES. Typical certificate use: Wi-Fi, VPN, device identity.
    • Network devices (routers, switches, firewalls): SCEP through Microsoft NDES. Typical certificate use: Device identity, VPN.
    • Linux servers and web servers: ACME, or CSR enrollment in the portal. Typical certificate use: TLS for web and internal services.
    • Applications and scripts: REST API. Typical certificate use: Automated issuance in DevOps pipelines.

    Mobile Device Management (MDM) tools such as Intune and Jamf do not issue certificates themselves. They ask each device to request a certificate through SCEP and deliver the settings that tell the device where to send the request.

    On this Page:
    Support Privacy Policy Terms of Service

    Copyright 2026 Encryption Consulting LLC. All rights reserved.