Rename .NET Aspire to Aspire

.openpublishing.redirection.json

@@ -809,6 +809,11 @@
       "source_path_from_root": "/data-api-builder/includes/database-isolation-levels.md",
       "redirect_url": "/azure/data-api-builder/feature-availability",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/data-api-builder/mcp/quickstart-dotnet-aspire.md",
+      "redirect_url": "/azure/data-api-builder/mcp/quickstart-aspire",
+      "redirect_document_id": false
     }
   ]
 }

data-api-builder/TOC.yml

@@ -286,8 +286,8 @@
       href: mcp/quickstart-visual-studio-code.md
     - name: "Get Started: Azure AI Foundry"
       href: mcp/quickstart-azure-ai-foundry.md
-    - name: "Get Started: .NET Aspire"
-      href: mcp/quickstart-dotnet-aspire.md
+    - name: "Get Started: Aspire"
+      href: mcp/quickstart-aspire.md
     - name: "Get Started: Azure Container Apps"
       href: mcp/quickstart-azure-container-apps.md
     - name: Authentication

data-api-builder/concept/monitor/open-telemetry.md

@@ -72,7 +72,7 @@ Use `dab add-telemetry` to add OpenTelemetry settings to your config.
 1. Confirm that traces and metrics are arriving for REST, GraphQL, or database calls.
 
 > [!NOTE]
-> The .NET Aspire dashboard is an ideal part of the developer loop. It includes built-in views for OpenTelemetry traces and metrics.
+> The Aspire dashboard is an ideal part of the developer loop. It includes built-in views for OpenTelemetry traces and metrics.
 
 ## Data API builder traces
 

data-api-builder/feature-availability.md

@@ -182,7 +182,7 @@ Data API builder runs in any environment with container support. The following a
 | [OpenTelemetry](concept/monitor/open-telemetry.md) | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
 | [Health Endpoints](concept/monitor/health-checks.md) | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
 | [Custom Log Levels](concept/monitor/log-levels.md) | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
-| [.NET Aspire](mcp/quickstart-dotnet-aspire.md) | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
+| [Aspire](mcp/quickstart-aspire.md) | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
 | [MCP³](mcp/overview.md) | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes |
 
 ## MCP Server

data-api-builder/index.yml

@@ -110,8 +110,8 @@ conceptualContent:
             - text: "Quickstart: Azure AI Foundry"
               url: mcp/quickstart-azure-ai-foundry.md
               itemType: quickstart
-            - text: "Quickstart: .NET Aspire"
-              url: mcp/quickstart-dotnet-aspire.md
+            - text: "Quickstart: Aspire"
+              url: mcp/quickstart-aspire.md
               itemType: quickstart
             - text: "Quickstart: Azure Container Apps"
               url: mcp/quickstart-azure-container-apps.md

data-api-builder/mcp/includes/section-quickstart-selector.md

@@ -6,7 +6,7 @@ ms.date: 12/22/2025
 > [!div class="op_single_selector"]
 >
 > - [Azure AI Foundry](../quickstart-azure-ai-foundry.md)
-> - [.NET Aspire](../quickstart-dotnet-aspire.md)
+> - [Aspire](../quickstart-aspire.md)
 > - [Visual Studio Code](../quickstart-visual-studio-code.md)
 > - [Azure Container Apps](../quickstart-azure-container-apps.md)
 >

data-api-builder/mcp/index.yml

@@ -30,8 +30,8 @@ landingContent:
         links:
           - text: Visual Studio Code
             url: quickstart-visual-studio-code.md
-          - text: .NET Aspire
-            url: quickstart-dotnet-aspire.md
+          - text: Aspire
+            url: quickstart-aspire.md
           - text: Azure AI Foundry
             url: quickstart-azure-ai-foundry.md
           - text: Azure Container Apps

data-api-builder/mcp/overview.md

@@ -258,5 +258,5 @@ MCP tool execution is fully instrumented with OpenTelemetry (OTEL) spans. Each M
 - [Data manipulation tools in SQL MCP Server](data-manipulation-language-tools.md)
 - [Deploy SQL MCP Server to Azure Container Apps](quickstart-azure-container-apps.md)
 - [Get started with SQL MCP Server in Visual Studio Code](quickstart-visual-studio-code.md)
-- [Get started with SQL MCP Server in .NET Aspire](quickstart-dotnet-aspire.md)
+- [Get started with SQL MCP Server in Aspire](quickstart-aspire.md)
 - [Get started with SQL MCP Server in Azure AI Foundry](quickstart-azure-ai-foundry.md)

data-api-builder/mcp/quickstart-dotnet-aspire.md → data-api-builder/mcp/quickstart-aspire.md

@@ -1,17 +1,17 @@
 ---
-title: Quickstart - .NET Aspire
-description: Start SQL MCP Server with .NET Aspire. Build container-based solutions with SQL database, Data API builder, and MCP Inspector. Get started now.
+title: Quickstart - Aspire
+description: Start SQL MCP Server with Aspire. Build container-based solutions with SQL database, Data API builder, and MCP Inspector. Get started now.
 author: jnixon
 ms.author: jnixon
 ms.topic: quickstart
 ms.date: 12/22/2025
 ---
 
-# Quickstart: Use SQL MCP Server with .NET Aspire
+# Quickstart: Use SQL MCP Server with Aspire
 
 [!INCLUDE[Section - Quickstart selector](includes/section-quickstart-selector.md)]
 
-![Diagram that shows the Aspire solution with SQL Server, SQL MCP Server, and MCP Inspector.](media/quickstart-dotnet-aspire/diagram.svg)
+![Diagram that shows the Aspire solution with SQL Server, SQL MCP Server, and MCP Inspector.](media/quickstart-aspire/diagram.svg)
 
 [!INCLUDE[Note - SQL MCP availability](includes/note-availability.md)]
 
@@ -194,7 +194,7 @@ This code configures the following resources:
     └── MCP Inspector (inspector)
 ```
 
-![Diagram showing the Aspire resources and their connections.](media/quickstart-dotnet-aspire/dashboard-resources-connections.png)
+![Diagram showing the Aspire resources and their connections.](media/quickstart-aspire/dashboard-resources-connections.png)
 
 ### 5. Create your dab-config.json file
 
@@ -246,7 +246,7 @@ aspire run
 
 When the dashboard opens, you see links for Swagger, MCP, and Inspector.
 
-![Screenshot of the Aspire dashboard showing the running environment.](media/quickstart-dotnet-aspire/dashboard-running-environment.png)
+![Screenshot of the Aspire dashboard showing the running environment.](media/quickstart-aspire/dashboard-running-environment.png)
 
 #### Expected URLs
 

data-api-builder/whats-new/version-1-6.md

@@ -217,7 +217,7 @@ DAB's new relative `nextLink` option lets developers configure the engine to emi
 
 ## Health checks
 
-To deliver a faster composite status, Data API builder health checks now run in parallel. This reduces latency in multi-source deployments, especially when several endpoints are involved and health checks are used to determine the deployment status of the DAB container, such as in the .NET Aspire application host.
+To deliver a faster composite status, Data API builder health checks now run in parallel. This reduces latency in multi-source deployments, especially when several endpoints are involved and health checks are used to determine the deployment status of the DAB container, such as in the Aspire application host.
 
 **Example Health DOP configuration:**