Merge pull request #279489 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-arc/servers/arc-gateway.md

@@ -82,7 +82,7 @@ There are six main steps to use the feature:
 
 1. Execute the following command to add the connectedmachine extension:
 
-    `az extension add --allow-limited preview true --yes --source [whl file path]`
+    `az extension add --allow-preview true --source [whl file path]`
 
 ### Step 2: Create an Arc gateway resource
 

articles/azure-monitor/app/opentelemetry-nodejs-migrate.md

@@ -40,12 +40,14 @@ This guide provides two options to upgrade from the Azure Monitor Application In
     Remove all Application Insights instrumentation from your code. Delete any sections where the Application Insights client is initialized, modified, or called.
 
 4. Enable Application Insights with the Azure Monitor OpenTelemetry Distro.
-
+    > [!IMPORTANT] 
+    > *Before* you import anything else, `useAzureMonitor` must be called. There might be telemetry loss if other libraries are imported first.
     Follow [getting started](opentelemetry-enable.md?tabs=nodejs) to onboard to the Azure Monitor OpenTelemetry Distro.
 
 #### Azure Monitor OpenTelemetry Distro changes and limitations
 
-The APIs from the Application Insights SDK 2.X aren't available in the Azure Monitor OpenTelemetry Distro. You can access these APIs through a nonbreaking upgrade path in the Application Insights SDK 3.X.
+   * The APIs from the Application Insights SDK 2.X aren't available in the Azure Monitor OpenTelemetry Distro. You can access these APIs through a nonbreaking upgrade path in the Application Insights SDK 3.X.
+   * Filtering dependencies, logs, and exceptions by operation name is not yet supported.
 
 ## [Upgrade](#tab/upgrade)
 

articles/managed-grafana/how-to-connect-to-data-source-privately.md

@@ -34,7 +34,7 @@ Managed private endpoints work with Azure services that support private link. Us
 - Azure SQL server
 - Private link services
 - Azure Databricks
-- Azure Database for PostgreSQL flexible servers
+- Azure Database for PostgreSQL flexible servers ([Only for servers that have public access networking](/azure/postgresql/flexible-server/concepts-networking-private-link))
 
 ## Prerequisites
 

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

@@ -58,6 +58,9 @@ Object replication requires that blob versioning is enabled on both the source a
 
 If your storage account has object replication policies in effect, you cannot disable blob versioning for that account. You must delete any object replication policies on the account before disabling blob versioning.
 
+> [!NOTE]
+> Only blobs are copied to the destination. A blob's version ID is not copied. The blob that is placed at the destination location is assigned a new version ID.
+
 ### Deleting a blob in the source account
 
 When a blob in the source account is deleted, the current version of the blob becomes a previous version, and there's no longer a current version. All existing previous versions of the blob are preserved. This state is replicated to the destination account. For more information about how to delete operations affect blob versions, see [Versioning on delete operations](versioning-overview.md#versioning-on-delete-operations).

articles/virtual-desktop/azure-stack-hci-overview.md

@@ -1,24 +1,24 @@
 ---
-title: Azure Virtual Desktop with Azure Stack HCI 
+title: Azure Virtual Desktop for Azure Stack HCI 
 description: Learn about using Azure Virtual Desktop with Azure Stack HCI, enablng you to deploy session hosts where you need them.
 ms.topic: conceptual
 author: dknappettmsft
 ms.author: daknappe
 ms.date: 04/11/2024
 ---
 
-# Azure Virtual Desktop with Azure Stack HCI
+# Azure Virtual Desktop for Azure Stack HCI
 
 > [!IMPORTANT]
-> Azure Virtual Desktop with Azure Stack HCI is currently in preview for Azure Government and Azure China. 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.
+> Azure Virtual Desktop for Azure Stack HCI is currently in preview for Azure Government and Azure China. 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.
 
