adding deploy section

windows/application-management/apps-in-windows-10.md

@@ -19,6 +19,16 @@ ms.topic: article
 >
 > - Windows 10
 
+## Before you begin
+
+As organizations become more global, and to support employees working from anywhere, it's recommended to use a Mobile Device Management (MDM) provider. MDM providers help manage your devices, and help manage apps on your devices. For Microsoft, that includes using Microsoft Endpoint Manager. Endpoint Manager includes Microsoft Intune, which is a cloud service, and Configuration Manager, which is on-premises.
+
+In this article, we mention these services. If you're not managing your devices using an MDM provider, the following resources may help you get started:
+
+- [Microsoft Endpoint Manager overview](mem/endpoint-manager-overview)
+- [What is Microsoft Intune](/mem/intune/fundamentals/what-is-intune) and [Microsoft Intune planning guide](/mem/intune/fundamentals/intune-planning-guide)
+- [What is Configuration Manager?](/mem/configmgr/core/understand/introduction)
+
 ## App types
 
 There are different types of apps that can run on your Windows client devices. This section lists some of the common apps used on Windows devices.
@@ -34,7 +44,7 @@ There are different types of apps that can run on your Windows client devices. T
   - **Windows Presentation Foundation (WPF)**: Using .NET, you can create a WPF desktop app that runs on the device, or create a WPF web app. This app is commonly used by organizations that create line of business (LOB) desktop apps. For more information, see [WPF Application Development](/dotnet/desktop/wpf/app-development).
   - **Windows Forms (WinForm)**: Using .NET, you can create a Windows Forms desktop app that runs on the device, and doesn't require a web browser or internet access. Just like Win32 apps, WinForm apps can access the local hardware and file system of the computer where the app is running. For more information, see [Desktop Guide (Windows Forms .NET)](/dotnet/desktop/winforms/overview).
 
-- **Windows apps**: These apps are included with the Windows OS, and can also installed from the Microsoft Store. There are two categories:
+- **Windows apps**: These apps are included with the Windows OS, and can also be installed from the Microsoft Store. There are two categories:
 
   - **Apps**: All apps installed in `C:\Program Files\WindowsApps`. There are two classes of apps:
 
@@ -62,29 +72,74 @@ There are different types of apps that can run on your Windows client devices. T
 
 ## Add or deploy apps to devices
 
-When your apps are ready, you can add or deploy these apps to your Windows devices.
+When your apps are ready, you can add or deploy these apps to your Windows devices. This section lists some common options.
 
 - **Manually install**: On your devices, users can install apps from the Microsoft Store and from the internet. These apps, and more, are listed in **Settings** > **Apps and Features**.
 
-- **Mobile device management (MDM)**: Use a MDM provider, such as Microsoft Intune (cloud) or Configuration Manager (on-premises), to deploy and configure apps. For example, you can create app policies that deploy Microsoft 365 apps, deploy Win32 apps, create shortcuts to web apps, add store apps, and more.
+  If you want to prevent users from downloading apps on organization owned devices, you can use an MDM provider, like Microsoft Intune. For example, you can create a policy that allows or prevents users from sideloading apps, only allow the private store, and more. For more information on the features you can restrict, see [Windows 10 (and newer) device settings to allow or restrict features using Intune](/mem/intune/configuration/device-restrictions-windows-10).
+
+  For an overview of the different types of device policies you can create, see [Apply features and settings on your devices using device profiles in Microsoft Intune](/mem/intune/configuration/device-profiles).
+
+- **Mobile device management (MDM)**: Use a MDM provider, like Microsoft Intune (cloud) or Configuration Manager (on-premises), to deploy apps. For example, you can create app policies that deploy Microsoft 365 apps, deploy Win32 apps, create shortcuts to web apps, add Store apps, and more.
 
   For more information, see:
 
   - [Add apps to Microsoft Intune](/mem/intune/apps/apps-add)
   - [Application management in Configuration Manager](/mem/configmgr/apps/understand/introduction-to-application-management)
 
-- Settings > Apps & features: Provisioned apps, apps installed by users, and apps installed by MDM providers are listed in **Settings** > **Apps and Features**.
+- **Microsoft Store**: Using the Microsoft Store app, Windows users can download apps from the public store, and download apps provided by your organization, which is called the "private store". If your organization creates its own apps, you can use **Windows Package Manager** to add apps to the private store.
-- Use Store
-- Windows Package Manager: https://docs.microsoft.com/en-us/windows/package-manager 
-  - Can install apps from store, or from package. It's a developer tool. 
-  - Only for Windows
 
