Merge pull request #268306 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: TimShererWithAquent

articles/ai-studio/how-to/deploy-models-mistral.md

@@ -26,6 +26,8 @@ You can browse the Mistral family of models in the [Model Catalog](model-catalog
 
 ## Mistral Large 
 
+In this article, you learn how to use Azure AI Studio to deploy the Mistral Large model as a service with pay-as-you-go billing.
+
 Mistral Large is Mistral AI's most advanced Large Language Model (LLM). It can be used on any language-based task thanks to its state-of-the-art reasoning and knowledge capabilities.
 
 Additionally, mistral-large is:
@@ -165,7 +167,7 @@ __Body__
 
 #### Response schema
 
-The response payload is a dictionary with the following fields.
+The response payload is a dictionary with the following fields:
 
 | Key       | Type      | Description                                                                |
 |-----------|-----------|----------------------------------------------------------------------------|
@@ -180,7 +182,7 @@ The response payload is a dictionary with the following fields.
 > In the streaming mode, for each chunk of response, `finish_reason` is always `null`, except from the last one which is terminated by a payload `[DONE]`. In each `choices` object, the key for `messages` is changed by `delta`.
 
 
-The `choices` object is a dictionary with the following fields. 
+The `choices` object is a dictionary with the following fields:
 
 | Key     | Type      | Description  |
 |---------|-----------|--------------|
@@ -190,7 +192,7 @@ The `choices` object is a dictionary with the following fields.
 | `logprobs` | `object` | The log probabilities of the generated tokens in the output text. |
 
 
-The `usage` object is a dictionary with the following fields. 
+The `usage` object is a dictionary with the following fields:
 
 | Key                 | Type      | Value                                         |
 |---------------------|-----------|-----------------------------------------------|
@@ -205,7 +207,7 @@ The `logprobs` object is a dictionary with the following fields:
 | `text_offsets`   | `array` of `integers`   | The position or index of each token in the completion output. |
 | `token_logprobs` | `array` of `float`      | Selected `logprobs` from dictionary in `top_logprobs` array.   |
 | `tokens`         | `array` of `string`     | Selected tokens.   |
-| `top_logprobs`   | `array` of `dictionary` | Array of dictionary. In each dictionary, the key is the token and the value is the prob. |
+| `top_logprobs`   | `array` of `dictionary` | Array of dictionary. In each dictionary, the key is the token and the value is the probability. |
 
 #### Example
 

articles/azure-functions/durable/durable-functions-error-handling.md

@@ -396,7 +396,7 @@ await ctx.CallActivityWithRetryAsync("FlakeyActivity", retryOptions, null);
 TaskOptions retryOptions = TaskOptions.FromRetryHandler(retryContext =>
 {
     // Don't retry anything that derives from ApplicationException
-    if (!retryContext.LastFailure.IsCausedBy<ApplicationException>())
+    if (retryContext.LastFailure.IsCausedBy<ApplicationException>())
     {
         return false;
     }

articles/azure-functions/functions-reference-node.md

@@ -1617,11 +1617,11 @@ Before upgrading your Node.js version, make sure your function app is running on
 Run the Azure CLI [`az functionapp config appsettings set`](/cli/azure/functionapp/config#az-functionapp-config-appsettings-set) command to update the Node.js version for your function app running on Windows:
 
 ```azurecli-interactive
-az functionapp config appsettings set  --settings WEBSITE_NODE_DEFAULT_VERSION=~18 \
+az functionapp config appsettings set  --settings WEBSITE_NODE_DEFAULT_VERSION=~20 \
  --name <FUNCTION_APP_NAME> --resource-group <RESOURCE_GROUP_NAME> 
 ```
 
-This sets the [`WEBSITE_NODE_DEFAULT_VERSION` application setting](./functions-app-settings.md#website_node_default_version) the supported LTS version of `~18`.
+This sets the [`WEBSITE_NODE_DEFAULT_VERSION` application setting](./functions-app-settings.md#website_node_default_version) the supported LTS version of `~20`.
 
 # [Azure portal](#tab/azure-portal/windows)
 
@@ -1634,11 +1634,11 @@ Use the following steps to change the Node.js version:
 Run the Azure CLI [`az functionapp config set`](/cli/azure/functionapp/config#az-functionapp-config-set) command to update the Node.js version for your function app running on Linux:
 
 ```azurecli-interactive
-az functionapp config set --linux-fx-version "node|18" --name "<FUNCTION_APP_NAME>" \
+az functionapp config set --linux-fx-version "node|20" --name "<FUNCTION_APP_NAME>" \
  --resource-group "<RESOURCE_GROUP_NAME>"
 ```
 
-This sets the base image of the Linux function app to Node.js version 18.
+This sets the base image of the Linux function app to Node.js version 20.
 
 # [Azure portal](#tab/azure-portal/linux)
 

articles/service-fabric/how-to-managed-identity-managed-cluster-virtual-machine-scale-sets.md

@@ -43,7 +43,7 @@ A user-assigned managed identity can be defined in the resources section of an A
 {
   "type": "Microsoft.ManagedIdentity/userAssignedIdentities",
   "name": "[parameters('userAssignedIdentityName')]",
-  "apiVersion": "2018-11-30",
+  "apiVersion": "2023-01-31",
   "location": "[resourceGroup().location]"
 }
 ```
@@ -90,14 +90,14 @@ This role assignment can be defined in the resources section template using the
 ```json
 {
   "type": "Microsoft.Authorization/roleAssignments",
-  "apiVersion": "2020-04-01-preview",
+  "apiVersion": "2022-04-01",
   "name": "[parameters('vmIdentityRoleNameGuid')]",
   "scope": "[concat('Microsoft.ManagedIdentity/userAssignedIdentities', '/', parameters('userAssignedIdentityName'))]",
   "dependsOn": [
     "[concat('Microsoft.ManagedIdentity/userAssignedIdentities/', parameters('userAssignedIdentityName'))]"
   ],
   "properties": {
-    "roleDefinitionId": "[concat('/subscriptions/', subscription().subscriptionId, '/providers/Microsoft.Authorization/roleDefinitions/', 'f1a07417-d97a-45cb-824c-7a7467783830')]",
+    "roleDefinitionId": "[resourceId('Microsoft.Authorization/roleDefinitions', 'f1a07417-d97a-45cb-824c-7a7467783830')]",
     "principalId": "<Service Fabric Resource Provider ID>"
   }
 }
@@ -126,8 +126,8 @@ Finally, add the `vmManagedIdentity` and `userAssignedIdentities` properties to
 
 ```json
 {
-  "type": "Microsoft.ServiceFabric/managedclusters/nodetypes",
-  "apiVersion": "2021-05-01",
+  "type": "Microsoft.ServiceFabric/managedClusters/nodeTypes",
+  "apiVersion": "2022-01-01",
   "properties": {
     "isPrimary": true,
     "vmInstanceCount": 5,

articles/virtual-machines/windows/run-command-managed.md

@@ -18,7 +18,7 @@ ms.custom: devx-track-azurepowershell, devx-track-azurecli
 > [!IMPORTANT]
 > **Managed Run Command**  is currently available in Azure CLI, PowerShell, and API at this time. Portal functionality will soon be available.
 
-The Run Command feature uses the virtual machine (VM) agent to scripts within an Azure Windows VM. You can use these scripts for general machine or application management. They can help you quickly diagnose and remediate VM access and network issues and get the VM back to a good state.
+The Run Command feature uses the virtual machine (VM) agent to execute scripts within an Azure Windows VM. You can use these scripts for general machine or application management. They can help you quickly diagnose and remediate VM access and network issues and get the VM back to a good state.
 
 The *updated* managed Run Command uses the same VM agent channel to execute scripts and provides the following enhancements over the [original action orientated Run Command](run-command.md): 
 - Support for updated Run Command through ARM deployment template