Merge pull request #295154 from RoseHJM/mdb-remove-windows-app

MDB - Update Windows App references

Author: JillGrant615

articles/dev-box/.openpublishing.redirection.dev-box.json

@@ -77,7 +77,7 @@
     },
     {
       "source_path_from_root": "/articles/dev-box/tutorial-connect-to-dev-box-with-remote-desktop-app.md",
-      "redirect_url": "/azure/dev-box/how-to-create-dev-boxes-developer-portal",
+      "redirect_url": "/azure/dev-box/how-to-configure-multiple-monitors",
       "redirect_document_id": false
     }
   ]

articles/dev-box/concept-dev-box-architecture.md

@@ -36,7 +36,7 @@ The network connection that is associated with a dev box pool determines where t
 
 Developers can create a dev box from a dev box pool by using the developer portal. They might choose from a specific pool based on the VM image, compute resources, or the location where the dev box is hosted.
 
-Once the dev box is running, dev box users can [remotely connect](#user-connectivity) to it by using a Remote Desktop client like Windows App, or directly from the browser. Dev box users have full control over the dev boxes they created, and can manage them from the developer portal. 
+Once the dev box is running, dev box users can [remotely connect](#user-connectivity) to it from the developer portal. Dev box users have full control over the dev boxes they create, and can manage them from the developer portal. 
 
 ## Microsoft Dev Box architecture
 
@@ -102,7 +102,7 @@ When you configure dev boxes to use [Microsoft Entra join](/azure/active-directo
 
 ### User connectivity
 
-When a dev box is running, developers can connect to the dev box by using a Remote Desktop client like Windows App, or directly from within the browser.
+When a dev box is running, developers can connect to it from the developer portal.
 
 Dev box connectivity is provided by Azure Virtual Desktop. No inbound connections direct from the Internet are made to the dev box. Instead, the following connections are made:
 

articles/dev-box/concept-dev-box-deployment-guide.md

@@ -38,8 +38,8 @@ Each of these roles has specific responsibilities during the deployment of Micro
     - Provide input to platform engineers for creating and managing dev box definitions in the dev center
 
 - **Developer**: self-serve one or more dev boxes within their assigned projects.
-    - Create and manage a dev box based on project dev box pool from the developer portal
-    - Connect to a dev box by using a Remote Desktop client like Windows App
+    - Connect to a dev box from the developer portal
+    - Create and manage a dev box from the developer portal
 
 :::image type="content" source="media/overview-what-is-microsoft-dev-box/dev-box-roles.png" alt-text="Diagram that shows roles and responsibilities for Dev Box platform engineers, team leads, and developers." lightbox="media/overview-what-is-microsoft-dev-box/dev-box-roles.png" border="false":::
 

articles/dev-box/how-to-configure-multiple-monitors.md

@@ -26,9 +26,6 @@ When you connect to your cloud-hosted developer machine in Microsoft Dev Box by
 | Remote Desktop Connection (MSTSC) | <sub>:::image type="icon" source="./media/how-to-configure-multiple-monitors/yes.svg" border="false":::</sub> | [Microsoft Remote Desktop Connection](/azure/dev-box/how-to-configure-multiple-monitors?branch=main&tabs=windows-connection#configure-remote-desktop-to-use-multiple-monitors) |
 | Microsoft Remote Desktop for macOS  | <sub>:::image type="icon" source="./media/how-to-configure-multiple-monitors/yes.svg" border="false":::</sub> | [Microsoft Remote Desktop for macOS](/azure/dev-box/how-to-configure-multiple-monitors?branch=main&tabs=macOS#configure-remote-desktop-to-use-multiple-monitors) |
 
-
-[!INCLUDE [note-windows-app](includes/note-windows-app.md)]
-
 ## Prerequisites
 
 To complete the steps in this article, you must install the appropriate Remote Desktop client on your local machine.

articles/dev-box/how-to-enable-single-sign-on.md

@@ -88,9 +88,9 @@ If you disable single sign-on for a pool, new dev boxes created from that pool p
 
 When single sign-on is enabled for a pool, your sign-on experience is as follows:
 
-The first time you connect to a dev box with single sign-on enabled, you first sign into your physical machine. Then you connect to your dev box from a remote desktop client like Windows App or the developer portal. When the dev box starts up, you must enter your credentials to access the dev box. 
+The first time you connect to a dev box with single sign-on enabled, you first sign into your physical machine. Then you connect to your dev box from the developer portal. When the dev box starts up, you must enter your credentials to access the dev box. 
 
-The next time you connect to your dev box, whether through the Windows App or through the developer portal, you don't have to enter your credentials. 
+The next time you connect to your dev box you don't have to enter your credentials. 
 
 If your connection to your dev box is interrupted because your client machine goes to sleep, you see a message explaining the issue, and you can reconnect by selecting the **Reconnect** button. You don't have to reenter your credentials. 
 

articles/dev-box/includes/note-windows-app.md

@@ -62,12 +62,8 @@ landingContent:
     linkLists:
       - linkListType: how-to-guide
         links:
-          - text: Connect with Windows App
-            url: /windows-app/get-started-connect-devices-desktops-apps?context=/azure/dev-box/context/context&pivots=dev-box
           - text: Use Dev Home to manage dev boxes
-            url: how-to-use-dev-home-customize-dev-box.md  
-          - text: Use multiple monitors with your dev box 
-            url: tutorial-configure-multiple-monitors.md 
+            url: how-to-use-dev-home-customize-dev-box.md 
       - linkListType: how-to-guide
         links:
           - text: Use the Troubleshoot and Repair tool