Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into smb

Author: stevenmatthew

articles/ai-services/openai/how-to/embeddings.md

@@ -48,7 +48,7 @@ embeddings = response['data'][0]['embedding']
 print(embeddings)
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```python
 import os

articles/ai-services/openai/includes/chat-completion.md

@@ -69,7 +69,7 @@ JSON formatting added artificially for ease of reading.
 
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```python
 import os
@@ -330,7 +330,7 @@ while True:
     print("\n" + response['choices'][0]['message']['content'] + "\n")
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```python
 import os
@@ -452,7 +452,7 @@ while True:
     print("\n" + response['choices'][0]['message']['content'] + "\n")
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```python
 import tiktoken

articles/ai-services/openai/includes/chatgpt-python.md

@@ -36,7 +36,7 @@ Install the OpenAI Python client library with:
 pip install openai==0.28.1
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```console
 pip install openai
@@ -86,7 +86,7 @@ print(response)
 print(response['choices'][0]['message']['content'])
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 You need to set the `model` variable to the deployment name you chose when you deployed the GPT-3.5-Turbo or GPT-4 models. Entering the model name will result in an error unless you chose a deployment name that is identical to the underlying model name.
 

articles/ai-services/openai/includes/python.md

@@ -35,7 +35,7 @@ Install the OpenAI Python client library with:
 pip install openai==0.28.1
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```console
 pip install openai
@@ -95,7 +95,7 @@ text = response['choices'][0]['text'].replace('\n', '').replace(' .', '.').strip
 print(start_phrase+text)
 ```
 
-# [OpenAI Python 1.0](#tab/python-new)
+# [OpenAI Python 1.x](#tab/python-new)
 
 ```python
 import os

articles/aks/create-node-pools.md

@@ -3,7 +3,7 @@ title: Create node pools in Azure Kubernetes Service (AKS)
 description: Learn how to create multiple node pools for a cluster in Azure Kubernetes Service (AKS).
 ms.topic: article
 ms.custom: event-tier1-build-2022, ignite-2022, devx-track-azurecli, build-2023
-ms.date: 07/18/2023
+ms.date: 11/06/2023
 ---
 
 # Create node pools for a cluster in Azure Kubernetes Service (AKS)
@@ -13,7 +13,7 @@ In Azure Kubernetes Service (AKS), nodes of the same configuration are grouped t
 To support applications that have different compute or storage demands, you can create *user node pools*. System node pools serve the primary purpose of hosting critical system pods such as CoreDNS and `konnectivity`. User node pools serve the primary purpose of hosting your application pods. For example, use more user node pools to provide GPUs for compute-intensive applications, or access to high-performance SSD storage. However, if you wish to have only one pool in your AKS cluster, you can schedule application pods on system node pools.
 
 > [!NOTE]
-> This feature enables more control over creating and managing multiple node pools and requires separate commands for create/update/delete operations. Previously, cluster operations through `az aks create` or `az aks update` used the managedCluster API and were the only options to change your control plane and a single node pool. This feature exposes a separate operation set for agent pools through the agentPool API and requires use of the `az aks nodepool` command set to execute operations on an individual node pool.
+> This feature enables more control over creating and managing multiple node pools and requires separate commands for *create/update/delete* (CRUD) operations. Previously, cluster operations through [`az aks create`][az-aks-create] or [`az aks update`][az-aks-update] used the managedCluster API and were the only options to change your control plane and a single node pool. This feature exposes a separate operation set for agent pools through the agentPool API and requires use of the [`az aks nodepool`][az-aks-nodepool] command set to execute operations on an individual node pool.
 
 This article shows you how to create one or more node pools in an AKS cluster.
 
@@ -29,7 +29,7 @@ The following limitations apply when you create AKS clusters that support multip
 * See [Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)](quotas-skus-regions.md).
 * You can delete system node pools if you have another system node pool to take its place in the AKS cluster.
 * System pools must contain at least one node, and user node pools may contain zero or more nodes.
