Merge pull request #312644 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-05 12:00 UTC

Author: learn-build-service-prod[bot]

articles/azure-app-configuration/monitor-app-configuration.md

@@ -49,12 +49,12 @@ For more information about App Configuration metrics, see [supported metrics for
 Azure App Configuration logs include activity logs and resource logs.
 
 ### Activity logs
-[Activity logs](/azure/azure-monitor/reference/tables/azureactivity) provide insight into subscription-level events and show management plane activities (create, update, delete operations on your App Configuration resource). However, they don't capture data plane operations like key-value reads and writes. You can view them in the **Activity log** blade. Alternatively, follow the steps in [Log collection](#log-collection) to route them to Log Analytics workspace for more complex querying scenarios.
+[Activity logs](/azure/azure-monitor/reference/tables/azureactivity) provide insight into subscription-level events and show all control plane CRUD operations for your App Configuration resource. However, they don't capture data plane operations like key-value reads and writes. You can view activity logs in the **Activity log** blade. Alternatively, follow the steps in [Log collection](#log-collection) to route them to a Log Analytics workspace for more complex querying scenarios.
 
 ### Resource logs
 App Configuration provides two types of resource logs.
-- **Audit logs**: Capture write operations (create, update, delete) on your data plane resources, such as key-values. Audit logs don't include data plane read operations but include management plane operations. Entries are unaggregated. Query them in the **AACAudit** table. For more information, refer to [AACAudit](/azure/azure-monitor/reference/tables/AACAudit).
-- **HTTP request logs**: Capture both read and write operations on your data plane resources, such as key-values. Operations are aggregated for better performance and to reduce log volume. Aggregation is based on HTTP method and status code. Each log entry may represent multiple similar operations within a certain time window. Query them in the **AACHttpRequest** table. For more information, refer to [AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest).
+- **Audit logs**: Capture data plane write operations (create, update, and delete), such as key-values modifications, and all control plane CRUD operations. Audit logs don't include data plane read operations. Unlike HTTP request logs, entries of audit logs are not aggregated. Query them in the **AACAudit** table. For more information, refer to [AACAudit](/azure/azure-monitor/reference/tables/AACAudit).
+- **HTTP request logs**: Capture both read and write operations on your data plane resources, such as key-values. Entries of HTTP request logs are aggregated for better performance and to reduce log volume. Aggregation is based on HTTP method and status code. Each log entry may represent multiple requests within a certain time window. Refer to the HitCount field for the number of requests whose logs are aggregated. Query them in the **AACHttpRequest** table. For more information, refer to [AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest).
 
 #### Log collection
 Metrics and the activity log are collected and stored automatically, and can be routed to other locations by using a diagnostic setting.

articles/azure-functions/functions-app-settings.md

@@ -973,7 +973,7 @@ In the [Flex Consumption plan](./flex-consumption-plan.md), these site propertie
 | `WEBSITE_VNET_ROUTE_ALL` |Not used for networking in Flex Consumption|
 | `properties.alwaysOn` |Not valid|
 | `properties.containerSize` |Renamed as `instanceMemoryMB`|
-| `properties.dnsConfiguration` | Custom DNS servers configured in the Azure Virtual Network are automatically used|
+| 'properties.dnsConfiguration.dnsServers'| DNS is inherited from the integrated virtual network in a Flex Consumption plan. |
 | `properties.ftpsState` | FTPS not supported | 
 | `properties.isReserved` |Not valid|
 | `properties.IsXenon` |Not valid|

articles/migrate/set-discovery-scope.md

@@ -18,6 +18,11 @@ This article describes how to limit the scope of discovery for servers in VMware
 
 When you set up the appliance, it connects to vCenter Server and starts discovery. Before you connect the appliance to vCenter Server, you can limit discovery to vCenter Server datacenters, clusters, a folder of clusters, hosts, a folder of hosts, or individual servers. To set the scope, you assign permissions on the account that the appliance uses to access the vCenter Server.
 
+Watch the following video to learn how to discover on-premises servers running in a VMware environment as part of your migration to Azure. 
+
+
+> [!VIDEO https://learn-video.azurefd.net/vod/player?id=edbc7f22-2ba1-44cd-a534-465dfd426a14]
+
 ## Before you start
 
 If you haven't set up a vCenter Server user account that Azure Migrate uses for discovery, do that now for [assessment](tutorial-discover-vmware.md#prepare-vmware) or [agentless migration](migrate-support-matrix-vmware-migration.md#agentless-migration).

articles/storage/blobs/network-file-system-protocol-known-issues.md

@@ -24,7 +24,9 @@ This article describes limitations and known issues of Network File System (NFS)
 
 - NFS 3.0 support can't be disabled in a storage account after you enable it.
 
-- Geo-redundant storage (GRS), Geo-zone-redundant storage (GZRS), and Read-access geo-redundant storage (RA-GRS) redundancy options aren't supported when you create an NFS 3.0 storage account.
+- Geo-Redundant Storage (GRS) is supported only for unplanned failover scenarios and isn't supported for planned failover.
+
+- Geo-zone-redundant storage (GZRS) and Read-access geo-redundant storage (RA-GRS) redundancy options aren't supported when you create an NFS 3.0 storage account.
 
 - Access control lists (ACLs) can't be used to authorize an NFS 3.0 request. In fact, if the ACL or a blob or directory contains an entry for a named user or group, that file becomes inaccessible on the client for nonroot users. You have to remove these entries to restore access to nonroot users on the client. For information about how to remove an ACL entry for named users and groups, see [How to set ACLs](data-lake-storage-access-control.md#how-to-set-acls).
 

articles/storage/blobs/object-replication-configure.md

@@ -319,6 +319,84 @@ N/A
 
 ---
 
+## Configure blob index tags replication (preview)
+
+Object replication now supports copying index tags from source blobs to destination blobs. You can configure this capability as part of a new or existing replication rule.
+
+> [!IMPORTANT]
+> Tag replication is currently in PREVIEW.
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
+
+### Prerequisites
+
+The source storage account must be registered for the EnableObjectReplicationTags preview feature before tag replication can be enabled. Register the preview feature in the Azure portal by following the steps in the [Azure Resource Manager preview features](/azure/azure-resource-manager/management/preview-features?tabs=azure-portal) documentation.
+
+### Enable Tags replication
+
+Tags replication can be enabled on both new and existing object replication policies. Any change to a source blob or it's index tags will trigger replication of tags.
+
+#### [Azure portal](#tab/portal)
+
+Enable tags replication from the Object Replication blade when creating a rule or update existing rules using the Tags replication column.
+
+To configure replicating blob index tags when creating a new rule, follow these steps:
+
+1. Navigate to the source storage account in the Azure portal.
+1. Under **Data management**, select **Object replication**.
+1. Select **Create replication rules**.
+1. Select **Enable tags replication** and finally select **Save and apply** to configure replicating blob index tags.
+
+To configure replicating blob index tags for exsiting rules, follow these steps:
+
+1. Navigate to **Your accounts tab** in **Object replication** page 
+1. Select **Enable** option under Tags replication column in **Objects copied from this account** table and select **OK**.
+1. Status of Tags replication column against a rule now shows **Enabled**.
+
+To disable replicating blob index tags for exsiting rules, follow these steps:
+
+1. Navigate to **Your accounts tab** in **Object replication** page 
+2. Select an exsiting rule and select **Edit rules** from the '…' menu
+3. Unselect **Enable tags replication** option and finally select **Save and apply** to disable replicating blob index tags.
+
+#### [PowerShell](#tab/powershell)
+
+N/A.
+
+#### [Azure CLI](#tab/azure-cli)
+
+N/A.
+
+#### [REST API](#tab/rest-api)
+
+Users can use existing REST APIs: [Object Replication Policies - Create Or Update - REST API](/rest/api/storagerp/object-replication-policies/create-or-update) to configure policies for replicating tags set on the Blobs. 
+
+Add the following line ``` “tagsReplication”: { “enabled”: true }``` when creating or updating the replication 
+rules on the source account.
+
+Tags replication is supported on API version 2022-05-01 and above. You can add the new tagsReplication field to the replication policy.
+
+Sample: 
+
+``` json
+{
+    "sourceAccount": "<source-account-name>",
+    "destinationAccount": "<destination-account-name>",
+    "tagsReplication":
+    {
+     "enabled": true
+    },
+    "rules":
+    [
+        {
+            "ruleId": "<rule-id>",
+            "sourceContainer": "<source-container-name>",
+            "destinationContainer": "<destination-container-name>"
+        }
+    ]
+}
+```
+---
+
 ## Configure replication metrics
 
 ### Enable replication metrics

articles/storage/blobs/object-replication-overview.md

@@ -76,9 +76,13 @@ When a blob in the source account is deleted, the current version of the blob be
 
 Object replication doesn't support blob snapshots. Any snapshots on a blob in the source account aren't replicated to the destination account.
 
-## Blob index tags
+### Blob index tags
 
-Object replication doesn't copy the source blob's index tags to the destination blob.
+Object replication now supports copying index tags from source blobs to destination blobs. You can configure this capability as part of a new or existing replication rule. For more information, see [Configure object replication](object-replication-configure.md#configure-blob-index-tags-replication-preview).
+
+> [!IMPORTANT]
+> Tag replication is currently in PREVIEW.
+> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 ### Blob tiering
 

articles/storage/blobs/storage-feature-support-in-storage-accounts.md

@@ -46,7 +46,7 @@ The following table describes whether a feature is supported in a standard gener
 | [Microsoft Entra security](authorize-access-azure-active-directory.md) | &#x2705; | &#x2705; | &#x2705;<sup>1</sup>  | &#x2705;<sup>1</sup>  |
 | [Azure DNS Zone endpoints (preview)](../common/storage-account-overview.md?toc=/azure/storage/blobs/toc.json#storage-account-endpoints) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
 | [Blob inventory](blob-inventory.md) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
-| [Blob index tags](storage-manage-find-blobs.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
+| [Blob index tags](storage-manage-find-blobs.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
 | [Blob snapshots](snapshots-overview.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
 | [Blob Storage APIs](reference.md) | &#x2705; | &#x2705;   | &#x2705; | &#x2705;  |
 | [Blob Storage Azure CLI commands](storage-quickstart-blobs-cli.md) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
@@ -57,7 +57,7 @@ The following table describes whether a feature is supported in a standard gener
 | [Change feed](storage-blob-change-feed.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
 | [Custom domains](storage-custom-domain-name.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
 | [Customer-managed planned failover](../common/storage-disaster-recovery-guidance.md#customer-managed-planned-failover) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &#x2705; |
-| [Customer-managed (unplanned) failover](../common/storage-disaster-recovery-guidance.md#customer-managed-unplanned-failover) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &#x2705; |
+| [Customer-managed (unplanned) failover](../common/storage-disaster-recovery-guidance.md#customer-managed-unplanned-failover) | &#x2705; | &#x2705; | &#x1F7E6; | &#x2705; |
 | [Customer-managed keys with key vault in the same tenant](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
 | [Customer-managed keys with key vault in a different tenant (cross-tenant)](../common/customer-managed-keys-overview.md?toc=/azure/storage/blobs/toc.json) | &#x2705; | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
 | [Customer-provided keys](encryption-customer-provided-keys.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
@@ -97,7 +97,7 @@ The following table describes whether a feature is supported in a premium block
 | [Microsoft Entra security](authorize-access-azure-active-directory.md) | &#x2705; | &#x2705; | &#x2705;<sup>1</sup>  | &#x2705;<sup>1</sup> |
 | [Azure DNS Zone endpoints (preview)](../common/storage-account-overview.md?toc=/azure/storage/blobs/toc.json#storage-account-endpoints) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
 | [Blob inventory](blob-inventory.md) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |
-| [Blob index tags](storage-manage-find-blobs.md) | &#x2705; | &nbsp;&#x2B24; | &nbsp;&#x2B24; | &nbsp;&#x2B24; |
+| [Blob index tags](storage-manage-find-blobs.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
 | [Blob snapshots](snapshots-overview.md) | &#x2705; | &#x1F7E6; | &#x1F7E6; | &#x1F7E6; |
 | [Blob Storage APIs](reference.md) | &#x2705; | &#x2705;   | &#x2705; | &#x2705;  |
 | [Blob Storage Azure CLI commands](storage-quickstart-blobs-cli.md) | &#x2705; | &#x2705; | &#x2705; | &#x2705; |

articles/storage/blobs/storage-manage-find-blobs.md

@@ -327,11 +327,14 @@ You're charged for the monthly average number of index tags within a storage acc
 
 [!INCLUDE [Blob Storage feature support in Azure Storage accounts](../../../includes/azure-storage-feature-support.md)]
 
+> [!NOTE]
+> Blob Tags without indexing is available in Preview for hierarchical namespace (HNS) enabled storage accounts. To try this feature, users must register for “Blob Tags for Hierarchical Namespace” under the Preview features section of their subscription. Currently, Blob Tags on HNS enabled accounts are not integrated with blob storage features like Lifecycle Management.
+
 ## Conditions and known issues
 
 This section describes known issues and conditions.
 
-- Only general-purpose v2 accounts and premium block blob accounts are supported. Premium page blob, legacy blob, and accounts with a hierarchical namespace enabled aren't supported. General-purpose v1 accounts won't be supported.
+- Only general-purpose v2 accounts and premium block blob accounts are supported. Premium page blob, legacy blob aren't supported. General-purpose v1 accounts won't be supported.
 
 - Uploading page blobs with index tags doesn't persist the tags. Set the tags after uploading a page blob.