MDB - Update Windows App references

RoseHJM · RoseHJM · commit 7703b8657589 · 2025-02-23T13:16:06.000-08:00
diff --git a/articles/dev-box/concept-dev-box-architecture.md b/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 created, 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 the dev box  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:
 
diff --git a/articles/dev-box/concept-dev-box-deployment-guide.md b/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":::
 
diff --git a/articles/dev-box/how-to-configure-multiple-monitors.md b/articles/dev-box/how-to-configure-multiple-monitors.md
@@ -27,8 +27,6 @@ When you connect to your cloud-hosted developer machine in Microsoft Dev Box by
 | 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.
diff --git a/articles/dev-box/how-to-create-dev-boxes-developer-portal.md b/articles/dev-box/how-to-create-dev-boxes-developer-portal.md
@@ -39,11 +39,11 @@ You can also create a dev box through the Azure CLI dev center extension. For mo
 
 ## Connect to a dev box
 
-After you create your dev box, you can connect to it through a Remote Desktop application or via the browser.
+After you create your dev box, you can connect to it from the developer portal.
 
-The new Windows App remote desktop client is the recommended client for Microsoft Dev Box; it provides an enhanced user experience, including support for multiple monitors. It's also available on multiple platforms, including Windows, macOS, iOS/iPadOS, Android/Chrome OS (preview), and web browsers. For more information, see [Get started with Windows App](https://aka.ms/dev-box/windows-app).
+Connecting to your dev box from the developer portal launches the Windows App remote desktop client, which provides an enhanced user experience, including support for multiple monitors. It's available on multiple platforms, including Windows, macOS, iOS/iPadOS, Android/Chrome OS (preview), and web browsers. For more information, see [Get started with Windows App](https://aka.ms/dev-box/windows-app).
 
-You can use the **browser** for lighter workloads. When you access your dev box via your phone or laptop, you can use the browser. The browser is useful for tasks such as a quick bug fix or a review of a GitHub pull request. For more information, see the [steps for using a browser to connect to a dev box](./quickstart-create-dev-box.md#connect-to-a-dev-box).
+Alternately, You can use the **browser** for lighter workloads. When you access your dev box via your phone or laptop, you can use the browser. The browser is useful for tasks such as a quick bug fix or a review of a GitHub pull request. For more information, see the [steps for using a browser to connect to a dev box](./quickstart-create-dev-box.md#connect-to-a-dev-box).
 
 ## Explore dev box actions
 
diff --git a/articles/dev-box/how-to-enable-single-sign-on.md b/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. 
 
diff --git a/articles/dev-box/includes/note-windows-app.md b/articles/dev-box/includes/note-windows-app.md
diff --git a/articles/dev-box/index.yml b/articles/dev-box/index.yml
@@ -62,8 +62,6 @@ 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 
diff --git a/articles/dev-box/overview-what-is-microsoft-dev-box.md b/articles/dev-box/overview-what-is-microsoft-dev-box.md
@@ -14,7 +14,7 @@ adobe-target: true
 
 Microsoft Dev Box gives developers self-service access to ready-to-code cloud workstations called *dev boxes*. You can configure dev boxes with tools, source code, and prebuilt binaries that are specific to a project, so developers can immediately start work. You can create your own customized image, or use a preconfigured image from Azure Marketplace, complete with Visual Studio already installed. 
 
-If you're a developer, you can use multiple dev boxes in your day-to-day workflows. You can access your dev boxes through a Remote Desktop client like Windows App, or through a web browser, like any virtual desktop.
+If you're a developer, you can use multiple dev boxes in your day-to-day workflows. You can access your dev boxes through the developer portal.
 
 The Dev Box service was designed with three organizational roles in mind: platform engineers, development team leads, and developers.
 
diff --git a/articles/dev-box/quickstart-create-dev-box.md b/articles/dev-box/quickstart-create-dev-box.md
@@ -16,7 +16,7 @@ ms.date: 01/30/2025
 # Quickstart: Create and connect to a dev box by using the Microsoft Dev Box developer portal
 
 
-In this quickstart, you get started with Microsoft Dev Box by creating a dev box through the developer portal. After you create the dev box, you can connect to it through a browser or through a Remote Desktop client like Windows App.
+In this quickstart, you get started with Microsoft Dev Box by creating a dev box through the developer portal. After you create the dev box, you can connect to it from the developer portal.
 
 You can create and manage multiple dev boxes as a dev box user. Create a dev box for each task that you're working on, and create multiple dev boxes within a single project to help streamline your workflow. For example, you might switch to another dev box to fix a bug in a previous version, or if you need to work on a different part of the application.
 
@@ -87,16 +87,14 @@ To connect to a dev box by using the browser:
 
 A new tab opens with a new session through which you can use your dev box. Use a work or school account to sign in to your dev box, not a personal Microsoft account.
 
-[!INCLUDE [note-windows-app](includes/note-windows-app.md)]
-
 ## Clean up resources
 
+In this quickstart, you created a dev box through the developer portal and connected to it by using a browser. 
+
 When you no longer need your dev box, you can delete it:
 
 [!INCLUDE [dev box runs on creation note](./includes/clean-up-resources.md)] 
 
 ## Related content
 
-In this quickstart, you created a dev box through the developer portal and connected to it by using a browser. 
-
-- Learn how to [Connect with Windows App](/windows-app/get-started-connect-devices-desktops-apps?context=/azure/dev-box/context/context&pivots=dev-box)
+- [Manage a dev box by using the Microsoft Dev Box developer portal](how-to-create-dev-boxes-developer-portal.md)
diff --git a/articles/dev-box/toc.yml b/articles/dev-box/toc.yml
@@ -82,10 +82,8 @@ items:
 - name: Create & connect to dev boxes
   items:
   - name: Manage a dev box through developer portal
+    displayName: Windows App, connect, access dev box, RDP, iPad   
     href: how-to-create-dev-boxes-developer-portal.md
-  - name: Connect with Windows App
-    displayName: Windows App, connect, access dev box, RDP, iPad 
-    href: /windows-app/get-started-connect-devices-desktops-apps?context=/azure/dev-box/context/context&pivots=dev-box
   - name: Use Dev Home to manage dev boxes
     href: how-to-use-dev-home-customize-dev-box.md
   - name: Connect with Remote Desktop
diff --git a/articles/dev-box/tutorial-connect-to-dev-box-with-remote-desktop-app.md b/articles/dev-box/tutorial-connect-to-dev-box-with-remote-desktop-app.md
@@ -18,8 +18,6 @@ In this tutorial, you download and use a remote desktop (RDP) client application
 
 Remote desktop apps let you use and control a dev box from almost any device. For your desktop or laptop, you can choose to download the Remote Desktop client for Windows Desktop or Microsoft Remote Desktop for Mac. You can also download a remote desktop app for your mobile device: Microsoft Remote Desktop for iOS or Microsoft Remote Desktop for Android. 
 
-[!INCLUDE [note-windows-app](includes/note-windows-app.md)]
-
 Alternately, you can access your dev box through the browser from the Microsoft Dev Box developer portal.
 
 In this tutorial, you learn how to:
