Merge pull request #171580 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/azure-arc/data/plan-azure-arc-data-services.md

@@ -39,6 +39,9 @@ Once the infrastructure is prepared, deploy Azure Arc-enabled data services in t
 1. Create an Azure Arc-enabled data controller on one of the validated distributions of a Kubernetes cluster
 1. Create an Azure Arc-enabled SQL managed instance and/or an Azure Arc-enabled PostgreSQL Hyperscale server group.
 
+> [!CAUTION]
+> Some of the data services tiers and modes are [generally available](release-notes.md) and some are in preview. We recommend that you don't mix GA and preview services on the same data controller. If you mix GA and preview services on the same data controller, you can't upgrade in place. In that scenario, when you want to upgrade, you must remove and re-create the data controller and data services.
+
 ## Overview: Create the Azure Arc-enabled data controller
 
 You can create Azure Arc-enabled data services on multiple different types of Kubernetes clusters and managed Kubernetes services using multiple different approaches.

articles/azure-sql/database/long-term-retention-overview.md

@@ -83,8 +83,6 @@ To learn how to configure long-term retention or restore a database from backup
 
 To learn how to configure long-term retention or restore a database from backup for SQL Managed Instance using the Azure portal or PowerShell, see [Manage Azure SQL Managed Instance long-term backup retention](../managed-instance/long-term-backup-retention-configure.md).
 
-To restore a database from the LTR storage, you can select a specific backup based on its timestamp. The database can be restored to any existing server under the same subscription as the original database. To learn how to restore your database from an LTR backup, using the Azure portal, or PowerShell, see [Manage Azure SQL Database long-term backup retention](long-term-backup-retention-configure.md). 
-
 ## Next steps
 
 Because database backups protect data from accidental corruption or deletion, they're an essential part of any business continuity and disaster recovery strategy. 

articles/azure-web-pubsub/quickstart-serverless.md

@@ -369,7 +369,7 @@ Use the following commands to create these items.
 
 1. Deploy the function project to Azure:
 
-    After you've successfully created your function app in Azure, you're now ready to deploy your local functions project by using the [func azure functionapp publish](/azure-functions/functions-run-local) command.
+    After you've successfully created your function app in Azure, you're now ready to deploy your local functions project by using the [func azure functionapp publish](./../azure-functions/functions-run-local.md) command.
 
     ```bash
     func azure functionapp publish <FUNCIONAPP_NAME> --publish-local-settings

articles/cognitive-services/Speech-Service/text-to-speech.md

@@ -80,7 +80,7 @@ For detailed information, see [Pricing](https://azure.microsoft.com/pricing/deta
 
 ## Migrate to Neural Voice
 
-We are retiring the standard voices on **31st August 2024** and they will no longer be supported after that date.  The announcement has been sent out to all existing Speech subscriptions before **31st August 2021**. During the retiring period (**31st August 2021- 31st August 2024**), existing users can continue to use their standard voices, all new users/new speech resources should move to the neural voices.
+We are retiring the standard voices on **31st August 2024** and they will no longer be supported after that date.  The announcement has been sent out to all existing Speech subscriptions before **31st August 2021**. During the retiring period (**31st August 2021- 31st August 2024**), existing standard voice users can continue to use their standard voices, all new users/new speech resources should move to the neural voices.
 
 **Action required**
 
@@ -95,4 +95,4 @@ We are retiring the standard voices on **31st August 2024** and they will no lon
 ## Next steps
 
 * [Get a free Speech service subscription](overview.md#try-the-speech-service-for-free)
-* [Get the Speech SDK](speech-sdk.md)
+* [Get the Speech SDK](speech-sdk.md)

articles/cognitive-services/personalizer/includes/quickstart-sdk-csharp.md

@@ -56,7 +56,7 @@ Build succeeded.
 Within the application directory, install the Personalizer client library for .NET with the following command:
 
 ```console
