-description: Get started with Azure Advisor.

-Learn how to access Advisor through the Azure portal, get and manage recommendations, and configure Advisor settings.

-> Azure Advisor runs in the background to find newly created resources. It can take up to 24 hours to provide recommendations on those resources.

-To access Azure Advisor, sign in to the [Azure portal](https://portal.azure.com). From there, select the [Advisor](https://aka.ms/azureadvisordashboard) icon at the top of the page, use the search bar at the top to search for Advisor, or use the left navigation pane **Advisor** link.<br> The Advisor **Overview** page opens by default.

-See personalized and actionable recommendations on the Advisor **Overview** page.

-* The links at the top offer options for **Feedback**, downloading recommendations as comma-separated or PDFs, and a quick-link to Advisor **Workbooks**.

-* The blue filter buttons below them focus the recommendations.

-* The tiles represent the different recommendation categories and include your current score in that category.

-* The **Get started** link takes you to options for direct access to Advisor workbooks, recommendations, and the Well Architected Framework main page.

-The tiles on the Advisor **Overview** page show the different categories of recommendations for all the subscriptions that you have access to, by default.

-You can filter the display using the buttons at the top of the page:

-* **Subscription**: Choose *All* for Advisor recommendations on all subscriptions. Alternatively, select specific subscriptions. Apply changes by clicking outside of the button.

-* **Recommendation Status**: *Active* (the default, recommendations not postponed or dismissed), *Postponed* or *Dismissed*. Apply changes by clicking outside of the button.

-* **Resource Group**: Choose *All* (the default) or specific resource groups. Apply changes by clicking outside of the button.

-* **Type**: Choose *All* (the default) or specific resources. Apply changes by clicking outside of the button.

-View recommendation details ΓÇô such as the recommended actions and impacted resources ΓÇô and the solution options, including postponing or dismissing a recommendation.

-1. To review details of a recommendation, including the affected resources, open the recommendation list for a category and then select the **Description** or the **Impacted resources** link for a specific recommendation. The following screenshot shows a **Reliability** recommendation details page.

- :::image type="content" source="./media/advisor-get-started/advisor-score-reliability-recommendation-page.png" alt-text="Screenshot of Azure Advisor reliability recommendation details example." lightbox="./media/advisor-get-started/advisor-score-reliability-recommendation-page.png":::

- Understand the recommendation before you act by clicking the **Learn more** link on the recommended action page, or at the top of the recommendations details page.

- :::image type="content" source="./media/advisor-get-started/advisor-recommendation-postpone.png" alt-text="Sreenshot of Azure Advisor recommendation postpone option." lightbox="./media/advisor-get-started/advisor-recommendation-postpone.png":::

-You can exclude subscriptions or resources, such as 'test' resources, from Advisor recommendations and configure Advisor to generate recommendations only for specific subscriptions and resource groups.

-> To change subscriptions or Advisor compute rules, you must be a subscription owner. If you do not have the required permissions, the option is disabled in the user interface. For information on permissions, see [Permissions in Azure Advisor](permissions.md). For details on right sizing VMs, see [Reduce service costs by using Azure Advisor](advisor-cost-recommendations.md).

-From any Azure Advisor page, select **Configuration** in the left navigation pane. The Advisor Configuration page opens with the **Resources** tab selected, by default.

-Use the **Resources** tab to select or unselect subscriptions for Advisor recommendations. When ready, select **Apply**. The page refreshes.

-Use the **VM/VMSS right sizing** tab to adjust Advisor virtual machine (VM) and virtual machine scale sets (VMSS) recommendations. Specifically, you can set up a filter for each subscription to only show recommendations for machines with certain CPU utilization. This setting filters recommendations by machine, but doesn't change how they're generated. Follow these steps.

-1. Select the subscriptions youΓÇÖd like to set up a filter for average CPU utilization, and then select **Edit**. Not all subscriptions can be edited for VM/VMSS right sizing and certain privileges are required; for more information on permissions, see [Permissions in Azure Advisor](permissions.md).

-1. Select the desired average CPU utilization value and select **Apply**. It can take up to 24 hours for the new settings to be reflected in recommendations.

- :::image type="content" source="./media/advisor-get-started/advisor-configure-rules.png" alt-text="Screenshot of Azure Advisor configuration option for VM/VMSS sizing rules." lightbox="./media/advisor-get-started/advisor-configure-rules.png":::

-## Next steps

-description: Use Azure Advisor to optimize your Azure deployments.

-You can access Advisor through the [Azure portal](https://aka.ms/azureadvisordashboard). Sign in to the [portal](https://portal.azure.com), locate **Advisor** in the navigation menu, or search for it in the **All services** menu.

-* **Reliability**: To ensure and improve the continuity of your business-critical applications. For more information, see [Advisor Reliability recommendations](advisor-reference-reliability-recommendations.md).

-* **Security**: To detect threats and vulnerabilities that might lead to security breaches. For more information, see [Advisor Security recommendations](advisor-security-recommendations.md).

-* **Performance**: To improve the speed of your applications. For more information, see [Advisor Performance recommendations](advisor-reference-performance-recommendations.md).

-* **Cost**: To optimize and reduce your overall Azure spending. For more information, see [Advisor Cost recommendations](advisor-reference-cost-recommendations.md).

-* **Operational Excellence**: To help you achieve process and workflow efficiency, resource manageability and deployment best practices. For more information, see [Advisor Operational Excellence recommendations](advisor-reference-operational-excellence-recommendations.md).

-Select a category to display the list of recommendations for that category, and select a recommendation to learn more about it. You can also learn about actions that you can perform to take advantage of an opportunity or resolve an issue.

-Select the recommended action for a recommendation to implement the recommendation. A simple interface opens that enables you to implement the recommendation or refer you to documentation that assists you with implementation. Once you implement a recommendation, it can take up to a day for Advisor to recognize that.

-If you don't intend to take immediate action on a recommendation, you can postpone it for a specified time period, or dismiss it. If you don't want to receive recommendations for a specific subscription or resource group, you can configure Advisor to only generate recommendations for specified subscriptions and resource groups.

-

-You can access Advisor through the [Azure portal](https://aka.ms/azureadvisordashboard). Sign in to the [portal](https://portal.azure.com), locate **Advisor** in the navigation menu, or search for it in the **All services** menu.

-

-You can access Advisor recommendations as *Owner*, *Contributor*, or *Reader* of a subscription, Resource Group, or Resource.

-### What resources does Advisor provide recommendations for?

-Advisor provides recommendations for the following

-Azure Advisor also includes your recommendations from [Microsoft Defender for Cloud](../defender-for-cloud/defender-for-cloud-introduction.md), which might include recommendations for other resource types.

-To postpone or dismiss a recommendation, select the **Postpone** or **Dismiss** link, and the recommendation is moved to the Postponed/Dismissed tab on the recommendation list page.

-## Next steps

-* [Advisor Reliability recommendations](advisor-reference-reliability-recommendations.md)

-* [Advisor Security recommendations](advisor-security-recommendations.md)

-* [Advisor Performance recommendations](advisor-reference-performance-recommendations.md)

-* [Advisor Cost recommendations](advisor-reference-cost-recommendations.md)

-* [Advisor Operational Excellence recommendations](advisor-reference-operational-excellence-recommendations.md)

-description: A description of what's new and changed in Azure Advisor

-Learn what's new in the service. These items might be release notes, videos, blog posts, and other types of information. Bookmark this page to stay up to date with the service.

-### Azure Advisor will no longer display aggregated potential yearly savings beginning 30 September 2024

-In the Azure portal, Azure Advisor currently shows potential aggregated cost savings under the label "Potential yearly savings based on retail pricing" on pages where cost recommendations are displayed (as shown in the image). This aggregated savings estimate will be removed from the Azure portal on 30 September 2024. However, you can still evaluate potential yearly savings tailored to your specific needs by following the steps in [Calculate cost savings](/azure/advisor/advisor-how-to-calculate-total-cost-savings). All individual recommendations and their associated potential savings will remain available.

-If you want to continue calculating aggregated potential yearly savings, follow [these steps](/azure/advisor/advisor-how-to-calculate-total-cost-savings). Note that individual recommendations might show savings that overlap with the savings shown in other recommendations, although you might not be able to benefit from them concurrently. For example, you can benefit from savings plans or from reservations for virtual machines, but not typically from both on the same virtual machines.

-### Public Preview: Resiliency Review on Azure Advisor

-Recommendations from WAF Reliability reviews in Advisor help you focus on the most important recommendations to ensure your workloads remain resilient. As part of the review, personalized and prioritized recommendations from Microsoft Cloud Solution Architects will be presented to you and your team. You can triage recommendations (accept or reject), manage their lifecycle on Advisor, and work with your Microsoft account team to track resolution. You can reach out to your account team to request Well Architected Reliability Assessment to successfully optimize workload resiliency and reliability by implementing curated recommendations and track its lifecycle on Advisor.

-To learn more, visit [Azure Advisor Resiliency Reviews](/azure/advisor/advisor-resiliency-reviews).

-### Well-Architected Framework (WAF) assessments & recommendations

-The Well-Architected Framework (WAF) assessment provides a curated view of a workloadΓÇÖs architecture. Now you can take the WAF assessment and manage recommendations on Azure Advisor to improve resiliency, security, cost, operational excellence, and performance efficiency. As a part of this release, we're announcing two key WAF assessments - [Mission Critical | Well-Architected Review](/assessments/23513bdb-e8a2-4f0b-8b6b-191ee1f52d34/) and [Azure Well-Architected Review](/assessments/azure-architecture-review/).

-To get started, visit [Use Azure WAF assessments](/azure/advisor/advisor-assessments).

-### ZRS recommendations for Azure Disks

-Azure Advisor now has Zone Redundant Storage (ZRS) recommendations for Azure Managed Disks. Disks with ZRS provide synchronous replication of data across three availability zones in a region, enabling disks to tolerate zonal failures without causing disruptions to your application. By adopting this recommendation, you can now design your solutions to utilize ZRS disks. Access these recommendations through the Advisor portal and APIs.

-To learn more, visit [Use Azure Disks with Zone Redundant Storage for higher resiliency and availability](/azure/advisor/advisor-reference-reliability-recommendations#use-azure-disks-with-zone-redundant-storage-for-higher-resiliency-and-availability).

-### New version of Service Retirement workbook

-Azure Advisor now has a new version of the Service Retirement workbook that includes three major changes:

-* 10 new services are onboarded to the workbook. The Retirement workbook now covers 40 services.

-* Seven services that completed their retirement lifecycle are off boarded.

-| Service | Retiring Feature |

-| Azure Monitor | Classic alerts for Azure Gov cloud and Azure China 21Vianet |

-| Azure Stack Edge | IoT Edge on K8s |

-| Application Insights | Trouble Shooting Guides Retirement |

-| Application Insights | Single URL Ping Test |

-| Service | Retiring Feature |

-| Virtual Machines | Classic IaaS |

-| Virtual Machines | Azure Dedicated Host SKUs (Dsv3-Type1, Esv3-Type1, Dsv3-Type2, Esv3-Type2) |

-UX improvements:

-* Resource details grid: Now, the resource details are readily available by default, whereas previously, they were only visible after selecting a service.

-* Resource link: The **Resource** link now opens in a context pane, previously it opened in the same tab.

-To learn more, visit [Prepare migration of your workloads impacted by service retirement](/azure/advisor/advisor-how-to-plan-migration-workloads-service-retirement).

-Azure Advisor now provides Service Health Alert recommendation for subscriptions, which do not have service health alerts configured. The action link will redirect you to the Service Health page where you can create and customize alerts based on the class of service health notification, affected subscriptions, services, and regions.

-Azure Service Health alerts keep you informed about issues and advisories in four areas (Service issues, Planned maintenance, Security and Health advisories) and can be crucial for incident preparedness.

-To learn more, visit [Service Health portal classic experience overview](/azure/service-health/service-health-overview).

-### Improved VM resiliency with Availability Zone recommendations

-Azure Advisor now provides availability zone recommendations. By adopting these recommendations, you can design your solutions to utilize zonal virtual machines (VMs), ensuring the isolation of your VMs from potential failures in other zones. With zonal deployment, you can expect enhanced resiliency in your workload by avoiding downtime and business interruptions.

-To learn more, visit [Use Availability zones for better resiliency and availability](/azure/advisor/advisor-reference-reliability-recommendations#use-availability-zones-for-better-resiliency-and-availability).

-### Introducing workload based recommendations management

-Azure Advisor now offers the capability of grouping and/or filtering recommendations by workload. The feature is available to selected customers based on their support contract.

-If you're interested in workload based recommendations, reach out to your account team for more information.

-The Azure Cost Optimization workbook serves as a centralized hub for some of the most used tools that can help you drive utilization and efficiency goals. It offers a range of recommendations, including Azure Advisor cost recommendations, identification of idle resources, and management of improperly deallocated Virtual Machines. Additionally, it provides insights into leveraging Azure Hybrid benefit options for Windows, Linux, and SQL databases.

-To learn more, visit [Understand and optimize your Azure costs using the Cost Optimization workbook](/azure/advisor/advisor-cost-optimization-workbook).

-Azure Advisor now offers new recommendation reminders to help you proactively manage and improve the resilience and health of your workloads before an important event. Customers in [Azure Event Management (AEM) program](https://www.microsoft.com/unifiedsupport/enhanced-solutions) are now reminded about outstanding recommendations for their subscriptions and resources that are critical for the event.

-Azure Advisor now has a Reliability workbook template. The new workbook helps you identify areas of improvement by checking configuration of selected Azure resources using the [resiliency checklist](/azure/architecture/checklist/resiliency-per-service) and documented best practices. You can use filters, subscription, resource group, and tags, to focus on resources that you care about most. Use the workbook recommendations to:

-To learn more, visit [Optimize your resources for reliability](https://aka.ms/advisor_improve_reliability).

-To assess the reliability of your workload using the tenets found in theΓÇ»[Microsoft Azure Well-Architected Framework](/azure/architecture/framework/), reference theΓÇ»[Microsoft Azure Well-Architected Review](/assessments/?id=azure-architecture-review&mode=pre-assessment).

-Azure Advisor data is now available in the Azure Resource Graph (ARG) in Azure China and US Government clouds. The ARG is useful for customers who can now get recommendations for all their subscriptions at once and build custom views of Advisor recommendation data. For example:

-* View impacted resource counts by recommendation category.

-To learn more, visit [Query for Advisor data in Resource Graph Explorer (Azure Resource Graph)](https://aka.ms/advisorarg).

-### Service retirement workbook

-Azure Advisor now provides a service retirement workbook. It's important to be aware of the upcoming Azure service and feature retirements to understand their impact on your workloads and plan migration. The [Service Retirement workbook](https://portal.azure.com/#view/Microsoft_Azure_Expert/AdvisorMenuBlade/~/workbooks) provides a single centralized resource level view of service retirements and helps you assess impact, evaluate options, and plan migration.

-The workbook includes 35 services and features planned for retirement. You can view planned retirement dates, list and map of impacted resources and get information to make the necessary actions.

-To learn more, visit [Prepare migration of your workloads impacted by service retirements](advisor-how-to-plan-migration-workloads-service-retirement.md).

-Azure Advisor now provides the option to postpone or dismiss a recommendation for multiple resources at once. Once you open a recommendations details page with a list of recommendations and associated resources, select the relevant resources and choose **Postpone** or **Dismiss** in the command bar at the top of the page.

-To learn more, visit [Dismissing and postponing recommendations](/azure/advisor/view-recommendations#dismissing-and-postponing-recommendations).

-### VM/VMSS right-sizing recommendations with custom lookback period

-You can now improve the relevance of recommendations to make them more actionable, resulting in additional cost savings.

-The right sizing recommendations help optimize costs by identifying idle or underutilized virtual machines based on their CPU, memory, and network activity over the default lookback period of seven days. Now, with this latest update, you can adjust the default look back period to get recommendations based on 14, 21, 30, 60, or even 90 days of use. The configuration can be applied at the subscription level. This is especially useful when the workloads have biweekly or monthly peaks (such as with payroll applications).

-To learn more, visit [Optimize Virtual Machine (VM) or Virtual Machine Scale Set (VMSS) spend by resizing or shutting down underutilized instances](advisor-cost-recommendations.md#optimize-virtual-machine-vm-or-virtual-machine-scale-set-vmss-spend-by-resizing-or-shutting-down-underutilized-instances).

-Azure Advisor now provides additional filtering capabilities. You can filter recommendations by resource group, resource type, impact and workload.

-### New cost recommendations for Virtual Machine Scale Sets

-Azure Advisor now offers cost optimization recommendations for Virtual Machine Scale Sets (VMSS). These include shutdown recommendations for resources that we detect aren't used at all, and SKU change or instance count reduction recommendations for resources that we detect are under-utilized. For example, for resources where we think customers are paying for more than what they might need based on the workloads running on the resources.

-To learn more, visit [

-Optimize virtual machine (VM) or virtual machine scale set (VMSS) spend by resizing or shutting down underutilized instances](/azure/advisor/advisor-cost-recommendations#optimize-virtual-machine-vm-or-virtual-machine-scale-set-vmss-spend-by-resizing-or-shutting-down-underutilized-instances).

-Azure Advisor provides a personalized list of best practices for optimizing your Azure Database for MySQL - Flexible Server instance. The feature analyzes your resource configuration and usage, and then recommends solutions to help you improve the cost effectiveness, performance, reliability, and security of your resources. With Azure Advisor, you can find recommendations based on transport layer security (TLS) configuration, CPU, and storage usage to prevent resource exhaustion.

-To learn more, visit [Azure Advisor for MySQL](/azure/mysql/single-server/concepts-azure-advisor-recommendations).

-It's easier now to get an overview of optimization opportunities available to your organization ΓÇô no need to spend time and effort to apply filters and process subscription in batches.

-To learn more, visit [Get started with Azure Advisor](advisor-get-started.md).

-You can now get Advisor recommendations scoped to a business unit, workload, or team. Filter recommendations and calculate scores using tags you have already assigned to Azure resources, resource groups and subscriptions. Apply tag filters to:

-* Identify cost saving opportunities by business units

-* Compare scores for workloads to optimize critical ones first

-To learn more, visit [How to filter Advisor recommendations using tags](advisor-tag-filtering.md).

-[**Shutdown/Resize your virtual machines**](advisor-cost-recommendations.md#optimize-virtual-machine-vm-or-virtual-machine-scale-set-vmss-spend-by-resizing-or-shutting-down-underutilized-instances) recommendation was enhanced to increase the quality, robustness, and applicability.

-Improvements include:

-1. Cross SKU family series resize recommendations are now available.

-1. Cross version resize recommendations are now available. In general, newer versions of SKU families are more optimized, provide more features, and have better performance/cost ratios than older versions.

-1. For better actionability, we updated recommendation criteria to include other SKU characteristics such as accelerated networking support, premium storage support, availability in a region, inclusion in an availability set, and more.

-Read the [How-to guide](advisor-cost-recommendations.md#optimize-virtual-machine-vm-or-virtual-machine-scale-set-vmss-spend-by-resizing-or-shutting-down-underutilized-instances) to learn more.

-description: Advisor permissions and how they may block your ability to configure subscriptions or postpone or dismiss recommendations.

-The following table defines the roles and the access they have within Advisor:

-| **Role** | **View recommendations** | **Edit rules** | **Edit subscription configuration** | **Edit resource group configuration**| **Dismiss and postpone recommendations**|

-Lack of proper permissions can block your ability to perform actions in Advisor. Following are some common problems.

-When you attempt to configure subscriptions or resource groups in Advisor, you may see that the option to include or exclude is disabled. This status indicates that you do not have a sufficient level of permission for that resource group or subscription. To resolve this issue, learn how to [grant a user access](../role-based-access-control/quickstart-assign-role-user-portal.md).

-If you receive an error when trying to postpone or dismiss a recommendation, you might not have sufficient permissions. Dismissing a recommendation means you can't see it again unless manually reactivated, so you might potentially overlook important advice for optimizing Azure deployments. Therefore, itΓÇÖs crucial that only users with sufficient permissions can dismiss recommendations. Make sure that you have at least contributor access to the impacted resource of the recommendation you're postponing or dismissing. To resolve this issue, learn how to [grant a user access](../role-based-access-control/quickstart-assign-role-user-portal.md).

-## Next steps

-This article gave an overview of how Advisor uses Azure RBAC to control user permissions and how to resolve common issues. To learn more about Advisor, see:

-|Language support | Multiple [language support](concept-custom-template.md#supported-languages-and-locales) | English, with preview support for Spanish, French, German, Italian, and Dutch [language support](concept-custom-neural.md#supported-languages-and-locales) |

-_See_ [**Virtual Network Support**](v3-0-reference.md#virtual-network-support) for Translator service selected network and private endpoint configuration and support.

-|Accept-Language|**Optional request header**.<br><br>The language to use for user interface strings. Some of the fields in the response are names of languages or names of regions. Use this parameter to define the language in which these names are returned. The language is specified by providing a well-formed BCP 47 language tag. For instance, use the value `fr` to request names in French or use the value `zh-Hant` to request names in Chinese Traditional.<br/>Names are provided in the English language when a target language isn't specified or when localization isn't available.|

-A client uses the `scope` query parameter to define which groups of languages it's interested in.

- The value of the `translation` property is a dictionary of (key, value) pairs. Each key is a BCP 47 language tag. A key identifies a language for which text can be translated to or translated from. The value associated with the key is a JSON object with properties that describe the language:

- The value of the `transliteration` property is a dictionary of (key, value) pairs. Each key is a BCP 47 language tag. A key identifies a language for which text can be converted from one script to another script. The value associated with the key is a JSON object with properties that describe the language and its supported scripts:

- The value of the `dictionary` property is a dictionary of (key, value) pairs. Each key is a BCP 47 language tag. The key identifies a language for which alternative translations and back-translations are available. The value is a JSON object that describes the source language and the target languages with available translations:

-The list of supported languages doesn't change frequently. To save network bandwidth and improve responsiveness, a client application should consider caching language resources and the corresponding entity tag (`ETag`). Then, the client application can periodically (for example, once every 24 hours) query the service to fetch the latest set of supported languages. Passing the current `ETag` value in an `If-None-Match` header field allows the service to optimize the response. If the resource hasn't been modified, the service returns status code 304 and an empty response body.

-|304|The resource hasn't been modified since the version specified by request headers `If-None-Match`.|

-|429|The server rejected the request because the client has exceeded request limits.|

-* [In-place OS SKU migration (preview)](../azure-linux/tutorial-azure-linux-migration.md#in-place-os-sku-migration-preview).

-* Azure CLI version 2.32.0 or later installed and configured. Run `az --version` to find the version. For more information about installing or upgrading the Azure CLI, see [Install Azure CLI][install-azure-cli].

-> The FIPS-enabled Linux image is a different image than the default Linux image used for Linux-based node pools. To enable FIPS on a node pool, you must create a new Linux-based node pool. You can't enable FIPS on existing node pools.

-When requesting FIPS enabled Ubuntu, if the default Ubuntu version does not support FIPS, AKS will default to the most recent FIPS-supported version of Ubuntu. For example, Ubuntu 22.04 is default for Linux node pools. Since 22.04 does not currently support FIPS, AKS will default to Ubuntu 20.04 for Linux FIPS-enabled nodepools.

-* In-place OS SKU migration (preview).

-## In-place OS SKU migration (preview)

-* The OS SKU migration feature isn't available through Terraform, PowerShell, or the Azure portal.

-* AgentPool `count` field must not change during the migration.

-* [Install the `aks-preview` extension](#install-the-aks-preview-extension).

-* [Register the `OSSKUMigrationPreview` feature flag on your subscription](#register-the-osskumigrationpreview-feature-flag).

-* You need Azure CLI version 0.5.172 or higher. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](/cli/azure/install-azure-cli).

-#### Install the `aks-preview` extension

-1. Install the `aks-preview` extension using the `az extension add` command.

- ```azurecli-interactive

- az extension add --name aks-preview

- ```

-2. Update the extension to make sure you have the latest version using the `az extension update` command.

- ```azurecli-interactive

- az extension update --name aks-preview

- ```

-#### Register the `OSSKUMigrationPreview` feature flag

-1. Register the `OSSKUMigrationPreview` feature flag on your subscription using the `az feature register` command.

- ```azurecli-interactive

- az feature register --namespace Microsoft.ContainerService --name OSSKUMigrationPreview

- ```

-2. Check the registration status using the `az feature list` command.

- ```azurecli-interactive

- az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/OSSKUMigrationPreview')].{Name:name,State:properties.state}"

- ```

- Your output should look similar to the following example output:

- ```output

- Name State

- - -

- Microsoft.ContainerService/OSSKUMigrationPreview Registered

- ```

-3. Refresh the registration of the `OSSKUMigrationPreview` feature flag using the `az provider register` command.

- ```azurecli-interactive

- az provider register --namespace Microsoft.ContainerService

- ```

-3. Migrate the OS SKU of your system node pool to Azure Linux using the `az deployment group create` command and the ManagedClusters API in the [1mcupdate.json example ARM template](#1mcupdatejson).

-4. Migrate the OS SKU of your system node pool back to Ubuntu using the `az deployment group create` command and the AgentPools API in the [2apupdate.json example ARM template](#2apupdatejson).

-1. Update your existing templates to set `OSSKU=AzureLinux`. In ARM templates, you use `"OSSKU: "AzureLinux"` in the `agentPoolProfile` section. In Bicep, you use `osSku: "AzureLinux"` in the `agentPoolProfile` section. Make sure that your `apiVersion` is set to `2023-07-01` or later.

-2. Redeploy your ARM template for the cluster to apply the new `OSSKU` setting. During this deploy, your cluster behaves as if it's taking a node image upgrade. Your cluster surges capacity, and then reboots your existing nodes one by one into the latest AKS image from your new OS SKU.

-* In-place OS SKU migration (preview).

-# Migrate from MMA custom text log to AMA DCR based custom text logs

-This article describes the steps to migrate a [MMA Custom text log](data-sources-custom-logs.md) table so you can use it as a destination for a new [AMA custom text logs](data-collection-log-text.md) DCR. When you follow the steps, you won't lose any data. If you're creating a new AMA custom text log table, then this article doesn't pertain to you.

-> Note: Once logs are migrated, MMA will not be able to write to the destination table. This is an issue for the migration of production system that we are actively working.

->

-## Background

-MMA custom text logs must be configured to support new features in order for AMA custom text log DCRs to write to it. The following actions are taken:

-## Migration procedure

-| June 2024 |**Windows**<ul><li>Fix encoding issues with Resource ID field.</li><li>AMA: Support new ingestion endpoint for GovSG environment.</li><li>MA: Fixes a CPU uptick issue for certain Bond serialization scenarios.</li><li>Upgrade AzureSecurityPack version to 4.33.0.1.</li><li>Upgrade Metrics Extension version to 2.2024.517.533.</li><li>Upgrade Health Extension version to 2024.528.1.</li></ul>**Linux**<ul><li>Coming Soon</li></ul>| 1.28.0 | |

-Before you can collect log data from a JSON file, you must create a custom table in your Log Analytics workspace to receive the data. The table schema must match the columns in the incoming stream, or you must add a transformation to ensure that the output schema matches the table. For example, you can use the following PowerShell script to create a custom table with multiple columns.

-The Azure portal provides a data collection rule wizard for collecting data from virtual machines and for collecting Prometheus metrics from containers.

- "query": "union (AzureActivity | where timestamp > ago(1d), (workspaces('AIFabrikamDemo').AzureActivity | where timestamp> ago(1d))"

- Cosmos DB | [CDBDataPlaneRequests](/azure/azure-monitor/reference/tables/cdbdataplanerequests)<br>[CDBPartitionKeyStatistics](/azure/azure-monitor/reference/tables/cdbpartitionkeystatistics)<br>[CDBPartitionKeyRUConsumption](/azure/azure-monitor/reference/tables/cdbpartitionkeyruconsumption)<br>[CDBQueryRuntimeStatistics](/azure/azure-monitor/reference/tables/cdbqueryruntimestatistics)<br>[CDBMongoRequests](/azure/azure-monitor/reference/tables/cdbmongorequests)<br>[CDBCassandraRequests](/azure/azure-monitor/reference/tables/cdbcassandrarequests)<br>[CDBGremlinRequests](/azure/azure-monitor/reference/tables/cdbgremlinrequests)<br>[CDBControlPlaneRequests](/azure/azure-monitor/reference/tables/cdbcontrolplanerequests) |

-> We recommend customers to [create a credential set](container-registry-artifact-cache.md#create-new-credentials) when sourcing content from Docker hub.

-| Docker Hub | Supports both authenticated and unauthenticated pulls. | Azure CLI |

-| Docker Hub | Supports authenticated pulls only. | Azure portal |

-> We recommend customers to [create a credential set](container-registry-artifact-cache.md#create-new-credentials) when sourcing content from Docker hub.

-| Docker Hub | Supports both authenticated and unauthenticated pulls. | Azure CLI |

-| Docker Hub | Supports authenticated pulls only. | Azure portal |

-description: Learn how data is managed and safeguarded in Microsoft Defender for Cloud.

-## Next steps

-In this document, you learned how data is managed and safeguarded in Microsoft Defender for Cloud.

-To learn more about Microsoft Defender for Cloud, see [What is Microsoft Defender for Cloud?](defender-for-cloud-introduction.md).

-The [500-MB benefit](faq-defender-for-servers.yml#is-the-500-mb-of-free-data-ingestion-allowance-applied-per-workspace-or-per-machine-) for data ingestion over the defined tables remains supported via the AMA agent for machines under subscriptions covered by Defender for Servers Plan 2. Every machine is eligible for the benefit only once, even if both Log Analytics agent and Azure Monitor agent are installed on it. For the data allowance to be granted, Defender for Servers Plan 2 needs to be enabled on the Log Analytics workspace AMA is connected to and on the machine's subscription.

-Learn more about how to [deploy AMA](../azure-monitor/vm/monitor-virtual-machine-agent.md#agent-deployment-options).

-Endpoint discovery and recommendations are currently provided by the Defender for Cloud Foundational CSPM and the Defender for Servers plans using the Log Analytics agent in GA, or in preview via the AMA. This experience will be replaced by security recommendations that are gathered using agentless machine scanning.ΓÇ»

-|Date | Category | Update|

-|--|--|--|

-|July 15|Preview|[Binary Drift Public Preview in Defender for Containers](#binary-drift-public-preview-now-available-in-defender-for-containers)|

-|July 14|GA|[Automated remediation scripts for AWS and GCP are now GA](#automated-remediation-scripts-for-aws-and-gcp-are-now-ga)|

-| July 10 | GA | [Compliance standards are now GA](#compliance-standards-are-now-ga) |

-| July 9 | Upcoming update | [Inventory experience improvement](#inventory-experience-improvement) |

-|July 8 | Upcoming update | [Container mapping tool to run by default in GitHub](#container-mapping-tool-to-run-by-default-in-github) |

-In March, we released automated remediation scripts for AWS & GCP to Public Preview, that allows you to remediate recommendations for AWS & GCP at scale programmatically.

-1. In your GitHub organization, navigate to the Microsoft Security DevOps application within **Settings > GitHub Apps** and accept the permissions request.

-|Date | Category | Update |

-|--|--|--|

-| June 27 | GA | [Checkov IaC Scanning in Defender for Cloud](#ga-checkov-iac-scanning-in-defender-for-cloud). |

-| June 24 | Update | [Change in pricing for multicloud Defender for Containers](#update-change-in-pricing-for-defender-for-containers-in-multicloud) |

-| June 20 | Upcoming deprecation | [Reminder of deprecation for adaptive recommendations at Microsoft Monitoring Agent (MMA) deprecation](#deprecation-reminder-of-deprecation-for-adaptive-recommendations).<br/><br/> Estimated deprecation August 2024. |

-| June 10 | Preview | [Copilot for Security in Defender for Cloud](#preview-copilot-for-security-in-defender-for-cloud) |

-| June 10 | Upcoming update |[SQL vulnerability assessment automatic enablement using express configuration on unconfigured servers](#update-sql-vulnerability-assessment-automatic-enablement).<br/><br/> Estimated update: July 10, 2024. |

-| June 3 | Upcoming update |[Changes in identity recommendations behavior](#update-changes-in-identity-recommendations-behavior)<br/><br/> Estimated update: July 10 2024. |

- that sends HTTP requests to Azure Resource Manager-based REST APIs. Instead, you can use the "Try

- It" feature in REST documentation or tooling like PowerShell's

- [Invoke-RestMethod](/powershell/module/microsoft.powershell.utility/invoke-restmethod) or

- [Postman](https://www.postman.com).

-## Generate and transfer your key to the Managed HSM

-To generate and transfer your key to a Managed HSM:

- - [Step 1: Generate a KEK](#step-1-generate-a-kek)

- - [Step 2: Download the KEK public key](#step-2-download-the-kek-public-key)

- - [Step 3: Generate and prepare your key for transfer](#step-3-generate-and-prepare-your-key-for-transfer)

- - [Step 4: Transfer your key to Managed HSM](#step-4-transfer-your-key-to-managed-hsm)

-| `endpoint_input_uri` | The endpoint's input data. Multiple data input types are supported. Ensure that the manage identity you are using for executing the job has access to the underlying location. Alternative, if using Data Stores, ensure the credentials are indicated there. | `azureml://datastores/.../paths/.../data/` |

-| `endpoint_input_uri` | The endpoint's input data. Multiple data input types are supported. Ensure that the manage identity you are using for executing the job has access to the underlying location. Alternative, if using Data Stores, ensure the credentials are indicated there. | `azureml://datastores/.../paths/.../data/` |

-> [!IMPORTANT]

-> Some Single Server instances may require mandatory inputs to perform a successful in-place automigration. Review the migration details in the Migration blade on Azure portal to provide those inputs. Failure to provide mandatory inputs 7 days before the scheduled migration will lead to re-scheduling of the migration to a later date.

-> [!NOTE]

-> The migration schedule will be locked 7 days prior to the scheduled migration window after which you'll be unable to reschedule.

- - Select the **confirmation checkbox** after performing the listed pre-requisite checks for migrating private endpoints.

- - Click on the **Authenticate** button to authenticate ARM connection required to migrate the private endpoints from source to target server.

- - Click on **Save** to save all the above steps.

- > If the mandatory inputs for migration are not provided atleast 7 days before the scheduled migration, the migration will be rescheduled to a later date.

-| Suppress specific alert types | Disable specific alert types with the Microsoft Defender for Cloud platform. For more information, visit [Suppress alerts from Microsoft Defender for Cloud guide](../../defender-for-cloud/alerts-suppression-rules.md). <br /><br /> Single Server users can use the API property: <br /> `properties.disabledAlerts` |

-| Email notifications | Define email notification for Microsoft Defender for Cloud Alerts for all resources in a subscription. For more information, visit [Configure email notifications for security alerts](../../defender-for-cloud/configure-email-notifications.md). <br /><br /> Single Server users can use the API properties: <br /> `properties.emailAccountAdmins`, <br /> `properties.emailAddresses` |

-| Export alerts for further processing and/or archiving | Alerts are stored in the Microsoft Defender for Cloud platform and exposed through the Azure Resource Graph. <br /> You can export alerts to a different store and manage retention separately. For more information, visit [Set up continuous export in the Azure portal - Microsoft Defender for Cloud](../../defender-for-cloud/continuous-export.md). <br /><br /> Single Server users can use the API properties: <br /> `properties.retentionDays`, <br /> `properties.storageAccountAccessKey`, <br /> `properties.storageEndpoint` |

-**A.** You can review the migration schedule by navigating to the Migration blade of your Single Server instance. If you wish to defer the migration, you can defer by a month at the most by navigating to the Migration blade of your single server instance on the Azure portal and rescheduling the migration by selecting another migration window within a month. The migration details will be locked seven days prior to the scheduled migration window after which you're unable to reschedule. This in-place migration can be deferred monthly until 16 September 2024.

-**A.** Your existing Azure Database for MySQL single server workloads continues to function as before and will be officially supported until the sunset date. However, no new updates are released for Single Server and we strongly advise you to start migrating to Azure Database for MySQL Flexible Server at the earliest. Post the sunset date, your Single Server instance, along with its data files, will be [force-migrated](./whats-happening-to-mysql-single-server.md#forced-migration-post-sunset-date) to an appropriate Flexible Server instance in a phased manner.

-In your application code that makes direct calls to the REST APIs, modify the `api-version` parameter on the requst header. For more information about structuring a REST call, see [Quickstart: using REST](search-get-started-rest.md#set-up-visual-studio-code).

-This quickstart helps you get started with [integrated vectorization (preview)](vector-search-integrated-vectorization.md) by using the **Import and vectorize data** wizard in the Azure portal. This wizard chunks your content and calls a user-specified embedding model to vectorize content during indexing and for queries.

-+ An embedding model on a supported platform. [Deployment instructions](#set-up-embedding-models) are provided in this article.

- | [Azure AI services multiservice account](/azure/ai-services/multi-service-resource) | [Azure AI Vision multimodal](/azure/ai-services/computer-vision/how-to/image-retrieval) for image and text vectorization. Azure AI Vision multimodal is available in selected regions: East US, West US, West US2, North Europe, West Europe, France Central, Sweden Central, Switzerland North, Southeast Asia, Korea Central, Australia East, or Japan East. [Check the documentation](/azure/ai-services/computer-vision/how-to/image-retrieval?tabs=csharp) for an updated list. |

-### [Azure Storage](#tab/sample-data-storage)

-1. On **Access control**, assign the [Storage Blob Data Reader](search-howto-managed-identities-data-sources.md#assign-a-role) role on the container to the search service identity. Or, get a connection string to the storage account from the **Access keys** page.

-Integrated vectorization and the **Import and vectorize data** wizard tap into deployed embedding models during indexing to convert text and images into vectors.

-You can use embedding models deployed in Azure OpenAI, in Azure AI Vision for multimodal embeddings, or in the model catalog in Azure AI Studio.

-**Import and vectorize data** supports `text-embedding-ada-002`, `text-embedding-3-large`, and `text-embedding-3-small`. Internally, the wizard uses the [AzureOpenAIEmbedding skill](cognitive-search-skill-azure-openai-embedding.md) to connect to Azure OpenAI.

-Use these instructions to assign permissions or get an API key for search service connection to Azure OpenAI. You should set up permissions or have connection information available before you run the wizard.

-**Import and vectorize data** supports Azure AI Vision image retrieval through multimodal embeddings (version 4.0). Internally, the wizard uses the [multimodal embeddings skill](cognitive-search-skill-vision-vectorize.md) to connect to Azure AI Vision.

-**Import and vectorize data** supports Azure, Cohere, and Facebook embedding models in the Azure AI Studio model catalog, but it doesn't currently support the OpenAI CLIP model. Internally, the wizard uses the [AML skill](cognitive-search-aml-skill.md) to connect to the catalog.

-Use these instructions to assign permissions or get an API key for search service connection to Azure OpenAI. You should set up permissions or have connection information available before you run the wizard.

-1. For the model catalog, you should have an [Azure OpenAI resource](/azure/ai-services/openai/how-to/create-resource), a [hub in Azure AI Studio](/azure/ai-studio/how-to/create-projects), and a [project](/azure/ai-studio/how-to/create-projects). Hubs and projects that have the same name can share connection information and permissions.

-1. In the **Import and vectorize data** wizard, on the **Set up your data connection** page, select **Azure Blob Storage** or **OneLake**.

-1. For OneLake, specify the lakehouse URL, or provide the workspace and lakehouse IDs.

- For Azure Storage, select the account and container that provide the data.

-1. Specify whether you want [deletion detection](search-howto-index-changed-deleted-blobs.md).

-1. On the **Vectorize your text** page, specify whether deployed models are on Azure OpenAI, the Azure AI Studio model catalog, or an existing Azure AI Vision multimodal resource in the same region as Azure AI Search.

-1. Specify the Azure subscription.

- 1. For Azure OpenAI, select the service, model deployment, and authentication type.

- 1. For AI Studio catalog, select the project, model deployment, and authentication type.

- 1. For AI Vision vectorization, select the account.

-+ Use optical character recognition (OCR) to recognize text in images.

-Server-side Encryption models refer to encryption that is performed by the Azure service. In that model, the Resource Provider performs the encrypt and decrypt operations. For example, Azure Storage may receive data in plain text operations and will perform the encryption and decryption internally. The Resource Provider might use encryption keys that are managed by Microsoft or by the customer depending on the provided configuration.

-

-Each of the server-side encryption at rest models implies distinctive characteristics of key management. This includes where and how encryption keys are created, and stored as well as the access models and the key rotation procedures.

-

-For many customers, the essential requirement is to ensure that the data is encrypted whenever it is at rest. Server-side encryption using service-managed Keys enables this model by allowing customers to mark the specific resource (Storage Account, SQL DB, etc.) for encryption and leaving all key management aspects such as key issuance, rotation, and backup to Microsoft. Most Azure services that support encryption at rest typically support this model of offloading the management of the encryption keys to Azure. The Azure resource provider creates the keys, places them in secure storage, and retrieves them when needed. This means that the service has full access to the keys and the service has full control over the credential lifecycle management.

-

-Server-side encryption with Microsoft-managed keys does imply the service has full access to store and manage the keys. While some customers may want to manage the keys because they feel they gain greater security, the cost and risk associated with a custom key storage solution should be considered when evaluating this model. In many cases, an organization may determine that resource constraints or risks of an on-premises solution may be greater than the risk of cloud management of the encryption at rest keys. However, this model might not be sufficient for organizations that have requirements to control the creation or lifecycle of the encryption keys or to have different personnel manage a service's encryption keys than those managing the service (that is, segregation of key management from the overall management model for the service).

-For scenarios where the requirement is to encrypt the data at rest and control the encryption keys customers can use server-side encryption using customer-managed Keys in Key Vault. Some services may store only the root Key Encryption Key in Azure Key Vault and store the encrypted Data Encryption Key in an internal location closer to the data. In that scenario customers can bring their own keys to Key Vault (BYOK ΓÇô Bring Your Own Key), or generate new ones, and use them to encrypt the desired resources. While the Resource Provider performs the encryption and decryption operations, it uses the configured key encryption key as the root key for all encryption operations.

->[!NOTE]

->For more detail on Key Vault authorization see the secure your key vault page in the [Azure Key Vault documentation](../../key-vault/general/security-features.md).

-Some Azure services enable the Host Your Own Key (HYOK) key management model. This management mode is useful in scenarios where there is a need to encrypt the data at rest and manage the keys in a proprietary repository outside of Microsoft's control. In this model, the service must use the key from an external site to decrypt the Data Encryption Key (DEK). Performance and availability guarantees are impacted, and configuration is more complex. Additionally, since the service does have access to the DEK during the encryption and decryption operations the overall security guarantees of this model are similar to when the keys are customer-managed in Azure Key Vault. As a result, this model is not appropriate for most organizations unless they have specific key management requirements. Due to these limitations, most Azure services do not support server-side encryption using customer-managed keys in customer-controlled hardware. One of two keys in [Double Key Encryption](/microsoft-365/compliance/double-key-encryption) follows this model.

-| Product, Feature, or Service | Server-Side Using Service-Managed Key | Server-Side Using Customer-Managed Key | Client-Side Using Client-Managed Key |

-|-|--|--|--|

-| **AI and Machine Learning** | | | |

-| Azure AI Search | Yes | Yes | - |

-| Azure AI services | Yes | Yes, including Managed HSM | - |

-| Azure Machine Learning | Yes | Yes | - |

-| Content Moderator | Yes | Yes, including Managed HSM | - |

-| Face | Yes | Yes, including Managed HSM | - |

-| Language Understanding | Yes | Yes, including Managed HSM | - |

-| Azure OpenAI | Yes | Yes, including Managed HSM | - |

-| Personalizer | Yes | Yes, including Managed HSM | - |

-| QnA Maker | Yes | Yes, including Managed HSM | - |

-| Speech Services | Yes | Yes, including Managed HSM | - |

-| Translator Text | Yes | Yes, including Managed HSM | - |

-| [Power Platform](https://www.microsoft.com/power-platform) | Yes | Yes, including Managed HSM | - |

-| [Dataverse](https://www.microsoft.com/power-platform/dataverse) | Yes | Yes, including Managed HSM | - |

-| [Dynamics 365](https://www.microsoft.com/dynamics-365) | Yes | Yes, including Managed HSM | - |

-| **Analytics** | | | |

-| Azure Stream Analytics | Yes | Yes\*\*, including Managed HSM | - |

-| Event Hubs | Yes | Yes | - |

-| Functions | Yes | Yes | - |

-| Azure Analysis Services | Yes | - | - |

-| Azure Data Catalog | Yes | - | - |

-| Azure HDInsight | Yes | Yes | - |

-| Azure Monitor Application Insights | Yes | Yes | - |

-| Azure Monitor Log Analytics | Yes | Yes, including Managed HSM | - |

-| Azure Data Explorer | Yes | Yes | - |

-| Azure Data Factory | Yes | Yes, including Managed HSM | - |

-| Azure Data Lake Store | Yes | Yes, RSA 2048-bit | - |

-| **Containers** | | | |

-| Azure Kubernetes Service | Yes | Yes, including Managed HSM | - |

-| Container Instances | Yes | Yes | - |

-| Container Registry | Yes | Yes | - |

-| **Compute** | | | |

-| Virtual Machines | Yes | Yes, including Managed HSM | - |

-| Virtual Machine Scale Set | Yes | Yes, including Managed HSM | - |

-| SAP HANA | Yes | Yes | - |

-| App Service | Yes | Yes\*\*, including Managed HSM | - |

-| Automation | Yes | Yes | - |

-| Azure Functions | Yes | Yes\*\*, including Managed HSM | - |

-| Azure portal | Yes | Yes\*\*, including Managed HSM | - |

-| Azure VMware Solution | Yes | Yes, including Managed HSM | - |

-| Logic Apps | Yes | Yes | - |

-| Azure-managed applications | Yes | Yes\*\*, including Managed HSM | - |

-| Service Bus | Yes | Yes | - |

-| Site Recovery | Yes | Yes | - |

-| **Databases** | | | |

-| SQL Server on Virtual Machines | Yes | Yes | Yes |

-| Azure SQL Database | Yes | Yes, RSA 3072-bit, including Managed HSM | Yes |

-| Azure SQL Managed Instance | Yes | Yes, RSA 3072-bit, including Managed HSM | Yes |

-| Azure SQL Database for MariaDB | Yes | - | - |

-| Azure SQL Database for MySQL | Yes | Yes | - |

-| Azure SQL Database for PostgreSQL | Yes | Yes, including Managed HSM | - |

-| Azure Synapse Analytics (dedicated SQL pool (formerly SQL DW) only) | Yes | Yes, RSA 3072-bit, including Managed HSM | - |

-| SQL Server Stretch Database | Yes | Yes, RSA 3072-bit | Yes |

-| Table Storage | Yes | Yes | Yes |

-| Azure Cosmos DB | Yes ([learn more](../../cosmos-db/database-security.md?tabs=sql-api)) | Yes, including Managed HSM ([learn more](../../cosmos-db/how-to-setup-cmk.md) and [learn more](../../cosmos-db/how-to-setup-customer-managed-keys-mhsm.md)) | - |

-| Azure Databricks | Yes | Yes, including Managed HSM | - |

-| Azure Database Migration Service | Yes | N/A\* | - |

-| **Identity** | | | |

-| Microsoft Entra ID | Yes | - | - |

-| Microsoft Entra Domain Services | Yes | Yes | - |

-| **Integration** | | | |

-| Service Bus | Yes | Yes | - |

-| Event Grid | Yes | - | - |

-| API Management | Yes | - | - |

-| **IoT Services** | | | |

-| IoT Hub | Yes | Yes | Yes |

-| IoT Hub Device Provisioning | Yes | Yes | - |

-| **Management and Governance** | | | |

-| Azure Managed Grafana | Yes | - | N/A |

-| Azure Site Recovery | Yes | - | - |

-| Azure Migrate | Yes | Yes | - |

-| **Media** | | | |

-| Media Services | Yes | Yes | Yes |

-| **Security** | | | |

-| Microsoft Defender for IoT | Yes | Yes | - |

-| Microsoft Sentinel | Yes | Yes, including Managed HSM | - |

-| **Storage** | | | |

-| Blob Storage | Yes | Yes, including Managed HSM | Yes |

-| Premium Blob Storage | Yes | Yes, including Managed HSM | Yes |

-| Disk Storage | Yes | Yes, including Managed HSM | - |

-| Ultra Disk Storage | Yes | Yes, including Managed HSM | - |

-| Managed Disk Storage | Yes | Yes, including Managed HSM | - |

-| File Storage | Yes | Yes, including Managed HSM | - |

-| File Premium Storage | Yes | Yes, including Managed HSM | - |

-| File Sync | Yes | Yes, including Managed HSM | - |

-| Queue Storage | Yes | Yes, including Managed HSM | Yes |

-| Data Lake Storage Gen2 | Yes | Yes, including Managed HSM | Yes |

-| Avere vFXT | Yes | - | - |

-| Azure Cache for Redis | Yes | Yes\*\*\*, including Managed HSM | - |

-| Azure NetApp Files | Yes | Yes | Yes |

-| Archive Storage | Yes | Yes | - |

-| StorSimple | Yes | Yes | Yes |

-| Azure Backup | Yes | Yes, including Managed HSM | Yes |

-| Data Box | Yes | - | Yes |

-| Data Box Edge | Yes | Yes | - |

-| **Other** | | | |

-| Azure Data Manager for Energy | Yes | Yes | Yes |

-## Next steps