dotnet · gewarren · Jun 29, 2026 · Jun 29, 2026 · Jun 29, 2026 · Jun 29, 2026
@@ -137,4 +137,4 @@ AI systems often stop being "just one app" once retrieval, tools, gateways, and
 
 Aspire isn't specifically the AI runtime; it's the multi-service application layer around it. It doesn't replace MEAI, MAF, or Azure AI Foundry.
 
-For more information, see the [Aspire documentation](/dotnet/aspire/).
+For more information, see the [Aspire documentation](https://aspire.dev/).
@@ -73,10 +73,10 @@ conceptualContent:
     - title: Create cloud native apps
       links:
         - itemType: overview
-          url: /dotnet/aspire/get-started/aspire-overview
-          text: Build cloud native apps using Aspire
+          url: https://aspire.dev/get-started/what-is-aspire/
+          text: What is Aspire?
         - itemType: quickstart
-          url: /dotnet/aspire/get-started/build-your-first-aspire-app?tabs=visual-studio
+          url: https://aspire.dev/get-started/first-app/
           text: Build your first Aspire app
         - itemType: quickstart
           text: Run and debug a microservice in Kubernetes

@@ -25,9 +25,6 @@ items:
           - name: Azure
             tocHref: /dotnet/azure/
             topicHref: /dotnet/azure/index
-          - name: Aspire
-            tocHref: /dotnet/aspire/
-            topicHref: /dotnet/aspire/index
           - name: Orleans
             tocHref: /dotnet/orleans/
             topicHref: /dotnet/orleans/index

@@ -11,7 +11,7 @@ ms.custom: "updateeachrelease"
 
 ## Cloud apps
 
-* [Aspire](/dotnet/aspire)
+* [Aspire](https://aspire.dev/)
 * [Serverless functions](/azure/azure-functions/functions-create-first-function-vs-code?pivots=programming-language-csharp)
 * [Web and microservices](/aspnet/core/introduction-to-aspnet-core#recommended-learning-path)
 

@@ -10,7 +10,7 @@ ms.custom: sfi-image-nochange
 
 This article is one of a series of examples to illustrate [.NET observability with OpenTelemetry](./observability-with-otel.md).
 
-In addition to being a standard part of Aspire, the Aspire Dashboard is available as a [standalone Docker container](/dotnet/aspire/fundamentals/dashboard/standalone?tabs=powershell), which provides an OTLP endpoint that telemetry can be sent to. The dashboard visualizes the logs, metrics, and traces. Using the dashboard in this way has no dependency on Aspire, and it visualizes telemetry from any application that sends it telemetry via OTLP. It works equally well for applications written in Java, GoLang, or Python provided they can send their telemetry to an OTLP endpoint.
+In addition to being a standard part of Aspire, the Aspire Dashboard is available as a [standalone Docker container](https://aspire.dev/dashboard/standalone/), which provides an OTLP endpoint that telemetry can be sent to. The dashboard visualizes the logs, metrics, and traces. Using the dashboard in this way has no dependency on Aspire, and it visualizes telemetry from any application that sends it telemetry via OTLP. It works equally well for applications written in Java, GoLang, or Python provided they can send their telemetry to an OTLP endpoint.
 
 Using the Aspire Dashboard has less configuration and setup steps than using Open Source solutions such as [Prometheus, Grafana, and Jaeger](./observability-prgrja-example.md). But unlike those tools, the Aspire Dashboard is intended as a developer visualization tool, and not for production monitoring.
 

@@ -97,19 +97,19 @@ This topic is continued with a couple of example walkthroughs for using OpenTele
 
 ## OpenTelemetry in Aspire
 
-[Aspire](/dotnet/aspire/get-started/aspire-overview) is a set of extensions to .NET to make it easy to create and work with distributed applications. One of the benefits of using Aspire is that telemetry is built in, using the OpenTelemetry libraries for .NET. The default project templates for Aspire contain a `ServiceDefaults` project, part of which is to setup and configure OTel. The Service Defaults project is referenced and initialized by each service in an Aspire solution.
+[Aspire](https://aspire.dev/get-started/what-is-aspire/) is a set of extensions to .NET to make it easy to create and work with distributed applications. One of the benefits of using Aspire is that telemetry is built in, using the OpenTelemetry libraries for .NET. The default project templates for Aspire contain a `ServiceDefaults` project, part of which is to setup and configure OTel. The Service Defaults project is referenced and initialized by each service in an Aspire solution.
 
-The Service Defaults project template includes the OTel SDK, ASP.NET, HttpClient and Runtime Instrumentation packages, and those are configured in the [`Extensions.cs`](https://github.com/dotnet/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-servicedefaults/Extensions.cs) file. For exporting telemetry, Aspire includes the OTLP exporter by default so that it can provide telemetry visualization using the Aspire Dashboard.
+The Service Defaults project template includes the OTel SDK, ASP.NET, HttpClient and Runtime Instrumentation packages, and those are configured in the [`Extensions.cs`](https://github.com/microsoft/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-servicedefaults/Extensions.cs) file. For exporting telemetry, Aspire includes the OTLP exporter by default so that it can provide telemetry visualization using the Aspire Dashboard.
 
 The Aspire Dashboard is designed to bring telemetry observation to the local debug cycle, which enables developers to not only ensure that the applications are producing telemetry, but also use that telemetry to diagnose those applications locally. Being able to observe the calls between services is proving to be just as useful at debug time as in production. The Aspire dashboard is launched automatically when you <kbd>F5</kbd> the `AppHost` Project from Visual Studio or `dotnet run` the `AppHost` project.
 
 [![Aspire Dashboard](./media/aspire-dashboard-thumb.png)](./media/aspire-dashboard.png#lightbox)
 
 For more details on Aspire see:
 
-- [Aspire Overview](/dotnet/aspire/get-started/aspire-overview)
-- [Telemetry in Aspire](/dotnet/aspire/fundamentals/telemetry)
-- [Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/explore)
+- [Aspire Overview](https://aspire.dev/get-started/what-is-aspire/)
+- [Telemetry in Aspire](https://aspire.dev/fundamentals/telemetry/)
+- [Aspire Dashboard](https://aspire.dev/dashboard/explore/)
 
 ### Reuse Service Defaults project without Aspire Orchestration
 

@@ -140,7 +140,7 @@ When you call either <xref:Microsoft.Extensions.Hosting.IHostBuilder.Build?displ
 
 If you're building for the web or writing a distributed application, you might need to use a different host builder. Consider the following list of additional host builders:
 
-- [DistributedApplicationBuilder](https://aspire.dev/reference/api/csharp/aspire.hosting/distributedapplicationbuilder/): A builder for creating distributed apps. For more information, see [Aspire](/dotnet/aspire).
+- [DistributedApplicationBuilder](https://aspire.dev/reference/api/csharp/aspire.hosting/distributedapplicationbuilder/): A builder for creating distributed apps. For more information, see [Aspire](https://aspire.dev/).
 - <xref:Microsoft.AspNetCore.Builder.WebApplicationBuilder>: A builder for web applications and services. For more information, see [ASP.NET Core](/aspnet/core).
 - <xref:Microsoft.AspNetCore.Hosting.WebHostBuilder>: A builder for `IWebHost`. For more information, see [ASP.NET Core web host](/aspnet/core/fundamentals/host/web-host).
 

@@ -150,4 +150,4 @@ If service discovery was added to the host using the `AddServiceDiscoveryCore` e
 
 ## See also
 
-- [Service discovery in Aspire](/dotnet/aspire/service-discovery/overview)
+- [Service discovery in Aspire](https://aspire.dev/fundamentals/service-discovery/)
@@ -22,7 +22,7 @@ The available SDKs include:
 | `Microsoft.NET.Sdk.Razor`  | The .NET [Razor SDK](/aspnet/core/razor-pages/sdk)                                   | <https://github.com/dotnet/aspnetcore> |
 | `Microsoft.NET.Sdk.BlazorWebAssembly` | The .NET [Blazor WebAssembly SDK](/aspnet/core/blazor#blazor-webassembly) | <https://github.com/dotnet/aspnetcore> |
 | `Microsoft.NET.Sdk.Worker` | The .NET [Worker Service SDK](../extensions/workers.md)                              | <https://github.com/dotnet/aspnetcore> |
-| `Aspire.AppHost.Sdk`       | The [Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk)                      | <https://github.com/dotnet/aspire>     |
+| `Aspire.AppHost.Sdk`       | The [Aspire SDK](https://aspire.dev/get-started/app-host/)                           | <https://github.com/microsoft/aspire>     |
 | `MSTest.Sdk`               | The [MSTest SDK](../testing/unit-testing-mstest-sdk.md)                              | <https://github.com/microsoft/testfx>  |
 
 The .NET SDK is the base SDK for .NET. The other SDKs reference the .NET SDK, and projects that are associated with the other SDKs have all the .NET SDK properties available to them. The Web SDK, for example, depends on both the .NET SDK and the Razor SDK.
@@ -54,7 +54,7 @@ The `Project/Sdk` attribute and `Sdk` element enable additive SDKs. Consider the
 </Project>
 ```
 
-In the preceding project file, both SDKs are used to resolve dependencies in an additive nature. For more information, see [Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk).
+In the preceding project file, both SDKs are used to resolve dependencies in an additive nature. For more information, see [Aspire SDK](https://aspire.dev/get-started/app-host/).
 
 To specify an SDK that comes from NuGet, include the version at the end of the name, or specify the name and version in the *global.json* file.
 

@@ -75,7 +75,7 @@ _Enrichment_ is the automatic augmentation of telemetry with well-known state, i
 
 ### How enrichment works
 
-Imagine 1,000 globally distributed service instances generating logs and metrics. When you encounter an issue on your [service dashboard](/dotnet/aspire/dashboard), it's crucial to quickly identify the problematic region or data center. Enrichment ensures that metric records contain the necessary information to pinpoint failures in distributed systems. Without enrichment, the burden falls on the app code to internally manage this state, integrate it into the logging process, and manually transmit it. Enrichment simplifies this process, seamlessly handling it without affecting the app's logic.
+Imagine 1,000 globally distributed service instances generating logs and metrics. When you encounter an issue on your [service dashboard](https://aspire.dev/dashboard/overview/), it's crucial to quickly identify the problematic region or data center. Enrichment ensures that metric records contain the necessary information to pinpoint failures in distributed systems. Without enrichment, the burden falls on the app code to internally manage this state, integrate it into the logging process, and manually transmit it. Enrichment simplifies this process, seamlessly handling it without affecting the app's logic.
 
 In the case of resiliency, when you add enrichment the following dimensions are added to the outgoing telemetry:
 

@@ -130,7 +130,7 @@ Outside of the selection of the runner and runner-specific extensions, `MSTest.S
 
 ### Test with Aspire
 
-Aspire is an opinionated, cloud-ready stack for building observable, production ready, distributed applications. Aspire is delivered through a collection of NuGet packages that handle specific cloud-native concerns. For more information, see the [Aspire docs](/dotnet/aspire/get-started/aspire-overview).
+Aspire is an opinionated, cloud-ready stack for building observable, production ready, distributed applications. Aspire is delivered through a collection of NuGet packages that handle specific cloud-native concerns. For more information, see the [Aspire docs](https://aspire.dev/get-started/what-is-aspire/).
 
 > [!NOTE]
 > This feature is available from MSTest.Sdk 3.4.0.

@@ -23,7 +23,7 @@ C# 12 shipped with the .NET 8 SDK. For more information, see [What's new in C# 1
 
 ## Aspire
 
-Aspire is an opinionated, cloud-ready stack for building observable, production ready, distributed applications. Aspire is delivered through a collection of NuGet packages that handle specific cloud-native concerns, and is available in preview for .NET 8. For more information, see [Aspire](/dotnet/aspire).
+Aspire is an opinionated, cloud-ready stack for building observable, production ready, distributed applications. Aspire is delivered through a collection of NuGet packages that handle specific cloud-native concerns, and is available in preview for .NET 8. For more information, see [Aspire](https://aspire.dev/).
 
 ## ASP.NET Core
 

@@ -223,9 +223,9 @@ additionalContent:
           links:
             - url: ../azure/index.yml
               text: Azure for .NET developers
-            - url: /dotnet/aspire
+            - url: https://aspire.dev/
               text: Aspire
-            - url: /dotnet/aspire/get-started/quickstart-build-your-first-aspire-app
+            - url: https://aspire.dev/get-started/first-app/
               text: Build cloud-native apps with Aspire
             - url: ../azure/migration/app-service.md?preserve-view=true&view=azure-dotnet
               text: Migrate on-premises .NET web apps or services

@@ -1,7 +1,7 @@
-A simple way to collect traces and metrics in ASP.NET applications is to use [Aspire](/dotnet/aspire/get-started/aspire-overview). Aspire is a set of extensions to .NET to make it easy to create and work with distributed applications. One of the benefits of using Aspire is that telemetry is built in, using the OpenTelemetry libraries for .NET.
+A simple way to collect traces and metrics in ASP.NET applications is to use [Aspire](https://aspire.dev/get-started/what-is-aspire/). Aspire is a set of extensions to .NET to make it easy to create and work with distributed applications. One of the benefits of using Aspire is that telemetry is built in, using the OpenTelemetry libraries for .NET.
 
 The default project templates for Aspire contain a `ServiceDefaults` project. Each service in the Aspire solution has a reference to the Service Defaults project. The services use it to set up and configure OTel.
 
-The Service Defaults project template includes the OTel SDK, ASP.NET, HttpClient, and Runtime Instrumentation packages. These instrumentation components are configured in the [Extensions.cs](https://github.com/dotnet/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-servicedefaults/Extensions.cs) file. To support telemetry visualization in Aspire Dashboard, the Service Defaults project also includes the OTLP exporter by default.
+The Service Defaults project template includes the OTel SDK, ASP.NET, HttpClient, and Runtime Instrumentation packages. These instrumentation components are configured in the [Extensions.cs](https://github.com/microsoft/aspire/blob/main/src/Aspire.ProjectTemplates/templates/aspire-servicedefaults/Extensions.cs) file. To support telemetry visualization in Aspire Dashboard, the Service Defaults project also includes the OTLP exporter by default.
 
 Aspire Dashboard is designed to bring telemetry observation to the local debug cycle, which enables developers to ensure that the applications are producing telemetry. The telemetry visualization also helps to diagnose those applications locally. Being able to observe the calls between services is as useful at debug time as in production. The Aspire dashboard is launched automatically when you <kbd>F5</kbd> the `AppHost` Project from Visual Studio or `dotnet run` the `AppHost` project from command line.
@@ -104,9 +104,9 @@ dotnet-counters monitor --counters System.Net.Http,System.Net.NameResolution -n
 
 For more information on Aspire, see:
 
-- [Aspire Overview](/dotnet/aspire/get-started/aspire-overview)
-- [Telemetry in Aspire](/dotnet/aspire/fundamentals/telemetry)
-- [Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/explore)
+- [Aspire Overview](https://aspire.dev/get-started/what-is-aspire/)
+- [Telemetry in Aspire](https://aspire.dev/fundamentals/telemetry/)
+- [Aspire Dashboard](https://aspire.dev/dashboard/explore/)
 
 ### Reuse Service Defaults project without Aspire orchestration
 

@@ -46,9 +46,9 @@ However, as an application developer, you would likely prefer to rely on the ric
 
 For more information on Aspire, see:
 
-- [Aspire Overview](/dotnet/aspire/get-started/aspire-overview)
-- [Telemetry in Aspire](/dotnet/aspire/fundamentals/telemetry)
-- [Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/explore)
+- [Aspire Overview](https://aspire.dev/get-started/what-is-aspire/)
+- [Telemetry in Aspire](https://aspire.dev/fundamentals/telemetry/)
+- [Aspire Dashboard](https://aspire.dev/dashboard/explore/)
 
 ### Reuse Service Defaults project without Aspire Orchestration
 
@@ -86,7 +86,7 @@ The following diagram illustrates the behavior of the spans and their relationsh
 
 ### Walkthrough: Using the experimental connection tracing in .NET 9
 
-This walkthrough uses a [.NET 9 Aspire Starter App](/dotnet/aspire/get-started/build-your-first-aspire-app) to demonstrate connection tracing, but it should be easy to set it up with [other monitoring tools](#collect-systemnet-traces) as well. The key step is to enable the ActivitySources.
+This walkthrough uses an [Aspire Starter App](https://aspire.dev/get-started/first-app/) to demonstrate connection tracing, but it should be easy to set it up with [other monitoring tools](#collect-systemnet-traces) as well. The key step is to enable the ActivitySources.
 
 1. Create an **Aspire 9 Starter App** by using `dotnet new`:
 
@@ -102,7 +102,7 @@ This walkthrough uses a [.NET 9 Aspire Starter App](/dotnet/aspire/get-started/b
 
     :::code language="csharp" source="snippets/tracing/ConnectionTracingDemo.ServiceDefaults/Extensions.cs" id="snippet_ConnectionTracing":::
 
-1. Start the solution. This should open the [Aspire Dashboard](/dotnet/aspire/fundamentals/dashboard/overview).
+1. Start the solution. This should open the [Aspire Dashboard](https://aspire.dev/dashboard/overview/).
 
 1. Navigate to the Weather page of the `webfrontend` app to generate an `HttpClient` request towards `apiservice`.
 

@@ -31,7 +31,6 @@ If your Orleans application uses [Aspire](../host/aspire-integration.md), you ca
 
 - [Aspire CLI](https://aspire.dev/get-started/install-cli/) installed
 - [Azure CLI](/cli/azure/install-azure-cli) installed
-- [Aspire workload](/dotnet/aspire/fundamentals/setup-tooling)
 - An Azure subscription with permissions to create resources
 - Docker Desktop or Podman running (for building container images)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -137,4 +137,4 @@ AI systems often stop being "just one app" once retrieval, tools, gateways, and

		Aspire isn't specifically the AI runtime; it's the multi-service application layer around it. It doesn't replace MEAI, MAF, or Azure AI Foundry.

		For more information, see the [Aspire documentation](/dotnet/aspire/).
		For more information, see the [Aspire documentation](https://aspire.dev/).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -150,4 +150,4 @@ If service discovery was added to the host using the `AddServiceDiscoveryCore` e

		## See also

		- [Service discovery in Aspire](/dotnet/aspire/service-discovery/overview)
		- [Service discovery in Aspire](https://aspire.dev/fundamentals/service-discovery/)