Merge pull request #14044 from MicrosoftDocs/main

Merged by Learn.Build PR Management system

Author: learn-build-service-prod[bot]

docs/azure/media/vs-azure-active-directory/owned-applications.png

@@ -1,114 +1,120 @@
 ---
-title: Use the Microsoft Identity platform connected service to use Microsoft Entra ID for authentication
-description: Connect Microsoft Entra ID (formerly Azure Active Directory) to your application by using Connected Services in Visual Studio on Windows.
+title: Entra ID Authentication With Connected Services
+description: Connect Microsoft Entra ID (formerly Azure Active Directory) to your application with Connected Services in Visual Studio on Windows.
 author: ghogen
 manager: mijacobs
 ms.subservice: azure-development
 ms.custom: devx-track-csharp
 ms.topic: how-to
-ms.date: 12/19/2023
+ms.date: 06/27/2025
 ms.author: ghogen
+#customer intent: As a developer, I want to use Connected Services in Visual Studio on Windows, so I can connect Microsoft Entra ID with my application for authentication.
 ---
 
-# Add Microsoft Entra ID authentication by using Connected Services in Visual Studio
+# Add Microsoft Entra ID authentication with Connected Services in Visual Studio
 
-You can add support for Microsoft Entra ID to an ASP.NET web app by using the Microsoft Identity platform connected service.
+You can add support for Microsoft Entra ID to an ASP.NET web application with the Microsoft identity platform connected service. Microsoft Entra ID enables support for user authentication to ASP.NET Model-View-Controller (MVC) web apps or Active Directory Authentication in web API services.
 
-By using Microsoft Entra ID, you can support user authentication for ASP.NET Model-View-Controller (MVC) web applications, or Active Directory Authentication in web API services. With Microsoft Entra authentication, your users can use their accounts from Microsoft Entra ID to connect to your web applications. The advantages of Microsoft Entra authentication with web API include enhanced data security when exposing an API from a web application. With Microsoft Entra ID, you do not have to manage a separate authentication system with its own account and user management.
+Microsoft Entra ID authentication offers many advantages:
 
