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

roygara · roygara · commit a7572f32022c · 2024-05-21T14:39:11.000-07:00
diff --git a/articles/ai-studio/how-to/deploy-models-serverless-availability.md b/articles/ai-studio/how-to/deploy-models-serverless-availability.md
@@ -6,17 +6,17 @@ manager: scottpolly
 ms.service: azure-ai-studio
 ms.topic: how-to
 ms.date: 5/21/2024
-ms.reviewer: mopeakande
-reviewer: msakande
-ms.author: fasantia
-author: santiagxf
+ms.author: mopeakande
+author: msakande
+ms.reviewer: fasantia
+reviewer: santiagxf
 ms.custom: 
  - build-2024
  - serverless
  - references_regions
 ---
 
-# Region availability for models in Serverless API endpoints | Azure AI Studio
+# Region availability for models in serverless API endpoints | Azure AI Studio
 
 [!INCLUDE [Feature preview](../includes/feature-preview.md)]
 
@@ -26,18 +26,7 @@ Certain models in the model catalog can be deployed as a serverless API with pay
 
 ## Region availability
 
-Serverless API endpoints are available in the following regions for the indicated models:
-
-| Model             | East US 2   | West US 3      | Sweden Central | France Central |
-| ----------------- | ----------- | -------------- | -------------- | -------------- |
-| Mistral-Small     | **&check;** |                | **&check;**    |                |
-| Mistral-Large     | **&check;** |                | **&check;**    | **&check;**    |
-| Cohere Command R  | **&check;** |                | **&check;**    |                |
-| Cohere Command R+ | **&check;** |                | **&check;**    |                |
-| Cohere Embed v3   | **&check;** |                | **&check;**    |                |
-| Meta Llama 2      | **&check;** | **&check;**    |                |                |
-| Meta Llama 3      | **&check;** |                |                |                |
-| Phi-3             | **&check;** |                | **&check;**    |                |
+[!INCLUDE [region-availabilitity-serverless-api](../includes/region-availabilitity-serverless-api.md)]
 
 ## Alternatives to region availability
 
