Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-arm

Author: halkazwini

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: 03/07/2025
+ms.date: 03/12/2025
 ms.topic: overview
 ms.service: azure-automation
 ---
@@ -28,7 +28,7 @@ Azure Change Tracking & Inventory service enhances the auditing and governance f
 1. **Change Tracking**
 
     a. Monitors changes, including modifications to files, registry keys, software installations, and Windows services or Linux daemons.</br>
-    b. Provides detailed logs of what and when the changes were made, who made them, enabling you to quickly detect configuration drifts or unauthorized changes. </br>
+    b. Provides detailed logs of what and when the changes were made, enabling you to quickly detect configuration drifts or unauthorized changes. </br>
     Change Tracking metadata will get ingested into the ConfigurationChange table in the connected LA workspace. [Learn more](/azure/azure-monitor/reference/tables/configurationchange)
 
 1. **Inventory**

articles/migrate/migrate-support-matrix.md

@@ -41,8 +41,7 @@ For Azure Migrate to work with Azure you need these permissions before you start
 **Task** | **Permissions** | **Details**
 --- | --- | ---
 Create a project | Your Azure account needs permissions to create a project. | Set up for [VMware](tutorial-discover-vmware.md#prepare-an-azure-user-account), [Hyper-V](./tutorial-discover-hyper-v.md#prepare-an-azure-user-account), or [physical servers](./tutorial-discover-physical.md#prepare-an-azure-user-account).
-Register the Azure Migrate appliance| Azure Migrate uses a lightweight [Azure Migrate appliance](migrate-appliance.md) to discover and assess servers with Azure Migrate: Discovery and assessment, and to run [agentless migration](server-migrate-overview.md) of VMware VMs with the Migration and modernization tool. This appliance discovers servers, and sends metadata and performance data to Azure Migrate.<br><br> During registration, register providers (Microsoft.OffAzure, Microsoft.Migrate, and Microsoft.KeyVault) are registered with the subscription chosen in the appliance, so that the subscription works with the resource provider. To register, you need Contributor or Owner access on the subscription.<br><br> **VMware**-During onboarding, Azure Migrate creates two Microsoft Entra apps. The first app communicates between the appliance agents and the Azure Migrate service. The app doesn't have permissions to make Azure resource management calls or have Azure RBAC access for resources. The second app accesses an Azure Key Vault created in the user subscription for agentless VMware migration only. In agentless migration, Azure Migrate creates a Key Vault to manage access keys to the replication storage account in your subscription. It has Azure RBAC access on the Azure Key Vault (in the customer tenant) when discovery is initiated from the appliance.<br><br> **Hyper-V**-During onboarding. Azure Migrate creates one Microsoft Entra app. The app communicates between the appliance agents and the Azure Migrate service. The app doesn't have permissions to make Azure resource management calls or have Azure RBAC access for resources. | Set up for [VMware](tutorial-discover-vmware.md#prepare-an-azure-user-account), [Hyper-V](./tutorial-discover-hyper-v.md#prepare-an-azure-user-account), or [physical servers](./tutorial-discover-physical.md#prepare-an-azure-user-account).
-Create a key vault for VMware agentless migration | To migrate VMware VMs with agentless Migration and modernization, Azure Migrate creates a Key Vault to manage access keys to the replication storage account in your subscription. To create the vault, you set permissions (Owner, or Contributor and User Access Administrator) on the resource group where the project resides. | [Set up](tutorial-discover-vmware.md#prepare-an-azure-user-account) permissions.
+Register the Azure Migrate appliance| Azure Migrate uses a lightweight [Azure Migrate appliance](migrate-appliance.md) to discover and assess servers with Azure Migrate: Discovery and assessment, and to run [agentless migration](server-migrate-overview.md) of VMware VMs with the Migration and modernization tool. This appliance discovers servers, and sends metadata and performance data to Azure Migrate.<br><br> During registration, register providers (Microsoft.OffAzure, Microsoft.Migrate, and Microsoft.KeyVault) are registered with the subscription chosen in the appliance, so that the subscription works with the resource provider. To register, you need Contributor or Owner access on the subscription.<br><br> During onboarding. Azure Migrate creates one Microsoft Entra app. The app communicates between the appliance agents and the Azure Migrate service. The app doesn't have permissions to make Azure resource management calls or have Azure RBAC access for resources. | Set up for [VMware](tutorial-discover-vmware.md#prepare-an-azure-user-account), [Hyper-V](./tutorial-discover-hyper-v.md#prepare-an-azure-user-account), or [physical servers](./tutorial-discover-physical.md#prepare-an-azure-user-account).
 
 ## Supported geographies 
 

articles/site-recovery/site-recovery-whats-new.md

@@ -5,7 +5,7 @@ ms.topic: overview
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 author: ankitaduttaMSFT
-ms.date: 01/28/2025
+ms.date: 03/12/2025
 ms.custom:
   - engagement-fy23
   - linux-related-content
@@ -24,7 +24,8 @@ For Site Recovery components, we support N-4 versions, where N is the latest rel
 
 **Update** |  **Unified Setup** | **Replication appliance / Configuration server** | **Mobility service agent** | **Site Recovery Provider** | **Recovery Services agent**
 --- | --- | --- | --- | --- | ---
-[Rollup 76](https://support.microsoft.com/en-us/topic/update-rollup-76-for-azure-site-recovery-6ca6833a-5b0f-4bdf-9946-41cd0aa8d6e4) | NA | NA | 9.63.7187.1 | 5.24.0902.11 | 2.0.9938.0
+[Rollup 77](https://support.microsoft.com/topic/update-rollup-77-for-azure-site-recovery-dbd00d14-6b52-48dc-84d7-72b2f71ce20c) | 9.64.7314.1 | NA | 9.64.7314.1 | NA | NA
+[Rollup 76](https://support.microsoft.com/topic/update-rollup-76-for-azure-site-recovery-6ca6833a-5b0f-4bdf-9946-41cd0aa8d6e4) | NA | NA | 9.63.7187.1 | 5.24.0902.11 | 2.0.9938.0
 [Rollup 75](https://support.microsoft.com/topic/update-rollup-75-for-azure-site-recovery-4884b937-8976-454a-9b80-57e0200eb2ec) | NA | NA | 9.62.7172.1 | 5.24.0814.2 | 2.0.9932.0
 [Rollup 74](https://support.microsoft.com/topic/update-rollup-74-for-azure-site-recovery-584e3586-4c55-4cc2-8b1c-63038b6b4464) | NA | NA | 9.62.7096.1 | 5.24.0614.1 | 2.0.9919.0
 [Rollup 73](https://support.microsoft.com/topic/update-rollup-73-for-azure-site-recovery-d3845f1e-2454-4ae8-b058-c1fec6206698) | 9.61.7016.1 | 9.61.7016.1 | 9.61.7016.1 | 5.24.0317.5 | 2.0.9917.0 
@@ -34,6 +35,19 @@ For Site Recovery components, we support N-4 versions, where N is the latest rel
 
 [Learn more](service-updates-how-to.md) about update installation and support.
 
+## Updates (March 2025)
+
+### Update Rollup 77
+
+Update [rollup 77](https://support.microsoft.com/topic/update-rollup-77-for-azure-site-recovery-dbd00d14-6b52-48dc-84d7-72b2f71ce20c) provides the following updates:
+
+**Update** | **Details**
+--- | ---
+**Providers and agents** | Updates to Site Recovery agents and providers as detailed in the rollup KB article.
+**Issue fixes/improvements** | Many fixes and improvement as detailed in the rollup KB article.
+**Azure VM disaster recovery** | Added support for Debian 11, SLES 12, SLES 15, Ubuntu 24.04 to 18.04 distros, Oracle Linux 9.4, and RHEL 9 Linux distros. 
+
+
 ## Updates (October 2024)
 
 ### Update Rollup 76

articles/storage/common/storage-failover-customer-managed-unplanned.md

@@ -124,10 +124,11 @@ Read access to the new secondary region isn't available again until the issue ca
 >
 > **To avoid a major data loss**, check the value of the [**Last Sync Time**](last-sync-time-get.md) property before failing back. Compare the last sync time to the last times that data was written to the new primary to evaluate potential data loss.
 
-After the issue causing the original outage is resolved, you can initiate failback to the original primary region. This process is described in the following image:
+After the issue causing the original outage is resolved, you can initiate failback to the original primary region. The failback process is the same as the original failover process previously explained.
 
-1. The current primary region becomes read only.
-1. With customer-initiated failover and failback, your data isn't allowed to finish replicating to the secondary region during the failback process. Therefore, it's important to check the value of the [**Last Sync Time**](last-sync-time-get.md) property before failing back.
+Important points to consider:
+
+1. With customer-initiated failover and failback, your data isn't allowed to finish replicating to the secondary region during the failback process. Therefore, it's important to check the value of the [**Last Sync Time**](last-sync-time-get.md) property before failing back. 
 1. The DNS entries for the storage service endpoints are switched. The endpoints within the secondary region become the new primary endpoints for your storage account.
 
 :::image type="content" source="media/storage-failover-customer-managed-unplanned/failback-to-primary-geo-redundant.png" alt-text="Diagram that shows how the customer initiates account failback to original primary region." lightbox="media/storage-failover-customer-managed-unplanned/failback-to-primary-geo-redundant.png":::
@@ -191,11 +192,12 @@ Read access to the new secondary region isn't available again until the original
 >
 > **To avoid a major data loss**, check the value of the [**Last Sync Time**](last-sync-time-get.md) property before failing back. Compare the last sync time to the last times that data was written to the new primary to evaluate potential data loss.
 
-After the issue causing the original outage is resolved, you can initiate failback to the original primary region. This process is described in the following image:
+After the issue causing the original outage is resolved, you can initiate failback to the original primary region. The failback process is the same as the original failover process previously explained.
+
+Important points to consider:
 
-1. The current primary region becomes read only.
-1. During customer-initiated failover and failback, your data isn't allowed to finish replicating to the secondary region during the failback process. Therefore, it's important to check the value of the [**Last Sync Time**](last-sync-time-get.md) property before failing back.
-1. The DNS entries for the storage service endpoints are switched. The secondary endpoints become the new primary endpoints for your storage account.
+1. With customer-initiated failover and failback, your data isn't allowed to finish replicating to the secondary region during the failback process. Therefore, it's important to check the value of the [**Last Sync Time**](last-sync-time-get.md) property before failing back. 
+1. The DNS entries for the storage service endpoints are switched. The endpoints within the secondary region become the new primary endpoints for your storage account.
 
 :::image type="content" source="media/storage-failover-customer-managed-unplanned/failback-to-primary-geo-zone-redundant.png" alt-text="Diagram that shows the customer initiating account failback to the original primary region." lightbox="media/storage-failover-customer-managed-unplanned/failback-to-primary-geo-zone-redundant.png":::
 

articles/storage/files/storage-how-to-create-file-share.md

@@ -531,8 +531,15 @@ $provisionedIops = 10000
 $provisionedThroughputMibPerSec = 2048
 
 # Update the file share provisioning.
-Update-AzRmStorageShare -ResourceGroupName $resourceGroupName -AccountName $storageAccountName -ShareName $shareName -ProvisionedBandwidthMibps $provisionedThroughputMibPerSec -ProvisionedIops $provisionedIops -QuotaGiB $provisionedStorageGib;
-$f = Get-AzRmStorageShare -ResourceGroupName $resourceGroupName -AccountName $storageAccountName -ShareName $shareName;
+Update-AzRmStorageShare `
+        -ResourceGroupName $resourceGroupName `
+        -AccountName $storageAccountName `
+        -ShareName $shareName `
+        -QuotaGiB $provisionedStorageGib `
+        -ProvisionedIops $provisionedIops `
+        -ProvisionedBandwidthMibps $provisionedThroughputMibPerSec
+
+$f = Get-AzRmStorageShare -ResourceGroupName $resourceGroupName -AccountName $storageAccountName -ShareName $shareName
 $f | fl
 ```
 
@@ -552,8 +559,13 @@ provisionedIops=10000
 provisionedThroughputMibPerSec=2048
 
 # Update the file share provisioning.
-az storage share-rm update --resource-group $resourceGroupName --name $shareName --storage-account $storageAccountName --quota $provisionedStorageGib --provisioned-iops $provisionedIops --provisioned-bandwidth-mibps $provisionedThroughputMibPerSec
-
+az storage share-rm update \
+        --resource-group $resourceGroupName \
+        --name $shareName \
+        --storage-account $storageAccountName \
+        --quota $provisionedStorageGib \
+        --provisioned-iops $provisionedIops \
+        --provisioned-bandwidth-mibps $provisionedThroughputMibPerSec
 ```
 
 ---
@@ -578,24 +590,54 @@ Follow these instructions to update the provisioning for your file share.
 
 5. Select **Save** to save provisioning changes. Storage, IOPS, and throughput changes are effective within a few minutes after a provisioning change.
 
+> [!NOTE]
+> You can use PowerShell and CLI to enable/disable paid bursting if desired. Paid burst is an advanced feature of the provisioned v1 billing model, consult [provisioned v1 paid bursting](./understanding-billing.md#provisioned-v1-paid-bursting) before enabling.
+
 # [PowerShell](#tab/azure-powershell)
-You can modify a provisioned v1 file share with the `Update-AzRmStorageShare` cmdlet. Remember to replace the values for the variables `$resourceGroupName`, `$storageAccountName`, `$fileShareName`, and `$provisionedStorageGib` with the desired values for your file share.
+You can modify a provisioned v1 file share with the `Update-AzRmStorageShare` cmdlet. Remember to replace the values for the variables `$resourceGroupName`, `$storageAccountName`, and `$fileShareName` with the desired values for your file share. Set `$provisionedStorageGib`, `$paidBurstingEnabled`, `$paidBurstingMaxIops`, and `$paidBurstingMaxThroughputMibPerSec` to non-null (`$null`) values to set on the file share. Paid bursting is an advanced feature of the provisioned v1 model, consult [provisioned v1 paid bursting](./understanding-billing.md#provisioned-v1-paid-bursting) before enabling.
 
 ```PowerShell
 # The path to the file share resource to be modified.
 $resourceGroupName = "<resource-group>"
 $storageAccountName = "<storage-account>"
 $fileShareName = "<file-share>"
 
-# The provisioning desired on the file share.
-$provisionedStorageGib = 10240
+# The provisioning desired on the file share. Set to $null to keep at the 
+# current level of provisioning.
+$provisionedStorageGib = 10240 
+
+# Paid bursting settings.
+$paidBurstingEnabled = $null # Set to $true or $false.
+$paidBurstingMaxIops = $null # Set to an integer value.
+$paidBurstingMaxThroughputMibPerSec = $null # Set to an integer value.
+
+# Configure parameter object for splatting.
+$params = @{
+    ResourceGroupName = $resourceGroupName;
+    StorageAccountName = $storageAccountName;
+    Name = $fileShareName;
+}
+
+if ($null -ne $provisionedStorageGib) { 
+    $params += @{ QuotaGiB = $provisionedStorageGib }
+}
+
+if ($null -ne $paidBurstingEnabled) {
+    $params += @{ PaidBurstingEnabled = $paidBurstingEnabled }
+}
+
+if ($null -ne $paidBurstingMaxIops) {
+    $params += @{ PaidBurstingMaxIops = $paidBurstingMaxIops }
+}
+
+if ($null -ne $paidBurstingMaxThroughputMibPerSec) {
+    $params += @{ 
+        PaidBurstingMaxBandwidthMibps = $paidBurstingMaxThroughputMibPerSec 
+    }
+}
 
 # Update the file share provisioning.
-Update-AzRmStorageShare `
-        -ResourceGroupName $resourceGroupName `
-        -StorageAccountName $storageAccountName `
-        -Name $fileShareName `
-        -QuotaGiB $provisionedStorageGib
+Update-AzRmStorageShare @params
 ```
 
 # [Azure CLI](#tab/azure-cli)
@@ -618,6 +660,20 @@ az storage share-rm update \
         --quota $provisionedStorageGib
 ```
 
+To toggle paid bursting, use the `--paid-bursting-enabled` parameter. Paid bursting is an advanced feature of the provisioned v1 model, consult [provisioned v1 paid bursting](./understanding-billing.md#provisioned-v1-paid-bursting) before enabling. You can optionally use the `--paid-bursting-max-iops` and `--paid-bursting-max-bandwidth-mibps` flags to set a restriction on the upper amount of paid bursting allowed for cost control purposes. Remember to replace the values for the variables `resourceGroupName`, `storageAccountName`, and `fileShareName` with the desired values for your file share.
+
+```bash
+resourceGroupName="<resource-group>"
+storageAccountName="<storage-account>"
+fileShareName="<file-share>"
+
+az storage share-rm update \
+        --resource-group $resourceGroupName \
+        --storage-account $storageAccountName \
+        --name $fileShareName \
+        --paid-bursting-enabled true
+```
+
 ---
 
 ### Change the cost and performance characteristics of a pay-as-you-go file share