-- App-V: 
+  To help manage the Microsoft Store on your devices, you can use policies:
-  - app-v server: might not support Win11. It's a separate download.
-  - app-v client: does support Win11. The OS ships with client installs.
 
-  Goal: Stop using app-v, and get on Azure Virtual desktop with msix app attach
+  - On premises, you can use Administrative Templates in group policy to control access to the Microsoft Store app (`User Configuration\Administrative Templates\Windows Components\Store`).
+  - Using Microsoft Intune, you can use [Administrative Templates](/mem/intune/configuration/administrative-templates-windows) or the [Settings Catalog](/mem/intune/configuration/settings-catalog) to control access to the Microsoft Store app.
 
+  For more information, see:
+
+  - [Microsoft Store for Business and Education](/microsoft-store/)
+  - [Evolving the Microsoft Store for Business and Education](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/evolving-the-microsoft-store-for-business-and-education/ba-p/2569423)
+
+- **MSIX for desktop apps**: MSIX packages your UWP, Win32, WPF, and WinForm desktop application files. MSIX reliably installs apps, helps optimize disk storage space, and reduces duplicate files. If your organization typically uses `.EXE` or `.MSI` files to install desktop apps, then you should look into MSIX.
+
+  To deploy MSIX packages and their apps, you can:
+
+  - Use an MDM provider, like Microsoft Intune and Configuration Manager.
+  - Use an App Installer so users double-click an installer file, or select a link on a web page.
+  - And more.
+
+  For more information, see:
+
+  - [What is MSIX?](/windows/msix/overview)
+  - [MSIX app distribution for enterprises](/windows/msix/desktop/managing-your-msix-deployment-enterprise)
+
+- **Windows Package Manager**: Windows Package Manager is a command line tool commonly used by developers to install Windows apps. Using the command line, you can can get apps from the Microsoft Store or from GitHub (and more), and install these apps on Windows devices. It's helpful if you want to bypass user interfaces for getting apps from organizations and from developers.
+
+  If your organization uses `.EXE`, `.MSIX`, or `.MSI` files, then Windows Package Manager might be the right deployment option for your organization.
+
+  For more information, see [Windows Package Manager](/windows/package-manager).
+
+- **Azure Virtual desktop with MSIX app attach**: With Azure virtual desktop, you can virtualize the Windows client OS desktop, and use virtual apps on this desktop. With MSIX app attach, you dynamically deliver MSIX packaged apps to users and user groups.
+
+  The benefit is to use the cloud to deliver virtual apps in real time, and as-needed. Users use the apps as if they were installed locally.
+
+  If you currently use App-V, and want to decrease your on-premises footprint, then **Azure Virtual desktop with MSIX app attach** might be the right deployment for your organization.
+
+  For more information, see:
+
+  - [What is Azure Virtual Desktop?](/azure/virtual-desktop/overview)
+  - [Set up MSIX app attach with the Azure portal](/azure/virtual-desktop/app-attach-azure-portal)
+
+- **Application Virtualization (App-V)**: App-V allows Win32 apps to be used as virtual apps. On an on-premises server, you install and configure the App-V server components, and then install your Win32 apps. On Windows Enterprise client devices, you use the App-V client components to run the virtualized apps. They allow users to open the virtual apps using the icons and file names they're familiar with. Users use the apps as if they were installed locally.
+
+  The benefit is to deliver virtual apps in real time, and as-needed. For more information, see [Application Virtualization (App-V) for Windows overview](./app-v/appv-for-windows.md).
+
+  To help manage App-V on your devices, you can use policies:
+
+  - On premises, you can use Administrative Templates in group policy to deploy App-V policies (`Computer Configuration\Administrative Templates\System\App-V`).
+  - Using Microsoft Intune, you can use [Administrative Templates](/mem/intune/configuration/administrative-templates-windows) or the [Settings Catalog](/mem/intune/configuration/settings-catalog) to deploy App-V policies.
+
+  > [!TIP]
+  > If you want to decrease your on-premises footprint, then **Azure Virtual desktop with MSIX app attach** might be the better deployment for your organization.
 
 ## Remove apps