From e37bff51386538be336b02696f8c0c5c1ce2962b Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Wed, 12 Nov 2025 17:10:30 -0800 Subject: [PATCH 01/14] Added documentation for DAB MCP and AI Foundry integration setup. --- docs/Testing/ai-foundry-integration.md | 85 ++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 docs/Testing/ai-foundry-integration.md diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md new file mode 100644 index 0000000000..0601199bbc --- /dev/null +++ b/docs/Testing/ai-foundry-integration.md @@ -0,0 +1,85 @@ +# Deploying Data API Builder (DAB) MCP Server and Integrating with Azure AI Foundry + +This document provides an end‑to‑end guide to stand up a **Data API Builder (DAB)** container that exposes **REST**, **GraphQL**, and **Model Context Protocol (MCP)** endpoints, and to integrate those endpoints with an **Azure AI Foundry Agent**. + +## 1. Architecture Overview + +**Components** +- **Azure SQL Database** hosting domain tables and stored procedures. +- **DAB container** (Azure Container Instances in this guide) that: + - reads `dab-config.json` from an **Azure Files** share at startup, + - exposes **REST**, **GraphQL**, and **MCP** endpoints. +- **Azure Storage (Files)** to store and version `dab-config.json`. +- **Azure AI Foundry Agent** configured with an **MCP tool** pointing to the DAB MCP endpoint. + +**Flow** +1. DAB starts in ACI → reads `dab-config.json` from the mounted Azure Files share. +2. DAB exposes `/api` (REST), `/graphql` (GraphQL), and `/mcp` (MCP). +3. Azure AI Foundry Agent invokes MCP tools to read/update data via DAB’s surface (entities and stored procedures). + + +## 2. Prerequisites +- Azure Subscription with permissions for Resource Groups, Storage, ACI, and Azure SQL. +- Azure SQL Database provisioned and reachable from ACI. +- Azure CLI (`az`) and .NET SDK installed locally. +- DAB CLI version **1.7.81 or later**. +- Outbound network access from ACI to your Azure SQL server. + + +## 3. Prepare the Database +Create tables and stored procedures: +- Tables +- Stored Procedures + +## 4. Install DAB CLI and Bootstrap Configuration +``` +dotnet tool install --global Microsoft.DataApiBuilder --version 1.7.81 +export DATABASE_CONNECTION_STRING="Server=.database.windows.net;Database=;User ID=;Password=;Encrypt=True;" + +dab init \ + --database-type "mssql" \ + --connection-string "@env('DATABASE_CONNECTION_STRING')" \ + --host-mode "Development" \ + --rest.enabled true \ + --graphql.enabled true \ + --mcp.enabled true \ + --mcp.path "/mcp" + +``` + +## 5. Add entities and stored procedure to `dab-config.json` and enable MCP tools in the config. + +## 6. Store dab-config.json in Azure Files +- Create a Storage Account and File Share. +- Upload dab-config.json. +- Record account name and key for mounting in ACI. + +## 7. Deploy DAB to Azure Container Instances + +``` +az container create \ + --resource-group \ + --name dab-mcp-demo \ + --image mcr.microsoft.com/azure-databases/data-api-builder:1.7.81-rc \ + --dns-name-label \ + --ports 5000 \ + --location \ + --environment-variables DAB_CONFIG_PATH="/aci/dab-config.json" \ + --azure-file-volume-share-name \ + --azure-file-volume-account-name \ + --azure-file-volume-account-key \ + --azure-file-volume-mount-path "/aci" + --os-type Linux \ + --cpu 1 \ + --memory 1.5 \ + --command-line "dotnet Azure.DataApiBuilder.Service.dll --ConfigFileName $configFile --LogLevel Debug" +``` +REST: http:///api/ +GraphQL: http:///graphql +MCP: http:///mcp + +## 8. Integrate with Azure AI Foundry +- Create or open a Project. +- Add an Agent. +- Add MCP tool with URL: http:///mcp. +- Test in Playground \ No newline at end of file From 5c1e6d830c7827aeb56d3e682e499a4cd79bea6f Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:57:13 -0800 Subject: [PATCH 02/14] Apply suggestion from @Aniruddh25 Co-authored-by: Aniruddh Munde --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index 0601199bbc..c52d1d3f8d 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -1,4 +1,4 @@ -# Deploying Data API Builder (DAB) MCP Server and Integrating with Azure AI Foundry +# Deploying SQL MCP Server implemented in Data API builder and Integrating with Azure AI Foundry This document provides an end‑to‑end guide to stand up a **Data API Builder (DAB)** container that exposes **REST**, **GraphQL**, and **Model Context Protocol (MCP)** endpoints, and to integrate those endpoints with an **Azure AI Foundry Agent**. From 15882fb36f768ad504bf56aa0e5dcedfb81139e8 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:57:24 -0800 Subject: [PATCH 03/14] Apply suggestion from @Aniruddh25 Co-authored-by: Aniruddh Munde --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index c52d1d3f8d..b6579bd476 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -1,6 +1,6 @@ # Deploying SQL MCP Server implemented in Data API builder and Integrating with Azure AI Foundry -This document provides an end‑to‑end guide to stand up a **Data API Builder (DAB)** container that exposes **REST**, **GraphQL**, and **Model Context Protocol (MCP)** endpoints, and to integrate those endpoints with an **Azure AI Foundry Agent**. +This document provides an end‑to‑end guide to stand up a **SQL MCP Server** with **Model Context Protocol (MCP)** tools implemented in **Data API builder (DAB)** container that also exposes **REST** and **GraphQL** endpoints, and to integrate those MCP tools with an **Azure AI Foundry Agent**. ## 1. Architecture Overview From 555fd04d8d3ac944103c4242717562bf7199cad5 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:57:32 -0800 Subject: [PATCH 04/14] Apply suggestion from @Aniruddh25 Co-authored-by: Aniruddh Munde --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index b6579bd476..d828c22c3e 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -10,7 +10,7 @@ This document provides an end‑to‑end guide to stand up a **SQL MCP Server** - reads `dab-config.json` from an **Azure Files** share at startup, - exposes **REST**, **GraphQL**, and **MCP** endpoints. - **Azure Storage (Files)** to store and version `dab-config.json`. -- **Azure AI Foundry Agent** configured with an **MCP tool** pointing to the DAB MCP endpoint. +- **Azure AI Foundry Agent** configured with an **MCP tool** pointing to the SQL MCP Server endpoint. **Flow** 1. DAB starts in ACI → reads `dab-config.json` from the mounted Azure Files share. From 252f6b291bce1afc572f99659ffca8ed274119b2 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:57:40 -0800 Subject: [PATCH 05/14] Apply suggestion from @Aniruddh25 Co-authored-by: Aniruddh Munde --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index d828c22c3e..d5e865c14e 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -15,7 +15,7 @@ This document provides an end‑to‑end guide to stand up a **SQL MCP Server** **Flow** 1. DAB starts in ACI → reads `dab-config.json` from the mounted Azure Files share. 2. DAB exposes `/api` (REST), `/graphql` (GraphQL), and `/mcp` (MCP). -3. Azure AI Foundry Agent invokes MCP tools to read/update data via DAB’s surface (entities and stored procedures). +3. Azure AI Foundry Agent invokes MCP tools to read/update data via DAB’s surface (tables, views and stored procedures). ## 2. Prerequisites From d0be94ccab4bf9e62f295ecd65a90e2cdcc2c00b Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:58:08 -0800 Subject: [PATCH 06/14] Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/Testing/ai-foundry-integration.md | 30 +++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index d5e865c14e..b0836483b5 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -27,10 +27,34 @@ This document provides an end‑to‑end guide to stand up a **SQL MCP Server** ## 3. Prepare the Database -Create tables and stored procedures: -- Tables -- Stored Procedures +You need to create the necessary tables and stored procedures in your Azure SQL Database. Below is an example of how to create a simple `Products` table and a stored procedure to retrieve products by category. + +**Example:** + +1. Connect to your Azure SQL Database using Azure Data Studio, SQL Server Management Studio, or the Azure Portal's Query Editor. + +2. Run the following SQL script to create a sample table and stored procedure: + +```sql +-- Create Products table +CREATE TABLE Products ( + ProductID INT IDENTITY(1,1) PRIMARY KEY, + Name NVARCHAR(100) NOT NULL, + Category NVARCHAR(50) NOT NULL, + Price DECIMAL(10,2) NOT NULL +); + +-- Create stored procedure to get products by category +CREATE PROCEDURE GetProductsByCategory + @Category NVARCHAR(50) +AS +BEGIN + SET NOCOUNT ON; + SELECT ProductID, Name, Category, Price + FROM Products + WHERE Category = @Category; +END; ## 4. Install DAB CLI and Bootstrap Configuration ``` dotnet tool install --global Microsoft.DataApiBuilder --version 1.7.81 From e506df8ab640d064e2111ab219ee76d69b4e6705 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:58:19 -0800 Subject: [PATCH 07/14] Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index b0836483b5..e72684e6e8 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -71,7 +71,7 @@ dab init \ ``` -## 5. Add entities and stored procedure to `dab-config.json` and enable MCP tools in the config. +## 5. Add entities and stored procedure to `dab-config.json` and enable MCP tools in the config ## 6. Store dab-config.json in Azure Files - Create a Storage Account and File Share. From 000615d02720c87b7d896ecb1a580c348659ecd0 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:59:29 -0800 Subject: [PATCH 08/14] Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/Testing/ai-foundry-integration.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index e72684e6e8..e496769c78 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -97,10 +97,6 @@ az container create \ --cpu 1 \ --memory 1.5 \ --command-line "dotnet Azure.DataApiBuilder.Service.dll --ConfigFileName $configFile --LogLevel Debug" -``` -REST: http:///api/ -GraphQL: http:///graphql -MCP: http:///mcp ## 8. Integrate with Azure AI Foundry - Create or open a Project. From c0b4365b8ab7bb4ce997ded9d3ae46049ba08d30 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 00:59:57 -0800 Subject: [PATCH 09/14] Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/Testing/ai-foundry-integration.md | 38 +++++++++++++++++++++++--- 1 file changed, 34 insertions(+), 4 deletions(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index e496769c78..d561207962 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -99,7 +99,37 @@ az container create \ --command-line "dotnet Azure.DataApiBuilder.Service.dll --ConfigFileName $configFile --LogLevel Debug" ## 8. Integrate with Azure AI Foundry -- Create or open a Project. -- Add an Agent. -- Add MCP tool with URL: http:///mcp. -- Test in Playground \ No newline at end of file + +Follow these steps to connect your DAB MCP endpoint to Azure AI Foundry and test the integration: + +1. **Create or Open a Project** + - Navigate to the [Azure AI Foundry portal](https://ai.azure.com/foundry) and sign in. + - On the dashboard, click **Projects** in the left navigation pane. + - To create a new project, click **New Project**, enter a name (e.g., `DAB-MCP-Demo`), and click **Create**. + - To use an existing project, select it from the list. + +2. **Add an Agent** + - Within your project, go to the **Agents** tab. + - Click **Add Agent**. + - Enter an agent name (e.g., `DAB-MCP-Agent`). + - (Optional) Add a description. + - Click **Create**. + +3. **Configure the MCP Tool** + - In the agent's configuration page, go to the **Tools** section. + - Click **Add Tool** and select **MCP** from the tool type dropdown. + - In the **MCP Endpoint URL** field, enter your DAB MCP endpoint, e.g., `http:///mcp`. + - (Optional) Configure authentication if your endpoint requires it. + - Click **Save** to add the tool. + +4. **Test in Playground** + - Go to the **Playground** tab in your project. + - Select the agent you created from the agent dropdown. + - In the input box, enter a prompt that will trigger the MCP tool, such as: + ``` + Get all records from the Customers entity. + ``` + - Click **Run**. + - The agent should invoke the MCP tool, which will call your DAB MCP endpoint and return the results. + - **Expected Result:** You should see the data returned from your DAB instance displayed in the Playground output panel. + - If there are errors, check the DAB container logs and ensure the MCP endpoint is reachable from Azure AI Foundry. \ No newline at end of file From 21fea4a1231e4fe8f55974a67963ad64079fa536 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 01:00:24 -0800 Subject: [PATCH 10/14] Apply suggestion from @Copilot Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index d561207962..7788dd68a1 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -96,7 +96,7 @@ az container create \ --os-type Linux \ --cpu 1 \ --memory 1.5 \ - --command-line "dotnet Azure.DataApiBuilder.Service.dll --ConfigFileName $configFile --LogLevel Debug" + --command-line "dotnet Azure.DataApiBuilder.Service.dll --ConfigFileName $DAB_CONFIG_PATH --LogLevel Debug" ## 8. Integrate with Azure AI Foundry From 97b05c863193cf448e92babc7cb535aac4a0abd6 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Sat, 20 Dec 2025 01:27:08 -0800 Subject: [PATCH 11/14] Improved the documentation --- docs/Testing/ai-foundry-integration.md | 148 ++++++++++++++++++++++++- 1 file changed, 143 insertions(+), 5 deletions(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index 7788dd68a1..d69b23d5ba 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -55,7 +55,10 @@ BEGIN FROM Products WHERE Category = @Category; END; +``` + ## 4. Install DAB CLI and Bootstrap Configuration + ``` dotnet tool install --global Microsoft.DataApiBuilder --version 1.7.81 export DATABASE_CONNECTION_STRING="Server=.database.windows.net;Database=;User ID=;Password=;Encrypt=True;" @@ -71,12 +74,146 @@ dab init \ ``` -## 5. Add entities and stored procedure to `dab-config.json` and enable MCP tools in the config +## 5. Add all required entities (tables and stored procedures) to `dab-config.json` and enable MCP tools in the config + +Here is how to add a table entity and a stored procedure to your `dab-config.json`, and ensure MCP tools are enabled: + +1. **Open your `dab-config.json` file.** + +2. **Add an entity (table) definition** under the `"entities"` section. For example, to expose a `Customers` table: + ``` + "entities": { + "Customers": { + "source": "Customers", + "rest": true, + "graphql": true, + "mcp": true, + "permissions": [ + { + "role": "anonymous", + "actions": [ "read", "create", "update", "delete" ] + } + ] + } + } + ``` + +3. **Add a stored procedure** under the "entities" section. For example, to expose a stored procedure called GetCustomerOrders: + + ``` + "GetCustomerOrders": { + "source": { + "object": "GetCustomerOrders", + "type": "stored-procedure" + }, + "rest": true, + "graphql": true, + "mcp": true, + "permissions": [ + { + "role": "anonymous", + "actions": [ "execute" ] + } + ] + } + ``` + +Note: Make sure the "entities" section is a valid JSON object. If you have multiple entities, separate them with commas. + +4. **Ensure MCP is enabled in the "runtime" section:** + +``` +"runtime": { + "rest": { "enabled": true }, + "graphql": { "enabled": true }, + "mcp": { + "enabled": true, + "path": "/mcp" + } +} +``` + +5. **Example dab-config.json structure:** + +``` +{ + "data-source": { + "database-type": "mssql", + "connection-string": "@env('DATABASE_CONNECTION_STRING')" + }, + "entities": { + "Customers": { + "source": "Customers", + "rest": true, + "graphql": true, + "mcp": true, + "permissions": [ + { + "role": "anonymous", + "actions": [ "read", "create", "update", "delete" ] + } + ] + }, + "GetCustomerOrders": { + "source": { + "object": "GetCustomerOrders", + "type": "stored-procedure" + }, + "rest": true, + "graphql": true, + "mcp": true, + "permissions": [ + { + "role": "anonymous", + "actions": [ "execute" ] + } + ] + } + }, + "runtime": { + "rest": { "enabled": true }, + "graphql": { "enabled": true }, + "mcp": { + "enabled": true, + "path": "/mcp" + } + } +} +``` + +6. **Save the file.** ## 6. Store dab-config.json in Azure Files -- Create a Storage Account and File Share. -- Upload dab-config.json. -- Record account name and key for mounting in ACI. + +1. **Create a Storage Account** (if you don't have one): +az storage account create +--name +--resource-group +--location +--sku Standard_LRS + + +2. **Create a File Share**: +az storage share create +--name +--account-name + + +3. **Upload `dab-config.json` to the File Share**: +az storage file upload +--account-name +--share-name +--source ./dab-config.json +--path dab-config.json + + +4. **Retrieve the Storage Account key** (needed for mounting in ACI): +az storage account keys list +--account-name +--resource-group + +Use the value of `key1` or `key2` as `` in the next step. + ## 7. Deploy DAB to Azure Container Instances @@ -92,11 +229,12 @@ az container create \ --azure-file-volume-share-name \ --azure-file-volume-account-name \ --azure-file-volume-account-key \ - --azure-file-volume-mount-path "/aci" + --azure-file-volume-mount-path "/aci" \ --os-type Linux \ --cpu 1 \ --memory 1.5 \ --command-line "dotnet Azure.DataApiBuilder.Service.dll --ConfigFileName $DAB_CONFIG_PATH --LogLevel Debug" +``` ## 8. Integrate with Azure AI Foundry From 5f8f46a6bc4eb8146ea3546bae1db1b8b61a5e7e Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Mon, 22 Dec 2025 15:32:28 -0800 Subject: [PATCH 12/14] Update docs/Testing/ai-foundry-integration.md Co-authored-by: Aniruddh Munde --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index d69b23d5ba..4c81257315 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -256,7 +256,7 @@ Follow these steps to connect your DAB MCP endpoint to Azure AI Foundry and test 3. **Configure the MCP Tool** - In the agent's configuration page, go to the **Tools** section. - Click **Add Tool** and select **MCP** from the tool type dropdown. - - In the **MCP Endpoint URL** field, enter your DAB MCP endpoint, e.g., `http:///mcp`. + - In the **MCP Endpoint URL** field, enter your SQL MCP endpoint in DAB, e.g., `http:///mcp`. - (Optional) Configure authentication if your endpoint requires it. - Click **Save** to add the tool. From ed894c5f7980cb9f45daba62bb350f2e71f0b64d Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Mon, 22 Dec 2025 15:32:40 -0800 Subject: [PATCH 13/14] Update docs/Testing/ai-foundry-integration.md Co-authored-by: Aniruddh Munde --- docs/Testing/ai-foundry-integration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index 4c81257315..dfad8f2cc7 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -238,7 +238,7 @@ az container create \ ## 8. Integrate with Azure AI Foundry -Follow these steps to connect your DAB MCP endpoint to Azure AI Foundry and test the integration: +Follow these steps to connect your SQL MCP endpoint deployed in DAB to Azure AI Foundry and test the integration: 1. **Create or Open a Project** - Navigate to the [Azure AI Foundry portal](https://ai.azure.com/foundry) and sign in. From 2b614b494f5ee2327b9cfabe4415da8a5f107556 Mon Sep 17 00:00:00 2001 From: Anusha Kolan Date: Mon, 22 Dec 2025 16:09:19 -0800 Subject: [PATCH 14/14] Refactor runtime configuration in ai-foundry-integration Re-ordered the structure of config file. --- docs/Testing/ai-foundry-integration.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/Testing/ai-foundry-integration.md b/docs/Testing/ai-foundry-integration.md index dfad8f2cc7..c43434a793 100644 --- a/docs/Testing/ai-foundry-integration.md +++ b/docs/Testing/ai-foundry-integration.md @@ -141,6 +141,14 @@ Note: Make sure the "entities" section is a valid JSON object. If you have multi "database-type": "mssql", "connection-string": "@env('DATABASE_CONNECTION_STRING')" }, + "runtime": { + "rest": { "enabled": true }, + "graphql": { "enabled": true }, + "mcp": { + "enabled": true, + "path": "/mcp" + } + }, "entities": { "Customers": { "source": "Customers", @@ -169,14 +177,6 @@ Note: Make sure the "entities" section is a valid JSON object. If you have multi } ] } - }, - "runtime": { - "rest": { "enabled": true }, - "graphql": { "enabled": true }, - "mcp": { - "enabled": true, - "path": "/mcp" - } } } ``` @@ -270,4 +270,4 @@ Follow these steps to connect your SQL MCP endpoint deployed in DAB to Azure AI - Click **Run**. - The agent should invoke the MCP tool, which will call your DAB MCP endpoint and return the results. - **Expected Result:** You should see the data returned from your DAB instance displayed in the Playground output panel. - - If there are errors, check the DAB container logs and ensure the MCP endpoint is reachable from Azure AI Foundry. \ No newline at end of file + - If there are errors, check the DAB container logs and ensure the MCP endpoint is reachable from Azure AI Foundry.