Merge pull request #295305 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-maps/power-bi-visual-get-started.md

@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
 description: This article discusses how to use Azure Maps Power BI visual.
 author: deniseatmicrosoft
 ms.author: limingchen
-ms.date: 01/27/2025
+ms.date: 02/25/2025
 ms.topic: how-to
 ms.service: azure-maps
 ms.subservice: power-bi-visual
@@ -153,7 +153,7 @@ The Azure Maps Power BI visual is available in the following services and applic
 | Power BI Desktop                         | Yes          |
 | Power BI service (app.powerbi.com)       | Yes          |
 | Power BI mobile applications             | Yes          |
-| Power BI publish to web                  | No           |
+| Power BI publish to web                  | Yes          |
 | Power BI Embedded                        | Yes          |
 | Power BI service embedding (PowerBI.com) | Yes          |
 

articles/communication-services/quickstarts/advanced-messaging/whatsapp/download-media.md

@@ -55,7 +55,7 @@ An example of an `AdvancedMessageReceived` event with media content:
 ::: zone-end
 
 ::: zone pivot="programming-language-javascript"
-[!INCLUDE [Download WhatsApp media messages with Javascript SDK](./includes/download-media/download-media-javascript.md)]
+[!INCLUDE [Download WhatsApp media messages with JavaScript SDK](./includes/download-media/download-media-javascript.md)]
 ::: zone-end
 
 ::: zone pivot="programming-language-python"

articles/container-apps/storage-mounts.md

@@ -6,7 +6,7 @@ author: craigshoemaker
 ms.service: azure-container-apps
 ms.custom: devx-track-azurecli
 ms.topic: conceptual
-ms.date: 01/31/2025
+ms.date: 02/25/2025
 ms.author: cshoe
 zone_pivot_groups: arm-azure-cli-portal
 ---
