Merge pull request #7581 from MicrosoftDocs/main637787523266038656

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: ghogen

docs/ide/media/vs-2022/add-personalization-account.png

@@ -1,10 +1,10 @@
 ---
 title: Multi-factor authentication with Visual Studio sign-ins
 titleSuffix: "" 
-ms.date: 05/27/2020
-ms.custom: SEO-VS-2020
+ms.date: 01/24/2020
+ms.custom: SEO-VS-2022
 ms.topic: how-to
-description: "Learn how to use Visual Studio with accounts that require multi-factor authentication."
+description: "Learn how to use Visual Studio with accounts that require multi-factor authentication (MFA)."
 author: anandmeg
 ms.author: meghaanand
 manager: jmartens
@@ -14,7 +14,11 @@ ms.workload:
 monikerRange: ">=vs-2019"
 ---
 
-# Use Visual Studio with accounts that require multi-factor authentication (MFA)
+# Work with accounts that require multi-factor authentication (MFA)
+
+In this article, you'll learn how to use Visual Studio with accounts that require multi-factor authentication (MFA).
+
+## Why enable MFA policies?
 
 When collaborating with external guest users, it's a good idea to protect your apps and data with **conditional access (CA)** policies such as **multi-factor authentication (MFA)**.  
 
@@ -23,7 +27,7 @@ Once enabled, guest users will need more than just a username and password to ac
 ## How is the Visual Studio experience affected by MFA policies?
 Versions of Visual Studio prior to 16.6 may have degraded authentication experiences when used with accounts that have enabled CA policies such as MFA, and are associated with two or more tenants.
 
-These issues can cause your instance of Visual Studio to prompt reauthentication multiple times per day. You may have to reenter your credentials for previously authenticated tenants, even during the course of the same Visual Studio session.
+These issues can cause your instance of Visual Studio to prompt reauthentication multiple times per day. You may have to re-enter your credentials for previously authenticated tenants, even during the course of the same Visual Studio session.
 
 ## Using Visual Studio with MFA policies
 In the 16.6 release, we added new capabilities to Visual Studio 2019 that streamline how users can access resources secured via CA policies such as MFA. To use this enhanced workflow, you'll need to opt into using your system's default web browser as the mechanism to add and reauthenticate Visual Studio accounts.  
@@ -38,52 +42,52 @@ In the 16.6 release, we added new capabilities to Visual Studio 2019 that stream
 
 To enable this workflow, go to Visual Studio's Options dialog **(Tools > Options…)**, select the **Accounts** tab and pick **System web browser** under the **Add and reauthenticate accounts using:** dropdown. 
 
-:::image type="content" source="media/select-system-web-browser.png" alt-text="Select system web browser from the menu.":::
+:::image type="content" source="media/vs-2022/select-system-web-browser.png" alt-text="Select system web browser from the menu.":::
 
 ### Sign into additional accounts with MFA policies 
 Once the system web browser workflow is enabled, you can sign in or add accounts to Visual Studio as you normally would, via the Account Settings dialog **(File > Account Settings…)**.   
 </br>
-:::image type="content" source="media/add-personalization-account.png" alt-text="Add a new personalization account to Visual Studio." border="false":::
+:::image type="content" source="media/vs-2022/add-personalization-account.png" alt-text="Add a new personalization account to Visual Studio." border="false":::
 
 This action will open your system's default web browser, ask you to sign into your account, and validate any required MFA policy.
 
-During the sign in process, you may receive an additional prompt asking you to stay signed in. This prompt will likely show up the second time an account is used to sign in. To minimize the need to re-enter your credentials, we recommend that you select **Yes**, as this ensures your credentials are preserved across browser sessions.
+During the sign-in process, you may receive an additional prompt asking you to stay signed in. This prompt will likely show up the second time an account is used to sign in. To minimize the need to re-enter your credentials, we recommend that you select **Yes**, as this ensures your credentials are preserved across browser sessions.
 
-:::image type="content" source="media/kmsi.png" alt-text="Stay signed in?":::
+:::image type="content" source="media/vs-2022/keep-me-signed-in.png" alt-text="Stay signed in?":::
 
-Based on your development activities and resource configuration, you may still be prompted to reenter your credentials during your session. This can occur when you add a new resource, or try accessing a resource without having previously met its CA/MFA authorization requirements.
+Based on your development activities and resource configuration, you may still be prompted to re-enter your credentials during your session. This can occur when you add a new resource, or try accessing a resource without having previously met its CA/MFA authorization requirements.
 
-## Reauthenticating an account  
-If there's a problem with your account, Visual Studio might ask you to reenter your account credentials.  
+## Reauthenticating an account
+If there's a problem with your account, Visual Studio might ask you to re-enter your account credentials.  
 
-:::image type="content" source="media/reauthenticate-account.png" alt-text="Reauthenticate your Visual Studio account.":::
+:::image type="content" source="media/vs-2022/reauthenticate-account.png" alt-text="Reauthenticate your Visual Studio account.":::
 
-Clicking on **Reenter your credentials** will open your system's default web browser and attempt to automatically refresh your credentials. If unsuccessful, you'll be asked to sign into your account and validate any required CA/MFA policy.
+Clicking on **Re-enter your credentials** will open your system's default web browser and attempt to automatically refresh your credentials. If unsuccessful, you'll be asked to sign into your account and validate any required CA/MFA policy.
 
 > [!NOTE] 
 > For the best experience, keep your browser open until all CA/MFA policies are validated for your resources. Closing the browser may result in losing the previously built MFA state, and may prompt additional authorization prompts.
 
 ## How to opt out of using a specific Azure Active Directory tenant in Visual Studio
 
