Merge branch 'MicrosoftDocs:main' into patch-2

Author: yelevin

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

@@ -4,7 +4,7 @@ description: This article tells how to use change tracking and inventory to trac
 services: automation
 ms.subservice: change-inventory-management
 ms.custom: linux-related-content
-ms.date: 09/19/2024
+ms.date: 11/19/2024
 ms.topic: how-to
 ms.service: azure-automation
 ---
@@ -25,7 +25,10 @@ To manage tracking and inventory, ensure that you enable Change tracking with AM
 
 1. In the [Azure portal](https://portal.azure.com), select the virtual machine.
 1. Select a specific VM for which you would like to configure the Change tracking settings. 
-1. Under **Operations**, select **Change tracking**
+1. Under **Operations**, select **Change tracking**.
+   
+   :::image type="content" source="media/manage-change-tracking-monitoring-agent/configure-file-settings.png" alt-text="Screenshot of selecting the change tracking to configure file settings." lightbox="media/manage-change-tracking-monitoring-agent/configure-file-settings.png":::
+
 1. Select **Settings** to view the **Data Collection Rule Configuration** (DCR) page. Here, you can do the following actions:
    1. Configure changes on a VM at a granular level.  
    1. Select the filter to configure the workspace.

articles/automation/change-tracking/media/manage-change-tracking-monitoring-agent/configure-file-settings.png

@@ -159,10 +159,6 @@
       href: managed-redis/managed-redis-how-to-import-export-data.md
     - name: Configure disk encryption 
       href: managed-redis/managed-redis-how-to-encryption.md
-    - name: Reboot
-      href: managed-redis/managed-redis-administration.md#reboot
-    - name: Update channel and schedule updates
-      href: managed-redis/managed-redis-administration.md#update-channel-and-schedule-updates
     - name: Configure redis-cli access
       href: managed-redis/managed-redis-how-to-redis-cli-tool.md
     - name: Management FAQs
@@ -488,4 +484,4 @@
   - name: Build your skills with Microsoft Learn training
     href: /training/browse/?products=azure-redis-cache
   - name: Azure Roadmap
-    href: https://azure.microsoft.com/roadmap/?category=databases
+    href: https://azure.microsoft.com/roadmap/?category=databases

articles/azure-cache-for-redis/TOC.yml

@@ -177,7 +177,7 @@ Optionally, select the **Use custom colors** toggle switch to toggle On/Off cust
 
 #### Semantic model
 
-| Datapoint   | Country | City     | Office name |
+| Datapoint   | Country/region | City     | Office name |
 |-------------|---------|----------|-------------|
 | Datapoint_1 | US      | New York | Office C    |
 | Datapoint_1 | US      | Seattle  | Office A    |

articles/azure-maps/power-bi-visual-add-reference-layer.md

@@ -46,7 +46,7 @@ The following diagram shows throughput limit examples of volumes in an auto QoS
 
 ### Throughput limit examples of volumes in a manual QoS capacity pool 
 
-If you use a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. When you create a volume in a manual QoS capacity pool, you can specify the throughput (MiB/S) value. The total throughput assigned to volumes in a manual QoS capacity pool depends on the size of the pool and the service level. Throughput limits are capped by a formula: cCapacity pool size in TiB x service level throughput/TiB. For instance, a 10-TiB capacity pool with the Ultra service level has a total throughput capacity of 1280 MiB/s (10 TiB x 128 MiB/s/TiB) available for the volumes.
+If you use a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. When you create a volume in a manual QoS capacity pool, you can specify the throughput (MiB/S) value. The total throughput assigned to volumes in a manual QoS capacity pool depends on the size of the pool and the service level. Throughput limits are capped by a formula: capacity pool size in TiB x service level throughput/TiB. For instance, a 10-TiB capacity pool with the Ultra service level has a total throughput capacity of 1280 MiB/s (10 TiB x 128 MiB/s/TiB) available for the volumes.
 
 For example, for an SAP HANA system, this capacity pool can be used to create the following volumes. Each volume provides the individual size and throughput to meet your application requirements:
 

articles/azure-netapp-files/azure-netapp-files-service-levels.md

@@ -5,7 +5,7 @@ author: Y-Sindo
 ms.author: zityang
 ms.service: azure-web-pubsub
 ms.topic: how-to
-ms.date: 09/30/2022
+ms.date: 11/20/2024
 ---
 
 # Send client events to Event Hubs
@@ -67,9 +67,9 @@ Find your Azure Web PubSub service from **Azure portal**. Navigate to **Identity
 
 ## Test your configuration with live demo
 
-1. Open this [Event Hubs Consumer Client](https://awpseventlistenerdemo.blob.core.windows.net/eventhub-consumer/index.html) web app, input the Event Hubs connection string to connect to an event hub as a consumer. If you get the Event Hubs connection string from an Event Hubs namespace resource instead of an event hub instance, then you need to specify the event hub name. This event hub consumer client is connected with the mode that only reads new events; the events published before aren't seen here. You can change the consumer client connection mode to read all the available events in the production environment.
+1. Open this [Event Hubs Consumer Client](https://awpseventlistenerdemo.z13.web.core.windows.net/eventhub-consumer/index.html) web app, input the Event Hubs connection string to connect to an event hub as a consumer. If you get the Event Hubs connection string from an Event Hubs namespace resource instead of an event hub instance, then you need to specify the event hub name. This event hub consumer client is connected with the mode that only reads new events; the events published before aren't seen here. You can change the consumer client connection mode to read all the available events in the production environment.
 
-1. Use this [WebSocket Client](https://awpseventlistenerdemo.blob.core.windows.net/webpubsub-client/websocket-client.html) web app to generate client events. If you've configured to send system event `connected` to that event hub, you should be able to see a printed `connected` event in the Event Hubs consumer client after connecting to Web PubSub service successfully. You can also generate a user event with the app.
+1. Use this [WebSocket Client](https://awpseventlistenerdemo.z13.web.core.windows.net/webpubsub-client/websocket-client.html) web app to generate client events. If you've configured to send system event `connected` to that event hub, you should be able to see a printed `connected` event in the Event Hubs consumer client after connecting to Web PubSub service successfully. You can also generate a user event with the app.
    :::image type="content" source="media/howto-develop-event-listener/eventhub-consumer-connected-event.png" alt-text="Screenshot of a printed connected event in the Event Hubs consumer client app.":::
    :::image type="content" source="media/howto-develop-event-listener/web-pubsub-client-specify-event-name.png" alt-text="Screenshot showing the area of the WebSocket client app to generate a user event.":::
 

articles/azure-web-pubsub/howto-develop-event-listener.md

@@ -2,7 +2,7 @@
 title: About Azure File share backup
 description: Learn how to back up Azure file shares in the Recovery Services vault
 ms.topic: overview
-ms.date: 09/09/2024
+ms.date: 11/20/2024
 ms.service: azure-backup
 ms.custom:
   - engagement-fy23
@@ -103,6 +103,12 @@ The following diagram explains the lifecycle of the lease acquired by Azure Back
 
 :::image type="content" source="./media/azure-file-share-backup-overview/backup-lease-lifecycle-diagram.png" alt-text="Diagram explaining the lifecycle of the lease acquired by Azure Backup." border="false":::
 
+## How Cross Subscription Backup for Azure File share (preview) works?
+
+Cross Subscription Backup (CSB) for Azure File share (preview) enables you to back up file shares across subscriptions. This feature is useful when you want to centralize backup management for file shares across different subscriptions. You can back up file shares from a source subscription to a Recovery Services vault in a target subscription.
+
+Learn about the [additional prerequisites](backup-azure-files.md#prerequisites) and [steps to configure Cross Subscription Backup for Azure File share (preview)](backup-azure-files.md#configure-the-backup). For information on the supported regions for Cross Subscription Backup, see the [Azure File share backup support matrix](azure-file-share-support-matrix.md#supported-regions-for-cross-subscription-backup-preview).
+
 ## Next steps
 
 * [Back up Azure File shares](backup-afs.md).

articles/backup/azure-file-share-backup-overview.md

@@ -2,7 +2,7 @@
 title: Support Matrix for Azure file share backup by using Azure Backup
 description: Provides a summary of support settings and limitations when backing up Azure file shares.
 ms.topic: reference
-ms.date: 09/09/2024
+ms.date: 11/20/2024
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -32,6 +32,10 @@ Vaulted backup for Azure Files (preview) is available in West Central US, Southe
 
 ---
 
+### Supported regions for Cross Subscription Backup (preview)
+
+Cross Subscription Backup (CSB) for Azure File share (preview) is currently available in the following regions: East Asia, Southeast Asia, UK South, UK West, Central India.
+
 ## Supported storage accounts
 
 **Choose a backup tier**:

articles/backup/azure-file-share-support-matrix.md

@@ -2,7 +2,7 @@
 title: Back up Azure File shares in the Azure portal
 description: Learn how to use the Azure portal to back up Azure File shares in the Recovery Services vault
 ms.topic: how-to
-ms.date: 07/29/2024
+ms.date: 11/20/2024
 ms.service: azure-backup
 ms.custom: engagement-fy23
 author: AbhishekMallick-MS
@@ -22,37 +22,42 @@ Azure File share backup is a native, cloud based backup solution that protects y
 
 ## Prerequisites
 
-* Ensure that the file share is present in one of the supported storage account types. Review the [support matrix](azure-file-share-support-matrix.md).
+* Ensure the file share is present in one of the supported storage account types. Review the [support matrix](azure-file-share-support-matrix.md).
 * Identify or create a [Recovery Services vault](#create-a-recovery-services-vault) in the same region and subscription as the storage account that hosts the file share.
 * In case you have restricted access to your storage account, check the firewall settings of the account to ensure that the exception "Allow Azure services on the trusted services list to access this storage account" is granted. You can refer to [this](../storage/common/storage-network-security.md?tabs=azure-portal#manage-exceptions) link for the steps to grant an exception.
+>[!Important]
+>To perform [Cross Subscription Backup (CSB)  for protecting Azure File share (preview)](azure-file-share-backup-overview.md#how-cross-subscription-backup-for-azure-file-share-preview-works) in another subscription, ensure you register `Microsoft.RecoveryServices` in the **subscription of the file share** in addition to the above prerequisites. Learn about the [supported regions for Cross Subscription Backup (preview)](azure-file-share-support-matrix.md#supported-regions-for-cross-subscription-backup-preview).
+
 
 [!INCLUDE [How to create a Recovery Services vault](../../includes/backup-create-rs-vault.md)]
 
 ## Configure the backup
 
-You can configure *snapshot backup* and *vaulted backup (preview)* for Azure File share from *Backup center* or *File share blade*.
+You can configure *snapshot backup* and *vaulted backup (preview)* for Azure File share from the *Recovery Services vault* or *File share blade*.
 
 **Choose an entry point**
 
-# [Backup center](#tab/backup-center)
+# [Recovery Services vault](#tab/recovery-services-vault)
 
-To configure backup for multiple file shares from the Backup center, follow these steps:
+To configure backup for multiple file shares from the Recovery Services vault, follow these steps:
 
-1. In the [Azure portal](https://portal.azure.com/), go to **Backup center** and select **+Backup**.
+1. In the [Azure portal](https://portal.azure.com/), go to the **Recovery Services vault** and select **+Backup**.
 
-   :::image type="content" source="./media/backup-afs/backup-center-configure-inline.png" alt-text="Screenshot showing to configure Backup for Azure File." lightbox="./media/backup-afs/backup-center-configure-expanded.png":::
+   :::image type="content" source="./media/backup-afs/azure-file-configure-backup.png" alt-text="Screenshot showing to configure Backup for Azure File." lightbox="./media/backup-afs/azure-file-configure-backup.png":::
 
 1. On the **Start: Configure Backup** blade, select **Azure Files (Azure Storage)** as the datasource type, select the vault that you want to protect the file shares with, and then select **Continue**.
 
    :::image type="content" source="./media/backup-afs/azure-file-share-select-vault.png" alt-text="Screenshot showing to select Azure Files.":::
 
-1. Click **Select** to select the storage account that contains the file shares to be backed-up.
+1. Click **Select** to select the storage account that contains the file shares to be backed up.
 
-   The **Select storage account** blade opens on the right, which lists a set of discovered supported storage accounts. They're either associated with this vault or present in the same region as the vault, but not yet associated to any Recovery Services vault.
+   The **Select storage account** blade opens on the right, which lists a set of discovered supported storage accounts. They're either associated with this vault or present in the same region as the vault, but not yet associated with any Recovery Services vault.
 
    :::image type="content" source="./media/backup-azure-files/azure-file-share-select-storage-account.png" alt-text="Screenshot showing to select a storage account." lightbox="./media/backup-azure-files/azure-file-share-select-storage-account.png":::
 
-1. On the **Select storage account** blade, from the list of discovered storage accounts, select an account, and select **OK**.
+1. On the **Select storage account** blade, by default it list the storage accounts from the current subscription. Select an account, and select **OK**.
+
+   If you want to configure the backup operation with a storage account in a different subscription ([Cross Subscription Backup - preview](azure-file-share-backup-overview.md#how-cross-subscription-backup-for-azure-file-share-preview-works)), choose the other subscription from the **Subscription** filter. The storage accounts from the selected subscription appear.
 
    :::image type="content" source="./media/backup-azure-files/azure-file-share-confirm-storage-account.png" alt-text="Screenshot showing to select one of the discovered storage accounts." lightbox="./media/backup-azure-files/azure-file-share-confirm-storage-account.png":::
 
@@ -80,7 +85,7 @@ To configure backup for multiple file shares from the Backup center, follow thes
       - **Snapshot**: Enables only snapshot-based backups that are stored locally and can only provide protection in case of accidental deletions.
       - **Vault-Standard (Preview)**: Provides comprehensive data protection.
 
-   1. Configure the *backup schedule* as per the requirement. You can configure up to *six backups* a day. The snapshots are taken as per the schedule defined in the policy. In case of vaulted backup, the data from the last snapshot of the day is transferred to the vault.
+   1. Configure the *backup schedule* as per the requirement. You can configure up to *six backups* per day. The snapshots are taken as per the schedule defined in the policy. In case of vaulted backup, the data from the last snapshot of the day is transferred to the vault.
 
    1. Configure the *Snapshot retention* and *Vault retention (preview)* duration to determine the expiry date of the recovery points.
 
@@ -144,7 +149,7 @@ The following steps explain how you can configure backup for individual file sha
       - **Snapshot**: Enables only snapshot-based backups that are stored locally and can only provide protection in case of accidental deletions.
       - **Vault-Standard (Preview)**: Provides comprehensive data protection.
 
-   1. Configure the *backup schedule* as per the requirement. You can configure up to *six backups* a day. The snapshots are taken as per the schedule defined in the policy. In case of vaulted backup, the data from the last snapshot of the day is transferred to the vault.
+   1. Configure the *backup schedule* as per the requirement. You can configure up to *six backups* per day. The snapshots are taken as per the schedule defined in the policy. In case of vaulted backup, the data from the last snapshot of the day is transferred to the vault.
 
    1. Configure the *Snapshot retention* and *Vault retention (preview)* duration to determine the expiry date of the recovery points.
 
@@ -176,15 +181,13 @@ Occasionally, you might want to generate a backup snapshot, or recovery point, o
 
 **Choose an entry point**
 
-# [Backup center](#tab/backup-center)
+# [Recovery Services vault](#tab/recovery-services-vault)
 
 To run an on-demand backup, follow these steps:
 
-1. Go to **Backup center** and select **Backup Instances** from the menu.
-
-   Filter for **Azure Files (Azure Storage)** as the datasource type.
+1. Go to the **Recovery Services vault** and select **Backup items** from the menu.
 
-   :::image type="content" source="./media/backup-afs/azure-file-share-backup-instances-inline.png" alt-text="Screenshot showing to select Backup instances." lightbox="./media/backup-afs/azure-file-share-backup-instances-expanded.png":::
+1. On the **Backup items** blade, select the **Backup Management Type** as **Azure Storage (Azure Files)**.
 
 1. Select the item for which you want to run an on-demand backup job.
 
@@ -198,9 +201,9 @@ To run an on-demand backup, follow these steps:
 
 1. Select **OK** to confirm the on-demand backup job that runs.
 
-1. Monitor the portal notifications to keep a track of backup job run completion.
+1. Monitor the portal notifications to keep track of backup job run completion.
 
-   To monitor the job progress in the **Backup center** dashboard, select **Backup center** -> **Backup Jobs** -> **In progress**.
+   To monitor the job progress in the **Recovery Services vault** dashboard, go to **Recovery Services vault** > **Backup Jobs** > **In progress**.
 
 # [File share blade](#tab/file-share-pane)
 

articles/backup/backup-azure-files.md

@@ -4,7 +4,7 @@ description: This article explains about the concept of Immutable vault for Azur
 ms.topic: overview
 ms.service: azure-backup
 ms.custom: references_regions, engagement-fy24
-ms.date: 11/11/2024
+ms.date: 11/20/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -15,7 +15,7 @@ Immutable vault can help you protect your backup data by blocking any operations
 
 ## Before you start
 
-- Use of WORM storage for immutable vaults in locked state is currently in GA for Recovery Services Vaults in the following regions: West Central US, West Europe, East US, North Europe, Australia East.
+- Use of WORM storage for immutable vaults in locked state is currently in GA for Recovery Services Vaults in the following regions: Australia Central 2, Switzerland West, South Africa West, Korea Central, Germany North, Korea South, Spain Central.
 - Use of WORM storage for immutable vaults in locked state is applicable for the following workloads: Azure Virtual machines, SQL in Azure VM, SAP HANA in Azure VM, Azure Backup Server, Azure Backup Agent, DPM.
 - Immutable vault is available in all Azure public and US Government regions.
 - Immutable vault is supported for Recovery Services vaults and Backup vaults.