@@ -321,9 +321,12 @@ For a step-by-step tutorial on mounting an SMB file share, refer to [Create an A
         - The `name` is an identifier for the volume.
         - For `storageType`, use `AzureFile` for SMB, or `NfsAzureFile` for NFS. This value must match the storage type you defined in the environment.
         - For `storageName`, use the name of the storage you defined in the environment.
+        - The `mountOptions` is a comma-separated string of mount options. For more information see [Use mountOptions settings in Azure Files](/troubleshoot/azure/azure-kubernetes/storage/mountoptions-settings-azure-files).
+        - The `secrets` list is a list of secrets to mount in the volume. For more information see [Mounting secrets in a volume](./manage-secrets.md#secrets-volume-mounts).
     - For each container in the template that you want to mount Azure Files storage, define a volume mount in the `volumeMounts` array of the container definition.
         - The `volumeName` is the name defined in the `volumes` array.
         - The `mountPath` is the path in the container to mount the volume.
+        - The `subPath` (optional) is the path in the volume to mount. If not specified, the volume root is mounted. For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).
 
     # [SMB](#tab/smb)
 
@@ -338,6 +341,7 @@ For a step-by-step tutorial on mounting an SMB file share, refer to [Create an A
           volumeMounts:
           - volumeName: azure-files-volume
             mountPath: /my-files
+            subPath: my-sub-path
         volumes:
         - name: azure-files-volume
           storageType: AzureFile
@@ -357,6 +361,7 @@ For a step-by-step tutorial on mounting an SMB file share, refer to [Create an A
           volumeMounts:
           - volumeName: azure-files-volume
             mountPath: /my-files
+            subPath: my-sub-path
         volumes:
         - name: azure-files-volume
           storageType: NfsAzureFile
@@ -501,7 +506,8 @@ The following ARM template snippets demonstrate how to add an Azure Files share
               "volumeMounts": [
                 {
                   "mountPath": "/myfiles",
-                  "volumeName": "azure-files-volume"
+                  "volumeName": "azure-files-volume",
+                  "subPath": "my-sub-path"
                 }
               ]
             }
@@ -547,7 +553,8 @@ The following ARM template snippets demonstrate how to add an Azure Files share
               "volumeMounts": [
                 {
                   "mountPath": "/myfiles",
-                  "volumeName": "azure-files-volume"
+                  "volumeName": "azure-files-volume",
+                  "subPath": "my-sub-path"
                 }
               ]
             }
@@ -574,9 +581,12 @@ The following ARM template snippets demonstrate how to add an Azure Files share
         - The `name` is an identifier for the volume.
         - For `storageType`, use `AzureFile` for SMB, or `NfsAzureFile` for NFS. This value must match the storage type you defined in the environment.
         - For `storageName`, use the name of the storage you defined in the environment.
+        - The `mountOptions` is a comma-separated string of mount options. For more information see [Use mountOptions settings in Azure Files](/troubleshoot/azure/azure-kubernetes/storage/mountoptions-settings-azure-files).
+        - The `secrets` list is a list of secrets to mount in the volume. For more information see [Mounting secrets in a volume](./manage-secrets.md#secrets-volume-mounts).
     - For each container in the template that you want to mount Azure Files storage, define a volume mount in the `volumeMounts` array of the container definition.
         - The `volumeName` is the name defined in the `volumes` array.
         - The `mountPath` is the path in the container to mount the volume.
+        - The `subPath` (optional) is the path in the volume to mount. If not specified, the volume root is mounted. For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).
 
 See the [ARM template API specification](azure-resource-manager-api-spec.md) for a full example.
 
@@ -632,6 +642,7 @@ To configure a volume mount for Azure Files storage in the Azure portal, add a f
     - **Volume type**: **Azure file volume**.
     - **Name**: Enter a volume name.
     - **File share name**: Select the file share you created previously.
+    - **Mount options**: Optionally, enter a comma-separated string of mount options. For more information see [Use mountOptions settings in Azure Files](/troubleshoot/azure/azure-kubernetes/storage/mountoptions-settings-azure-files).
 
 1. Select **Add** to exit the context pane.
 
@@ -645,6 +656,8 @@ To configure a volume mount for Azure Files storage in the Azure portal, add a f
 
 1. In **Mount path**, enter the absolute path in the container to mount the volume.
 
+1. In **Sub path (optional)**, enter the path in the volume to mount. If not specified, the volume root is mounted. For more information see [using subPath](https://kubernetes.io/docs/concepts/storage/volumes/#using-subpath).
+
 1. Select **Save** to save changes and exit the context pane.
 
 1. Select **Create** to create the new revision.

articles/governance/machine-configuration/overview.md

@@ -24,7 +24,7 @@ such as:
 
 Configurations are distinct from policy definitions. Machine configuration uses Azure Policy to
 dynamically assign configurations to machines. You can also assign configurations to machines
-[manually][03], or by using other Azure services such as [Automanage][04].
+[manually][03].
 
 Examples of each scenario are provided in the following table.
 

articles/managed-grafana/encryption.md

@@ -32,7 +32,7 @@ For more information, go to [Encryption at rest in Azure Cosmos DB](/azure/cosmo
 
 The encryption model used by Azure Managed Grafana is the server-side encryption model with Service-Managed keys.
 
-In this model, all key management aspects such as key issuance, rotation, and backup are managed by Microsoft. The Azure resource providers create the keys, place them in secure storage, and retrieve them when needed. For more information, go to [Server-side encryption using service-managed keys](../security/fundamentals/encryption-models.md#server-side-encryption-using-service-managed-keys).
+In this model, all key management aspects, such as key issuance, rotation, and backup, are managed by Microsoft. The Azure resource providers create the keys, place them in secure storage, and retrieve them when needed. For more information, go to [Server-side encryption using service-managed keys](../security/fundamentals/encryption-models.md#server-side-encryption-using-service-managed-keys).
 
 ## Next steps