> 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/ja/azure-gou-cheng.md).

# Azure 構成

- [Application Insights](https://docs.scepman.com/ja/azure-gou-cheng/application-insights.md)
- [App Service サイジング](https://docs.scepman.com/ja/azure-gou-cheng/azure-sizing.md)
- [自動スケーリング](https://docs.scepman.com/ja/azure-gou-cheng/azure-sizing/autoscaling.md): 自動スケーリングは、需要に応じて稼働インスタンス数を自動調整し、パフォーマンスを維持しつつコストを管理します。
- [バックアップに関する考慮事項](https://docs.scepman.com/ja/azure-gou-cheng/backup-considerations.md)
- [カスタム ドメイン](https://docs.scepman.com/ja/azure-gou-cheng/custom-domain.md)
- [地理冗長性](https://docs.scepman.com/ja/azure-gou-cheng/geo-redundancy.md)
- [ヘルスチェック](https://docs.scepman.com/ja/azure-gou-cheng/health-check.md)
- [サードパーティ製監視の使用](https://docs.scepman.com/ja/azure-gou-cheng/health-check/using-3rd-party-monitoring.md)
- [ログ管理](https://docs.scepman.com/ja/azure-gou-cheng/log-configuration.md)
- [リソースの移動](https://docs.scepman.com/ja/azure-gou-cheng/move-scepman-resources.md): このガイドでは、同じ Tenant 内で SCEPman リソースをあるサブスクリプションから別のサブスクリプションにある新しいリソース グループへ移動する方法を説明します。
- [プライベート エンドポイント](https://docs.scepman.com/ja/azure-gou-cheng/private-endpoints.md)
- [分割テナンシー](https://docs.scepman.com/ja/azure-gou-cheng/split-tenancy.md)
- [更新戦略](https://docs.scepman.com/ja/azure-gou-cheng/update-strategy.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/ja/azure-gou-cheng.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.