diff --git a/articles/ai-studio/how-to/deploy-models-timegen-1.md b/articles/ai-studio/how-to/deploy-models-timegen-1.md
@@ -31,10 +31,18 @@ You can deploy TimeGEN-1 as a serverless API with pay-as-you-go billing. Nixtla
 ### Prerequisites
 
 - An Azure subscription with a valid payment method. Free or trial Azure subscriptions don't work. If you don't have an Azure subscription, create a [paid Azure account](https://azure.microsoft.com/pricing/purchase-options/pay-as-you-go) to begin.
-- An [AI Studio hub](../how-to/create-azure-ai-resource.md).
+- An [AI Studio hub](../how-to/create-azure-ai-resource.md). The serverless API model deployment offering for TimeGEN-1 is only available with hubs created in these regions:
 
-  > [!IMPORTANT]
-  > The serverless API model deployment offering for TimeGEN-1 is only available with hubs created in the **East US 2** or **Sweden Central** regions.
+    > [!div class="checklist"]
+    > * East US
+    > * East US 2
+    > * North Central US
+    > * South Central US
+    > * West US
+    > * West US 3
+    > * Sweden Central
+
+    For a list of  regions that are available for each of the models supporting serverless API endpoint deployments, see [Region availability for models in serverless API endpoints](deploy-models-serverless-availability.md).
 
 - An [Azure AI Studio project](../how-to/create-projects.md).
 - Azure role-based access controls (Azure RBAC) are used to grant access to operations in Azure AI Studio. To perform the steps in this article, your user account must be assigned the __Azure AI Developer role__ on the resource group. For more information on permissions, visit [Role-based access control in Azure AI Studio](../concepts/rbac-ai-studio.md).
@@ -52,7 +60,7 @@ These steps demonstrate the deployment of TimeGEN-1. To create a deployment:
     1. Select **+ Create deployment**.
     1. Search for and select **TimeGEN-1**. to open the Model's Details page.
     1. Select **Confirm** to open a serverless API deployment window for the model.
-1. Select the project in which you want to deploy your model. To deploy the TimeGEN-1 model, your project must be in the **East US 2** or **Sweden Central**  region.
+1. Select the project in which you want to deploy your model. To deploy the TimeGEN-1 model, your project must be in one of the regions listed in the [Prerequisites](#prerequisites) section.
 1. In the deployment wizard, select the link to **Azure Marketplace Terms**, to learn more about the terms of use.
 1. Select the **Pricing and terms** tab to learn about pricing for the selected model.
 1. Select the **Subscribe and Deploy** button. If this is your first time deploying the model in the project, you have to subscribe your project for the particular offering. This step requires that your account has the **Azure AI Developer role** permissions on the resource group, as listed in the prerequisites. Each project has its own subscription to the particular Azure Marketplace offering of the model, which allows you to control and monitor spending. Currently, you can have only one deployment for each model within a project.
diff --git a/articles/ai-studio/includes/region-availabilitity-serverless-api.md b/articles/ai-studio/includes/region-availabilitity-serverless-api.md
@@ -0,0 +1,71 @@
+---
+title: include file
+description: include file
+ms.service: azure-ai-studio
+ms.topic: include
+ms.date: 05/21/2024
+ms.author: mopeakande
+author: msakande
+ms.reviewer: fasantia
+reviewer: santiagxf
+ms.custom: include file
+
+# Also used in Azure Machine Learning documentation
+---
+
+Availability of serverless API endpoints for select models are listed in the following tables:
+
+<!-- | Model             | East US     | East US 2   | North Central US | South Central US | West US     | West US 3   | France Central | Sweden Central |
+|:-----------------:|:-----------:|:-----------:|:----------------:|:----------------:|:-----------:|:-----------:|:--------------:|:--------------:|
+| Mistral-Small     |             | **&check;** |                  |                  |             |             |                | **&check;**    |
+| Mistral-Large     |             | **&check;** |                  |                  |             |             | **&check;**    | **&check;**    |
+| Cohere Command R  |             | **&check;** |                  |                  |             |             |                | **&check;**    |
+| Cohere Command R+ |             | **&check;** |                  |                  |             |             |                | **&check;**    |
+| Cohere Embed v3   |             | **&check;** |                  |                  |             |             |                | **&check;**    |
+| Meta Llama 2      |             | **&check;** |                  |                  |             | **&check;** |                |                |
+| Meta Llama 3      |             | **&check;** |                  |                  |             |             |                |                |
+| Phi-3             |             | **&check;** |                  |                  |             |             |                | **&check;**    |
+| Nixtla TimeGEN-1  | **&check;** | **&check;** | **&check;**      | **&check;**      | **&check;** | **&check;** |                | **&check;**    | -->
+
+
+#### Cohere models
+
+| Region           | Cohere Command R | Cohere Command R+ | Cohere Embed v3 |
+|----------------|:----------------:|:-----------------:|:---------------:|
+| East US 2        | **&check;**      | **&check;**       | **&check;**     |
+| Sweden Central   | **&check;**      | **&check;**       | **&check;**     |
+
+#### Mistral models
+
+|   Region         | Mistral-Small | Mistral-Large |
+|----------------|:-------------:|:-------------:|
+| East US 2        | **&check;**   | **&check;**   |
+| France Central   | unavailable   | **&check;**   |
+| Sweden Central   | **&check;**   | **&check;**   |
+
+#### Meta Llama models
+
+| Region    | Llama-2     | Llama-3     |
+|-----------|:-----------:|:-----------:|
+| East US 2 | **&check;** | **&check;** |
+| West US 3 | **&check;** | unavailable |
+
+#### Nixtla TimeGEN-1 model
+
+| Region           | Nixtla TimeGEN-1 |
+|------------------|:----------------:|
+| East US          | **&check;**      |
+| East US 2        | **&check;**      |
+| North Central US | **&check;**      |
+| South Central US | **&check;**      |
+| West US          | **&check;**      |
+| West US 3        | **&check;**      |
+| France Central   | unavailable      |
+| Sweden Central   | **&check;**      |
+
+#### Phi 3 models
+
+| Region         | Phi 3       |
+|----------------|:-----------:|
+| East US 2      | **&check;** |
+| Sweden Central | **&check;** |
diff --git a/articles/azure-arc/kubernetes/extensions-release.md b/articles/azure-arc/kubernetes/extensions-release.md
@@ -1,6 +1,6 @@
 ---
 title: "Available extensions for Azure Arc-enabled Kubernetes clusters"
-ms.date: 04/30/2024
+ms.date: 05/21/2024
 ms.topic: how-to
 description: "See which extensions are currently available for Azure Arc-enabled Kubernetes clusters and view release notes."
 ---
@@ -150,10 +150,13 @@ Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1
 
 Changes made for this version:
 
-- Updated source-controller to v1.2.5
+- Updated source-controller to v1.2.5 [to address security vulnerability](https://github.com/advisories/GHSA-v554-xwgw-hc3w)
 
 ### 1.8.3 (March 2024)
 
+> [!NOTE]
+> We recommend upgrading to version 1.8.4 or later due to a [security vulnerability](https://github.com/advisories/GHSA-v554-xwgw-hc3w) that has been fixed starting with 1.8.4.
+
 Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)
 
 - source-controller: v1.1.2
diff --git a/articles/azure-cache-for-redis/cache-how-to-active-geo-replication.md b/articles/azure-cache-for-redis/cache-how-to-active-geo-replication.md
@@ -40,7 +40,7 @@ There are a few restrictions when using active geo replication:
 
 ## Create or join an active geo-replication group
 
-1. When creating a new Azure Cache for Redis resource, select the **Advanced** tab. Complete the first part of the form including clustering policy. For more information on choosing **Clustering policy**, see [Clustering Policy](quickstart-create-redis-enterprise.md#clustering-policy).
+1. When creating a new Azure Cache for Redis resource, select the **Advanced** tab. Complete the first part of the form including clustering policy. For more information on choosing **Clustering policy**, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise).
 
 1. Select **Configure** to set up **Active geo-replication**.
 
diff --git a/articles/azure-cache-for-redis/cache-redis-modules.md b/articles/azure-cache-for-redis/cache-redis-modules.md
@@ -84,7 +84,7 @@ Additionally, **RediSearch** can function as a secondary index, expanding your c
 You can use **RediSearch** is used in a wide variety of use-cases, including real-time inventory, enterprise search, and in indexing external databases. [For more information, see the RediSearch documentation page](https://redis.io/search/).
 
 >[!IMPORTANT]
-> The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering Policy](quickstart-create-redis-enterprise.md#clustering-policy) and [Memory Policies](cache-configure.md#memory-policies)
+> The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise) and [Memory Policies](cache-configure.md#memory-policies)
 >
 
 ### RedisBloom
diff --git a/articles/azure-cache-for-redis/quickstart-create-redis-enterprise.md b/articles/azure-cache-for-redis/quickstart-create-redis-enterprise.md
@@ -54,9 +54,11 @@ Azure Cache for Redis is continually expanding into new regions. To check the av
 
 1. Select **Next: Advanced**.
 
-   Enable **Non-TLS access only** if you plan to connect to the new cache without using TLS. Disabling TLS is **not** recommended, however. You can't change the eviction policy or clustering policy of an Enterprise cache instance after you create it. If you're using this cache instance in a replication group, be sure to know the policies of your primary nodes before you create the cache. For more information on replication, see [Active geo-replication prerequisites](cache-how-to-active-geo-replication.md#active-geo-replication-prerequisites).
+   Enable **Non-TLS access only** if you plan to connect to the new cache without using TLS. Disabling TLS is **not** recommended, however. 
 
-   Set **Clustering policy** to **Enterprise** for a nonclustered cache. For more information on choosing **Clustering policy**, see [Clustering Policy](#clustering-policy).
+   Set **Clustering policy** to **Enterprise** for a nonclustered cache, or to **OSS** for a clustered cache. For more information on choosing **Clustering policy**, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise).
+
+  
 
    :::image type="content" source="media/cache-create/cache-clustering-policy.png" alt-text="Screenshot that shows the Enterprise tier Advanced tab.":::
 
@@ -67,6 +69,14 @@ Azure Cache for Redis is continually expanding into new regions. To check the av
    > For more information, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise).
    >
 
+   > [!IMPORTANT]
+   > You can't change the clustering policy of an Enterprise cache instance after you create it. If you're using [RediSearch](cache-redis-modules.md#redisearch), the Enterprise cluster policy is required, and `NoEviction` is the only eviction policy supported. 
+   >
+
+   > [!IMPORTANT]
+   >  If you're using this cache instance in a geo-replication group, eviction policies cannot be changed after the instance is created. Be sure to know the eviction policies of your primary nodes before you create the cache. For more information on active geo-replication, see [Active geo-replication prerequisites](cache-how-to-active-geo-replication.md#active-geo-replication-prerequisites).
+   >
+   
    > [!IMPORTANT]
    > You can't change modules after you create a cache instance. Modules must be enabled at the time you create an Azure Cache for Redis instance. There is no option to enable the configuration of a module after you create a cache.
    >
@@ -80,12 +90,7 @@ Azure Cache for Redis is continually expanding into new regions. To check the av
 1. Review the settings and select **Create**.
 
    It takes some time for the cache to create. You can monitor progress on the Azure Cache for Redis **Overview** page. When **Status** shows as **Running**, the cache is ready to use.
-
-## Clustering Policy
-
-The OSS Cluster mode allows clients to communicate with Redis using the same Redis Cluster API as open-source Redis. This mode provides optimal latency and near-linear scalability improvements when scaling the cluster. Your client library must support clustering to use the OSS Cluster mode.
-
-The Enterprise Cluster mode is a simpler configuration that exposes a single endpoint for client connections. This mode allows an application designed to use a standalone, or nonclustered, Redis server to seamlessly operate with a scalable, multi-node, Redis implementation. Enterprise Cluster mode abstracts the Redis Cluster implementation from the client by internally routing requests to the correct node in the cluster. Clients aren't required to support OSS Cluster mode.
+   
 
 ## Related content
 
diff --git a/articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md b/articles/azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md
@@ -31,9 +31,9 @@ Creating a capacity pool enables you to create volumes within it.
         ```
         You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
 
->[!IMPORTANT]
->To create a 1-TiB capacity pool with a tag, you must use API versions `2023-07-01_preview` to `2024-01-01_preview` or stable releases from 2024-01-01. 
-
+    >[!IMPORTANT]
+    >To create a 1-TiB capacity pool with a tag, you must use API versions `2023-07-01_preview` to `2024-01-01_preview` or stable releases from `2024-01-01`. 
+    
 ## Steps 
 
 1. In the Azure portal, go to your NetApp account. From the navigation pane, select **Capacity pools**.  
diff --git a/articles/azure-netapp-files/create-cross-zone-replication.md b/articles/azure-netapp-files/create-cross-zone-replication.md
@@ -20,26 +20,6 @@ Before you begin, you should review the [requirements and considerations for cro
 
 [!INCLUDE [Azure NetApp Files cross-zone-replication supported regions](includes/cross-zone-regions.md)]
 
-## Register the feature 
-
-Cross-zone replication is currently in preview. You need to register the feature before using it for the first time. After registration, the feature is enabled and works in the background. No UI control is required. 
-
-1. Register the feature: 
-
-    ```azurepowershell-interactive
-    Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCrossZoneReplication
-    ```
-
-2. Check the status of the feature registration: 
-
-    > [!NOTE]
-    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
-
-    ```azurepowershell-interactive
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFCrossZoneReplication
-    ```
-You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. 
-
 ## Create the source volume with an availability zone  
 
 This process requires that your account is subscribed to the [availability zone volume placement feature](use-availability-zones.md).
diff --git a/articles/azure-netapp-files/manage-availability-zone-volume-placement.md b/articles/azure-netapp-files/manage-availability-zone-volume-placement.md
@@ -11,7 +11,7 @@ ms.author: anfdocs
 ---
 # Manage availability zone volume placement for Azure NetApp Files
 
-You can deploy new volumes in the logical availability zone of your choice. You can also populate existing volumes with availability zone information. To better understand availability zones, see [Using availability zones for high availability](use-availability-zones.md).
+You can deploy new volumes in the logical availability zone of your choice. You can also populate existing volumes with availability zone information. To better understand availability zones, see [Use availability zones for high availability](use-availability-zones.md).
 
 ## Requirements and considerations 
 
@@ -84,26 +84,8 @@ You can deploy new volumes in the logical availability zone of your choice. You
 
     :::image type="content" source="./media/manage-availability-zone-volume-placement/availability-zone-volume-overview.png" alt-text="Screenshot of volume properties interface." lightbox="./media/manage-availability-zone-volume-placement/availability-zone-volume-overview.png":::
 
-## Populate an existing volume with availability zone information
+## <a name="populate-an-existing-volume-with-availability-zone-information"></a> Populate an existing volume with availability zone information (preview)
 
-1. The feature to populate existing volumes with availability zone information is currently in preview. If you're using this feature for the first time, you need to register the feature first.  
-    1. Register the feature: 
-
-    ```azurepowershell-interactive
-     Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFPopulateAvailabilityZone
-    ```   
-    2. Check the status of the feature registration: 
-
-    ```azurepowershell-interactive
-   
-    Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFPopulateAvailabilityZone
-    ```
-
-    > [!NOTE]
-    > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is **Registered** before continuing.
-    
-    You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.   
-    
 1. Navigate to the volume that you want to populate with availability zone information.
 1. Select **Populate availability zone**.
 1. The Populate Availability Zone window appears and displays the availability zone in which the Azure NetApp Files volume is deployed.
diff --git a/articles/container-registry/container-registry-import-images.md b/articles/container-registry/container-registry-import-images.md
@@ -275,6 +275,8 @@ Import-AzContainerRegistryImage -RegistryName myregistry -ResourceGroupName myRe
 
 To import from an Azure container registry in a different Microsoft Entra tenant, specify the source registry by login server name, and provide credentials that enable pull access to the registry. 
 
+* Cross-tenant import over public access disabled registry is not supported.   
+
 ### Cross-tenant import with username and password
 
 For example, use a [repository-scoped token](container-registry-repository-scoped-permissions.md) and password, or the appID and password of an Active Directory [service principal](container-registry-auth-service-principal.md) that has ACRPull access to the source registry.
diff --git a/articles/cost-management-billing/costs/tutorial-acm-create-budgets.md b/articles/cost-management-billing/costs/tutorial-acm-create-budgets.md
diff --git a/articles/machine-learning/concept-endpoint-serverless-availability.md b/articles/machine-learning/concept-endpoint-serverless-availability.md
diff --git a/articles/machine-learning/how-to-deploy-models-timegen-1.md b/articles/machine-learning/how-to-deploy-models-timegen-1.md
diff --git a/articles/search/vector-search-integrated-vectorization.md b/articles/search/vector-search-integrated-vectorization.md

Original file line number	Diff line number	Diff line change
`@@ -84,7 +84,7 @@ Additionally, RediSearch can function as a secondary index, expanding your c`
`84`	`84`	`You can use RediSearch is used in a wide variety of use-cases, including real-time inventory, enterprise search, and in indexing external databases. [For more information, see the RediSearch documentation page](https://redis.io/search/).`
`85`	`85`
`86`	`86`	`>[!IMPORTANT]`
`87`		-> The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering Policy](quickstart-create-redis-enterprise.md#clustering-policy) and [Memory Policies](cache-configure.md#memory-policies)
	`87`	+> The RediSearch module requires use of the `Enterprise` clustering policy and the `NoEviction` eviction policy. For more information, see [Clustering on Enterprise](cache-best-practices-enterprise-tiers.md#clustering-on-enterprise) and [Memory Policies](cache-configure.md#memory-policies)
`88`	`88`	`>`
`89`	`89`
`90`	`90`	`### RedisBloom`