@@ -8,7 +8,7 @@ ms.service: azure-ai-search
 ms.custom:
   - build-2025
 ms.topic: reference
-ms.date: 08/27/2025
+ms.date: 09/18/2025
 ---
 
 # GenAI Prompt skill
@@ -35,11 +35,13 @@ The GenAI Prompt skill is available in the [latest preview REST API](/rest/api/s
 
 ## Supported models
 
-You can use any [chat completion inference model](/azure/ai-foundry/model-inference/concepts/models) deployed in AI Foundry, such as GPT models, Deepseek R#, Llama-4-Mavericj, Cohere-command-r, and so forth.
+- You can use any [chat completion inference model](/azure/ai-foundry/model-inference/concepts/models) deployed in AI Foundry, such as GPT models, Deepseek R#, Llama-4-Mavericj, Cohere-command-r, and so forth.
 
-For image verbalization, the model you use to analyze the image determines what image formats are supported.
+- For image verbalization, the model you use to analyze the image determines what image formats are supported.
 
-Billing is based on the pricing of the model you use.
+- For GPT-5 model, the `temperature` parameter is not supported in the same way as previous models. If defined, it must be set to `1.0`, as other values will result in errors.
+
+- Billing is based on the pricing of the model you use.
 
 > [!NOTE]
 > The search service connects to your model over a public endpoint, so there are no region location requirements, but if you're using an all-up Azure solution, you should check the [Azure AI Search regions](search-region-support.md) and the [Azure OpenAI model regions](/azure/ai-services/openai/concepts/models) to find suitable pairs, especially if you have data residency requirements.
@@ -59,6 +61,7 @@ Billing is based on the pricing of the model you use.
 
   - For AI Foundry models, assign [**Azure AI User**](/azure/ai-foundry/concepts/rbac-azure-ai-foundry#azure-ai-user).
 
+
 ## @odata.type  
 
 `#Microsoft.Skills.Custom.ChatCompletionSkill`

@@ -47,7 +47,7 @@ To run the wizard:
 
 1. On the **Overview** page, select **Import data**.
 
-   :::image type="content" source="../../media/search-import-data-portal/import-data-button.png" alt-text="Screenshot of the Import data command." border="true" lightbox="../../media/search-import-data-portal/import-data-button.png":::
+   :::image type="content" source="../../media/search-import-data-portal/import-data-button.png" alt-text="Screenshot of the Import data command." border="true":::
 
 ### Step 1: Create a data source
 

@@ -4,7 +4,7 @@ titleSuffix: Azure AI Search
 description: Learn how to configure Azure AI Search indexers for ingesting Azure Role-Based Access (RBAC) metadata on Azure blobs.
 ms.service: azure-ai-search  
 ms.topic: how-to
-ms.date: 09/01/2025
+ms.date: 09/18/2025
 author: vaishalishah
 ms.author: vaishalishah
 ---  
@@ -39,7 +39,7 @@ The indexer approach is built on this foundation:
 
 + You should understand how indexers work and how to create an index. This article explains the configuration settings for the data source and indexer, but doesn't provide steps for creating the index. For more information about indexes designed for permission filters, see [Create an index with permission filter fields](search-index-access-control-lists-and-rbac-push-api.md#create-an-index-with-permission-filter-fields).
 
-Permission filters aren't supported in the indexers and indexes created through the [Import wizards](search-import-data-portal.md). Use a programmatic approach to create or modify existing objects for document-level access.
++ This functionality is currently not supported in the Azure portal, this includes Permission filters created through the [Import wizards](search-import-data-portal.md). Use a programmatic approach to create or modify existing objects for document-level access. 
 
 ## Configure Blob storage
 

@@ -4,7 +4,7 @@ titleSuffix: Azure AI Search
 description: Learn how to use the REST API for indexing documents with ACLs and RBAC metadata.  
 ms.service: azure-ai-search  
 ms.topic: how-to 
-ms.date: 08/27/2025 
+ms.date: 09/18/2025 
 author: admayber
 ms.author: admayber  
 ---  
@@ -43,6 +43,8 @@ This article explains how to use the push REST API to index document-level permi
 
 - Each permissionFilter field should have `filterable` set to true.
 
+- This functionality is currently not supported in the Azure portal.
+
 ## Create an index with permission filter fields
 
 Indexing document ACLs and RBAC metadata with the REST API requires setting up an index schema that enables permission filters and has fields with permission filter assignments.

@@ -4,9 +4,9 @@ titleSuffix: Azure AI Search
 description: Learn how to configure Azure AI Search indexers for ingesting Access Control Lists (ACLs) and Azure Role-Based Access (RBAC) metadata on Azure Data Lake Storage (ADLS) Gen2 blobs.
 ms.service: azure-ai-search
 ms.topic: how-to
-ms.date: 08/27/2025  
-author: wlifuture
-ms.author: wli
+ms.date: 09/18/2025  
+author: gmndrg
+ms.author: gimondra
 ---  
 
 # Use an ADLS Gen2 indexer to ingest permission metadata and filter search results based on user access rights
@@ -51,6 +51,8 @@ This article supplements [**Index data from ADLS  Gen2**](search-howto-index-azu
   + [Knowledge store](knowledge-store-concept-intro.md)
   + [Indexer enrichment cache](enrichment-cache-how-to-configure.md)
   + [Debug sessions](cognitive-search-debug-session.md)
+ 
++ This functionality is currently not supported in the Azure portal.
 
 ## Support for the permission model
 
@@ -300,4 +302,4 @@ To effectively manage blob deletion, ensure that you have enabled [deletion trac
 
 + [Connect to Azure AI Search using roles](search-security-rbac.md)
 + [Query-Time ACL and RBAC enforcement](search-query-access-control-rbac-enforcement.md)
-+ [azure-search-python-samples/Quickstart-Document-Permissions-Push-API](https://github.com/Azure-Samples/azure-search-python-samples/blob/main/Quickstart-Document-Permissions-Push-API)
\ No newline at end of file
++ [azure-search-python-samples/Quickstart-Document-Permissions-Push-API](https://github.com/Azure-Samples/azure-search-python-samples/blob/main/Quickstart-Document-Permissions-Push-API)