-This article and its companion articles provide details of using the Visual Studio Connected Service feature for Active Directory.
+- Users can authenticate with their accounts from Microsoft Entra ID to connect to your web apps.
+- You gain enhanced data security when you expose an API from a web app. 
+- You don't have to manage a separate authentication system with its own account and user management.
+
+This article and its [companion articles](#related-content) describe how to use the Visual Studio Connected Service feature for Active Directory.
 
 ## Prerequisites
 
+To complete the procedures in this article, the following prerequisites must be satisfied:
+
 - [!INCLUDE [prerequisites-azure-subscription](includes/prerequisites-azure-subscription.md)]
-- **Visual Studio 2015** or later. [Download Visual Studio now](https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs).
 
-<a name='connect-to-azure-active-directory-using-the-connected-services-dialog'></a>
+- **Visual Studio**. [Download Visual Studio now](https://aka.ms/vsdownload?utm_source=mscom&utm_campaign=msdocs).
 
-### Connect to Microsoft Identity platform
+## Connect to Microsoft identity platform
 
-:::moniker range=">=vs-2022"
+Add Microsoft identity platform as a connected service to your application by following these steps:
 
 1. In Visual Studio, create or open an ASP.NET MVC project, or an ASP.NET Web API project.
 
-1. Select the **Project**, **Connected Services**, **Add** menu command, or right-click the **Connected Services** node found under the project in Solution Explorer, and choose **Add**, **Microsoft Identity platform**.
-
-   If you are missing the .NET MSIdentity tool, the screen prompts you to install it.
-
-   ![Screenshot of required components window.](./media/vs-azure-active-directory/required-components.png)
-
-1. The **Configure Microsoft identity platform** screen appears. If you haven't signed in to Azure, you're asked to sign in. Once you're signed in, you see a list of your applications.
+1. Use one of the following methods to add the Microsoft identity platform connected service:
 
-   ![Screenshot showing list of owned applications.](./media/vs-azure-active-directory/owned-applications.png)
+   :::moniker range=">=vs-2022"
 
-1. If you don't have an application, choose **Create new**, and enter the application name. For Microsoft Entra ID, choose Microsoft as the tenant.
+   - Select **Project** > **Connected Services** > **Add** > **Microsoft identity platform**.
+   
+   - In **Solution Explorer**, right-click the **Connected Services** node for the project, and select **Add** > **Microsoft identity platform**.
 
-   ![Screenshot showing how to register a new application.](./media/vs-azure-active-directory/register-an-application.png)
+   :::moniker-end
+   :::moniker range="<=vs-2019"
 
-   The application you entered now shows in the list. Select it and choose **Next**.
+   - Select **Project** > **Manage Connected Services** > **Add a service dependency** > **Microsoft identity platform**.
+   
+   - In **Solution Explorer**, right-click the **Connected Services** node for the project, and select **Manage Connected Services > Add a service dependency** > **Microsoft identity platform**.
 
-1. On the next screen, you can choose to enable Microsoft.Graph or allow another API project to have access. You can configure this later if you don't have the information yet.
+      :::image type="content" source="./media/vs-azure-active-directory/vs-2019/add-dependency-microsoft-identity-platform.png" border="false" alt-text="Screenshot showing the Microsoft identity platform option in Visual Studio.":::
 
-   ![Screenshot of additional options for adding APIs.](./media/vs-azure-active-directory/additional-settings.png)
+   :::moniker-end
 
-1. Choose **Next**. The **Summary of changes** screen appears showing what is being changed in the project.
+   If your installation is missing the .NET MSIdentity tool, the **Required components** window opens with a message to complete the install:
 
-   ![Screenshot showing Summary of changes screen.](./media/vs-azure-active-directory/summary-of-changes.png)
+   :::image type="content" source="./media/vs-azure-active-directory/required-components.png" border="false" alt-text="Screenshot of the Required Components window with a message to install the .NET MSIdentity tool.":::
 
-1. The **Dependency configuration process** screen shows the specific changes that are being made to your project.
+   As needed, follow the steps to install the .NET MSIdentity tool, and then continue with this procedure.
 
-Now the new service dependency shows on the Connected Services screen.
+1. The **Microsoft identity platform** configuration screen opens.
 
-![Screenshot showing the Microsoft Identity platform service dependency has been created.](./media/vs-azure-active-directory/identity-platform-service-dependency.png)
-
-If you want to modify it, such as to add support for an API such as Microsoft.Graph, click on the three dots, and then choose **Edit dependency**. You can repeat the steps and choose the APIs that you want to grant access to.
-
-You can also see the Active Directory domain on the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
-
-:::moniker-end
-:::moniker range="<=vs-2019"
-1. In Visual Studio, create or open an ASP.NET MVC project, or an ASP.NET Web API project.
+   As needed, sign in to Azure. After you sign in, you see a list of your applications for the selected **Tenant**:
 
-1. Select the **Project**, **Manage Connected Services** menu command, or right-click the **Connected Services** node found under the project in Solution Explorer, and choose **Manage Connected Services**, and then select the link **Add a service dependency** and choose **Microsoft Identity platform**.
+   :::image type="content" source="./media/vs-azure-active-directory/owned-applications.png" border="false" alt-text="Screenshot showing the list of owned applications.":::
 
-   ![Screenshot showing the Microsoft Identity platform option.](./media/vs-azure-active-directory/vs-2019/add-dependency-microsoft-identity-platform.png)
+   If you don't have an application, select **Create new**:
+   
+   1. For Microsoft Entra ID, select **Microsoft** as the tenant.
+   
+   1. Enter the display name for the new application.
+   
+   1. Select **Register**:
 
-   If you are missing the .NET MSIdentity tool, the screen prompts you to install it.
+      :::image type="content" source="./media/vs-azure-active-directory/register-an-application.png" border="false" alt-text="Screenshot showing how to register a new application.":::
 
-   ![Screenshot of required components window.](./media/vs-azure-active-directory/required-components.png)
+   After the new application registers, it appears in the application list.
+   
+1. In the application list, select the application to use, and select **Next**.
 
-   If you had to install the tool, you might need to restart the process again from step 1.
+   <a name="update-service-settings"> </a>
+   
+1. On the **Additional settings** screen, choose your preferred settings. You can enable Microsoft Graph or allow another API project to have access. You can also configure these settings later.
 
-1. The **Configure Microsoft identity platform** screen appears. If you haven't signed in to Azure, you're asked to sign in. Once you're signed in, you see a list of your applications.
+   :::image type="content" source="./media/vs-azure-active-directory/additional-settings.png" border="false" alt-text="Screenshot of additional options for the application, including enable Microsoft Graph and allow API access.":::
 
-   ![Screenshot showing list of owned applications.](./media/vs-azure-active-directory/owned-applications.png)
+1. Select **Next**. The **Summary of changes** screen appears for the project, including updates to dependencies to support Microsoft identity platform:
 
-1. If you don't have an application, choose **Create new**, and enter the application name. For Microsoft Entra ID, choose Microsoft as the tenant.
+   :::image type="content" source="./media/vs-azure-active-directory/summary-of-changes.png" border="false" alt-text="Screenshot showing Summary of changes screen for the project.":::
 
-   ![Screenshot showing how to register a new application.](./media/vs-azure-active-directory/register-an-application.png)
+1. Select **Finish**. The **Dependency configuration progress** screen shows the process status. When the process finishes successfully, the status shows the statement "Complete. Microsoft identity platform \<application> is configured."
 
-   The application you entered now shows in the list. Select it and choose **Next**.
+1. Select **Close** to close the window.
 
-1. On the next screen, you can choose to enable Microsoft.Graph or allow another API project to have access. You can configure this later if you don't have the information yet.
+The new connection is listed under **Service Dependencies** in the **Connected Services** screen for the project:
 
-   ![Screenshot of additional options for adding APIs.](./media/vs-azure-active-directory/additional-settings.png)
+:::image type="content" source="./media/vs-azure-active-directory/identity-platform-service-dependency.png" border="false" alt-text="Screenshot showing the Microsoft identity platform service dependency listed as a connected service for the project.":::
 
-1. Choose **Next**. The **Summary of changes** screen appears showing what is being changed in the project.
+You can also see the Microsoft Entra ID domain for the application connection in the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
 
-   ![Screenshot showing Summary of changes screen.](./media/vs-azure-active-directory/summary-of-changes.png)
+## Modify connected service settings
 
-1. The **Dependency configuration process** screen shows the specific changes that are being made to your project.
+After you add Microsoft identity platform as a connected service, you can modify the settings as needed:
 
-Now the new service dependency shows on the Connected Services screen.
+1. In the **Connected Services** > **Service Dependencies** screen, locate the **Microsoft identity platform** service.
 
-![Screenshot showing the Microsoft Identity platform service dependency has been created.](./media/vs-azure-active-directory/identity-platform-service-dependency.png)
+1. Select **More options** (**...**) for the service, and then select **Edit dependency**.
 
-If you want to modify it, such as to add support for an API such as Microsoft.Graph, click on the three dots, and then choose **Edit dependency**. You can repeat the steps and choose the APIs that you want to grant access to.
+1. Select the tenant that contains the application, select the application, and then select **Next**.
 
-You can also see the Active Directory domain on the [Azure portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
-:::moniker-end
+Follow the process described earlier to [modify and apply your preferred settings](#update-service-settings). Repeat the process as needed to grant project access for necessary APIs.
 
 ## Related content
 
-- [Authentication scenarios for Microsoft Entra ID](/azure/active-directory/develop/authentication-vs-authorization)
-- [Add sign-in with Microsoft to an ASP.NET web app](/azure/active-directory/develop/quickstart-v2-aspnet-webapp)
+- [Authentication scenarios for Microsoft Entra ID](/entra/identity-platform/authentication-vs-authorization)
+- [Add sign-in with Microsoft to an ASP.NET web app](/entra/identity-platform/quickstart-web-app-sign-in)

docs/azure/media/vs-azure-active-directory/register-an-application.png

@@ -207,7 +207,7 @@ dialog looks like this:
 
 In this dialog, you can choose what modules you *do not* want Visual Studio to load symbols for.
 In this scenario, Visual Studio attempts to load symbols for every module in your debugged
-proces (including modules by third parties), unless you add a matching filter to exclude them.
+process (including modules by third parties), unless you add a matching filter to exclude them.
 The only other way that this behavior will be modified is by your [Just My Code](just-my-code.md)
 settings.
 

docs/azure/media/vs-azure-active-directory/required-components.png

@@ -1,15 +1,14 @@
 ---
 title: Publish an ASP.NET web app
 description: Use the Publish tool in Visual Studio to deploy ASP.NET and ASP.NET Core apps to local web servers like IIS or remote cloud environments like Azure App Service.
-ms.date: 07/15/2024
+ms.date: 6/27/2025
 ms.topic: quickstart
 helpviewer_keywords:
   - "deployment, web app"
 author: ghogen
 ms.author: ghogen
 manager: mijacobs
 ms.subservice: deployment
-monikerRange: '>= vs-2019'
 ---
 # Quickstart: Publish an ASP.NET web app
 
@@ -42,15 +41,13 @@ If you're publishing this web app for the first time, next you see the Publish w
 > [!NOTE]
 > Visual Studio filters the list of destinations depending on the type of web app.
 
-## [Azure](#tab/azure)
-## Publish your web app to Azure
+## Azure
 
 For detailed steps on publishing your web app, see [Quickstart: Deploy an ASP.NET web app](/azure/app-service/quickstart-dotnetcore?tabs=netcore31&pivots=development-environment-vs#publish-your-web-app).
 
-## [Docker](#tab/docker)
-## Publish your web app to Docker Container Registry
+## Container registry
 
-You can publish your web app as a Docker container to any compatible Docker Container Registry.
+This sections describes publishing to a container registry. You can publish your web app as a Docker container to any compatible Docker Container Registry.
 
 ![Screenshot showing the Publish wizard, with Publish to Docker Container Registry highlighted.](./media/publish-docker-container-registry-highlighted.png)
 
@@ -76,7 +73,7 @@ Next, for other Docker container registries, provide the URI and publish credent
 
 ![Screenshot showing the option to publish to another Docker Container Registry.](./media/publish-custom-docker-registry-details.png)
 
-### Finish the Publish wizard
+### Publish container image
 
 Next, you see the summary page for the new [publish profile](./publish-overview.md) that you just created using the Publish wizard. Click **Publish** and Visual Studio deploys your web app to the specified Docker Container Registry.
 
@@ -85,8 +82,7 @@ Next, you see the summary page for the new [publish profile](./publish-overview.
 > [!NOTE]
 > The above screenshot is showing a publish profile targeting Azure Docker Registry, but the same Publish button is available for all three Docker Container Registry options.
 
-## [Folder](#tab/folder)
-## Publish your web app to a folder
+## Filesystem folder
 
 You can publish your web app to both local and network folders.
 
@@ -102,8 +98,7 @@ Next, you see the summary page for the new [publish profile](./publish-overview.
 
 You can come back to this summary page after you close it. Next time you right-click and choose **Publish**, Visual Studio opens this summary page. (To get back to the Publish wizard just click **New** in the summary page.)
 
-## [FTP/FTPS](#tab/ftp-ftps)
-## Publish your web app to an FTP/FTPS server
+## FTP/FTPS server
 
 You can publish your web app using FTP or FTPS.
 
@@ -119,8 +114,7 @@ Next, you see the summary page for the new [publish profile](./publish-overview.
 
 You can come back to this summary page after you close it. The next time you right-click and publish, Visual Studio opens this summary page. (To get back to the Publish wizard just click **New** in the summary page.)
 
-## [Web Server](#tab/web-server)
-## Publish your web app to Web Server (IIS)
+## Web Server (IIS)
 
 You can publish your web app to IIS if IIS is configured. By default, IIS Express is installed, but you should install the IIS Management tools if you're deploying to IIS from Visual Studio. Note that you don't need to run Visual Studio as Administrator to deploy to IIS Express, only to full IIS.
 
@@ -172,13 +166,10 @@ Next, you see the summary page for the new [publish profile](./publish-overview.
 
 ![Screenshot showing the Publish wizard, publish to IIS summary page.](./media/publish-iis-web-deploy-package-summary-page.png)
 
-## [Import profile](#tab/import-profile)
-## Import Profile
+## Import publish profile
 
 You can import publish settings [from IIS](./tutorial-import-publish-settings-iis.md) and [Azure App Service](./tutorial-import-publish-settings-azure.md#create-the-publish-settings-file-in-azure-app-service)
 
----
-
 ## Next steps
 
 Manage settings for your web application deployment. By managing settings, you can control the .NET deployment options, as well as behaviors such as how to handle existing files that are not part of the deployment process at the deployment destination. See [Manage web deployment settings](web-deployment-settings.md).

docs/azure/media/vs-azure-active-directory/summary-of-changes.png

@@ -38,7 +38,7 @@ MSB1042: Node reuse value is not valid. This version of MSBuild does not support
 <!--
 {StrBegin="MSBUILD : error MSB1042: "}
      UE: This message does not need in-line parameters because the exception takes care of displaying the invalid arg.
-     This error is shown when a user specifies a node reuse value that is not equivilant to Boolean.TrueString or Boolean.FalseString.
+     This error is shown when a user specifies a node reuse value that is not equivalent to Boolean.TrueString or Boolean.FalseString.
      LOCALIZATION: The prefix "MSBUILD : error MSBxxxx:" should not be localized.
 
 {StrBegin="MSBUILD : error MSB1042: "}

docs/azure/vs-active-directory-add-connected-service.md

@@ -9,7 +9,7 @@ ms.topic: how-to
 ms.date: 02/28/2025
 helpviewer_keywords:
 - DefaultTargets attribute [MSBuild]
-- MSBuild, specifying the defalut target
+- MSBuild, specifying the default target
 - MSBuild, DefaultTargets attribute
 
 # Customer intent: As a developer, I want to understand how to specify which MSBuild targets to build first so I can control how my project is built.

docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md

@@ -1,6 +1,6 @@
 ---
 title: MSBuild Server
-description: Learn how MSBuild Server supports frequent build scenarios by cacheing build context over multiple builds.
+description: Learn how MSBuild Server supports frequent build scenarios by caching build context over multiple builds.
 ms.date: 10/11/2022
 ms.topic: overview
 helpviewer_keywords: