# Welcome

## Overview

SCEPman is a slim and resource-friendly solution to issue and validate certificates using Simple Certificate Enrollment Protocol (SCEP). **It is an Azure Web App providing the SCEP protocol and works directly with the Microsoft Graph and Intune API.** SCEPman uses an Azure Key Vault based Root CA and certificate creation. By default, no other component is involved, neither a database nor any other stateful storage except the Azure Key Vault itself. That said, SCEPman **will not need any backup procedures** or other operation level tasks. Only an Azure subscription is necessary to deploy it.

SCEPman is a service that gets **deployed into your Azure tenant**, giving you full control on how and where SCEPman processes and stores data. No data leaves your tenant and there is no need to grant external vendor permissions in your tenant.

![SCEP flow with Microsoft Intune](https://2535731700-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LoGejQeUQcw7lqnQ3WX%2Fuploads%2Fgit-blob-907b29197c481875ec25c9bcc3b7c6e86e5a0f85%2Fscepman-flowchart.webp?alt=media)

The following documentation will show you a straightforward way to deploy certificates to modern cloud managed clients. Without any on-premises PKI your users and devices will be able to get certificates.

## SCEPman vs. Legacy PKI

If you are interested in learning more about the effort involved in installing and operating a legacy/on-premises PKI such as the Certificate Connector for Intune / Active Directory Certificate Services (ADCS) in comparison to SCEPman, please refer to below article.

{% content-ref url="other/faqs/certificate-connector" %}
[certificate-connector](https://docs.scepman.com/other/faqs/certificate-connector)
{% endcontent-ref %}

## Get more details about SCEPman

{% embed url="<https://www.youtube.com/watch?v=kr8uBPlG4J8>" %}
SCEPman 2.0 - What's new?
{% endembed %}

{% content-ref url="details" %}
[details](https://docs.scepman.com/details)
{% endcontent-ref %}

{% content-ref url="editions" %}
[editions](https://docs.scepman.com/editions)
{% endcontent-ref %}

## SCEPman Guides

We offer two guides to deploy the SCEPman environment. Please follow below link for guidance on which guide is best suited for your scenario and deployment requirements:

{% content-ref url="scepman-deployment/deployment-guides" %}
[deployment-guides](https://docs.scepman.com/scepman-deployment/deployment-guides)
{% endcontent-ref %}

## Change Log

News from our development and our roadmap can be found under the **Change Log**.

{% content-ref url="changelog" %}
[changelog](https://docs.scepman.com/changelog)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.scepman.com/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.