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

# ステータス

{% hint style="info" %}
使用するには <code class="expression">space.vars.SCEPmanSAAS\_ProductName</code>、まず **設定** > [**SCEPman**](/ja/ptaru/scepman-saas/she-ding.md).
{% endhint %}

この **SCEPman** メニュー hive から、RADIUSaaS に組み込まれた SCEPman SaaS インスタンスにアクセスできます（別途ライセンスが必要です）。

サブメニューでは、Certificate Master コンポーネントを利用して手動の証明書タスクを実行できます。方法の詳細については **証明書の管理**, **証明書の要求**、および **タスク**については、対応する SCEPman ドキュメントを参照してください：

{% embed url="<https://docs.scepman.com/certificate-management/certificate-master>" %}

## ステータス

お使いの <code class="expression">space.vars.SCEPmanSAAS\_ProductName</code> インスタンスのステータスページでは、環境向けにサービスを構成する際に必要な、最も関連性の高い情報を確認できます。これにより、

* Key Vault、Graph API (Intune)、または Jamf Pro などの依存先への接続状態を確認し、
* CA 証明書の公開部分をダウンロードしたり、
* MDM システムでの構成に必要な SCEP 登録エンドポイントにアクセスしたりできます。

<figure><img src="https://992520889-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWU1DQ4UGkqER7uGNUOm%2Fuploads%2FGBIiXP3W44fbhTmrxL4K%2Fimage.png?alt=media&amp;token=4953f960-8539-4543-a10e-91d99c3a1a7c" alt=""><figcaption></figcaption></figure>


---

# 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.radiusaas.com/ja/ptaru/scepman-saas/suttasu.md?ask=<question>&goal=<user_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.