-Visual Studio 2019 version 16.6 offers the flexibility to filter out tenants individually or globally, effectively hiding them from Visual Studio. Filtering eliminates the need to authenticate with that tenant, but it also means that you won't be able to access any associated resources.
+Visual Studio 2019 version 16.6 and above offers the flexibility to filter out tenants individually or globally, effectively hiding them from Visual Studio. Filtering eliminates the need to authenticate with that tenant, but it also means that you won't be able to access any associated resources.
 
 This functionality is useful when you have multiple tenants, but want to optimize your development environment by targeting a specific subset. It can also help in instances when you can't validate a particular CA/MFA policy, as you can filter out the offending tenant. 
 
 ### How to filter out all tenants
-To globally filter out all tenants, open the Account Settings dialog **(File > Account Settings…)** and deselect the **Authenticate Across all Azure Active Directories** checkbox.
+To globally filter out all tenants, open the Account Settings dialog **(File > Account Settings... > Account options)** and deselect the **Authenticate across all Azure Active Directories** checkbox.
 
 Deselecting that option ensures you’ll only authenticate with the account’s default tenant. It also means that you won't be able to access any resources associated with other tenants your account might be a guest on.
 
 ### How to filter out individual tenants
-To filter tenants that are associated with  your Visual Studio account, open the Account Settings dialog **(File > Account Settings…)** and click on **Apply filter**. 
+To filter tenants that are associated with your Visual Studio account, open the Account Settings dialog **(File > Account Settings…)** and click on **Apply filter**. 
 </br>
 </br>
 
-:::image type="content" source="media/apply-filter.png" alt-text="Apply filter." border="false":::
+:::image type="content" source="media/vs-2022/apply-filter.png" alt-text="Apply filter." border="false":::
 
 The **Filter account** dialog will appear, allowing you to select which tenants you want to use with your account. 
 
-:::image type="content" source="media/select-filter-account.png" alt-text="Select account to filter.":::
+:::image type="content" source="media/vs-2022/select-filter-account.png" alt-text="Select account to filter.":::
 
 ## See also
 

docs/ide/media/vs-2022/apply-filter.png

@@ -5,7 +5,7 @@ description: A list of released versions and build numbers for Visual Studio, so
 author: TerryGLee
 ms.author: tglee
 manager: jmartens
-ms.date: 01/19/2022
+ms.date: 01/25/2022
 ms.custom: vs-acquisition
 ms.topic: reference
 ms.workload:
@@ -24,6 +24,7 @@ The following table lists the build numbers and release dates for Visual Studio
 
 | **Version**| **Channel** | **Release date** | **Build version** |
 | ---------------------- | ----------- | ---------------- | ----------------- |
+| 17.1.0 | Preview 4 | January 25, 2022 | 17.1.32120.378 |
 | 17.1.0 | Preview 3 | January 19, 2022 | 17.1.32113.165 |
 | 17.0.5 | Release | January 13, 2022  | 17.0.32112.339 |
 | 17.1.0 | Preview 2 | January 5, 2022 | 17.1.32104.313 |

docs/ide/media/vs-2022/keep-me-signed-in.png

@@ -34,7 +34,7 @@ Make sure to have the following installed:
 
 - Visual Studio 2022 Preview 2 or later with the **ASP.NET and web development** workload installed. Go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/) page to install it for free.
   If you need to install the workload and already have Visual Studio, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the **ASP.NET and web development** workload, then choose **Modify**.
-- npm ([https://www.npmjs.com/](https://www.npmjs.com/)) 
+- npm ([https://www.npmjs.com/](https://www.npmjs.com/package/npm)) 
 - npx ([https://www.npmjs.com/package/npx](https://www.npmjs.com/package/npx))
 
 ## Create the frontend app
@@ -59,6 +59,10 @@ Make sure to have the following installed:
    - App.js (modified)
    - App.test.js (modified)
 
+1. Select an installed browser from the Debug toolbar, such as Chrome or Microsoft Edge.
+
+   If the browser you want is not yet installed, install the browser first, and then select it.
+
 ## Create the backend app
 
 1. In the solution explorer, right-click the solution name, hover over **Add**, and then select **New Project**. 
@@ -80,13 +84,13 @@ Make sure to have the following installed:
 1. Right-click the ASP.NET Core project and choose **Properties**.
 
    :::image type="content" source="media/vs-2022/asp-net-core-project-properties.png" alt-text="Open project properties"::: 
- 
+
 1. Go to the Debug menu and select **Open debug launch profiles UI** option. Uncheck the **Launch Browser** option.
 
    :::image type="content" source="media/vs-2022/asp-net-core-with-react-deselect-launch-browser.png" alt-text="Open debug launch profiles UI"::: 
 
 1. Next, right-click the React project and select the **Properties** menu and go the **Debugging** section. Change the Debugger to launch to the **launch.json** option.
- 
+
    :::image type="content" source="media/vs-2022/asp-net-core-with-react-choose-debugger.png" alt-text="Choose the debugger (launch.json)":::
 
 ## Set the startup project