-dotnet add package Microsoft.Azure.CognitiveServices.Personalizer --version 0.8.0-preview
+dotnet add package Microsoft.Azure.CognitiveServices.Personalizer --version 1.0.0
 ```
 
 > [!TIP]

articles/data-factory/format-common-data-model.md

@@ -50,7 +50,7 @@ When selecting "Entity Reference" both in the Source and Sink transformations, y
 
 * Local uses the entity defined in the manifest file already being used by ADF
 * Custom will ask you to point to an entity manifest file that is different from the manifest file ADF is using
-* Standard will use an entity reference from the standard library of CDM entities maintained in ```Github```.
+* Standard will use an entity reference from the standard library of CDM entities maintained in GitHub.
 
 ### Sink settings
 

articles/expressroute/how-to-configure-connection-monitor.md

@@ -102,7 +102,7 @@ $solution = @{
     ResourceGroupName = $resourceGroup
 }
 
-New-AzureRmResource @solution -Force
+New-AzResource @solution -Force
 ```
 
 Once you've configured the monitoring solution. Continue to the next step of installing and configuring the monitoring agents on your servers.
@@ -250,4 +250,4 @@ For a high-level overview of how to create a connection monitor, tests, and test
 
 ## Next steps
 
-Learn more about [Monitoring Azure ExpressRoute](monitor-expressroute.md)
+Learn more about [Monitoring Azure ExpressRoute](monitor-expressroute.md)

articles/firewall/premium-features.md

@@ -139,7 +139,7 @@ Azure Firewall Premium has the following known issues:
 |Client Certificates (TLS)|Client certificates are used to build a mutual identity trust between the client and the server. Client certificates are used during a TLS negotiation. Azure firewall renegotiates a connection with the server and has no access to the private key of the client certificates.|None|
 |QUIC/HTTP3|QUIC is the new major version of HTTP. It's a UDP-based protocol over 80 (PLAN) and 443 (SSL). FQDN/URL/TLS inspection won't be supported.|Configure passing UDP 80/443 as network rules.|
 Untrusted customer signed certificates|Customer signed certificates are not trusted by the firewall once received from an intranet-based web server.|A fix is being investigated.
-|Wrong source IP address in Alerts with IDPS for HTTP (without TLS inspection).|When plain text HTTP traffic is in use, and IDPS issues a new alert, and the destination is public an IP address, the displayed source IP address is wrong (the internal IP address is displayed instead of the original IP address).|A fix is being investigated.|
+|Wrong source IP address in Alerts with IDPS for HTTP (without TLS inspection).|When plain text HTTP traffic is in use, and IDPS issues a new alert, and the destination is a public IP address, the displayed source IP address is wrong (the internal IP address is displayed instead of the original IP address).|A fix is being investigated.|
 |Certificate Propagation|After a CA certificate is applied on the firewall, it may take between 5-10 minutes for the certificate to take effect.|A fix is being investigated.|
 |TLS 1.3 support|TLS 1.3 is partially supported. The TLS tunnel from client to the firewall is based on TLS 1.2, and from the firewall to the external Web server is based on TLS 1.3.|Updates are being investigated.|
 |KeyVault Private Endpoint|KeyVault supports Private Endpoint access to limit its network exposure. Trusted Azure Services can bypass this limitation if an exception is configured as described in the [KeyVault documentation](../key-vault/general/overview-vnet-service-endpoints.md#trusted-services). Azure Firewall is not currently listed as a trusted service and can't access the Key Vault.|A fix is being investigated.|

articles/machine-learning/how-to-consume-web-service.md

@@ -95,7 +95,7 @@ The following table shows what these URIs look like:
 | Swagger URI | `http://104.214.29.152/api/v1/service/<service-name>/swagger.json` |
 
 > [!TIP]
-> The IP address will be different for your deployment. Each AKS cluster will hve it's own IP address that is shared by deployments to that cluster.
+> The IP address will be different for your deployment. Each AKS cluster will have its own IP address that is shared by deployments to that cluster.
 
 ### Secured web service
 

articles/virtual-machines/linux/quick-create-cli.md

@@ -41,7 +41,7 @@ az group create --name myResourceGroup --location eastus
 
 Create a VM with the [az vm create](/cli/azure/vm) command.
 
-The following example creates a VM named *myVM* and adds a user account named *azureuser*. The `--generate-ssh-keys` parameter is used to automatically generate an SSH key, and put it in the default key location (*~/.ssh*). To use a specific set of keys instead, use the `--ssh-key-value` option.
+The following example creates a VM named *myVM* and adds a user account named *azureuser*. The `--generate-ssh-keys` parameter is used to automatically generate an SSH key, and put it in the default key location (*~/.ssh*). To use a specific set of keys instead, use the `--ssh-key-values` option.
 
 ```azurecli-interactive
 az vm create \