-* The AKS cluster must use the Standard SKU load balancer to use multiple node pools. The feature isn't supported with Basic SKU load balancers.
+* The AKS cluster must use the Standard SKU load balancer to use multiple node pools. This feature isn't supported with Basic SKU load balancers.
 * The AKS cluster must use Virtual Machine Scale Sets for the nodes.
 * The name of a node pool may only contain lowercase alphanumeric characters and must begin with a lowercase letter.
   * For Linux node pools, the length must be between 1-11 characters.
@@ -182,8 +182,8 @@ A workload may require splitting cluster nodes into separate pools for logical i
 
 * All subnets assigned to node pools must belong to the same virtual network.
 * System pods must have access to all nodes and pods in the cluster to provide critical functionality, such as DNS resolution and tunneling kubectl logs/exec/port-forward proxy.
-* If you expand your VNET after creating the cluster, you must update your cluster before adding a subnet outside the original CIDR block. While AKS errors-out on the agent pool add, the `aks-preview` Azure CLI extension (version 0.5.66+) now supports running `az aks update -g <resourceGroup> -n <clusterName>` without any optional arguments. This command performs an update operation without making any changes, which can recover a cluster stuck in a failed state.
-* In clusters with Kubernetes version < 1.23.3, kube-proxy will SNAT traffic from new subnets, which can cause Azure Network Policy to drop the packets.
+* If you expand your VNET after creating the cluster, you must update your cluster before adding a subnet outside the original CIDR block. While AKS errors-out on the agent pool add, the `aks-preview` Azure CLI extension (version 0.5.66 and higher) now supports running [`az aks update`][az-aks-update] command with only the required `-g <resourceGroup> -n <clusterName>` arguments. This command performs an update operation without making any changes, which can recover a cluster stuck in a failed state.
+* In clusters with Kubernetes version less than 1.23.3, kube-proxy SNATs traffic from new subnets, which can cause Azure Network Policy to drop the packets.
 * Windows nodes SNAT traffic to the new subnets until the node pool is reimaged.
 * Internal load balancers default to one of the node pool subnets.
 
@@ -212,8 +212,8 @@ Beginning in Kubernetes version 1.20 and higher, you can specify `containerd` as
 > When using `containerd` with Windows Server 2019 node pools:
 >
 > * Both the control plane and Windows Server 2019 node pools must use Kubernetes version 1.20 or greater.
-> * When you create or update a node pool to run Windows Server containers, the default value for `--node-vm-size` is *Standard_D2s_v3*, which was minimum recommended size for Windows Server 2019 node pools prior to Kubernetes 1.20. The minimum recommended size for Windows Server 2019 node pools using `containerd` is *Standard_D4s_v3*. When setting the `--node-vm-size` parameter, please check the list of [restricted VM sizes][restricted-vm-sizes].
-> * We highly recommended using [taints or labels][aks-taints] with your Windows Server 2019 node pools running `containerd` and tolerations or node selectors with your deployments to guarantee your workloads are scheduled correctly.
+> * When you create or update a node pool to run Windows Server containers, the default value for `--node-vm-size` is *Standard_D2s_v3*, which was minimum recommended size for Windows Server 2019 node pools prior to Kubernetes version 1.20. The minimum recommended size for Windows Server 2019 node pools using `containerd` is *Standard_D4s_v3*. When setting the `--node-vm-size` parameter, check the list of [restricted VM sizes][restricted-vm-sizes].
+> * We recommended using [taints or labels][aks-taints] with your Windows Server 2019 node pools running `containerd` and tolerations or node selectors with your deployments to guarantee your workloads are scheduled correctly.
 
 ### Add a Windows Server node pool with `containerd`
 
@@ -285,7 +285,9 @@ In this article, you learned how to create multiple node pools in an AKS cluster
 [arm-sku-vm3]: ../virtual-machines/epsv5-epdsv5-series.md
 [az-aks-get-credentials]: /cli/azure/aks#az_aks_get_credentials
 [az-aks-create]: /cli/azure/aks#az_aks_create
+[az-aks-update]: /cli/azure/aks#az_aks_update
 [az-aks-delete]: /cli/azure/aks#az_aks_delete
