Merge pull request #6046 from MicrosoftDocs/master

Taojunshen · web-flow · commit a6a8af08e4b0 · 2021-11-04T06:35:32.000+08:00
11/3/2021 PM Publish
diff --git a/memdocs/intune/protect/encrypt-devices.md b/memdocs/intune/protect/encrypt-devices.md
@@ -39,7 +39,7 @@ Use one of the following policy types to configure BitLocker on your managed dev
 
 - **[Device configuration profile for endpoint protection for BitLocker](#create-an-endpoint-security-policy-for-bitlocker)**. BitLocker settings are one of the available settings categories for Windows 10/11 endpoint protection.
 
-  View the BitLocker settings that are available for [BitLocker in endpoint protection profiles form device configuration policy](../protect/endpoint-protection-windows-10.md#windows-settings).
+  View the BitLocker settings that are available for [BitLocker in endpoint protection profiles from device configuration policy](../protect/endpoint-protection-windows-10.md#windows-settings).
 
 > [!TIP]
 > Intune provides a built-in [encryption report](encryption-monitor.md) that presents details about the encryption status of devices, across all your managed devices. After Intune encrypts a Windows device with BitLocker, you can view and manage BitLocker recovery keys when you view the encryption report.
diff --git a/memdocs/intune/protect/use-network-locations.md b/memdocs/intune/protect/use-network-locations.md
@@ -17,7 +17,8 @@ ms.assetid:
 
 # optional metadata
 
-#ROBOTS:
+#ROBOTS: NOINDEX
+
 #audience:
 
 ms.reviewer: janisjones
diff --git a/windows-365/business/TOC.yml b/windows-365/business/TOC.yml
@@ -5,6 +5,8 @@ items:
   href: get-started-windows-365-business.md
 - name: Features in development 
   href: in-development.md
+- name: What's New 
+  href: whats-new.md
 - name: Cloud PC sizes 
   href: windows-365-business-sizing.md
 - name: Cloud PC location 
diff --git a/windows-365/business/get-started-windows-365-business.md b/windows-365/business/get-started-windows-365-business.md
@@ -103,7 +103,7 @@ Users can navigate to **https://windows365.microsoft.com** to access their Cloud
 
 On their Windows 365 home page, users see the Cloud PCs they have access to in the **Your Cloud PCs** section.
 
-![Windows 365 home.](./media/get-started-windows-365-business/cloudpc-home.png)
+![Windows 365 home.](./media/get-started-windows-365-business/cloud-pc-home.png)
 
 Users can select **Open in browser** to open their Cloud PC.
 
@@ -114,7 +114,7 @@ Users can select **Open in browser** to open their Cloud PC.
 
 While on the Windows 365 home page, users can perform actions on their Cloud PCs by selecting the gear icon on a Cloud PC card.
 
-![Card menu.](./media/get-started-windows-365-business/cloudpc-gear.png)
+![Card menu.](./media/get-started-windows-365-business/cloud-pc-gear.png)
 
 - **Restart**: Restarts the Cloud PC.
 
diff --git a/windows-365/business/media/get-started-windows-365-business/cloud-pc-gear.png b/windows-365/business/media/get-started-windows-365-business/cloud-pc-gear.png
diff --git a/windows-365/business/media/get-started-windows-365-business/cloud-pc-home.png b/windows-365/business/media/get-started-windows-365-business/cloud-pc-home.png
diff --git a/windows-365/business/media/get-started-windows-365-business/cloudpc-home.png b/windows-365/business/media/get-started-windows-365-business/cloudpc-home.png
diff --git a/windows-365/business/whats-new.md b/windows-365/business/whats-new.md
@@ -0,0 +1,70 @@
+---
+# required metadata
+title: What's new in Windows 365 Business
+titleSuffix:
+description: Find out what's new in Windows 365 Business
+keywords:
+author: ErikjeMS  
+ms.author: erikje
+manager: dougeby
+ms.date: 11/03/2021
+ms.topic: reference
+ms.service: cloudpc
+ms.subservice:
+ms.localizationpriority: high
+ms.technology:
+ms.assetid: 
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+
+ms.reviewer: traceyadams
+ms.suite: ems
+search.appverid: MET150
+#ms.tgt_pltfrm:
+ms.custom: intune-azure; get-started
+ms.collection: M365-identity-device-management
+---
+
+# What's new in Windows 365 Business
+
+Learn what new features are available in Windows 365 Business.
+
+> [!Note]
+> Each monthly update may take up to a week to rollout to all customers.
+
+<!-- Common categories:  
+### App management
+### Device configuration
+### Device provisioning
+### Device management
+### Device security
+### Intune apps
+### Monitor and troubleshoot
+### Role-based access control
+### Scripts
+-->
+
+<!-- ########################## -->
+## Week of November 1, 2021 (Service release 2110)
+
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Device management
+
+#### Improved user interface for online access to Cloud PCs<!--36735456 -->
+
+The user interface on [windows365.microsoft.com](https://windows365.microsoft.com) has been improved with:
+
+- Faster load times.
+- Higher performance reliability.
+- Local resource settings (printer, microphone, clipboard).
+- Alternative keyboard settings.
+- Edit settings in-session.
+- Accessibility support.
+
+<!-- ########################## -->
+## Next steps
+
+[Get started with Windows 365 Business](get-started-windows-365-business.md).
diff --git a/windows-365/enterprise/health-checks.md b/windows-365/enterprise/health-checks.md
@@ -54,12 +54,11 @@ Every failed OPNC or success with warning error state includes the technical det
 
 - **DNS can resolve Active Directory domain**: Resolve the provided Active Directory domain name.
 - **Active directory domain join**: A domain join using the credentials, domain, and OU provided.
-- **Endpoint connectivity**: Connectivity to the required [URL/endpoints](requirements-network.md). 
+- **Endpoint connectivity**: Connectivity to the required [URL/endpoints](requirements-network.md).
 - **Azure AD device sync (warning)**: Azure AD sync is enabled on the Azure AD tenant, and the computer object is being synced within 90 minutes.
 - **Azure subnet IP address usage**: Sufficient IP addresses are available in the provided Azure subnet.
-- **Azure subscription is valid**: The defined Azure subscription is enabled and ready for use.
-- **Azure policy restrictions**: No Azure policy restrictions are blocking Windows 365 resources from being created.
-- **Azure vNet in a supported region**: The defined vNet is in a Windows 365 supported region.
+- **Azure tenant readiness**: The defined Azure subscription is enabled and ready for use. No Azure policy restrictions are blocking Windows 365 resources from being created.
+- **Azure virtual network readiness**: The defined vNet is in a Windows 365 supported region.
 - **First party app permissions exist on Azure subscription**: Sufficient permissions exist on the Azure subscription.
 - **First party app permissions exist on Azure resource group**: Sufficient permissions exist on the Azure resource group.
 - **First party app permissions exist on Azure virtual network**: Sufficient permissions exist on the Azure vNet.
diff --git a/windows-365/enterprise/in-development.md b/windows-365/enterprise/in-development.md
@@ -76,18 +76,11 @@ Windows 365 Enterprise will support Cloud PCs that are Azure AD Joined. These de
 New Windows 365 licenses will be available that include virtual graphics processing unit options that support advanced graphic workloads on Cloud PCs.
 
 <!-- ***********************************************-->
-## Provisioning
-
-### Provisioning maximum timeout changing to five hours<!--36461463-->
-
-To improve reliability, the maximum provisioning timeout will be changed to five hours.
+<!--## Provisioning-->
 
 <!-- ***********************************************-->
-## Role-based access control
-
-### Custom Windows 365 RBAC roles<!--36222579 -->
+<!--## Role-based access control-->
 
-In a future release, custom Windows 365 role-based access control (RBAC) roles will be available in the Microsoft Endpoint Manager admin center. You’ll be able to mix-and-match Windows 365 permissions to create custom roles for your organization's needs. You’ll also be able to create both Windows 365 and Intune custom roles and give granular admin permissions to admins for both services.
 
 ## Next steps
 
diff --git a/windows-365/enterprise/index.yml b/windows-365/enterprise/index.yml
@@ -16,9 +16,18 @@ highlightedContent:
     - title: What is Windows 365 Enterprise?
       itemType: overview
       url: overview.md
+    - title: What's new in Windows 365 Enterprise?
+      itemType: overview
+      url: whats-new.md
+    - title: Features in development
+      itemType: overview
+      url: in-development.md
     - title: Planning your Windows 365 deployment
       itemType: get-started
       url: planning-guide.md
+    - title: Requirements
+      itemType: how-to-guide
+      url: requirements.md
     - title: What is provisioning?
       itemType: overview
       url: provisioning.md
diff --git a/windows-365/enterprise/provisioning-errors.md b/windows-365/enterprise/provisioning-errors.md
@@ -56,7 +56,7 @@ Windows 365 doesn’t perform any hybrid Azure Active Directory (Azure AD) join
 
 If provisioning fails because of hybrid Azure AD join, it’s likely because of an insufficient sync period configured in your AD Sync service. Make sure that Azure AD connect is configured to sync the AD computer objects every 30 minutes, and no more than 60 minutes. This step will time out if the Azure AD object doesn’t appear within 90 minutes.
 
-Another factor to consider is your on-premises AD replication time. Make sure that the domain controller being used for Windows 365 will be replicated fast enough to make it into Azure AD within this timeout window.
+Another factor to consider is your on-premises AD replication time. Make sure that the domain controller being used for Windows 365 will be replicated fast enough to make it into Azure AD within this five hour timeout window.
 
 If your organization uses Active Directory Federation Services (ADFS), this registration process is optimized and may result in Cloud PC provisioning completing faster than an Azure AD Connect sync might.
 
diff --git a/windows-365/enterprise/role-based-access.md b/windows-365/enterprise/role-based-access.md
@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 08/02/2021 
+ms.date: 11/03/2021 
 ms.topic: how-to
 ms.service: cloudpc
 ms.subservice:
@@ -50,9 +50,19 @@ Two built-in roles are available for Cloud PC:
 
 **Cloud PC Reader**: Views Cloud PC data available in the Cloud PC node in Microsoft Endpoint Manager, but can’t make changes.
 
-## Custom roles
+## Custom roles (public preview)
 
-Custom roles aren't supported for Cloud PCs.
+You can create custom roles for Windows 365 in [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431). For more information, see [Create a custom role]( /mem/intune/fundamentals/create-custom-role).
+
+To create a provisioning policy, an admin needs the following permissions:
+
+- Provisioning Policy Read/Create
+- On-premises network connection Read
+- Supported region Read
+- Image Read permissions
+
+  > [!IMPORTANT]
+  > Custom role support for Windows 365 is in public preview. This preview version is provided without a service level agreement (SLA). It's not recommended to use in production. Certain features might not be supported, or might have restricted behavior. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
 
 <!-- ########################## -->
 ## Next steps
diff --git a/windows-365/enterprise/troubleshoot-on-premises-network-connection.md b/windows-365/enterprise/troubleshoot-on-premises-network-connection.md
@@ -57,12 +57,6 @@ If provisioning fails, make sure that:
 - Azure AD Connect is running correctly and there are no issues with the sync server.  
 - You manually perform an Add-Computer into the OU provided for Cloud PCs. Time how long it takes for that computer object to appear in Azure AD.
 
-## Azure policy restrictions
-
-Many organizations use Azure policies to make sure that resources are only provisioned into certain regions and services. You should make sure that any Azure policies have considered the Cloud PC service and the supported regions.  
-
-To troubleshoot this failure, visit the Azure portal and view Policies. Make sure that there are no policies blocking resource creation.  
-
 ## Azure subnet IP address range usage
 
 As part of the OPNC setup, you provide a subnet. This subnet is used for all Cloud PCs during the provisioning process. Each Cloud PC provisioning will create a virtual NIC and consume an IP address from the subnet.  
@@ -76,13 +70,17 @@ If this check fails, make sure that:
 - You clean out any unused vNICs and IP addresses. It’s best to use a dedicated subnet for Cloud PCs only to make sure that no other services are eating allocation.  
 - You expand the subnet to make more addresses are available.
 
-## Azure subscription is valid
+## Azure tenant readiness
 
 When checks are performed, we check that the provided Azure subscription is valid and healthy. If it's not valid and healthy, we’re unable to connect Cloud PCs back to your vNet during provisioning. Problems such as billing issues may cause subscriptions to become disabled.  
 
-Sign in to the Azure portal and make sure that the Azure subscription is enabled, valid, and healthy.  
+Many organizations use Azure policies to make sure that resources are only provisioned into certain regions and services. You should make sure that any Azure policies have considered the Cloud PC service and the supported regions.
+
+Sign in to the Azure portal and make sure that the Azure subscription is enabled, valid, and healthy.
+
+Also, visit the Azure portal and view Policies. Make sure that there are no policies blocking resource creation.  
 
-## Azure vNet in a supported region
+## Azure virtual network readiness
 
 When creating an OPNC, we block the use of any vNet located in an unsupported region. For a list of supported regions, see [Requirements](requirements.md).  
 
diff --git a/windows-365/enterprise/whats-new.md b/windows-365/enterprise/whats-new.md
@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 10/14/2021
+ms.date: 11/03/2021
 ms.topic: reference
 ms.service: cloudpc
 ms.subservice:
@@ -47,6 +47,37 @@ Learn what new features are available in Windows 365 Enterprise.
 ### Scripts
 -->
 
+<!-- ########################## -->
+## Week of November 1, 2021 (Service release 2110)
+
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Device management
+
+#### Improved user interface for online access to Cloud PCs<!--36735456 -->
+
+The user interface on [windows365.microsoft.com](https://windows365.microsoft.com) has been improved with:
+
+- Faster load times.
+- Higher performance reliability.
+- Local resource settings (printer, microphone, clipboard).
+- Alternative keyboard settings.
+- Edit settings in-session.
+- Accessibility support.
+
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Provisioning
+
+#### Provisioning maximum timeout changed to five hours<!--36461463-->
+
+To improve reliability, the maximum provisioning timeout has been changed to five hours.
+
+<!-- vvvvvvvvvvvvvvvvvvvvvv -->
+### Role-based access control
+
+#### Custom Windows 365 RBAC roles in public preview<!--36222579  -->
+
+Custom Windows 365 role-based access control (RBAC) roles are now available in the Microsoft Endpoint Manager admin center. You can mix-and-match Windows 365 permissions to create custom roles for your organization's needs. You can also create both Windows 365 and Intune custom roles and give granular admin permissions to admins for both services. For more information, see [Custom roles](role-based-access.md#custom-roles-public-preview).
+
 <!-- ########################## -->
 ## Week of October 11, 2021 (Service release 2109)
 
diff --git a/windows-365/overview.md b/windows-365/overview.md
@@ -55,3 +55,5 @@ Managed Server Providers (MSPs) can manage Cloud PCs in Microsoft 365 Lighthouse
 [Learn more about Windows 365 Business](/windows-365/business/get-started-windows-365-business).
 
 [Learn more about Windows 365 Enterprise](/windows-365/enterprise/overview).
+
+[Read the Windows 365 service description](/office365/servicedescriptions/windows-365-service-description/windows-365-service-description).
