> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/v21-ja-jp/azure-virtual-desktop/azure-virtual-desktop-no-1/tenpurtoazure-virtual-desktopno/notenpurtono.md).

# 既存のテンプレートの管理

**テンプレートの変更**

既存のテンプレートを変更するには、テンプレートを右クリックして **\[プロパティ]** を選択します。多くのプロパティは変更できますが、いくつかのプロパティは変更できません。個別のプロパティと設定については、[**「テンプレートの作成」**](https://download.parallels.com/ras/v19/docs/ja_JP/Parallels-RAS-19-Administrators-Guide/47812.htm)の説明を参照してください。

テンプレートを削除するには、リストからテンプレートを選択し、**\[タスク]** > **\[削除]** をクリックします。なお、本ガイドの執筆時点で、RAS Console でテンプレートを削除すると、テンプレートと関連するホストが Microsoft Azure から完全に削除されない可能性があるという既知の問題があります。該当のオブジェクトがすべて削除されていることの確認は、Azure ポータルから実行できます。


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/ras-admin-guide/v21-ja-jp/azure-virtual-desktop/azure-virtual-desktop-no-1/tenpurtoazure-virtual-desktopno/notenpurtono.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 `build a script that syncs our docs to a CMS` 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.