+[az-aks-nodepool]: /cli/azure/aks/nodepool
 [az-aks-nodepool-add]: /cli/azure/aks/nodepool#az_aks_nodepool_add
 [az-aks-nodepool-list]: /cli/azure/aks/nodepool#az_aks_nodepool_list
 [az-aks-nodepool-upgrade]: /cli/azure/aks/nodepool#az_aks_nodepool_upgrade

articles/aks/egress-outboundtype.md

@@ -6,7 +6,7 @@ ms.subservice: aks-networking
 ms.custom: devx-track-azurecli
 ms.author: allensu
 ms.topic: how-to
-ms.date: 06/06/2023
+ms.date: 11/06/2023
 #Customer intent: As a cluster operator, I want to define my own egress paths with user-defined routes. Since I define this up front I do not want AKS provided load balancer configurations.
 ---
 
@@ -15,7 +15,7 @@ ms.date: 06/06/2023
 You can customize egress for an AKS cluster to fit specific scenarios. By default, AKS will provision a standard SKU load balancer to be set up and used for egress. However, the default setup may not meet the requirements of all scenarios if public IPs are disallowed or additional hops are required for egress.
 
 This article covers the various types of outbound connectivity that are available in AKS clusters.
-how 
+ 
 > [!NOTE]
 > You can now update the `outboundType` after cluster creation. This feature is in preview. See [Updating `outboundType after cluster creation (preview)](#updating-outboundtype-after-cluster-creation-preview).
 

articles/app-service/identity-scenarios.md

@@ -1,16 +1,16 @@
 ---
 title: 'App Service authentication recommendations'
-description: There are several different authentication solutions available for web apps or web APIs hosted on App Service. This article provides recommendations on which auth solution(s) can be used for specific scenarios such as quickly and simply limiting access to your web app, custom authorization, and incremental consent.  
+description: Learn about the different authentication options available for web apps or web APIs hosted on App Service. This article provides recommendations on which auth solution(s) can be used for specific scenarios such as quickly and simply limiting access to your web app, custom authorization, and incremental consent.  Learn about the benefits and drawbacks of using built-in authentication versus code implementation of authentication.
 author: rwike77
 manager: CelesteDG
 ms.author: ryanwi
 ms.topic: conceptual
-ms.date: 08/10/2023
+ms.date: 10/31/2023
 ms.custom: AppServiceIdentity
 ---
 # Authentication scenarios and recommendations
 
-If you have a web app or an API running in Azure App Service, you can restrict access to it based on the identity of the users or applications that request it. App Service offers several authentication solutions to help you achieve this goal. In this article, you will learn about the different authentication solutions, their benefits and drawbacks, and which authentication solution to use for specific scenarios.
+If you have a web app or an API running in Azure App Service, you can restrict access to it based on the identity of the users or applications that request it. App Service offers several authentication solutions to help you achieve this goal. In this article, you will learn about the different authentication options, their benefits and drawbacks, and which authentication solution to use for specific scenarios.  
 
 ## Authentication solutions
 

articles/azure-cache-for-redis/cache-best-practices-performance.md

@@ -101,6 +101,10 @@ redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t  GET -n
 >These numbers might change as we post newer results periodically.
 >
 
+>[!IMPORTANT]
+>Microsoft periodically updates the underlying VM used in cache instances. This can change the performance characteristics from cache to cache and from region to region. The example benchmarking values on this page reflect older generation cache hardware in a single region. You may see better or different results in practice.
+>
+
 ### Standard tier
 
 | Instance | Size | vCPUs | Expected network bandwidth (Mbps)| GET requests per second without SSL (1-kB value size) | GET requests per second with SSL (1-kB value size) |

articles/azure-functions/durable/durable-functions-bindings.md

@@ -21,14 +21,9 @@ Make sure to choose your Durable Functions development language at the top of th
 
 ## Python v2 programming model
 
-Durable Functions provides preview support of the new [Python v2 programming model](../functions-reference-python.md?pivots=python-mode-decorators). To use the v2 model, you must install the Durable Functions SDK, which is the PyPI package `azure-functions-durable`, version `1.2.2` or a later version. During the preview, you can provide feedback and suggestions in the [Durable Functions SDK for Python repo](https://github.com/Azure/azure-functions-durable-python/issues).
-
-Using [Extension Bundles](../functions-bindings-register.md#extension-bundles) isn't currently supported for the v2 model with Durable Functions. You'll instead need to manage your extensions manually as follows:
-
-1. Remove the `extensionBundle` section of your `host.json` file.
- 
-1. Run the `func extensions install --package Microsoft.Azure.WebJobs.Extensions.DurableTask --version 2.9.1` command on your terminal. This installs the Durable Functions extension for your app, which allows you to use the v2 model preview. For more information, see [func extensions install](../functions-core-tools-reference.md#func-extensions-install).
+Durable Functions is supported in the new [Python v2 programming model](../functions-reference-python.md?pivots=python-mode-decorators). To use the v2 model, you must install the Durable Functions SDK, which is the PyPI package `azure-functions-durable`, version `1.2.2` or a later version. You must also check `host.json` to make sure your app is referencing [Extension Bundles](../functions-bindings-register.md#extension-bundles) version 4.x to use the v2 model with Durable Functions. 
 
+You can provide feedback and suggestions in the [Durable Functions SDK for Python repo](https://github.com/Azure/azure-functions-durable-python/issues).
 ::: zone-end
 
 ## Orchestration trigger

articles/azure-functions/functions-bindings-event-grid-output.md

@@ -576,6 +576,7 @@ The following table explains the properties that you can set on the `options` ob
 |---------|---------|----------------------|
 |**topicEndpointUri** | The name of an app setting that contains the URI for the custom topic, such as `MyTopicEndpointUri`. |
 |**topicKeySetting** | The name of an app setting that contains an access key for the custom topic. |
+|**connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. When setting the `connection` property, the `topicEndpointUri` and `topicKeySetting` properties shouldn't be set. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication).  | 
 
 # [Model v3](#tab/nodejs-v3)
 
@@ -588,7 +589,7 @@ The following table explains the binding configuration properties that you set i
 |**name** | The variable name used in function code that represents the event. |
 |**topicEndpointUri** | The name of an app setting that contains the URI for the custom topic, such as `MyTopicEndpointUri`. |
 |**topicKeySetting** | The name of an app setting that contains an access key for the custom topic. |
-|**connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication).  | 
+|**connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. When setting the `connection` property, the `topicEndpointUri` and `topicKeySetting` properties shouldn't be set. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication).  | 
 
 ---
 
@@ -722,15 +723,15 @@ Use the following steps to configure a topic key:
 
 When using version 3.3.x or higher of the extension, you can connect to an Event Grid topic using an [Microsoft Entra identity](../active-directory/fundamentals/active-directory-whatis.md) to avoid having to obtain and work with topic keys. 
 
-To do this, create an application setting that returns the topic endpoint URI, where the name of the setting combines a unique _common prefix_, such as `myawesometopic`, with the value `__topicEndpointUri`. You then use the common prefix `myawesometopic` when you define the `Connection` property in the binding.
+You need to create an application setting that returns the topic endpoint URI. The name of the setting should combine a _unique common prefix_ (for example, `myawesometopic`) with the value `__topicEndpointUri`. Then, you must use that common prefix (in this case, `myawesometopic`) when you define the `Connection` property in the binding.
 
 In this mode, the extension requires the following properties:
 
 | Property           | Environment variable template                | Description         | Example value |
 |--------------------|----------------------------------------------|---------------------|---------------|
 | Topic Endpoint URI | `<CONNECTION_NAME_PREFIX>__topicEndpointUri` | The topic endpoint. | `https://<topic-name>.centralus-1.eventgrid.azure.net/api/events`  |
 
-More properties may be set to customize the connection. See [Common properties for identity-based connections](functions-reference.md#common-properties-for-identity-based-connections).
+More properties can be used to customize the connection. See [Common properties for identity-based connections](functions-reference.md#common-properties-for-identity-based-connections).
 
 > [!NOTE]
 > When using [Azure App Configuration](../azure-app-configuration/quickstart-azure-functions-csharp.md) or [Key Vault](../key-vault/general/overview.md) to provide settings for managed identity-based connections, setting names should use a valid key separator such as `:` or `/` in place of the `__` to ensure names are resolved correctly.