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

Author: asudbring

articles/advisor/advisor-alerts-bicep.md

@@ -1,9 +1,7 @@
 ---
 title: Create Azure Advisor alerts for new recommendations using Bicep
 description: Learn how to set up an alert for new recommendations from Azure Advisor using Bicep.
-author: orspod
 ms.topic: quickstart
-ms.author: orspodek
 ms.custom: subject-armqs, mode-arm, devx-track-bicep
 ms.date: 04/26/2022
 ---

articles/advisor/advisor-azure-resource-graph.md

@@ -1,11 +1,8 @@
 ---
 title: Advisor data in Azure Resource Graph
 description: Make queries for Advisor data in Azure Resource Graph
-author: orspod
 ms.topic: article
 ms.date: 03/12/2020
-ms.author: orspodek
-
 ---
 
 # Query for Advisor data in Resource Graph Explorer (Azure Resource Graph)

articles/advisor/advisor-quick-fix.md

@@ -1,11 +1,8 @@
 ---
 title: Quick Fix remediation for Advisor recommendations
 description: Perform bulk remediation using Quick Fix in Advisor
-author: orspod
 ms.topic: article
 ms.date: 03/13/2020
-ms.author: orspodek
-
 ---
 
 # Quick Fix remediation for Advisor

articles/advisor/advisor-recommendations-digest.md

@@ -1,12 +1,8 @@
 ---
-
 title: Recommendation digest for Azure Advisor
 description: Get periodic summary for your active recommendations
-author: orspod
 ms.topic: article
 ms.date: 03/16/2020
-ms.author: orspodek
-
 ---
 
 # Configure periodic summary for recommendations

articles/ai-services/openai/concepts/models.md

