> 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/es/despliegue-de-scepman/first-run-root-cert.md).
# CA raíz
Después de haber implementado su entorno SCEPman, debe crear un certificado raíz.
Si desea usar un certificado intermedio (solo Enterprise Edition), puede consultar esta guía:
{% content-ref url="/pages/cdbd98cc925fba2df84317317964f2d5ec3a33c2" %}
[CA intermedia](/es/despliegue-de-scepman/intermediate-certificate.md)
{% endcontent-ref %}
**Para una configuración estándar de SCEPman, recomendamos generar un nuevo certificado raíz con los siguientes pasos:**
## Crear certificado raíz de SCEPman
1. Ve a **Servicios de aplicaciones**.
2. Elija la aplicación SCEPman y haga clic en **Examinar** para ver el sitio web de SCEPman.
3. Cuando todo funciona según lo previsto **Intune**, **Leer AAD, Leer Intune,** y **Storage Account** están marcados en verde como **conectado**.
4\. La opción **haga clic aquí para comenzar** creando el certificado RootCA de Azure Key Vault. El certificado raíz inicial solo debe crearse una vez en una granja.\
5\. Seleccione **He leído la documentación\[...]** y haga clic en **Crear primer nodo**.\
6\. Después de unos segundos/minutos puede actualizar la página. Ahora debería ver que el certificado raíz está disponible.
¡Ahora está listo para comenzar! Consulte [Implementación de certificados mediante Microsoft Intune](/es/administracion-de-certificados/microsoft-intune.md)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.scepman.com/es/despliegue-de-scepman/first-run-root-cert.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
