Migration 3 of several

.openpublishing.redirection.json

@@ -843,6 +843,22 @@
     {
       "source_path_from_root": "/docs/diagnostics/aspireazure002.md",
       "redirect_url": "https://aspire.dev/diagnostics/aspireazure002/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/health-checks.md",
+      "redirect_url": "https://aspire.dev/fundamentals/health-checks/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/service-defaults.md",
+      "redirect_url": "https://aspire.dev/fundamentals/service-defaults/"
+    },
+    {
+      "source_path_from_root": "/docs/fundamentals/launch-profiles.md",
+      "redirect_url": "https://aspire.dev/fundamentals/launch-profiles/"
+    },
+    {
+      "source_path_from_root": "/docs/service-discovery/overview.md",
+      "redirect_url": "https://aspire.dev/fundamentals/service-discovery/"
     }
   ]
 }

docs/app-host/configuration.md

@@ -44,7 +44,7 @@ The preceding launch settings file:
   - The `applicationUrl` property configures the dashboard launch address (`ASPNETCORE_URLS`).
   - Environment variables such as `ASPIRE_DASHBOARD_OTLP_ENDPOINT_URL` and `ASPIRE_RESOURCE_SERVICE_ENDPOINT_URL` are set on the AppHost.
 
-For more information, see [Aspire and launch profiles](../fundamentals/launch-profiles.md).
+For more information, see [Aspire and launch profiles](https://aspire.dev/fundamentals/launch-profiles/).
 
 > [!NOTE]
 > Configuration described on this page is for Aspire AppHost project. To configure the standalone dashboard, see [dashboard configuration](https://aspire.dev/dashboard/configuration/).

docs/deployment/aspire-deploy/application-insights.md

@@ -153,7 +153,7 @@ builder.Build().Run();
 
 To make exporting to Azure Monitor simpler, this example uses the Azure Monitor Exporter Repo. This is a wrapper package around the Azure Monitor OpenTelemetry Exporter package that makes it easier to export to Azure Monitor with a set of common defaults.
 
-Add the following package to the `ServiceDefaults` project, so that it will be included in each of the Aspire services. For more information, see [Aspire service defaults](../../fundamentals/service-defaults.md).
+Add the following package to the `ServiceDefaults` project, so that it will be included in each of the Aspire services. For more information, see [Aspire service defaults](https://aspire.dev/fundamentals/service-defaults/).
 
 ``` xml
 <PackageReference Include="Azure.Monitor.OpenTelemetry.AspNetCore" 

docs/deployment/manifest-format.md

@@ -167,7 +167,7 @@ builder.AddProject<Projects.AspireApp_Web>("webfrontend")
 builder.Build().Run();
 ```
 
-References between project resource types result in [service discovery](../service-discovery/overview.md) variables being injected into the referencing project. References to well known reference types such as Redis result in connection strings being injected.
+References between project resource types result in [service discovery](https://aspire.dev/fundamentals/service-discovery/) variables being injected into the referencing project. References to well known reference types such as Redis result in connection strings being injected.
 
 :::image type="content" source="media/manifest-placeholder-strings.png" lightbox="media/manifest-placeholder-strings.png" alt-text="A diagram showing which resources contribute to which corresponding placeholder strings.":::
 
@@ -920,4 +920,4 @@ When resources as configured as Azure resources, the `azure.bicep.v0` resource t
 - [Aspire overview](../get-started/aspire-overview.md)
 - [Aspire orchestration overview](../fundamentals/app-host-overview.md)
 - [Aspire integrations overview](../fundamentals/integrations-overview.md)
-- [Service discovery in Aspire](../service-discovery/overview.md)
+- [Service discovery in Aspire](https://aspire.dev/fundamentals/service-discovery/)

docs/extensibility/custom-client-integration.md

@@ -87,7 +87,7 @@ The registration of health checks, and telemetry are described in a bit more det
 
 ### Add health checks
 
-[Health checks](../fundamentals/health-checks.md) are a way to monitor the health of an integration. With MailKit, you can check if the connection to the SMTP server is healthy. Add the following code to the `MailKit.Client` project in a file named _MailKitHealthCheck.cs_:
+[Health checks](https://aspire.dev/fundamentals/health-checks/) are a way to monitor the health of an integration. With MailKit, you can check if the connection to the SMTP server is healthy. Add the following code to the `MailKit.Client` project in a file named _MailKitHealthCheck.cs_:
 
 :::code source="snippets/MailDevResourceAndComponent/MailKit.Client/MailKitHealthCheck.cs":::
 

docs/extensibility/custom-hosting-integration.md

@@ -60,7 +60,7 @@ dir
 Once the project is created, you should see a listing containing the following:
 
 - `MailDevResource.AppHost`: The [AppHost](../fundamentals/app-host-overview.md) used to test out the custom resource.
-- `MailDevResource.ServiceDefaults`: The [service defaults](../fundamentals/service-defaults.md) project for use in service-related projects.
+- `MailDevResource.ServiceDefaults`: The [service defaults](https://aspire.dev/fundamentals/service-defaults/) project for use in service-related projects.
 - `MailDevResource.sln`: The solution file referencing both projects.
 
 Verify that the project can build and run successfully by executing the following command:

docs/extensibility/dev-tunnels-integration.md

@@ -98,7 +98,7 @@ The preceding code:
 
 ### Service discovery integration
 
-When another resource references a dev tunnel, environment variables are injected using the [Aspire service discovery](../service-discovery/overview.md) configuration format. Use the `WithReference` overloads that accept the `IResourceBuilder<DevTunnelResource>` parameter to reference a dev tunnel. This injects environment variables like:
+When another resource references a dev tunnel, environment variables are injected using the [Aspire service discovery](https://aspire.dev/fundamentals/service-discovery/) configuration format. Use the `WithReference` overloads that accept the `IResourceBuilder<DevTunnelResource>` parameter to reference a dev tunnel. This injects environment variables like:
 
 ```env
 WEB_HTTPS=https://myweb-1234.westeurope.devtunnels.ms/
@@ -180,5 +180,5 @@ Verify that:
 
 - [Dev tunnels service documentation](/azure/developer/dev-tunnels/overview)
 - [Dev tunnels FAQ](/azure/developer/dev-tunnels/faq)
-- [Aspire service discovery](../service-discovery/overview.md)
+- [Aspire service discovery](https://aspire.dev/fundamentals/service-discovery/)
 - [Aspire networking overview](../fundamentals/networking-overview.md)

docs/extensibility/secure-communication-between-integrations.md

@@ -24,7 +24,7 @@ The resulting solution from these previous articles contains the following proje
 - _MailDev.Hosting_: Contains the custom resource type for the MailDev container.
 - _MailDevResource.AppHost_: The [AppHost](../fundamentals/app-host-overview.md) that uses the custom resource and defines it as a dependency for a Newsletter service.
 - _MailDevResource.NewsletterService_: An ASP.NET Core Web API project that sends emails using the MailDev container.
-- _MailDevResource.ServiceDefaults_: Contains the [default service configurations](../fundamentals/service-defaults.md) intended for sharing.
+- _MailDevResource.ServiceDefaults_: Contains the [default service configurations](https://aspire.dev/fundamentals/service-defaults/) intended for sharing.
 - _MailKit.Client_: Contains the custom client integration that exposes the MailKit `SmtpClient` through a factory.
 
 ## Update the MailDev resource

docs/fundamentals/app-host-overview.md

@@ -194,7 +194,7 @@ builder.AddProject<Projects.AspireApp_Web>("webfrontend")
        .WithReference(cache);
 ```
 
-The "webfrontend" project resource uses <xref:Aspire.Hosting.ResourceBuilderExtensions.WithReference%2A> to add a dependency on the "cache" container resource. These dependencies can represent connection strings or [service discovery](../service-discovery/overview.md) information. In the preceding example, an environment variable is _injected_ into the "webfrontend" resource with the name `ConnectionStrings__cache`. This environment variable contains a connection string that the `webfrontend` uses to connect to Redis via the [Aspire Redis integration](https://aspire.dev/integrations/caching/redis/), for example, `ConnectionStrings__cache="localhost:62354"`.
+The "webfrontend" project resource uses <xref:Aspire.Hosting.ResourceBuilderExtensions.WithReference%2A> to add a dependency on the "cache" container resource. These dependencies can represent connection strings or [service discovery](https://aspire.dev/fundamentals/service-discovery/) information. In the preceding example, an environment variable is _injected_ into the "webfrontend" resource with the name `ConnectionStrings__cache`. This environment variable contains a connection string that the `webfrontend` uses to connect to Redis via the [Aspire Redis integration](https://aspire.dev/integrations/caching/redis/), for example, `ConnectionStrings__cache="localhost:62354"`.
 
 ### Connection string and endpoint references
 
@@ -226,7 +226,7 @@ Aspire injects two types of environment variables for service references:
 - **Simplified format** (e.g., `APISERVICE_HTTP`): Uses the pattern `{RESOURCENAME}_{ENDPOINTNAME}` in uppercase. This format is simpler and more suitable for non-.NET languages and polyglot scenarios.
 - **.NET service discovery format** (e.g., `services__apiservice__http__0`): Uses the pattern `services__{servicename}__{endpointname}__{index}` in lowercase. This format is used by .NET's configuration-based service discovery.
 
-For more information, see [Aspire service discovery](../service-discovery/overview.md).
+For more information, see [Aspire service discovery](https://aspire.dev/fundamentals/service-discovery/).
 
 To get specific endpoints from a <xref:Aspire.Hosting.ApplicationModel.ContainerResource> or an <xref:Aspire.Hosting.ApplicationModel.ExecutableResource>, use one of the following endpoint APIs:
 
@@ -252,7 +252,7 @@ var apiservice = builder.AddProject<Projects.AspireApp_ApiService>("apiservice")
 |---------------------------|-------------------------------------------------------|
 | `WithReference(endpoint)` | `MYAPP_ENDPOINT="https://localhost:9043"` <br /> `services__myapp__endpoint__0="https://localhost:9043"` |
 
-The `port` parameter is the port that the container is listening on. For more information on container ports, see [Container ports](networking-overview.md#container-ports). For more information on service discovery, see [Aspire service discovery](../service-discovery/overview.md).
+The `port` parameter is the port that the container is listening on. For more information on container ports, see [Container ports](networking-overview.md#container-ports). For more information on service discovery, see [Aspire service discovery](https://aspire.dev/fundamentals/service-discovery/).
 
 ### Service endpoint environment variable format
 
@@ -377,7 +377,7 @@ This logic can easily be inverted to connect to an existing Redis resource when
 - [Aspire integrations overview](integrations-overview.md)
 - [Aspire SDK](dotnet-aspire-sdk.md)
 - [Eventing in Aspire](../app-host/eventing.md)
-- [Service discovery in Aspire](../service-discovery/overview.md)
-- [Aspire service defaults](service-defaults.md)
+- [Service discovery in Aspire](https://aspire.dev/fundamentals/service-discovery/)
+- [Aspire service defaults](https://aspire.dev/fundamentals/service-defaults/)
 - [Expressing external parameters](external-parameters.md)
 - [Aspire inner-loop networking overview](networking-overview.md)

docs/fundamentals/aspire-sdk-templates.md

@@ -27,7 +27,7 @@ The following Aspire solution templates are available, assume the solution is na
 - **Aspire Empty App**: A minimal Aspire project that includes the following:
 
   - [**AspireSample.AppHost**](#app-host): An orchestrator project designed to connect and configure the different projects and services of your app.
-  - [**AspireSample.ServiceDefaults**](#service-defaults): A Aspire shared project to manage configurations that are reused across the projects in your solution related to [resilience](/dotnet/core/resilience/http-resilience), [service discovery](../service-discovery/overview.md), and [telemetry](telemetry.md).
+  - [**AspireSample.ServiceDefaults**](#service-defaults): A Aspire shared project to manage configurations that are reused across the projects in your solution related to [resilience](/dotnet/core/resilience/http-resilience), [service discovery](https://aspire.dev/fundamentals/service-discovery/), and [telemetry](telemetry.md).
 
 <a name="starter-app"></a>
 
@@ -59,10 +59,10 @@ The following Aspire project templates are available:
 
 <a name="service-defaults"></a>
 
-- **Aspire Service Defaults**: A standalone **.ServiceDefaults** project that can be used to manage configurations that are reused across the projects in your solution related to [resilience](/dotnet/core/resilience/http-resilience), [service discovery](../service-discovery/overview.md), and [telemetry](./telemetry.md).
+- **Aspire Service Defaults**: A standalone **.ServiceDefaults** project that can be used to manage configurations that are reused across the projects in your solution related to [resilience](/dotnet/core/resilience/http-resilience), [service discovery](https://aspire.dev/fundamentals/service-discovery/), and [telemetry](./telemetry.md).
 
   > [!IMPORTANT]
-  > The service defaults project template takes a `FrameworkReference` dependency on `Microsoft.AspNetCore.App`. This may not be ideal for some project types. For more information, see [Aspire service defaults](service-defaults.md).
+  > The service defaults project template takes a `FrameworkReference` dependency on `Microsoft.AspNetCore.App`. This may not be ideal for some project types. For more information, see [Aspire service defaults](https://aspire.dev/fundamentals/service-defaults/).
 
 ## Install the Aspire templates