Merge pull request #13554 from ghogen/aspire-blurb

Add .NET Aspire section

Author: prmerger-automator[bot]

docs/azure/overview.md

@@ -56,6 +56,14 @@ What are you deploying?
 
 If you need help configuring CI/CD for a GitHub repo for the first time, Visual Studio can help you get started with GitHub Action starter workflows. Learn more at [Deploy your application to Azure using GitHub Actions workflows created by Visual Studio](azure-deployment-using-github-actions.md). Read more about setting up CI/CD for deployment to Azure at [Continuous deployment to Azure App Service](/azure/app-service/deploy-continuous-deployment?tabs=github).
 
+## .NET Aspire
+
+[.NET Aspire](/dotnet/aspire) provides infrastructure for orchestrating services and components of observable, cloud-based apps. *Observable apps* are those that are set up to be thoroughly monitored in real-time while executing. .NET Aspire is particularly relevant during development time as a means of organizing and coordinating multiple services, databases, and other dependencies.
+
+Visual Studio 17.9 and later, with the **ASP.NET and web development** and **Azure development** workloads installed, includes the [.NET Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk) and provides [project templates](/dotnet/aspire/fundamentals/aspire-sdk-templates?pivots=visual-studio) for .NET Aspire.
+
+ASP.NET Core projects include an option to enlist in Aspire orchestration at project creation time, and a context menu item, **Add** > **NET Aspire Orchestrator Support** in Solution Explorer that you can use to enlist a project in Aspire orchestration. These actions add Aspire orchestration projects (AppHost and ServiceDefaults) to the solution (unless already present). In Visual Studio 17.13 and later, this functionality is also supported for Azure Functions projects. For more detailed information, see [.NET Aspire tooling](/dotnet/aspire/fundamentals/setup-tooling?tabs=windows&pivots=visual-studio).
+
 ## Debug in Azure using Visual Studio
 
 You can use Visual Studio debug your application while it's running in Azure, so that you can identify and reproduce problems in an environment that is as close as possible to a production environment. For web apps hosted in Azure App Service, see [Remote debug ASP.NET Core on Azure App Service](../debugger/remote-debugging-azure-app-service.md). For Azure Functions, see [Develop Azure Functions with Visual Studio - Remote debugging](/azure/azure-functions/functions-develop-vs#remote-debugging?tabs=isolated-process).