> For the complete documentation index, see [llms.txt](https://docs.scepman.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scepman.com/scepman-deployment/deployment-options/marketplace-deployment.md).

# Marketplace deployment

* To deploy SCEPman from Azure Marketplace, please visit this [**link**](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/glueckkanja-gabag.scepman?tab=Overview).
* Click **Get it now** and afterwards **Continue**. You will be re-directed to the marketplace item on Azure Portal.

<figure><img src="/files/Gi06ZEkHE5psaypCC1y2" alt=""><figcaption></figcaption></figure>

* Click **Create**.
* Now, follow these steps to deploy SCEPman in your Azure tenant:

<figure><img src="/files/Bdpdq6k7wcMGS1xCrpKh" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If you have a license key, you can paste it into the field **License Key**. Leave it empty to use the free Community Edition of SCEPman.
{% endhint %}

{% hint style="warning" %}
To maximize compatibility, for the **Organization Name** we recommend to omit

* language-specific special characters (e.g. ö, ø, é, ...)
* a leading space (spaces between words can be used)
* quotation marks
  {% endhint %}

1. Select an existing **resource group** or create a new one (SCEPman resources will be deployed in this group)
2. Set the **region** according to your preferred data center location. It **must** match the region of the resource group - in case you have selected an existing one. It will be assigned to the resource group otherwise.
3. Set an **Organization Name**. This field is **important** as the organization provided here will manifest itself in the O= field of the Root CA that is going to be created later on.
4. Select your preferred **Update Channel**. By default, the [Evergreen approach](/azure-configuration/update-strategy.md#evergreen-approach) is configured as [update strategy](/azure-configuration/update-strategy.md). This parameter determines from which [channel](/scepman-configuration/application-artifacts.md) the binaries for SCEPman will be loaded. For production environments, we recommend to use the **Production Channel** (default).
5. Click **Review + Create**.
6. Click **Create**.

Congratulations! The deployment of SCEPman is done. Please continue with the [next step](/scepman-deployment/deployment-guides/community-guide.md#step-2-perform-post-deployment-steps-permission-assignments) of the [Standard Guide](/scepman-deployment/deployment-guides/community-guide.md) to complete the installation of SCEPman.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.scepman.com/scepman-deployment/deployment-options/marketplace-deployment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.