Merge pull request #279198 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/aks/app-routing-nginx-configuration.md

@@ -551,3 +551,4 @@ Learn about monitoring the ingress-nginx controller metrics included with the ap
 [azure-dns-overview]: ../dns/dns-overview.md
 [az-keyvault-certificate-show]: /cli/azure/keyvault/certificate#az-keyvault-certificate-show
 [prometheus-in-grafana]: app-routing-nginx-prometheus.md
+[az-role-assignment-create]: /cli/azure/role/assignment#az-role-assignment-create

articles/container-apps/opentelemetry-agents.md

@@ -199,15 +199,15 @@ While you can set up as many OTLP-configured endpoints as you like, each endpoin
 # [Azure CLI](#tab/azure-cli)
 
 ```azurecli
-az containerap env telemetry otlp add \
-  --name "otlp1"
+az containerapp env telemetry otlp add \
+  --name "otlp1" \
   --endpoint "ENDPOINT_URL_1" \
   --insecure false \
   --headers "api-key-1=key" \
   --enable-open-telemetry-traces true \
   --enable-open-telemetry-metrics true
-az containerap env telemetry otlp add \
-  --name "otlp2"
+az containerapp env telemetry otlp add \
+  --name "otlp2" \
   --endpoint "ENDPOINT_URL_2" \
   --insecure true \
   --enable-open-telemetry-traces true \

articles/container-apps/tutorial-event-driven-jobs.md

@@ -12,7 +12,7 @@ ms.author: cshoe
 
 # Tutorial: Deploy an event-driven job with Azure Container Apps
 
-Azure Container Apps [jobs](jobs.md) allow you to run containerized tasks that execute for a finite duration and exit. You can trigger a job execution manually, on a schedule, or based on events. Jobs are best suited to for tasks such as data processing, machine learning, or any scenario that requires serverless ephemeral compute resources.
+Azure Container Apps [jobs](jobs.md) allow you to run containerized tasks that execute for a finite duration and exit. You can trigger a job execution manually, on a schedule, or based on events. Jobs are best suited to for tasks such as data processing, machine learning, resource cleanup, or any scenario that requires serverless ephemeral compute resources.
 
 In this tutorial, you learn how to work with [event-driven jobs](jobs.md#event-driven-jobs).
 

articles/cosmos-db/continuous-backup-restore-introduction.md

@@ -148,8 +148,6 @@ Currently the point in time restore functionality has the following limitations:
 
 * Azure Cosmos DB for MongoDB accounts with continuous backup don't support creating a unique index for an existing collection. For such an account, unique indexes must be created along with their collection; it can be done using the create collection [extension commands](mongodb/custom-commands.md).
 
-* The point-in-time restore functionality always restores to a new Azure Cosmos DB account. Restoring to an existing account is currently not supported. If you're interested in providing feedback about in-place restore, contact the Azure Cosmos DB team via your account representative.
-
 * After restoring, it's possible that for certain collections the consistent index may be rebuilding. You can check the status of the rebuild operation via the [IndexTransformationProgress](how-to-manage-indexing-policy.md) property.
 
 * The restore process restores all the properties of a container including its TTL configuration by default, you can pass parameter to disable TTL while doing the restore. As a result, it's possible that the data restored is deleted immediately if you configured that way. In order to prevent this situation, the restore timestamp must be before the TTL properties were added into the container.

articles/cosmos-db/mongodb/vcore/how-to-private-link.md

@@ -90,8 +90,7 @@ To create a private endpoint to a node in an existing cluster, open the
    > default values for the form fields might not be correct. Check them and
    > update if necessary.
 
-3. Select **Next: Resource**. For **Target sub-resource**, choose the target
-   node of the cluster. Usually **coordinator** is the desired node.
+3. Select **Next: Resource**. Choose "Microsoft.DocumentDB/mongoClusters" for **Resource type**, and choose the target cluster for **Resource**. For **Target sub-resource**, choose "MongoCluster".
 
 4. Select **Next: Virtual Network**. Choose the desired **Virtual network** and
    **Subnet**. Under **Private IP configuration**, select **Statically allocate IP address** or keep the default, **Dynamically allocate IP address**.

articles/machine-learning/concept-compute-target.md

@@ -141,12 +141,12 @@ While Azure Machine Learning supports these VM series, they might not be availab
 :::moniker range="azureml-api-1"
 > [!NOTE]
 > Azure Machine Learning doesn't support all VM sizes that Azure Compute supports. To list the available VM sizes, use the following method:
-> * [REST API](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2020-08-01/examples/ListVMSizesResult.json)
+> * [REST API](/rest/api/azureml/virtual-machine-sizes/list)
 :::moniker-end
 :::moniker range="azureml-api-2"
 > [!NOTE]
 > Azure Machine Learning doesn't support all VM sizes that Azure Compute supports. To list the available VM sizes, use one of the following methods:
-> * [REST API](https://github.com/Azure/azure-rest-api-specs/blob/master/specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/stable/2020-08-01/examples/ListVMSizesResult.json)
+> * [REST API](/rest/api/azureml/virtual-machine-sizes/list)
 > * The [Azure CLI extension 2.0 for machine learning](how-to-configure-cli.md) command, [az ml compute list-sizes](/cli/azure/ml/compute#az-ml-compute-list-sizes).
 :::moniker-end
 

articles/static-web-apps/apex-domain-external.md

@@ -31,6 +31,10 @@ This guide demonstrates three options for configuring an apex domain.
 
 * Use the steps to [set up with an A Record](#set-up-with-an-a-record) if the above options do not suit you. With an `A` record, your traffic is directed to a single Static Web Apps host, and your app no longer benefit from the performance improvements provided by global distribution.
 
+> [!NOTE]  
+> `CNAME` record maps a domain name to another domain (or subdomain) whereas `A` record maps a domain name to an IP address. If the IP address changes, a `CNAME` entry is still valid, unlike `A` record.
+
+
 ## Set up with an ALIAS record
 
 Before you create the `ALIAS` record, you first need to validate that you own the domain.

articles/static-web-apps/application-settings.yml

@@ -77,12 +77,12 @@ procedureSection:
       
       1. Open your static web app.
       
-      1. Select **Configuration** in the sidebar.
+      1. Select **Environment variables** in the sidebar.
       
-      1. Select the environment to which you want to apply the application settings. You can configure application settings per environment. When you create a pull request, staging environments are automatically created, and then promoted into production when you merge the pull request. 
+      1. Select the environment to which you want to create environment variables. You can create variables per environment. When you create a pull request, staging environments are automatically created, and then promoted into production when you merge the pull request. 
       
-      1. Select **+ Add** to add a new app setting.
-          :::image type="content" source="media/application-settings/configuration.png" alt-text="Screenshot of Azure Static Web Apps configuration view":::
+      1. Select **+ Add** to add a new environment variable.
+          :::image type="content" source="media/application-settings/configuration.png" alt-text="Screenshot of Azure Static Web Apps environment variables view":::
       
       1. Enter a **Name** and **Value**.