-Using Azure Virtual Desktop with Azure Stack HCI, you can deploy session hosts for Azure Virtual Desktop where you need them. If you already have an existing on-premises virtual desktop infrastructure (VDI) deployment, Azure Virtual Desktop with Azure Stack HCI can improve your experience. If you're already using Azure Virtual Desktop with your session hosts in Azure, you can extend your deployment to your on-premises infrastructure to better meet your performance or data locality needs.
+Using Azure Virtual Desktop for Azure Stack HCI, you can deploy session hosts for Azure Virtual Desktop where you need them. If you already have an existing on-premises virtual desktop infrastructure (VDI) deployment, Azure Virtual Desktop with Azure Stack HCI can improve your experience. If you're already using Azure Virtual Desktop with your session hosts in Azure, you can extend your deployment to your on-premises infrastructure to better meet your performance or data locality needs.
 
 Azure Virtual Desktop service components, such as host pools, workspaces, and application groups are all deployed in Azure, but you can choose to deploy session hosts on Azure Stack HCI. As Azure Virtual Desktop with Azure Stack HCI isn't an Azure Arc-enabled service, it's not supported as a standalone service outside of Azure, in a multicloud environment, or on other Azure Arc-enabled servers.
 
 ## Benefits
 
-Using Azure Virtual Desktop with Azure Stack HCI, you can:
+Using Azure Virtual Desktop for Azure Stack HCI, you can:
 
 - Improve performance for Azure Virtual Desktop users in areas with poor connectivity to the Azure public cloud by giving them session hosts closer to their location.
 
@@ -57,13 +57,13 @@ Finally, users can connect using the same [Remote Desktop clients](users/remote-
 
 ## Licensing and pricing
 
-To run Azure Virtual Desktop with Azure Stack HCI, you need to make sure you're licensed correctly and be aware of the pricing model. There are three components that affect how much it costs to run Azure Virtual Desktop with Azure Stack HCI:
+To run Azure Virtual Desktop for Azure Stack HCI, you need to make sure you're licensed correctly and be aware of the pricing model. There are three components that affect how much it costs to run Azure Virtual Desktop with Azure Stack HCI:
 
-- **User access rights.** The same licenses that grant access to Azure Virtual Desktop on Azure also apply to Azure Virtual Desktop with Azure Stack HCI. Learn more at [Azure Virtual Desktop pricing](https://azure.microsoft.com/pricing/details/virtual-desktop/).
+- **User access rights.** The same licenses that grant access to Azure Virtual Desktop on Azure also apply to Azure Virtual Desktop for Azure Stack HCI. Learn more at [Azure Virtual Desktop pricing](https://azure.microsoft.com/pricing/details/virtual-desktop/).
 
 - **Azure Stack HCI service fee.** Learn more at [Azure Stack HCI pricing](https://azure.microsoft.com/pricing/details/azure-stack/hci/).
 
-- **Azure Virtual Desktop on Azure Stack HCI service fee.** This fee requires you to pay for each active virtual CPU (vCPU) for your Azure Virtual Desktop session hosts running on Azure Stack HCI. Learn more at [Azure Virtual Desktop pricing](https://azure.microsoft.com/pricing/details/virtual-desktop/).
+- **Azure Virtual Desktop for Azure Stack HCI service fee.** This fee requires you to pay for each active virtual CPU (vCPU) for your Azure Virtual Desktop session hosts running on Azure Stack HCI. Learn more at [Azure Virtual Desktop pricing](https://azure.microsoft.com/pricing/details/virtual-desktop/).
 
 ## Data storage
 
@@ -73,12 +73,6 @@ There are different classifications of data for Azure Virtual Desktop, such as c
 
 Azure Virtual Desktop with Azure Stack HCI has the following limitations:
 
-- You can't use some Azure Virtual Desktop features when session hosts running on Azure Stack HCI, such as:
-    
-    - [Azure Virtual Desktop Insights](insights.md)
-    - [Session host scaling with Azure Automation](set-up-scaling-script.md)
-    - [Per-user access pricing](licensing.md)
-
 - Each host pool must only contain session hosts on Azure or on Azure Stack HCI. You can't mix session hosts on Azure and on Azure Stack HCI in the same host pool.
 
 - Azure Stack HCI supports many types of hardware and on-premises networking capabilities, so performance and user density might vary compared to session hosts running on Azure. Azure Virtual Desktop's [virtual machine sizing guidelines](/windows-server/remote/remote-desktop-services/virtual-machine-recs) are broad, so you should use them for initial performance estimates and monitor after deployment.