Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sfi-ropc-remediation

Author: asudbring

articles/automation/change-tracking/overview-monitoring-agent.md

@@ -3,7 +3,7 @@ title: Azure Automation Change Tracking and Inventory overview using Azure Monit
 description: This article describes the Change Tracking and Inventory feature using Azure monitoring agent, which helps you identify software and Microsoft service changes in your environment.
 services: automation
 ms.subservice: change-inventory-management
-ms.date: 12/09/2024
+ms.date: 02/26/2025
 ms.topic: overview
 ms.service: azure-automation
 ---
@@ -39,10 +39,9 @@ Azure Change Tracking & Inventory service enhances the auditing and governance f
 
 |**Component**| **Applies to**|
 |---| ---|
-| Operating systems| Windows </br> Linux | 
-| Resource types | Azure VMs </br> Azure Arc-enabled VMs </br> Virtual machines scale set|
-| Data types     | Windows registry </br> Windows services </br> Linux Daemons |
-| Files | Windows </br> Linux |
+|Operating systems| Windows </br> Linux | 
+|Resource types | Azure VMs </br> Azure Arc-enabled VMs </br> Virtual machines scale set|
+|Data types | Windows registry </br> Windows services </br> Linux Daemons </br> Files </br> Software
 
 ## Key benefits
 

articles/azure-netapp-files/large-volumes-requirements-considerations.md

@@ -6,7 +6,7 @@ author: b-ahibbard
 ms.service: azure-netapp-files
 ms.custom: references_regions
 ms.topic: conceptual
-ms.date: 02/18/2025
+ms.date: 02/25/2025
 ms.author: anfdocs
 ---
 # Requirements and considerations for large volumes
@@ -79,23 +79,38 @@ Whereas regular volumes use 32-bit file IDs, large volumes employ 64-bit file ID
 
 Support for Azure NetApp Files large volumes is available in the following regions:
 
+* Australia Central
+* Australia Central 2
 * Australia East
 * Australia Southeast
 * Brazil South
+* Brazil Southeast
 * Canada Central
+* Canada East
 * Central India
 * Central US
+* East Asia
 * East US
 * East US 2
 * France Central
+* Germany North 
 * Germany West Central
+* Italy North
 * Japan East
+* Japan West
+* Korea Central
+* Korea South
+* North Central US
 * North Europe
+* Norway East
+* Norway West
 * Qatar Central
 * South Africa North 
 * South Central US
 * Southeast Asia
+* Sweden Central
 * Switzerland North
+* Switzerland West
 * UAE North
 * UK West
 * UK South

articles/azure-vmware/enable-hcx-access-over-internet.md

@@ -2,7 +2,7 @@
 title: Enable HCX access over the internet
 description: This article describes how to access HCX over a public IP address using Azure VMware solution.
 ms.topic: how-to
-ms.date: 01/08/2025
+ms.date: 02/26/2025
 ms.custom: engagement-fy23
 ---
 # Enable HCX access over the internet
@@ -135,4 +135,4 @@ After the network is extended to destination site, VMs can be migrated over Laye
 ## Next steps
 [Enable Public IP to the NSX Edge for Azure VMware Solution](./enable-public-ip-nsx-edge.md)
 
-For detailed information on HCX network underlay minimum requirements, see [Network Underlay Minimum Requirements](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-9/vmware-hcx-user-guide-4-9/preparing-for-hcx-installations/network-underlay-minimum-requirements.html).
+For detailed information on HCX network underlay minimum requirements, see [Network Underlay Minimum Requirements](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/preparing-for-hcx-installations/network-underlay-minimum-requirements.html).

articles/azure-vmware/move-azure-vmware-solution-across-regions.md

@@ -42,7 +42,7 @@ In this article, walk through the steps to:
 
 ## Prerequisites
 
