Merge pull request #284743 from MicrosoftDocs/main

8/15 11:00 AM IST Publish

Author: Saisang

.openpublishing.redirection.virtual-machines.json

@@ -4,6 +4,6 @@
             "source_path_from_root": "/articles/virtual-machines/security-recommendations.md",
             "redirect_url": "/security/benchmark/azure/baselines/virtual-machines-windows-virtual-machines-security-baseline",
             "redirect_document_id": false
-        }
+        }        
     ]
 }

articles/ai-services/openai/api-version-deprecation.md

@@ -69,9 +69,9 @@ This version contains support for the latest GA features like Whisper, DALL-E 3,
 
 We recommend first testing the upgrade to new API versions to confirm there's no impact to your application from the API update before making the change globally across your environment.
 
-If you're using the OpenAI Python client library or the REST API, you'll need to update your code directly to the latest preview API version.
+If you're using the OpenAI Python or JavaScript client libraries, or the REST API, you'll need to update your code directly to the latest preview API version.
 
-If you're using one of the Azure OpenAI SDKs for C#, Go, Java, or JavaScript you'll instead need to update to the latest version of the SDK. Each SDK release is hardcoded to work with specific versions of the Azure OpenAI API.
+If you're using one of the Azure OpenAI SDKs for C#, Go, or Java, you'll instead need to update to the latest version of the SDK. Each SDK release is hardcoded to work with specific versions of the Azure OpenAI API.
 
 ## Next steps
 

articles/ai-services/translator/containers/translate-text-parameters.md

@@ -7,7 +7,7 @@ manager: nitinme
 
 ms.service: azure-ai-translator
 ms.topic: reference
-ms.date: 04/29/2024
+ms.date: 08/14/2024
 ms.author: lajanuar
 ---
 
@@ -90,7 +90,7 @@ The body of the request is a JSON array. Each array element is a JSON object wit
 The following limitations apply:
 
 * The array can have at most 100 elements.
-* The entire text included in the request can't exceed 10,000 characters including spaces.
+* The entire text included in the request can't exceed 50,000 characters including spaces.
 
 ## Response body
 
@@ -380,13 +380,13 @@ This feature works the same way with `textType=text` or with `textType=html`. Th
 
 ## Request limits
 
-Each translate request is limited to 10,000 characters, across all the target languages you're translating to. For example, sending a translate request of 3,000 characters to translate to three different languages results in a request size of 3000x3 = 9,000 characters, which satisfy the request limit. You're charged per character, not by the number of requests. We recommended sending shorter requests.
+Each translate request is limited to 50,000 characters, across all the target languages you're translating to. For example, sending a translate request of 3,000 characters to translate to three different languages results in a request size of 3000x3 = 9,000 characters, which satisfy the request limit. You're charged per character, not by the number of requests. We recommended sending shorter requests.
 
 The following table lists array element and character limits for the Translator **translation** operation.
 
 | Operation | Maximum size of array element | Maximum number of array elements | Maximum request size (characters) |
 |:----|:----|:----|:----|
-| translate | 10,000 | 100 | 10,000 |
+| translate | 10,000 | 100 | 50,000 |
 
 ## Use docker compose: Translator with supporting containers
 

articles/ai-studio/toc.yml

@@ -104,6 +104,8 @@ items:
         href: how-to/deploy-models-cohere-command.md
       - name: Cohere Embed models
         href: how-to/deploy-models-cohere-embed.md
+      - name: Cohere Rerank models
+        href: how-to/deploy-models-cohere-rerank.md
     - name: Meta Llama models
       items:
       - name: Meta Llama family models

articles/app-service/webjobs-create.md

@@ -17,27 +17,23 @@ adobe-target-content: ./webjobs-create-ieux
 
 # Run background tasks with WebJobs in Azure App Service
 
-=======
-> [!NOTE]
-> WebJobs for **Windows container**, **Linux code**, and **Linux container** is in preview. WebJobs for Windows code is generally available and not in preview.
-
-
-[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
-
 Deploy WebJobs by using the [Azure portal](https://portal.azure.com) to upload an executable or script. You can run background tasks in the Azure App Service.
 
 If instead of the Azure App Service, you're using Visual Studio to develop and deploy WebJobs, see [Deploy WebJobs using Visual Studio](webjobs-dotnet-deploy-vs.md).
 
+> [!NOTE]
+> WebJobs for **Windows container**, **Linux code**, and **Linux container** is in preview. WebJobs for Windows code is generally available and not in preview.
+
 ## Overview
 
 WebJobs is a feature of [Azure App Service](index.yml) that enables you to run a program or script in the same instance as a web app. All app service plans support WebJobs. There's no extra cost to use WebJobs.
 
+[!INCLUDE [regionalization-note](./includes/regionalization-note.md)]
+
 You can use the Azure WebJobs SDK with WebJobs to simplify many programming tasks. For more information, see [What is the WebJobs SDK](https://github.com/Azure/azure-webjobs-sdk/wiki).
 
 Azure Functions provides another way to run programs and scripts. For a comparison between WebJobs and Functions, see [Choose between Flow, Logic Apps, Functions, and WebJobs](../azure-functions/functions-compare-logic-apps-ms-flow-webjobs.md).
 
-
-
 ## WebJob types
 
 ### <a name="acceptablefiles"></a>Supported file types for scripts or programs

articles/azure-arc/kubernetes/azure-rbac.md

@@ -33,8 +33,11 @@ For a conceptual overview of this feature, see [Azure RBAC on Azure Arc-enabled
   - [Upgrade your agents](agent-upgrade.md#manually-upgrade-agents) to the latest version.
 
 > [!NOTE]
-> You can't set up this feature for Red Hat OpenShift, or for managed Kubernetes offerings of cloud providers like Elastic Kubernetes Service or Google Kubernetes Engine where the user doesn't have access to the API server of the cluster. For Azure Kubernetes Service (AKS) clusters, this [feature is available natively](/azure/aks/manage-azure-rbac) and doesn't require the AKS cluster to be connected to Azure Arc.
-
+> Azure RBAC is not available for Red Hat OpenShift or managed Kubernetes offerings where user access to the API server is restricted (ex: Amazon Elastic Kubernetes Service (EKS), Google Kubernetes Engine (GKE)).
+>
+> Azure RBAC does not currently support Kubernetes clusters operating on ARM64 architecture. Please use [Kubernetes RBAC](identity-access-overview.md#kubernetes-rbac-authorization) to manage access control for ARM64-based Kubernetes clusters. 
+> 
+> For Azure Kubernetes Service (AKS) clusters, this [feature is available natively](/azure/aks/manage-azure-rbac) and doesn't require the AKS cluster to be connected to Azure Arc.
 ## Enable Azure RBAC on the cluster
 
 1. Get the cluster MSI identity by running the following command:

articles/azure-fluid-relay/TOC.yml

@@ -50,6 +50,8 @@
       href: how-tos/container-recovery.md
     - name: 'How to: Use audience features in the Fluid Framework'
       href: how-tos/use-audience-in-fluid.md
+    - name: 'How to: Rotate Azure Fluid Relay access keys'
+      href: how-tos/rotate-fluid-relay-access-keys.md
 - name: Reference
   items:
     - name: Service limits

articles/azure-fluid-relay/how-tos/rotate-fluid-relay-access-keys.md

@@ -0,0 +1,101 @@
+---
+description: Learn how to rotate Azure Fluid Relay access keys.
+title: Rotate Azure Fluid Relay access keys
+ms.date: 08/13/2024
+ms.service: azure-fluid
+ms.topic: reference
+---
+
+# How to rotate Fluid Relay Server access keys
+This article provides an overview of managing access keys (tenant keys) in Azure Fluid Relay Service. Microsoft recommends that you regularly rotate your keys for better security.
+
+## Primary / Secondary keys
+Customers use the access keys to sign the access tokens that are used to access Azure Fluid Relay Services. Azure Fluid Relay uses the keys to validate the tokens.
+
+Two keys are associated with each Azure Fluid Relay Service: a primary key and secondary key. The purpose of dual keys is to let you regenerate, or roll, keys, providing continuous access to your account and data.
+
+## View your access keys
+
+### [Azure portal](#tab/azure-portal)
+To see your access keys, search for your Azure Fluid Relay Service in the Azure portal. On the left menu of Azure Fluid Relay Service page, select **Settings**. Then, select **Access Keys**. Select the **Copy** button to copy the selected key.
+
+[![Screenshot that shows the Access Keys page.](../images/rotate-tenant-keys.png)](../images/rotate-tenant-keys.png#lightbox)
+
+### [PowerShell](#tab/azure-powershell)
+To retrieve your access keys with PowerShell, you need to install [Azure Fluid Relay module](/powershell/module/az.fluidrelay) first.
+
+```azurepowershell
+Install-Module Az.FluidRelay
+```
+
+Then call the [Get-AzFluidRelayServerKey](/powershell/module/az.fluidrelay/get-azfluidrelayserverkey) command.
+
+```azurepowershell
+Get-AzFluidRelayServerKey -FluidRelayServerName <Fluid Relay Service name> -ResourceGroup <resource group> -SubscriptionId <subscription id>
+```
+
+### [Azure CLI](#tab/azure-cli)
+To retrieve your access keys with Azure CLI, you need to install [fluid-relay](/cli/azure/fluid-relay) extension first. See [instructions](/cli/azure/azure-cli-extensions-overview).
+
+Then use [az fluid-relay server list-key](/cli/azure/fluid-relay/server?view=azure-cli-latest&preserve-view=true#az-fluid-relay-server-list-key) command to list access keys.
+
+```azurecli
+az fluid-relay server list-key --resource-group <resource group> --server-name <Fluid Relay Service name>
+```
+
+---
+
+## Rotate your access keys
+Two access keys are assigned so that your Azure Fluid Relay Service does not have to be taken offline when you rotate a key. Having two keys ensures that your application maintains access to Azure Fluid Relay throughout the process. You should rotate one of two keys at one time to avoid service interruptions.
+
+The process of rotating primary and secondary keys is the same. The following steps are for primary keys.
+
+### [Azure portal](#tab/azure-portal)
+To rotate your Azure Fluid Relay primary key in the Azure portal:
+
+1. Update the access keys in your application code to use the secondary access key for the Azure Fluid Relay.
+
+2. Navigate to your Fluid Relay Service in the Azure portal.
+
+3. Under **Settings**, select **Access key**.
+
+4. To regenerate the primary access key for your Azure Fluid Relay Service, select the **Regenerate Primary Key** button above the Access Information.
+
+5. Update the primary key in your code to reference the new primary access key.
+
+### [PowerShell](#tab/azure-powershell)
+To rotate your Fluid Relay primary key with PowerShell, you need to install [Azure Fluid Relay module](/powershell/module/az.fluidrelay) first.
+
+```azurepowershell
+Install-Module Az.FluidRelay
+```
+
+Then follow steps below:
+
+1. Update the access keys in your application code to use the secondary access key for the Azure Fluid Relay.
+
+2. Call the [New-AzFluidRelayServerKey](/powershell/module/az.fluidrelay/new-azfluidrelayserverkey) command to regenerate the primary access key, as shown in the following example:
+
+
+```azurepowershell
+New-AzFluidRelayServerKey -FluidRelayServerName <Fluid Relay Service name> -ResourceGroup <resource group> -KeyName <key name>
+```
+
+3. Update the primary key in your code to reference the new primary access key.
+
+### [Azure CLI](#tab/azure-cli)
+To rotate your Fluid Relay primary key with Azure CLI, you need to install [fluid-relay](/cli/azure/fluid-relay) extension first. See [instructions](/cli/azure/azure-cli-extensions-overview).
+
+Then follow steps below:
+
+1. Update the access keys in your application code to use the secondary access key for the Azure Fluid Relay.
+
+2. Call the [az fluid-relay server regenerate-key](/cli/azure/fluid-relay/server?view=azure-cli-latest&preserve-view=true#az-fluid-relay-server-regenerate-key) command to regenerate the primary access key, as shown in the following example:
+
+```azurecli
+az fluid-relay server regenerate-key --resource-group <resource group>--server-name <Fluid Relay Service name>--key-name <key name>
+```
+
+3. Update the primary key in your code to reference the new primary access key.
+
+---

articles/azure-fluid-relay/images/rotate-tenant-keys.png

@@ -55,6 +55,11 @@ public static class QueueFunctions
 
 ---
 
+For an end-to-end example of how to configure an output binding to Queue storage, see one of these articles:
+
++ [Connect functions to Azure Storage using Visual Studio](functions-add-output-binding-storage-queue-vs.md)
++ [Connect functions to Azure Storage using Visual Studio Code](functions-add-output-binding-storage-queue-vs-code.md?pivots=programming-language-csharp)
++ [Connect functions to Azure Storage using command line tools](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-csharp)
 ::: zone-end
 ::: zone pivot="programming-language-java"
 
@@ -74,6 +79,10 @@ The following example shows a Java function that creates a queue message for whe
 
 In the [Java functions runtime library](/java/api/overview/azure/functions/runtime), use the `@QueueOutput` annotation on parameters whose value would be written to Queue storage.  The parameter type should be `OutputBinding<T>`, where `T` is any native Java type of a POJO.
 
+For an end-to-end example of how to configure an output binding to Queue storage, see one of these articles:
+
++ [Connect functions to Azure Storage using Visual Studio Code](functions-add-output-binding-storage-queue-vs-code.md?pivots=programming-language-java)
++ [Connect functions to Azure Storage using command line tools](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-java)
 ::: zone-end  
 ::: zone pivot="programming-language-typescript"  
 
@@ -106,6 +115,11 @@ To output multiple messages, return an array instead of a single object. For exa
 
 :::code language="javascript" source="~/azure-functions-nodejs-v4/js/src/functions/storageQueueOutput2.js" id="displayInDocs" :::
 
+For an end-to-end example of how to configure an output binding to Queue storage, see one of these articles:
+
++ [Connect functions to Azure Storage using Visual Studio Code](functions-add-output-binding-storage-queue-vs-code.md?pivots=programming-language-javascript)
++ [Connect functions to Azure Storage using command line tools](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-javascript)
+
 # [Model v3](#tab/nodejs-v3)
 
 The following example shows an HTTP trigger binding in a *function.json* file and a [JavaScript function](functions-reference-node.md) that uses the binding. The function creates a queue item for each HTTP request received.
@@ -231,6 +245,10 @@ Push-OutputBinding -Name Response -Value ([HttpResponseContext]@{
 })
 ```
 
+For an end-to-end example of how to configure an output binding to Queue storage, see one of these articles:
+
++ [Connect functions to Azure Storage using Visual Studio Code](functions-add-output-binding-storage-queue-vs-code.md?pivots=programming-language-powershell)
++ [Connect functions to Azure Storage using command line tools](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-powershell)
 ::: zone-end  
 ::: zone pivot="programming-language-python"  
 
@@ -258,6 +276,12 @@ def main(req: func.HttpRequest, msg: func.Out[str]) -> func.HttpResponse:
     logging.info(f'name: {name}')
     return 'OK'
 ```
+
+For an end-to-end example of how to configure an output binding to Queue storage, see one of these articles:
+
++ [Connect functions to Azure Storage using Visual Studio Code](functions-add-output-binding-storage-queue-vs-code.md?pivots=programming-language-python)
++ [Connect functions to Azure Storage using command line tools](functions-add-output-binding-storage-queue-cli.md?pivots=programming-language-python)
+  
 # [v1](#tab/python-v1)
 
 A Storage queue binding is defined in *function.json* where *type* is set to `queue`.