Merge pull request #300638 from MicrosoftDocs/main

5/30/2025 PM Publish

Author: Taojunshen

articles/api-center/build-register-apis-vscode-extension.md

@@ -4,7 +4,7 @@ description: API developers can use the Azure API Center extension for Visual St
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 11/08/2024
+ms.date: 05/28/2025
 ms.author: danlep 
 ms.collection: ce-skilling-ai-copilot
 ms.custom: 
@@ -60,6 +60,8 @@ Use the power of [GitHub Copilot](https://marketplace.visualstudio.com/items?ite
 
 :::image type="content" source="media/build-register-apis-vscode-extension/generate-api-documentation.gif" alt-text="Animation showing how to use GitHub Copilot to generate an OpenAPI spec from code." lightbox="media/build-register-apis-vscode-extension/generate-api-documentation.gif":::
 
+You can also generate an OpenAPI specification from all of the files in your current project. Use the **Azure API Center: Generate OpenAPI Spec from Entire Project** command from the Command Palette. 
+
 After generating the OpenAPI specification file and checking for accuracy, you can register the API with your API center using the **Azure API Center: Register API** command.
 
 > [!TIP]
@@ -70,6 +72,6 @@ After generating the OpenAPI specification file and checking for accuracy, you c
 * [Azure API Center - key concepts](key-concepts.md)
 * [Discover and consume APIs with the Azure API Center extension for Visual Studio Code](discover-apis-vscode-extension.md)
 * [Govern APIs with the Azure API Center extension for Visual Studio Code](govern-apis-vscode-extension.md)
-* [Enable and view API Center portal in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
+* [Enable API Center portal view in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
 * [Overview of GitHub Copilot for Azure](/azure/developer/github-copilot-azure/introduction)
 

articles/api-center/discover-apis-vscode-extension.md

@@ -4,7 +4,7 @@ description: API developers can use the Azure API Center extension for Visual St
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 10/16/2024
+ms.date: 05/27/2025
 ms.author: danlep 
 ms.custom: 
 # Customer intent: As an API developer, I want to use my Visual Studio Code environment to discover and consume APIs in my organizations API center.
@@ -21,12 +21,13 @@ API developers in your organization can discover and consume APIs in your [API c
 API developers can also take advantage of features in the extension to [register APIs](build-register-apis-vscode-extension.md) in the API center and ensure [API governance](govern-apis-vscode-extension.md).
 
 > [!TIP]
-> If you want enterprise app developers to discover your APIs in a centralized location, optionally enable the read-only [API Center portal](enable-api-center-portal-vs-code-extension.md) in Visual Studio Code. 
+> If you want enterprise app developers to discover your APIs in a centralized location, optionally enable the read-only [API Center portal view](enable-api-center-portal-vs-code-extension.md) in Visual Studio Code. 
 
 [!INCLUDE [vscode-extension-basic-prerequisites](includes/vscode-extension-basic-prerequisites.md)]  
 
 * [REST client extension](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) - to send HTTP requests and view the responses in Visual Studio Code directly
 * [Microsoft Kiota extension](https://marketplace.visualstudio.com/items?itemName=ms-graph.kiota) - to generate API clients
+- [Microsoft 365 Agents Toolkit](https://marketplace.visualstudio.com/items?itemName=TeamsDevApp.ms-teams-vscode-extension) - to create Microsoft 365 declarative agents
 
 [!INCLUDE [vscode-extension-setup](includes/vscode-extension-setup.md)]   
 
@@ -36,7 +37,7 @@ API center resources appear in the tree view on the left-hand side. Expand an AP
 
 :::image type="content" source="media/discover-apis-vscode-extension/explore-api-centers.png" alt-text="Screenshot of API Center tree view in Visual Studio Code." lightbox="media/discover-apis-vscode-extension/explore-api-centers.png":::
 
-Search for APIs within an API Center by using the search icon shown in the **Apis** tree view item.
+Search for APIs within an API Center by using the search icon shown in the **APIs** tree view item.
 
 ## View API documentation
 
@@ -53,7 +54,7 @@ You can view the documentation for an API definition in your API center and try
     > Depending on the API, you might need to provide authorization credentials or an API key to try the API.
 
     > [!TIP]
-    > Using the pre-release version of the extension, you can generate API documentation in Markdown, a format that's easy to maintain and share with end users. Right-click on the definition, and select **Generate Markdown**.
+    > You can generate API documentation in Markdown, a format that's easy to maintain and share with end users. Right-click on the definition, and select **Generate Markdown**.
 
 ## Generate HTTP file
 
@@ -103,10 +104,24 @@ You can also export a specification using the Command Palette:
 1. Select **Azure API Center: Export API Specification Document**.
 1. Make selections to navigate to an API definition. A new tab appears that renders an API specification document.
 
-## Related content
+    
+## Create M365 declarative agent
+
+You can create a [declarative agent for Microsoft 365 Copilot](/microsoft-365-copilot/extensibility/overview-declarative-agent) from an OpenAPI definition in your API center. With a declarative agent, you customize Microsoft 365 Copilot to help you meet the unique business needs of your users. When you build a declarative agent, you provide the instructions, actions, and knowledge to tailor Copilot for your business scenarios. 
+
+To export a declarative agent in the extension's tree view:
+
+1. Expand the API Center tree view to show an OpenAPI definition.
+1. Right-click on the definition, and select **Export M365 Declarative Agent**. 
+1. When prompted:
+    1. Select one or more API operations that Copilot can interact with.
+    1. Select a workspace folder.
+    1. Enter an application name.
+
+The declarative agent is created in the selected workspace folder. Use the Microsoft 365 Agents Toolkit to further customize and deploy the agent.
 
 * [Azure API Center - key concepts](key-concepts.md)
 * [Build and register APIs with the Azure API Center extension for Visual Studio Code](build-register-apis-vscode-extension.md)
 * [Govern APIs with the Azure API Center extension for Visual Studio Code](govern-apis-vscode-extension.md)
-* [Enable and view API Center portal in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
+* [Enable API Center portal view in Visual Studio Code](enable-api-center-portal-vs-code-extension.md)
 

articles/api-center/enable-api-center-portal-vs-code-extension.md

@@ -4,7 +4,7 @@ description: Enable enterprise developers to view the enterprise's API Center po
 author: dlepow
 ms.service: azure-api-center
 ms.topic: how-to
-ms.date: 03/20/2025
+ms.date: 05/27/2025
 ms.author: danlep 
 ms.custom: 
 # Customer intent: As an API program manager, I want to enable an API catalog so that app developers in my organization can discover and consume the APIs in my organization's API center without needing to manage the API inventory itself.
@@ -19,6 +19,8 @@ This article shows how to provide enterprise developers access to the Azure API
 
 ## Prerequisites
 
+### For API center administrators
+
 * An API center in your Azure subscription. If you haven't created one already, see [Quickstart: Create your API center](set-up-api-center.md).
 
 * Permissions to create an app registration in a Microsoft Entra tenant associated with your Azure subscription, and permissions to grant access to data in your API center. 
@@ -27,10 +29,13 @@ This article shows how to provide enterprise developers access to the Azure API
 
 * [Azure API Center extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=apidev.azure-api-center)
 
+    > [!NOTE]
+    > Where noted, certain features are available only in the Azure API Center extension's pre-release version. [!INCLUDE [vscode-extension-prerelease-features](includes/vscode-extension-prerelease-features.md)]
     
-The following Visual Studio Code extension is optional:
+The following Visual Studio Code extensions are optional:
 
 * [Microsoft Kiota extension](https://marketplace.visualstudio.com/items?itemName=ms-graph.kiota) - to generate API clients
+* GitHub Copilot and GitHub Copilot Chat, provided with [access to GitHub Copilot](https://code.visualstudio.com/docs/copilot/setup) - to use language model tools in agent mode for discovering APIs 
 
 ## Steps for API center administrators to enable access to API Center portal view
 
@@ -48,12 +53,10 @@ Enterprise developers must sign in with a Microsoft account to see the API Cente
 
 ## Steps for enterprise developers to access the API Center portal view
 
-Developers can follow these steps to connect and sign in to view an API Center portal view using the Visual Studio Code extension. Settings to connect to the API center need to be provided by the API center administrator.
+Developers can follow these steps to connect and sign in to an API Center portal view using the Visual Studio Code extension. Settings to connect to the API center need to be provided by the API center administrator. After connecting, developers can discover and consume the APIs in the API center.
 
 ### Connect to an API center
 
-1. Install the pre-release version of the [Azure API Center extension for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=apidev.azure-api-center) for Visual Studio Code. 
-
 1. In Visual Studio Code, in the Activity Bar on the left, select API Center.
 
     :::image type="content" source="media/enable-api-center-portal-vs-code-extension/api-center-activity-bar.png" alt-text="Screenshot of the API Center icon in the Activity Bar.":::
@@ -66,7 +69,7 @@ Developers can follow these steps to connect and sign in to view an API Center p
     1. The directory (tenant) ID from the app registration configured by the administrator in the previous section.
 
     > [!TIP]
-    > An API center administrator needs to provide these connection details to developers, or provide a direct link in the following format:  
+    > An API center administrator needs to provide the preceding connection details to developers, or provide a direct link in the following format:  
     > `vscode://apidev.azure-api-center?clientId=<Client ID>&tenantId=<tenant ID>&runtimeUrl=<service-name>.data.<region>.azure-apicenter.ms`
 
     After you connect to the API center, the name of the API center appears in the API Center portal view. 
@@ -90,6 +93,33 @@ The API Center portal view helps enterprise developers discover API details and
 * **Generate Markdown** - Generate API documentation in Markdown format
 * **OpenAPI documentation** - View the documentation for an API definition and try operations in a Swagger UI (only available for OpenAPI definitions)
 
+## Use language model tools 
+
+In the pre-release version of the Azure API Center extension, developers with access to the API Center portal view can add API Center language model tools to use in GitHub Copilot's agent mode. [Learn more about using tools in agent mode](https://code.visualstudio.com/docs/copilot/chat/chat-agent-mode#_agent-mode-tools). 
+
+The API Center tools can be used in agent mode to help search for APIs and API versions, API definitions and specifications, deployments, and more using natural language prompts.
+
+To add and use API Center language mode tools in GitHub Copilot's agent mode:
+
+1. [Connect to an API center](#create-microsoft-entra-app-registration) as described in a previous section.
+1. Open GitHub Copilot Chat in Visual Studio Code. 
+1. Set the mode of GitHub Copilot Chat to **Agent**.
+1. Select the **Tools** icon in the chat window.
+
+    :::image type="content" source="media/enable-api-center-portal-vs-code-extension/language-model-tools.png" alt-text="Screenshot of GitHub Copilot chat window in Visual Studio Code.":::
+
+1. Select one or more API Center tools to be available in the chat.
+
+    :::image type="content" source="media/enable-api-center-portal-vs-code-extension/api-center-tools.png" alt-text="Screenshot of selecting API Center tools in Visual Studio Code.":::
+
+1. Enter a prompt in the chat window to use the available tools. For example:
+
+    ```copilot-prompt
+    Find potential MCP servers for a project I'm working on. I need the deployment URLs from my API center of any MCP servers that can run code snippets.
+    ```
+
+1. Review the responses from GitHub Copilot Chat. Continue with the conversation to refine the results or ask follow-up questions.
+
 
 ## Troubleshooting
 

articles/api-center/includes/api-center-portal-app-registration.md

@@ -6,13 +6,28 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 03/20/2025
+ms.date: 05/28/2025
 ms.author: danlep
 ms.custom: Include file
 ---
 
 First configure an app registration in your Microsoft Entra ID tenant. The app registration enables the API Center portal to access data from your API center on behalf of a signed-in user.
 
+API Center can set up the app registration automatically, or you can create the app registration manually. 
+
+#### Set up the app registration automatically
+
+To set up the app registration automatically, follow these steps:
+
+1. In the [Azure portal](https://portal.azure.com), navigate to your API center.
+1. In the left-hand menu, select **API Center portal** > **Settings**.
+1. On the **Identity provider** tab, select **Start set up**.
+1. Select **Save + publish**.
+
+#### Set up the app registration manually
+
+If you want to create the app registration manually, follow these steps:
+
 1. In the [Azure portal](https://portal.azure.com), navigate to **Microsoft Entra ID** > **App registrations**.
 1. Select **+ New registration**. 
 1. On the **Register an application** page, set the values as follows:
@@ -23,12 +38,15 @@ First configure an app registration in your Microsoft Entra ID tenant. The app r
         Enter the URI of your API Center portal deployment, in the following form: `https://<service-name>.portal.<location>.azure-api-center.ms`. Replace `<service name>` and `<location>` with the name of your API center and the location where it's deployed, Example: `https://myapicenter.portal.eastus.azure-api-center.ms`.
     1. Select **Register**.
 
-When enabling the API Center portal in the Visual Studio Code extension for API Center, also configure the following redirect URIs. 
+#### Configure additional redirect URIs for VS Code extension
+
+When enabling the API Center portal view in the Visual Studio Code extension for API Center, also configure the following redirect URIs in the app registration:
 
-1. On the **Manage** > **Authentication** page, Select **Add a platform** and select **Mobile and desktop applications**. 
+1. In the [Azure portal](https://portal.azure.com), navigate to your app registration.
+1. On the **Manage** > **Authentication** page, select **Add a platform** and select **Mobile and desktop applications**. 
 1. Configure the following three custom redirect URIs:<br/>
     `https://vscode.dev/redirect`<br/>
     `http://localhost`<br/>
     `ms-appx-web://Microsoft.AAD.BrokerPlugin/<application-client-id>`<br/>
 
-    Replace `<application-client-id>` with the application (client) ID of this app. You can find this value on the **Overview** page. 
+    Replace `<application-client-id>` with the application (client) ID of this app. You can find this value on the **Overview** page of the app registration. 

articles/api-center/media/enable-api-center-portal-vs-code-extension/api-center-tools.png

@@ -3,16 +3,13 @@ title: Use extensions in Bicep
 description: This article describes how to use Bicep extensions.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 04/09/2025
+ms.date: 05/14/2025
 ---
 
 # Use Bicep extensions
 
 Bicep was initially created to enhance the authoring experience compared to Azure Resource Manager JSON templates, simplifying the deployment and management of Azure resources. Bicep extensions build on this foundation, enabling Bicep files to reference resources beyond the scope of Azure Resource Manager. This article describes how to use Bicep extensions.
 
-> [!NOTE]
-> The experimental feature `extensibility` must be enabled from the [Bicep config file](./bicep-config.md#enable-experimental-features) to use this feature.
-
 The syntax for importing Bicep extensions is:
 
 ```bicep

articles/api-center/media/enable-api-center-portal-vs-code-extension/language-model-tools.png

@@ -3,7 +3,7 @@ title: Bicep functions - deployment
 description: Describes the functions to use in a Bicep file to retrieve deployment information.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 02/12/2025
+ms.date: 05/16/2025
 ---
 
 # Deployment functions for Bicep
@@ -14,18 +14,26 @@ This article describes the Bicep functions for getting values related to the cur
 
 `deployer()`
 
-Returns the information about the current deployment principal.
+Returns information about the principal (identity) that initiated the current deployment. The principal can be a user, service principal, or managed identity, depending on how the deployment was started.
 
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
 ### Return value
 
-This function returns the information about the current deployment principal, including tenant ID and object ID.
+This function returns an object with details about the deployment principal, including:
+
+- `objectId`: The Microsoft Entra ID object ID of the principal.
+- `tenantId`: The Microsoft Entra ID tenant ID.
+- `userPrincipalName`: The user principal name (UPN) if available. For service principals or managed identities, this property may be empty.
+
+> [!NOTE]
+> The returned values depend on the deployment context. For example, `userPrincipalName` may be empty for service principals or managed identities.
 
 ```json
 {
-  "objectId": "",
-  "tenantId": ""
+  "objectId": "<principal-object-id>",
+  "tenantId": "<tenant-id>",
+  "userPrincipalName": "<[email protected] or empty>"
 }
 ```
 
@@ -37,15 +45,18 @@ The following example Bicep file returns the deployer object.
 output deployer object = deployer()
 ```
 
-The preceding example returns the following object:
+Sample output (values differ based on your deployment):
 
 ```json
 {
   "objectId":"aaaaaaaa-0000-1111-2222-bbbbbbbbbbbb",
-  "tenantId":"aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e"
+  "tenantId":"aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e",
+  "userPrincipalName":"[email protected]"
 }
 ```
 
+For more information about Azure identities, see [What is an Azure Active Directory identity?](/azure/active-directory/fundamentals/active-directory-whatis).
+
 ## deployment
 
 `deployment()`
@@ -141,7 +152,7 @@ The preceding example returns the following object:
 
 `environment()`
 
-Returns information about the Azure environment used for deployment. The `environment()` function is not aware of resource configurations. It can only return a single default DNS suffix for each resource type.
+Returns information about the Azure environment used for deployment. The `environment()` function isn't aware of resource configurations. It can only return a single default DNS suffix for each resource type.
 
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 

articles/azure-resource-manager/bicep/bicep-extension.md

@@ -3,7 +3,7 @@ title: Imports in Bicep
 description: This article describes how to import shared functionality and namespaces in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 12/06/2024
+ms.date: 05/16/2025
 ---
 
 # Imports in Bicep
@@ -47,6 +47,8 @@ Only statements that were [exported](#export-variables-types-and-functions) in t
 
 You can use functionality that was imported from another file without restrictions. For example, you can use imported variables anywhere that a variable declared in-file would normally be valid.
 
+Starting with [Bicep CLI version 0.31.X](https://github.com/Azure/bicep/releases/tag/v0.31.34), variables imported from other Bicep files are accessible within your user-defined functions, just like variables defined locally. For more information, see [User-defined functions](./user-defined-functions.md#define-functions).
+
 ### Example
 
 *exports.bicep*