Standard Guide

This will guide you through all steps necessary to set up SCEPman in your PoC or Production environment based on our best practices.

Azure Deployment

Let's start with the requirements and a resource overview. Keep in mind that you need to plan a useful Azure resource design.

Prerequisites

Mandatory

• Azure subscription (at least Contributor rights on that subscription).

• Azure owner rights (at least on Resource Group level).

• Microsoft Entra ID (Azure AD) "Global administrator" (Consent to access Graph API).

• Make sure to define your Azure policies according to SCEPman requirements (e.g. do not enforce TLS).

Optional

• Public Domain CNAME (scepman.yourdomain.com), if a custom domain is used.

• SSL (Wildcard-) Certificate (or use App Service Managed Certificate), if a custom domain is used.

Overview Azure Resource

All these resources are recommended for a production environment.

Type	Description
App Service (x2)	A virtual Azure environment to run the SCEPman Core and Cert Master applications and provides a UI to configure different application specific settings like CNAME, SSL certificate and App Settings.
App Service Plan	A virtual set of compute resources and configurations for the "App Service(s)". Here you can configure the pricing tier and resource scaling.
Key Vault	Tool to securely store secrets and certificates. The SCEPman application will generate and save the root certificate in your Key Vault.
Application Insights	Application Performance Management (APM) tool to get insights of the SCEPman applications and requests. Needed to measure performance and good for service optimization.
Storage account	Storage platform used by SCEPman's Certificate Master component to store certain attributes of the manually issued TLS server certificates for revocation purposes. Optional: The "App Service" will load the artifacts from a blob storage URI if manual updates are configured.
Log Analytics workspace	A centralized and cloud-based log storage. The "App Service" will save all platform logs and metrics into this workspace.
Data Collection Rule	Since v 3.0 to allow SCEPman to write logs to the Log Analytics Workspace using Microsofts Log Ingestion API

Additionally, if you are using Private Endpoints, you have seven more Azure Resources.

Type	Description
Virtual Network	The SCEPman App Services, the Key Vault, and the Storage Account connect over this VNET.
Private Endpoint (×2)	One for the Key Vault and one for the Storage Account. It makes them accessible over the VNET.
Private DNS zone (×2)	One for the Key Vault and one for the Storage Account. They both have an internal IP address in the VNET, for which they have a name in their respective Private DNS zone.
Network Interface (×2)	One for the Key Vault and one for the Storage Account. It connects the Private Endpoint to the VNET.

Configuration Steps

1

Deploy SCEPman Base Services

This is a mandatory step.

To start with the deployment, please follow our deployment instructions:

Marketplace deployment

2

Perform Post-Deployment Steps (Permission Assignments)

This is a mandatory step.

To properly link all components of SCEPman 2, several permissions need to be assigned. Please follow these steps to establish the relevant connections:

Managed Identities

3

Add Certificate Master Permissions

This is a mandatory step for Enterprise Edition customers. Community Edition users may skip this step.

The Certificate Master is an Enterprise Edition feature that allows administrators to manually generate and revoke certificates. Please follow these steps to provide access to the Certificate Master.

Certificate Master RBAC

4

Create Root certificate

This is a mandatory step.

After the deployment and permission assignment is complete, you need to create the root certificate for SCEPman:

Root CA

5

Configure a Custom Domain and SSL Certificate

This is an optional step.

To have your SCEPman available under your specific domain you need to create a Custom Domain in the App Service.

Custom Domain

6

Manual Updates

This is an optional step.

By default, SCEPman adopts an evergreen approach towards updates. In case you require full control over your SCEPman updates, please configure a deployment slot as described in the following guide under section Deployment Slot Configuration.

Update Strategy

7

Deploy Application Insights

This is recommended step.

The Application Insights can be used to get an overview of the App Service performance and to get deeper insights of the request processing of SCEPman. We recommend to always configure Application Insights to monitor, maintain and optimize the App Service.

Application Insights

8

Configure Health Check

This is recommended step.

We can configure a Health Check for the App Service to get direct notifications in case that the SCEPman stops working.

Health Check

9

Ensure that SCEPman has sufficient Resources

This is a mandatory step.

Once you move SCEPman into a production environment, you should ensure that SCEPman is equipped with sufficient computing power. Therefore, please review our Azure Sizing guide and upgrade your App Service Plan tier if need be. You may postpone this until after your PoC or trial phase.

App Service Sizing

10

Configure your MDM Deployment Profiles

This is a recommended step.

With the completion of the above steps, we have a working SCEPman implementation and can now deploy certificates to the devices.

Please use one (or more) of the following articles, to deploy certificates with your preferred MDM solution:

Microsoft IntuneJamf ProOther MDM Solutions

11

Manually Issue Certificates or sign CSRs using the Certificate Master

This is an optional step.

Please follow below link, to learn how to issue TLS server or other certificates or how to sign any CSR using the Certificate Master component.

Certificate Master