-- [VMware HCX appliance is upgraded to the latest patch](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-9/vmware-hcx-user-guide-4-9/updating-vmware-hcx.html) to avoid migration issues if any.
+- [VMware HCX appliance is upgraded to the latest patch](https://techdocs.broadcom.com/us/en/vmware-cis/hcx/vmware-hcx/4-10/vmware-hcx-user-guide-4-10/updating-vmware-hcx.html) to avoid migration issues if any.
 
 - Source's local content library is a [published content library](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-virtual-machine-administration-guide-8-0/using-content-librariesvsphere-vm-admin/publish-the-contents-of-a-library-and-a-single-template-to-a-subscribervsphere-vm-admin.html).
 

articles/communication-services/concepts/rooms/room-concept.md

@@ -168,7 +168,7 @@ The following table provides detailed capabilities mapped to the roles. At a hig
 | - Show if a participant is muted | ✔️ | ✔️ | ✔️ |
 | - Show the reason why a participant left a call | ✔️ | ✔️ | ✔️ |
 | - Start call captions | ✔️ | ✔️ | ✔️ |
-| - Change captions language | ✔️ | ✔️ | ❌ |
+| - Change captions language | ✔️ | ✔️ | ✔️ |
 | - Invite to join a Virtual Room participant to a call | ✔️ | ❌ | ❌ |
 | **Screen sharing** | | |
 | - Share screen | ✔️ *  | ❌ | ❌ |

articles/iot-operations/deploy-iot-ops/howto-prepare-cluster.md

@@ -199,7 +199,7 @@ Connect your cluster to Azure Arc so that it can be managed remotely.
    ```
 
    > [!NOTE]
-   >If you receive the error: "Unable to fetch oid of 'custom-locations' app. Proceeding without enabling the feature. Insufficient privileges to complete the operation", then your service principal might lack the necessary permissions to retrieve the object ID of the custom location. Log into Azure CLI with a Microsoft Entra user account that meets the prerequisites. For more information, see [Create and manage custom locations](https://aka.ms/enable-cl-sp).
+   >If you receive the error: "Unable to fetch oid of 'custom-locations' app. Proceeding without enabling the feature. Insufficient privileges to complete the operation," then your service principal might lack the necessary permissions to retrieve the object ID of the custom location. Log into Azure CLI with a Microsoft Entra user account that meets the prerequisites. For more information, see [Create and manage custom locations](https://aka.ms/enable-cl-sp).
 
 1. Use the [az connectedk8s enable-features](/cli/azure/connectedk8s#az-connectedk8s-enable-features) command to enable the custom location feature on your Arc cluster. This command uses the OBJECT_ID environment variable saved from the previous step to set the value for the custom-locations-oid parameter. Run this command on the machine where you deployed the Kubernetes cluster: 
 
@@ -215,10 +215,12 @@ Connect your cluster to Azure Arc so that it can be managed remotely.
 
 ### Configure multi-node clusters for Azure Container Storage
 
-On multi-node clusters with at least three nodes, you have the option of enabling fault tolerance for storage with [Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/overview) when you deploy Azure IoT Operations. 
+On multi-node Ubuntu clusters with at least three nodes, you have the option of enabling fault tolerance for storage with [Azure Container Storage enabled by Azure Arc](/azure/azure-arc/container-storage/overview) when you deploy Azure IoT Operations.
 
 If you want to enable fault tolerance during deployment, configure your clusters by following the steps in [Prepare Linux for Edge Volumes using a multi-node Ubuntu cluster](/azure/azure-arc/container-storage/multi-node-cluster-edge-volumes?pivots=ubuntu).
 
+If you're running your cluster on a Kubernetes distribution other than k3s, review the guidance to [Prepare Linux with other platforms](/azure/azure-arc/container-storage/multi-node-cluster-edge-volumes?pivots=other).
+
 ### [AKS Edge Essentials](#tab/aks-edge-essentials)
 
 [Azure Kubernetes Service Edge Essentials](/azure/aks/hybrid/aks-edge-overview) is an on-premises Kubernetes implementation of Azure Kubernetes Service (AKS) that automates running containerized applications at scale. AKS Edge Essentials includes a Microsoft-supported Kubernetes platform that includes a lightweight Kubernetes distribution with a small footprint and simple installation experience that supports PC-class or "light" edge hardware.

articles/load-balancer/load-balancer-overview.md

@@ -67,13 +67,13 @@ Key scenarios that you can accomplish by using Azure Standard Load Balancer incl
 
 ### <a name="securebydefault"></a>Security by default
 
-- Standard Load Balancer is built on the Zero Trust network security model.
+- [Standard Load Balancer](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) is built on the Zero Trust network security model.
 
-- Standard Load Balancer is part of your virtual network, which is private and isolated for security.
+- [Standard Load Balancer](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) is part of your virtual network, which is private and isolated for security.
 
 - Standard load balancers and standard public IP addresses are closed to inbound connections, unless network security groups (NSGs) open them. You use NSGs to explicitly permit allowed traffic. If you don't have an NSG on a subnet or network interface card (NIC) of your virtual machine resource, traffic isn't allowed to reach the resource. To learn about NSGs and how to apply them to your scenario, see [Network security groups](../virtual-network/network-security-groups-overview.md).
 
-- Basic Load Balancer is open to the internet by default.
+- [Basic Load Balancer](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/load-balancer/skus.md) is open to the internet by default.
 
 - Azure Load Balancer doesn't store customer data.
 

articles/managed-grafana/how-to-upgrade-grafana-11.md

@@ -0,0 +1,101 @@
+--- 
+title: Upgrade Azure Managed Grafana to Grafana 11
+titleSuffix: Azure Managed Grafana
+description: "Learn how to upgrade an Azure Managed Grafana workspace from Grafana 10 to Grafana 11."
+ms.service: azure-managed-grafana
+author: maud-lv  
+ms.author: malev 
+ms.date: 02/28/2025 
+ms.topic: how-to 
+# customerIntent: As a user of Azure Managed Grafana, I want to upgrade my workspce from Grafana 10 to Grafana 11.
+--- 
+
+# Upgrade to Grafana 11
+
+Azure Managed Grafana will stop offering Grafana 10 as a supported software version on July 31, 2025. This guide provides information about the retirement of Grafana 10 and guides you through updating your Azure Managed Grafana workspace to Grafana 11.
+
+> [!IMPORTANT]
+> We recommend that you familiarize yourself with the [breaking changes introduced in Grafana 11](https://grafana.com/docs/grafana/latest/breaking-changes/breaking-changes-v11-0/) and upgrade your workspace to Grafana 11 before August 2025. If your workspace is still running Grafana version 10 in August 2025, it will be automatically upgraded to Grafana 11.
+
+## Prerequisites
+
+- An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free).
+- An existing Azure Managed Grafana instance. [Create one if you haven't already](quickstart-managed-grafana-portal.md).
+
+## Retirement timeline
+
+The following table outlines the retirement timeline.
+
+| Key dates   | Status                                                                                                                                                    |
+|-------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| March 2025  | Users can start to upgrade existing workspaces to Grafana 11.                                                                                             |
+| June 2025   | <li>All new workspaces use Grafana 11. Creating new workspaces on Grafana 10 is disabled. <li> Users can still upgrade existing workspaces to Grafana 11. |
+| August 2025 | All workspaces are forcibly upgraded to Grafana 11.                                        |
+
+## Check the version of your Grafana workspace
+
+To find out if your Azure Managed Grafana workspace needs to be upgraded, check the version of Grafana your workspace is running.
+
+### [Portal](#tab/azure-portal)
+  
+In the Azure portal:
+
+  1. Open your Azure Managed Grafana workspace.
+  1. In the left menu, under **Settings** select **Configuration**.
+  1. Review the Grafana version listed under **Grafana Version**. If version 10 is selected in the dropdown menu, your workspace is on the Grafana version that is reaching end of life and is scheduled for retirement. We recommend that you upgrade your workspace to Grafana 11 by following the steps below. If your Grafana version is Grafana 11, no further action is necessary.
+
+      :::image type="content" source="media/grafana-11-upgrade/check-grafana-version.jpg" alt-text="Screenshot of the Azure platform showing Grafana Version 9.":::
+  
+### [Azure CLI](#tab/azure-cli)
+
+Run the command [az grafana show](/cli/azure/grafana#az-grafana-show) in the Azure CLI to retrieve the properties of the Azure Managed Grafana workspace. Replace the placeholder `<azure-managed-grafana-workspace>` with the name of the Azure Managed Grafana instance.
+
+```azurecli
+az grafana show --name <azure-managed-grafana-workspace>
+```
+
+The version number is listed in the output after `grafanaMajorVersion`. If version is `10`, your workspace is on the Grafana version that is reaching end of life and is scheduled for retirement. We recommend that you upgrade your workspace to Grafana 11 by following the steps below. If your Grafana version is `11`, no further action is necessary.
+
+---
+
+## Upgrade to Grafana 11
+
+Upgrade from Grafana 10 to Grafana 11 by following the steps below.
+
+> [!IMPORTANT]  
+> Grafana 11 includes significant breaking changes. Make sure to review the [Grafana Breaking changes in Grafana v11.0](https://grafana.com/docs/grafana/latest/breaking-changes/breaking-changes-v11-0/) article thoroughly before upgrading your workspace.
+
+> [!CAUTION]  
+> Upgrading to Grafana 11 is irreversible.
+
+### [Portal](#tab/azure-portal)
+
+In the Azure portal:
+
+1. Once you have reviewed the breaking changes in Grafana 11 and are ready to proceed with the upgrade, open your workspace and select **Settings** > **Configuration** from the left menu.
+1. Under **Grafana Version**, select **11**.
+1. Select **Save** on top to save the new settings and trigger the upgrade to Grafana version 11.
+
+    :::image type="content" source="media/grafana-11-upgrade/save-upgrade.jpg" alt-text="Screenshot of the Azure portal showing Grafana version 11 selected in the dropdown menu and the Save button highlighted.":::
+
+1. A notification appears, indicating that the upgrade is in progress. In the **Overview** page, Grafana’s **Provisioning State** is **Provisioning** until the upgrade is complete. After a few minutes, a notification appears, and the provisioning state becomes **Succeeded**.
+
+### [Azure CLI](#tab/azure-cli)
+
+In the Azure CLI:
+
+1. Once you have reviewed the breaking changes in Grafana 11 and are ready to proceed with the upgrade, run the [az grafana update](/cli/azure/grafana#az-grafana-update) command and replace `<azure-managed-grafana-workspace>` with the name of your Azure Managed Grafana workspace.
+
+    ```azurecli
+    az grafana update --name <azure-managed-grafana-workspace> --major-version 11
+    ```
+
+1. The CLI displays a warning indicating that upgrading to Grafana version 11 is a permanent an irreversible operation.
+---
+
+## Next step
+
+In this article, you have been guided through upgrading your Azure Managed Grafana workspace from Grafana 10 to Grafana 11. If needed, go to the following guide for additional support.
+
+> [!div class="nextstepaction"]
+> [Find help or open a support ticket](./find-help-open-support-ticket.md)