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

Author: gitName

articles/api-center/frequently-asked-questions.yml

@@ -50,7 +50,7 @@ sections:
           To upgrade your API center from the Free plan to the Standard plan, follow these steps:
 
           1. In the Azure portal, navigate to your API center.
-          2. In the left menu, select **Overview** > **Select plan**.
+          2. In the left menu, select **Overview** > **Manage plan**.
           3. Select **Standard plan**.
           4. Select **Submit**.
 

articles/api-center/includes/api-center-service-limits.md

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 03/18/2025
+ms.date: 03/ 18/2025
 ms.author: danlep
 ms.custom: Include file
 ---
@@ -27,6 +27,7 @@ ms.custom: Include file
 | Maximum number of analysis profiles | 1 | 3 |
 | Maximum number of linked API sources<sup>5</sup> | 1  |  3 |
 | Maximum number of APIs synchronized from a linked API source | 200 | 2,000<sup>4</sup>  |
+| Semantic search in API Center portal | No | Yes |
 
 <sup>1</sup> Free plan provided for 90 days, then service is soft-deleted. Use of full service features including API analysis is limited.<br/>
 <sup>2</sup> To increase a limit in the Standard plan, contact [support](https://azure.microsoft.com/support/options/).<br/>

articles/api-center/media/set-up-api-center-portal/semantic-search.png

@@ -1,12 +1,13 @@
 ---
-title: Set up the API Center portal
+title: Set Up the API Center Portal
 description: How to set up the API Center portal, a managed website that enables discovery of the API inventory in your Azure API center.
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 04/28/2025
+ms.date: 04/30/2025
 ms.author: danlep 
 ms.custom: 
+ms.collection: ce-skilling-ai-copilot
 # Customer intent: As an API program manager, I want to enable an Azure-managed portal for developers and other API stakeholders in my organization to discover the APIs in my organization's API center.
 ---
 
@@ -62,7 +63,32 @@ To make only specific APIs visible, go to the **API visibility** tab in the API
 
 ## Enable access to test console for APIs
 
-You can configure user settings to granularly authorize access to APIs and their specific versions in your API center. For example, you can configure certain API versions to use API keys for authentication, and create an access policy that permits only specific users to authenticate using those keys. This policy also applies to the "Try this API" capability for APIs in the API Center portal, ensuring that only portal users with the appropriate access policy can use the test console for those API versions. [Learn more about authorizing access to APIs](authorize-api-access.md)
+You can configure user settings to granularly authorize access to APIs and their specific versions in your API center. For example, configure certain API versions to use API keys for authentication, and create an access policy that permits only specific users to authenticate using those keys. This policy also applies to the "Try this API" capability for APIs in the API Center portal, ensuring that only portal users with the appropriate access policy can use the test console for those API versions. [Learn more about authorizing access to APIs](authorize-api-access.md)
+
+## API discovery and consumption in the API Center portal
+
+The API Center portal supports and streamlines the work of developers who use and create APIs within your organization. Signed-in users can:
+
+* **Search for APIs** by name or using [AI-assisted semantic search](#search-with-ai) 
+
+* **Filter APIs** by type or lifecycle stage
+
+* **View API details and definitions** including endpoints, methods, parameters, and response formats
+
+* **Download API definitions** to a local computer or open them in Visual Studio Code
+
+* **Try out APIs** that support API key authentication or OAuth 2.0 authorization
+
+## Search with AI
+
+In the Standard plan of Azure API Center, the API Center portal supplements basic name-based API search with AI-assisted *semantic search* built on API names and descriptions. Users can search for APIs using natural language queries, making it easier to find APIs based on their intent. For example, if a developer searches for "I need an API for inventory management," the portal can suggest relevant APIs, even if their names or descriptions don't include those exact words.
+
+> [!TIP]
+> If you're using the Free plan of Azure API Center, you can [upgrade easily](frequently-asked-questions.yml#how-do-i-upgrade-my-api-center-from-the-free-plan-to-the-standard-plan) to the Standard plan to enable full service features including semantic search in the API Center portal.
+
+To use AI-assisted search when signed in to the API Center portal, click in the search box, select **Search with AI**, and enter a query.
+
+:::image type="content" source="media/set-up-api-center-portal/semantic-search.png" alt-text="Screenshot of semantic search results in API Center portal.":::
 
 [!INCLUDE [api-center-portal-compare-apim-dev-portal](includes/api-center-portal-compare-apim-dev-portal.md)]
 

articles/api-center/set-up-api-center-portal.md

@@ -0,0 +1,72 @@
+---
+title: Azure App Configuration preview API life cycle
+titleSuffix: Azure App Configuration
+description: Learn about the preview API life cycle.
+services: azure-app-configuration
+author: amerjusupovic
+ms.author: ajusupovic
+ms.service: azure-app-configuration
+ms.topic: conceptual
+ms.date: 02/12/2025
+---
+
+# Preview API life cycle
+
+The Azure App Configuration preview APIs (all APIs that ends in `-preview`) are deprecated 90 days after a newer preview, or stable, API version is released. The policy applies to all API versions released after, and including, 2023-09-01-preview.
+
+We love when people try our preview features and give us feedback, so we encourage you to use the preview APIs.
+
+After an API version is deprecated, it will no longer function! We recommend you routinely:
+- Update your ARM/BICEP templates using preview API versions to use the latest version of the preview API.
+- Update any preview SDKs or other tools built on the preview API to the latest version.
+
+You should perform these updates at a minimum every 6-9 months. If you fail to do so, you'll be notified that you're using a soon-to-be deprecated API version as deprecation approaches.
+
+> [!NOTE]
+> API versions before 2023-09-01-preview won't follow the 90 day pattern outlined in the beginning of this document. Refer to the [Upcoming Deprecations](#upcoming-deprecations) and [Completed Deprecations](#completed-deprecations) tables to see if a preview API version you're using has a deprecation date. 
+
+## How to check what API versions you're using
+
+If you're unsure what client or tool is using this API version, check the [activity logs](/azure/azure-monitor/essentials/activity-log)
+using the following command:
+
+### [bash](#tab/bash)
+
+```bash
+API_VERSION=<impacted API version, such as 2021-10-01-preview>
+az monitor activity-log list --offset 30d --max-events 10000 --namespace Microsoft.AppConfiguration --query "[?eventName.value == 'EndRequest' && httpRequest.uri != null && contains(httpRequest.uri, '$API_VERSION')].[eventTimestamp, httpRequest.uri]" --output table
+```
+
+### [PowerShell](#tab/PowerShell)
+
+```powershell
+$API_VERSION=<impacted API version, such as 2021-10-01-preview>
+az monitor activity-log list --offset 30d --max-events 10000 --namespace Microsoft.AppConfiguration | ConvertFrom-Json | Where-Object { $_.eventName.value -eq "EndRequest" -and $_.httpRequest.uri -match $API_VERSION } | Select-Object eventTimestamp, httpRequest | Format-Table -Wrap -AutoSize
+```
+
+---
+
+## How to find the available API versions
+
+If you want to know what API versions are available, you can use the following command for a resource type:
+
+```bash
+az provider show --namespace Microsoft.AppConfiguration --query "resourceTypes[?resourceType=='configurationStores'].apiVersions"
+```
+
+## How to update to a newer version of the API
+
+- For Azure SDKs: Use a newer API version by updating to a [newer version of the SDK](https://github.com/Azure/AppConfiguration?tab=readme-ov-file#sdks).
+- For Azure CLI: Update the CLI itself, usually by running `az upgrade`.
+- For REST requests: Update the `api-version` query parameter.
+- For other tools: Update the tool to the latest version.
+
+## Upcoming deprecations
+
+| API version        | Announce Date     | Deprecation Date  |
+|--------------------|-------------------|-------------------|
+| 2023-09-01-preview | April 30, 2025    | July 29, 2025     |
+
+## Completed deprecations
+
+There are no completed deprecations yet.

articles/azure-app-configuration/concept-preview-api-lifecycle.md

@@ -45,6 +45,9 @@ When using data flows in Azure Synapse workspaces, you will have an additional o
 
 Mapping data flow follows an extract, load, and transform (ELT) approach and works with *staging* datasets that are all in Azure. Currently, the following datasets can be used in a sink transformation.
 
+>[!TIP]
+>Your sink can be a different format than your source. This is one step of how you can transform from one format to another. For example, from a CSV to a Parquet sink. You might need to make some transformations in your data flow between source and sink for this to work correctly. (For example, Parquet has more specific header requirements than CSV.)
+
 | Connector | Format | Dataset/inline |
 | --------- | ------ | -------------- |
 | [Azure Blob Storage](connector-azure-blob-storage.md#mapping-data-flow-properties) | [Avro](format-avro.md#mapping-data-flow-properties) <br>[Delimited text](format-delimited-text.md#mapping-data-flow-properties) <br>[Delta](format-delta.md) <br>[JSON](format-json.md#mapping-data-flow-properties) <br/>[ORC](format-orc.md#mapping-data-flow-properties)<br>[Parquet](format-parquet.md#mapping-data-flow-properties) | ✓/✓ <br>✓/✓ <br>-/✓ <br>✓/✓ <br>✓/✓<br>✓/✓ |

articles/data-factory/data-flow-sink.md

@@ -16,8 +16,6 @@ ms.date: 11/06/2024
 # Quickstart: Create a dev box by using team customizations
 
 In this quickstart, you create a dev box by using Microsoft Dev Box team customizations. The feature uses an image definition file so that you can create consistently customized dev boxes for your development team and provide a tailored environment for your projects.
-
-[!INCLUDE [customizations-preview-text](includes/customizations-preview-text.md)]
 
 ## Prerequisites
 
@@ -212,4 +210,4 @@ Dev Box applies customizations as the final stage of the creation process. Dev B
 ## Related content
 
 - [Microsoft Dev Box team customizations](concept-what-are-team-customizations.md)
-- [Write a customization file for a dev box](./how-to-write-customization-file.md)
+- [Write a customization file for a dev box](./how-to-write-customization-file.md)

articles/dev-box/quickstart-team-customizations.md

@@ -1,7 +1,7 @@
 ---
 title: Regulatory Compliance details for Australian Government ISM PROTECTED
 description: Details of the Australian Government ISM PROTECTED Regulatory Compliance built-in initiative. Each control is mapped to one or more Azure Policy definitions that assist with assessment.
-ms.date: 04/25/2025
+ms.date: 04/30/2025
 ms.topic: generated-reference
 ms.custom: generated
 ---

articles/governance/policy/samples/australia-ism.md

@@ -1,7 +1,7 @@
 ---
 title: Regulatory Compliance details for Microsoft cloud security benchmark
 description: Details of the Microsoft cloud security benchmark Regulatory Compliance built-in initiative. Each control is mapped to one or more Azure Policy definitions that assist with assessment.
-ms.date: 04/25/2025
+ms.date: 04/30/2025
 ms.topic: generated-reference
 ms.custom: generated
 ---
@@ -248,6 +248,7 @@ initiative definition.
 |---|---|---|---|
 |[API Management subscriptions should not be scoped to all APIs](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F3aa03346-d8c5-4994-a5bc-7652c2a2aef1) |API Management subscriptions should be scoped to a product or an individual API instead of all APIs, which could result in an excessive data exposure. |Audit, Disabled, Deny |[1.1.0](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/API%20Management/AllApiSubscription_AuditDeny.json) |
 |[Audit usage of custom RBAC roles](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fa451c1ef-c6ca-483d-87ed-f49761e3ffb5) |Audit built-in roles such as 'Owner, Contributer, Reader' instead of custom RBAC roles, which are error prone. Using custom roles is treated as an exception and requires a rigorous review and threat modeling |Audit, Disabled |[1.0.1](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/General/Subscription_AuditCustomRBACRoles_Audit.json) |
+|[Azure Key Vault should use RBAC permission model](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2F12d4fa5e-1f9f-4c21-97a9-b99b3c6611b5) |Enable RBAC permission model across Key Vaults. Learn more at: [https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-migration](/azure/key-vault/general/rbac-migration) |Audit, Deny, Disabled |[1.0.1](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Key%20Vault/Should_Use_RBAC.json) |
 |[Role-Based Access Control (RBAC) should be used on Kubernetes Services](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2Fproviders%2FMicrosoft.Authorization%2FpolicyDefinitions%2Fac4a19c2-fa67-49b4-8ae5-0b2e78c49457) |To provide granular filtering on the actions that users can perform, use Role-Based Access Control (RBAC) to manage permissions in Kubernetes Service Clusters and configure relevant authorization policies. |Audit, Disabled |[1.1.0](https://github.com/Azure/azure-policy/blob/master/built-in-policies/policyDefinitions/Security%20Center/ASC_EnableRBAC_KubernetesService_Audit.json) |
 
 ## Data Protection

articles/governance/policy/samples/azure-security-benchmark.md

@@ -1,7 +1,7 @@
 ---
 title: List of built-in policy initiatives
 description: List built-in policy initiatives for Azure Policy. Categories include Regulatory Compliance, Azure Machine Configuration, and more.
-ms.date: 04/27/2025
+ms.date: 04/30/2025
 ms.topic: generated-reference
 ms.custom: generated
 ---