@@ -254,13 +254,18 @@ The following Embeddings models are available with [Azure Government](/azure/azu
 
 ### Assistants (Preview)
 
-For Assistants you need a combination of a supported model and a supported region. Certain tools and capabilities require the latest models. For example, [parallel function calling](../how-to/assistant-functions.md) requires the latest 1106 models.
+For Assistants you need a combination of a supported model, and a supported region. Certain tools and capabilities require the latest models. The following models are available in the Assistants API, SDK, Azure AI Studio and Azure OpenAI Studio..
 
 | Region | `gpt-35-turbo (0613)` | `gpt-35-turbo (1106)` | `gpt-4 (0613)` | `gpt-4 (1106)` | `gpt-4 (0125)` | 
 |-----|---|---|---|---|---|
 | Australia East | ✅ | ✅ | ✅ |✅ | |
-| East US 2 | ✅ | | ✅ |✅ | |
-| Sweden Central | ✅ |✅ |✅ |✅| |
+| East US  | ✅ | | | | ✅ |
+| East US 2 | ✅ |  | ✅ |✅ | |
+| France Central  | ✅ | ✅ |✅ |✅ |  |
+| Norway East | |  | | ✅ |  |
+| Sweden Central  | ✅ |✅ |✅ |✅| |
+| UK South  | ✅ |  ✅ | ✅ |✅ | |
+
 
 For information on Provisioned Throughput Unit (PTU) availability, see [provisioned throughput](./provisioned-throughput.md). 
 

articles/ai-services/openai/how-to/use-your-data-securely.md

@@ -105,7 +105,9 @@ When using the API, pass the `filter` parameter in each API request. For example
 
 ## Resources configuration
 
-Use the following sections to configure your resources for optimal secure usage. Even if you plan to only secure part of your resources, you still need to follow all the steps below.
+Use the following sections to configure your resources for optimal secure usage. Even if you plan to only secure part of your resources, you still need to follow all the steps below. 
+
+This article describes network settings related to disabling public network for Azure OpenAI resources, Azure AI search resources, and storage accounts. Using selected networks with IP rules is not supported, because the services' IP addresses are dynamic.
 
 ## Create resource group
 
@@ -372,40 +374,4 @@ curl -i -X GET https://my-resource.openai.azure.com/openai/extensions/on-your-da
 
 ### Inference API
 
-See the [inference API reference article](/azure/ai-services/openai/reference#completions-extensions) for details on the request and response objects used by the inference API.   
-
-More notes:
-
-* **Do not** set `dataSources[0].parameters.key`. The service uses system assigned managed identity to authenticate the Azure AI Search.
-* **Do not** set `embeddingEndpoint` or `embeddingKey`. Instead, to enable vector search (with `queryType` set properly), use `embeddingDeploymentName`.
-
-Example:
-
-```bash
-accessToken=$(az account get-access-token --resource https://cognitiveservices.azure.com/ --query "accessToken" --output tsv)
-curl -i -X POST https://my-resource.openai.azure.com/openai/deployments/turbo/extensions/chat/completions?api-version=2023-10-01-preview \
--H "Content-Type: application/json" \
--H "Authorization: Bearer $accessToken" \
--d \
-'
-{
-    "dataSources": [
-        {
-            "type": "AzureCognitiveSearch",
-            "parameters": {
-                "endpoint": "https://my-search-service.search.windows.net",
-                "indexName": "my-index",
-                "queryType": "vector",
-                "embeddingDeploymentName": "ada"
-            }
-        }
-    ],
-    "messages": [
-        {
-            "role": "user",
-            "content": "Who is the primary DRI for QnA v2 Authoring service?"
-        }
-    ]
-}
-'
-```
+See the [inference API reference article](../references/on-your-data.md) for details on the request and response objects used by the inference API.   

articles/aks/azure-cni-overlay.md

@@ -196,16 +196,13 @@ Since the cluster is already using a private CIDR for pods which doesn't overlap
 > [!NOTE]
 > When upgrading from Kubenet to CNI Overlay, the route table will no longer be required for pod routing. If the cluster is using a customer provided route table, the routes which were being used to direct pod traffic to the correct node will automatically be deleted during the migration operation. If the cluster is using a managed route table (the route table was created by AKS and lives in the node resource group) then that route table will be deleted as part of the migration.
 
-## Dual-stack Networking (Preview)
+## Dual-stack Networking
 
 You can deploy your AKS clusters in a dual-stack mode when using Overlay networking and a dual-stack Azure virtual network. In this configuration, nodes receive both an IPv4 and IPv6 address from the Azure virtual network subnet. Pods receive both an IPv4 and IPv6 address from a logically different address space to the Azure virtual network subnet of the nodes. Network address translation (NAT) is then configured so that the pods can reach resources on the Azure virtual network. The source IP address of the traffic is NAT'd to the node's primary IP address of the same family (IPv4 to IPv4 and IPv6 to IPv6).
 
-[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
-
 ### Prerequisites
 
   - You must have Azure CLI 2.48.0 or later installed.
-  - You must register the `Microsoft.ContainerService` `AzureOverlayDualStackPreview` feature flag.
   - Kubernetes version 1.26.3 or greater.
 
 ### Limitations
@@ -231,26 +228,6 @@ The following attributes are provided to support dual-stack clusters:
   * If no values are supplied, the default value `10.0.0.0/16,fd12:3456:789a:1::/108` is used.
   * The IPv6 subnet assigned to `--service-cidrs` can be no larger than a /108.
 
-### Register the `AzureOverlayDualStackPreview` feature flag
-
-1. Register the `AzureOverlayDualStackPreview` feature flag using the [`az feature register`][az-feature-register] command. It takes a few minutes for the status to show *Registered*.
-
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "AzureOverlayDualStackPreview"
-```
-
-2. Verify the registration status using the [`az feature show`][az-feature-show] command.
-
-```azurecli-interactive
-az feature show --namespace "Microsoft.ContainerService" --name "AzureOverlayDualStackPreview"
-```
-
-3. When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider using the [`az provider register`][az-provider-register] command.
-
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-```
-
 ### Create a dual-stack AKS cluster
 
 1. Create an Azure resource group for the cluster using the [`az group create`][az-group-create] command.

articles/aks/load-balancer-standard.md

@@ -5,7 +5,7 @@ description: Learn how to use a public load balancer with a Standard SKU to expo
 ms.subservice: aks-networking
 ms.custom: devx-track-azurecli
 ms.topic: how-to
-ms.date: 10/30/2023
+ms.date: 01/23/2024
 ms.author: allensu
 author: asudbring
 #Customer intent: As a cluster operator or developer, I want to learn how to create a service in AKS that uses an Azure Load Balancer with a Standard SKU.
@@ -125,7 +125,7 @@ You can customize different settings for your standard public load balancer at c
 > [!IMPORTANT]
 > Only one outbound IP option (managed IPs, bring your own IP, or IP prefix) can be used at a given time.
 
-### Change the inbound pool type (PREVIEW)
+### Change the inbound pool type
 
 AKS nodes can be referenced in the load balancer backend pools by either their IP configuration (Azure Virtual Machine Scale Sets based membership) or by their IP address only. Utilizing the IP address based backend pool membership provides higher efficiencies when updating services and provisioning load balancers, especially at high node counts. Provisioning new clusters with IP based backend pools and converting existing clusters is now supported. When combined with NAT Gateway or user-defined routing egress types, provisioning of new nodes and services are more performant.
 
@@ -136,48 +136,13 @@ Two different pool membership types are available:
 
 #### Requirements
 
-* The `aks-preview` extension must be at least version 0.5.103.
 * The AKS cluster must be version 1.23 or newer.
 * The AKS cluster must be using standard load balancers and virtual machine scale sets.
 
 #### Limitations
 
 * Clusters using IP based backend pools are limited to 2500 nodes.
 
-[!INCLUDE [preview features callout](./includes/preview/preview-callout.md)]
-
-#### Install the aks-preview CLI extension
-
-```azurecli-interactive
-# Install the aks-preview extension
-az extension add --name aks-preview
-
-# Update the extension to make sure you have the latest version installed
-az extension update --name aks-preview
-```
-
-#### Register the `IPBasedLoadBalancerPreview` preview feature
-
-To create an AKS cluster with IP based backend pools, you must enable the `IPBasedLoadBalancerPreview` feature flag on your subscription.
-
-Register the `IPBasedLoadBalancerPreview` feature flag by using the `az feature register` command, as shown in the following example:
-
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "IPBasedLoadBalancerPreview"
-```
-
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the `az feature list` command:
-
-```azurecli-interactive
-az feature list -o table --query "[?contains(name, 'Microsoft.ContainerService/IPBasedLoadBalancerPreview')].{Name:name,State:properties.state}"
-```
-
-When the feature has been registered, refresh the registration of the *Microsoft.ContainerService* resource provider by using the `az provider register` command:
-
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-```
-
 #### Create a new AKS cluster with IP-based inbound pool membership
 
 ```azurecli-interactive

articles/aks/use-node-public-ips.md

@@ -3,7 +3,7 @@ title: Use instance-level public IPs in Azure Kubernetes Service (AKS)
 description: Learn how to manage instance-level public IPs Azure Kubernetes Service (AKS)
 ms.topic: article
 ms.custom: devx-track-azurecli
-ms.date: 1/12/2023
+ms.date: 01/23/2024
 ms.author: pahealy
 author: phealy
 ---
@@ -132,7 +132,7 @@ az aks nodepool add --cluster-name <clusterName> -n <nodepoolName> -l <location>
   --node-public-ip-tags RoutingPreference=Internet
 ```
 
-## Allow host port connections and add node pools to application security groups (PREVIEW)
+## Allow host port connections and add node pools to application security groups
 
 AKS nodes utilizing node public IPs that host services on their host address need to have an NSG rule added to allow the traffic. Adding the desired ports in the node pool configuration will create the appropriate allow rules in the cluster network security group.
 
@@ -149,47 +149,11 @@ Examples:
 - 53/udp,80/tcp
 - 50000-60000/tcp
 
-[!INCLUDE [preview features callout](includes/preview/preview-callout.md)]
-
 ### Requirements
 
 * AKS version 1.24 or greater is required.
 * Version 0.5.110 of the aks-preview extension is required.
 
-### Install the aks-preview Azure CLI extension
-
-To install the aks-preview extension, run the following command:
-
-```azurecli
-az extension add --name aks-preview
-```
-
-Run the following command to update to the latest version of the extension released:
-
-```azurecli
-az extension update --name aks-preview
-```
-
-### Register the 'NodePublicIPNSGControlPreview' feature flag
-
-Register the `NodePublicIPNSGControlPreview` feature flag by using the [az feature register][az-feature-register] command, as shown in the following example:
-
-```azurecli-interactive
-az feature register --namespace "Microsoft.ContainerService" --name "NodePublicIPNSGControlPreview"
-```
-
-It takes a few minutes for the status to show *Registered*. Verify the registration status by using the [az feature show][az-feature-show] command:
-
-```azurecli-interactive
-az feature show --namespace "Microsoft.ContainerService" --name "NodePublicIPNSGControlPreview"
-```
-
-When the status reflects *Registered*, refresh the registration of the *Microsoft.ContainerService* resource provider by using the [az provider register][az-provider-register] command:
-
-```azurecli-interactive
-az provider register --namespace Microsoft.ContainerService
-```
-
 ### Create a new cluster with allowed ports and application security groups
 
 ```azurecli-interactive