Merge pull request #6745 from MicrosoftDocs/release-win365-2201

move win365 2201 release branch to main

Author: dougeby

windows-365/business-enterprise-comparison.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 10/04/2021
+ms.date: 02/08/2022
 ms.topic: overview
 ms.service: cloudpc
 ms.subservice:
@@ -36,27 +36,27 @@ Windows 365 is available in two editions: [Windows 365 Business](./business/inde
 
 | Capability | Windows 365 Business | Windows 365 Enterprise |
 | --- | --- | --- |
-| Domain Join | Azure AD without Azure Virtual Network (VNet) support. | Hybrid Azure AD with VNet support.<br>For other domain support, see [In development for Windows 365 Enterprise](./enterprise/in-development.md). |
+| Domain Join | Azure AD Join without Azure Virtual Network (VNet) support. | Azure AD Join without VNet support.<br>Azure AD Join with VNet support.<br>Hybrid Azure AD with VNet support.<br>For other domain support, see [In development for Windows 365 Enterprise](./enterprise/in-development.md). |
 
 ## Purchasing and licensing comparisons
 
 | Capability | Windows 365 Business | Windows 365 Enterprise |
 | --- | --- | --- |
 | Purchase channels | Web direct, self-service, Cloud Solution Provider (CSP). | Web direct, Enterprise Agreements (EA), CSP. |
-| License assignment | Microsoft 365 Admin Center or the Azure AD portal. | Microsoft 365 Admin Center. |
-| Licensing requirements | No licensing pre-requirements to buy and deploy Windows 365 Business. Other features (like device management) can be used if users are licensed for Microsoft Endpoint Management.| Each user must be licensed for Windows 10 or 11 Enterprise, Microsoft Endpoint Manager, and Azure AD P1. |
-| Networking costs | Outbound data/month is based on the RAM of the Cloud PC:<br>- 2 GB RAM = 12 GB outbound data<br>- 4 or 8 GB RAM = 20 GB outbound data<br>- 16 GB RAM = 40 GB outbound data<br>- 32 GB RAM = 70 GB outbound data<br>Data bandwidth may be restricted when these levels are exceeded. | Networking goes through the customer's Azure VNet and isn't included in the license. [Azure bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/) applies for these network usage costs.
+| License assignment | Microsoft 365 Admin Center or the Azure AD portal. | Microsoft 365 Admin Center or the Azure AD portal. |
+| Licensing requirements | No licensing pre-requirements to buy and deploy Windows 365 Business. Other features (like device management) can be used if users are licensed for Microsoft Endpoint Management.| Each user must be licensed for Windows 10 or 11 Enterprise (when available), Microsoft Endpoint Manager, and Azure AD P1. |
+| Networking costs | Outbound data/month is based on the RAM of the Cloud PC:<br>- 2-GB RAM = 12-GB outbound data<br>- 4 or 8-GB RAM = 20-GB outbound data<br>- 16-GB RAM = 40-GB outbound data<br>- 32-GB RAM = 70-GB outbound data<br>Data bandwidth may be restricted when these levels are exceeded. | When providing a network, Networking goes through the customer's Azure VNet and isn't included in the license. [Azure bandwidth pricing](https://azure.microsoft.com/pricing/details/bandwidth/) applies for these network usage costs. <br>If using a Microsoft-hosted network, the same charges (as described in Windows 365 Business networking charges) apply.|
 | Seat limits | Capped to 300 seats per tenant. [Commercial Licensing Terms](https://www.microsoft.com/licensing/terms/productoffering/Windows365/MOSA) | No seat cap per tenant. [Commercial Licensing Terms](https://www.microsoft.com/licensing/terms/productoffering/Windows365/MOSA) |
 
 ## Administrative comparisons
 
 | Capability | Windows 365 Business | Windows 365 Enterprise |
 | --- | --- | --- |
-| Provisioning | Provisioning is simplified and uses default configurations.<br>Cloud PCs are automatically provisioned with a standard image after a Cloud PC license is assigned. | Provisioning is configurable and customizable to the needs of the organization.<br>Admins set up the VNet, configure user permissions (local admin or not), and assign the policy to an Azure AD group.<br>Cloud PCs are then provisioned by using standard gallery images or custom images (admin choice). |
+| Provisioning | Provisioning is simplified and uses default configurations.<br>Cloud PCs are automatically provisioned with a standard image after a Cloud PC license is assigned. | Provisioning is configurable and customizable to the needs of the organization.<br>Admins select the network, configure user permissions (local admin or not), and assign the policy to an Azure AD group.<br>Cloud PCs are then provisioned by using standard gallery images or custom images (admin choice). |
 | Policy management | Not Supported. | Group Policy Objects (GPO) and Intune MDM are supported. |
 | Application deployment | Supported only if you have Intune license. | Supported. |
-| Windows updates | Default Windows Update for Business settings are configured for users. With an Intune license these can be edited. | Can be managed by using Microsoft Endpoint Manager. |
-| Device management | Device management is limited to assigning and unassigning of Cloud PC licenses in the Microsoft Admin Center. Some device management is possible in Microsoft Endpoint Manager if you have an Intune license but Cloud PCs will not be visible in the Windows 365 blade. | Microsoft Endpoint Manager admin center options, including image management, link and access on-premises resources, granular targeting of policies, resizing Cloud PCs, other user experience settings, and all the policy-based management options available to physical devices. |
+| Windows updates | Default Windows Update for Business settings are configured for users. With an Intune license, these settings can be edited. | Can be managed by using Microsoft Endpoint Manager. |
+| Device management | Device management is limited to assigning and unassigning of Cloud PC licenses in the Microsoft Admin Center. Some device management is possible in Microsoft Endpoint Manager if you have an Intune license but Cloud PCs won't be visible in the Windows 365 blade. | Microsoft Endpoint Manager admin center options, including image management, link and access on-premises resources, granular targeting of policies, resizing Cloud PCs, other user experience settings, and all the policy-based management options available to physical devices. |
 | Monitoring | Not supported. | Endpoint Analytics reporting and monitoring, service health, and operational health alerts. |
 | Troubleshooting | Not supported | Microsoft Endpoint Manager troubleshooting including the Troubleshooting blade, device management actions, and reprovisioning of Cloud PCs to their initial state. |
 | Partner/programmatic access | Not supported | Partners can manage Cloud PCs through Microsoft 365 Lighthouse or restful web APIs (Graph) to support Managed Service Provider tooling for up to 300 seats.  |
@@ -75,7 +75,7 @@ Windows 365 is available in two editions: [Windows 365 Business](./business/inde
 | Capability | Windows 365 Business | Windows 365 Enterprise |
 | --- | --- | --- |
 | Conditional Access | Conditional Access policies can be deployed only by using Azure AD with an Azure AD P1 license. | Conditional Access policies can be deployed by using the Microsoft Endpoint Manager admin center or Azure AD. |
-| [Per-user multi-factor authentication (MFA)](/azure/active-directory/authentication/howto-mfa-userstates) | Only MFA using [Azure AD Conditional Access](/azure/active-directory/authentication/tutorial-enable-azure-mfa) is supported. Legacy per-user MFA is not supported. | Supported. |
+| [Per-user multi-factor authentication (MFA)](/azure/active-directory/authentication/howto-mfa-userstates) | Only MFA using [Azure AD Conditional Access](/azure/active-directory/authentication/tutorial-enable-azure-mfa) is supported. Legacy per-user MFA isn't supported. | Legacy per-user MFA is supported for user connections to Hybrid Azure AD joined Cloud PCs.  It's not supported for user connections to Azure AD joined Cloud PCs. |
 | Security baselines | Not supported. | Dedicated Security Baselines can be edited and deployed by using Microsoft Endpoint Manager. |
 | Microsoft Defender for Endpoint | Supported if the customer separately has the requisite E5 license. | Integration with Defender for Endpoint. If the customer has an E5 license, all Cloud PCs will respond to Defender for Endpoint policies and show up in MDE dashboards. |
 

windows-365/business/change-organization-default-settings.md

@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 12/08/2021
+ms.date: 02/08/2022
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice: 
@@ -36,6 +36,8 @@ By default, new Cloud PCs are created with the Windows 11 operating system and t
 2. Select **Your organization’s Cloud PCs** > **Update organization settings**.
 3. Select your preferred operating system and account type > **Save**.
 
+You can also change your organization's default settings in the Microsoft 365 admin center. For more information, see [Change your organization's address, technical contact, and more](/microsoft-365/admin/manage/change-address-contact-and-more).
+
 Organization settings only apply to newly created Cloud PCs. When these settings are changed, they won’t change the OS or account type of existing Cloud PCs.
 
 > [!NOTE]  

windows-365/business/known-issues.md

@@ -1,5 +1,5 @@
 ---
-title: Known issues for Windows 365 Business Cloud PC setup issues
+title: Known issues for Windows 365 Business Cloud PC
 description: Learn about known issues for Windows 365 Business.
 f1.keywords:
 - NOCSH
@@ -88,6 +88,8 @@ If your email service uses Simple Mail Transfer Protocol (SMTP) for your email c
 
 Or you can ask your email service provider for help to configure their email client app to use secure SMTP over Transport Layer Security (TLS), which uses a different port.
 
+[!INCLUDE [Missing start menu and taskbar when using iPad and the Remote Desktop app to access a Cloud PC](../includes/known-issues.md)]
+
 ## Next steps
 
 [Troubleshoot Windows 365 Business Cloud PC setup issues](troubleshoot-windows-365-business.md)

windows-365/enterprise/TOC.yml

@@ -145,22 +145,26 @@ items:
         href: /mem/intune/protect/windows-10-update-rings?context=/windows-365/context/pr-context
       - name: Windows 10 feature updates
         href: /mem/intune/protect/windows-10-feature-updates?context=/windows-365/context/pr-context
-    - name: End user experience
+    - name: End-user experience
       items:
-      - name: End user hardware requirements
+      - name: End-user hardware requirements
         href: end-user-hardware-requirements.md
       - name: Access a Cloud PC
         href: end-user-access-cloud-pc.md
 - name: Troubleshoot
   items:
     - name: Troubleshooting
       href: troubleshooting.md
+    - name: Known issues 
+      href: known-issues-enterprise.md
     - name: On-premises network connections
       href: troubleshoot-on-premises-network-connection.md
     - name: On-premises network connection health checklist
       href: health-checks.md
     - name: Remote Desktop client
       href: /azure/virtual-desktop/troubleshoot-client?context=/windows-365/context/pr-context
+    - name: Connection errors
+      href: connection-errors.md
     - name: Provisioning errors
       href: provisioning-errors.md
 - name: Reference

windows-365/enterprise/add-device-images.md

@@ -30,24 +30,30 @@ ms.collection: M365-identity-device-management
 
 # Add or delete custom device images
 
-If you want to use a custom device image, you can add it into your Azure subscription and then use it for provisioning Cloud PCs. You can use standard Azure Marketplace gallery images or [create your own custom managed image](/azure/virtual-machines/windows/capture-image-resource). If you currently use a Shared Image Gallery in Microsoft Azure, you can convert one of those images into a managed imaged using the steps to [export an image version to a managed disk](/azure/virtual-machines/managed-disk-from-image-version) and then [create an image from a managed disk](/azure/virtual-machines/windows/capture-image-resource#create-an-image-from-a-snapshot-using-powershell).
+If you want to use a custom device image, you can add it into your Azure subscription and then use it for provisioning Cloud PCs. You can use standard Azure Marketplace gallery images or [create your own custom managed image](/azure/virtual-machines/windows/capture-image-resource). If you currently use a Shared Image Gallery in Microsoft Azure, you can convert one of those images into a managed image. To convert, use the steps to [export an image version to a managed disk](/azure/virtual-machines/managed-disk-from-image-version) and then [create an image from a managed disk](/azure/virtual-machines/windows/capture-image-resource#create-an-image-from-a-snapshot-using-powershell).
 
 > [!NOTE]
-> - Windows 10 images should not contain Azure Virtual Desktop client components. Additionally, you cannot import Windows 10 Multisession images into Windows 365.
+>
+> - Windows 10 images should not contain Azure Virtual Desktop client components. Additionally, you can't import Windows 10 Multisession images into Windows 365.
 > - For information about support for Windows 11 custom device images, see [What's New for Windows 365 Enterprise](whats-new.md#support-for-windows-11).
 
 ## Add a custom device image
 
-You can upload the custom image to the Windows 365 service by following these steps:
+For both hybrid Azure Active Directory (Azure AD) join and Azure AD join connections, you can upload the custom image to the Windows 365 service by following these steps:
 
-1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431), select **Devices** > **Windows 365** (under **Provisioning**) > **Device images** > **Add**.
+1. For Azure AD join on-premises network connections (OPNC) without your own network, you must first [create an on-premises network connection](create-on-premises-network-connection.md) with the Azure subscription associated with the targeted custom images.
+
+2. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
+
+3. Select **Devices** > **Windows 365** (under **Provisioning**) > **Device images** > **Add**.
 ![Screenshot of add device image](./media/add-device-images/add-device-image.png)
-2. In the **Add image** pane, provide the following information:
+
+4. In the **Add image** pane, provide the following information:
     - **Image name**: The name of the image you want to add.
     - **Image version**: A version number of the image with this format: Major(int).Minor(int).Patch(int) format. For example: 0.0.1, 1.5.13.
     - **Source Image**: Choose an image to add. The list will populate with all custom images from your subscription that meet the pre-requisites.
 
-3. Select **Add** to add the image to your device image list.
+5. Select **Add** to add the image to your device image list.
 
 ## Delete a custom device image
 
@@ -57,7 +63,7 @@ You can delete a custom image from Windows 365 by following these steps:
 2. On the **Device images** page, select the check box next to the image > **Delete**.
 3. Select **Yes** on the confirmation pop up to permanently delete the image.
 
-Device images being used in a provisioning policy cannot be deleted. Delete the provisioning policy first and then the associated device image.
+Device images being used in a provisioning policy can't be deleted. Delete the provisioning policy first and then the associated device image.
 
 <!-- ########################## -->
 ## Next steps