> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/cloud-tools/recommendations/azure-recommendations.md).

# Azure Recommendations

Manage your Azure recommendations.

Microsoft Azure recommendations are divided into the following categories:

* **Savings** - These recommendations enable cost savings.
* **Risk** - These recommendations help mitigate compliance risk for licenses that may come from a non-compliance position.
* **Security** - These recommendations help to improve the security of an Azure environment.
* **High Availability** - These recommendations help to improve the availability of an Azure environment.
* **Performance** - These recommendations help improve the performance of an Azure environment.

All Azure Recommendations have a Cloud Recommendation type. The following are some examples of the Azure recommendations:

* Buy Reserved Instances
* Shutdown or Resize your Virtual Machine
* Security Center Recommendations
* Enable Soft Delete
* Enable Backup

## Associate recommendations with resources <a href="#associating-recommendations-with-resources" id="associating-recommendations-with-resources"></a>

All Azure recommendations that are recommended by Azure (and not by SoftwareOne services) are automatically associated with resources whether they are virtual machines, storage accounts, or databases. For example, recommendations of **SQL DB Advisor recommendations** type are associated with SQL databases that need to be acted on.

The association from a recommendation to a related Client Portal resource is available on the **Related Resources** tab:

<figure><img src="https://content.gitbook.com/content/Z5DNbniz33mXCZoO62Rm/blobs/G8pw4tg1I5QZskygiILa/image.png" alt=""><figcaption><p>Related Resources tab</p></figcaption></figure>

## Complete Azure recommendations <a href="#completion-of-azure-recommendations" id="completion-of-azure-recommendations"></a>

The Client Portal can detect the completion of recommendations in Azure. When a recommendation is completed in Azure:

* The status of that recommendation is set to **Completed** in the Client Portal.&#x20;
* The potential savings amount on the recommendations is set to **Realised**.
* The recommendation is moved from the **Active** tab to the **Realised** tab.
* The realized savings from the recommendation are displayed on the **Savings** tile.

{% hint style="info" %}
The Client Portal doesn't track the realization of Reserved Instance recommendations from Microsoft Azure. It means that when a Buy Reserved Instances or Renew Reserved Instances recommendation is completed, the Client Portal won't track any savings realized as part of completing these recommendations.
{% endhint %}


---

# 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.platform.softwareone.com/extensions/cloud-tools/recommendations/azure-recommendations.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.