Merge branch 'main' into release-cm2207-cb

v-alje · v-alje · commit dc63eaa7793b · 2022-08-09T10:31:56.000-07:00
diff --git a/memdocs/autopilot/autopilot-mbr.md b/memdocs/autopilot/autopilot-mbr.md
@@ -180,10 +180,6 @@ To reregister an Autopilot device from Intune, an IT Admin would:
 2. Navigate to Device enrollment > Windows enrollment > Devices > Import.
 3. Click the **Import** button to upload a csv file containing the device ID of the device to be reregistered. The device ID was the 4K HH captured by the PowerShell script or OA3 tool described previously in this document.
 
-The following video provides a good overview of how to (re)register devices via MSfB.<br>
-
-> [!VIDEO https://www.youtube.com/embed/IpLIZU_j7Z0]
-
 ### Reregister from MPC
 
 To reregister an Autopilot device from MPC, an OEM or CSP would:
diff --git a/memdocs/autopilot/windows-autopilot-whats-new.md b/memdocs/autopilot/windows-autopilot-whats-new.md
@@ -20,7 +20,7 @@ ms.topic: article
 ## Update Intune Connector for Active Directory for Hybrid Azure AD joined devices
 <!-- 2209 -->
 
-Starting in September 2022, the Intune Connector for Active Directory (ODJ connector) will require .NET Framework version 4.7.2 or later. If you're not already using .NET 4.7.2 or later, the Intune Connector may not work for Autopilot hybrid Azure AD deployments and will result in failures. When you install a new Intune Connector, don't use the connector installation package that was previously downloaded. Download a new version from the **Intune Connector for Active Directory** section of the Microsoft Endpoint Manager admin center. If you're not using the latest version, it may continue to work, but the auto-upgrade feature to provide updates to the Intune Connector won't work.
+Starting in September 2022, the Intune Connector for Active Directory (ODJ connector) will require .NET Framework version 4.7.2 or later. If you're not already using .NET 4.7.2 or later, the Intune Connector may not work for Autopilot hybrid Azure AD deployments and will result in failures. When you install a new Intune Connector, don't use the connector installation package that was previously downloaded. Before you install a new connector, update the .NET Framework to version 4.7.2 or later. Download a new version from the **Intune Connector for Active Directory** section of the Microsoft Endpoint Manager admin center. If you're not using the latest version, it may continue to work, but the auto-upgrade feature to provide updates to the Intune Connector won't work.
 
 ## Enroll to co-management from Windows Autopilot
 <!-- 11300628 -->
diff --git a/memdocs/configmgr/core/servers/manage/maintenance-tasks.md b/memdocs/configmgr/core/servers/manage/maintenance-tasks.md
@@ -136,9 +136,6 @@ When the Configuration Manager database is reindexing, either through the [built
 
 If the state change during a reindex is problematic for your monitoring, each replication link has a set of [thresholds that can be modified](../../plan-design/hierarchy/database-replication.md#database-replication-thresholds) to adjust when the link goes into a degraded state or when it goes into a failed state. Replication links contain multiple replication groups, which are broken up into two types: global data and site data. Global data attempts to sync every one minute and site data syncs every five minutes. By default, the link changes to degraded when the threshold of 12 failures is reached then changes to the failed state at 24. To set these thresholds, select the link under the **Database Replication** node then select **Link Properties**. In the **Alerts** tab, there are thresholds for setting the link to degraded or failed. By default these values are set to 12 and 24 respectively.
 
-> [!IMPORTANT]
-> Take caution when changing these values since the higher the value the longer it will take you to be notified of a problem. When choosing to increase or decrease the value, increment or decrement by 1 and monitor the link closely before making another change to it.
-
 ## Next steps
 
 [Reference for maintenance tasks](reference-for-maintenance-tasks.md)
diff --git a/memdocs/intune/enrollment/toc.yml b/memdocs/intune/enrollment/toc.yml
@@ -31,14 +31,23 @@ items:
     displayName: COD   
   - name: Incomplete user enrollment report
     href: enrollment-report-company-portal-abandon.md
-  - name: Restrictions
-    href: enrollment-restrictions-set.md  
   - name: Terms and conditions
     href: terms-and-conditions-create.md
   - name: Intune and Azure AD device limits  
     href: device-limit-intune-azure.md    
 - name: How-to guides
   items:
+  - name: Set enrollment restrictions
+    href: enrollment-restrictions-set.md  
+  - name: Add device enrollment manager  
+    href: device-enrollment-manager-enroll.md  
+  - name: Configure device categories  
+    href: device-group-mapping.md   
+  - name: Get Apple MDM push certificate  
+    href: apple-mdm-push-certificate-get.md 
+  - name: Require multi-factor authentication  
+    href: multi-factor-authentication.md
+    displayName: mfa; multifactor   
   - name: Set up Windows enrollment
     items:
     - name: Windows enrollment methods
@@ -145,15 +154,6 @@ items:
       href: device-enrollment-program-enroll-macos.md
     - name: Direct Enrollment for macOS devices
       href: device-enrollment-direct-enroll-macos.md      
-  - name: Add device enrollment manager  
-    href: device-enrollment-manager-enroll.md  
-  - name: Configure device categories  
-    href: device-group-mapping.md   
-  - name: Get Apple MDM push certificate  
-    href: apple-mdm-push-certificate-get.md 
-  - name: Require multi-factor authentication  
-    href: multi-factor-authentication.md
-    displayName: mfa; multifactor   
   - name: Troubleshoot enrollment
     items:
     - name: Troubleshoot device enrollment
diff --git a/memdocs/intune/enrollment/windows-enroll.md b/memdocs/intune/enrollment/windows-enroll.md
@@ -124,18 +124,22 @@ Using a method other than the CNAME configuration isn't supported. For example,
 
 ## Tell users how to enroll Windows devices
 
-Tell your users how to enroll their Windows devices and what to expect after they're brought into management.
+The Microsoft Intune user-help docs provide conceptual information, tutorials, and how-to guides for employees and students setting up their devices. You can point people directly to them or use these articles as guidance when developing and updating your org's own device management docs.  
+
+These articles describe how to enroll devices running Windows: 
+
+ * [Enroll Windows 10/11 device](../user-help/enroll-windows-10-device.md) 
+ * [Enroll Windows 8.1 or Windows RT 8.1 device](../user-help/enroll-your-w81-or-rt81-windows.md)
+
+For information about how enrollment affects the device and the information on it, see [What information can my organization see when I enroll my device?](../user-help/what-info-can-your-company-see-when-you-enroll-your-device-in-intune.md)  
 
 > [!NOTE]
 > End users must access the Company Portal website through Microsoft Edge to view Windows apps that you've assigned for specific versions of Windows. Other browsers, including Google Chrome, Mozilla Firefox, and Internet Explorer do not support this type of filtering.
 
-For end-user enrollment instructions, see [Enroll Windows 10/11 device](../user-help/enroll-windows-10-device.md) and [Enroll Windows 8.1 or Windows RT 8.1 device](../user-help/enroll-your-w81-or-rt81-windows.md). You can also tell users to review [What can my IT admin see on my device](../user-help/what-info-can-your-company-see-when-you-enroll-your-device-in-intune.md).  
 
 >[!IMPORTANT]
 > If you do not have Auto-MDM enrollment enabled, but you have Windows 10/11 devices that have been joined to Azure AD, two records will be visible in the Intune console after enrollment. You can stop this by making sure that users with Azure AD joined devices go to **Accounts** > **Access work or school** and **Connect** using the same account.
 
-For more information about end-user tasks, see [Resources about the end-user experience with Microsoft Intune](../fundamentals/end-user-educate.md).
-
 ## Registration and Enrollment CNAMEs
 
 Azure Active Directory has a different CNAME that it uses for device registration for iOS/iPadOS, Android, and Windows devices. Intune conditional access requires devices to be registered, also called "workplace joined". If you plan to use conditional access, you should also configure the EnterpriseRegistration CNAME for each company name you have.
diff --git a/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md b/memdocs/intune/fundamentals/azure-virtual-desktop-multi-session.md
@@ -8,7 +8,7 @@ keywords:
 author: smbhardwaj  
 ms.author: smbhardwaj
 manager: dougeby
-ms.date: 06/21/2022
+ms.date: 08/03/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -70,6 +70,7 @@ This feature supports Windows 10 or Windows 11 Enterprise multi-session VMs, whi
   - Configured with [Active Directory group policy](/windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy), set to use Device credentials, and set to automatically enroll devices that are Hybrid Azure AD-joined.
   - [Configuration Manager co-management](/configmgr/comanage/overview).
 - Azure AD-joined and enrolled in Microsoft Intune by enabling [Enroll the VM with Intune](/azure/virtual-desktop/deploy-azure-ad-joined-vm#deploy-azure-ad-joined-vms) in the Azure portal.
+- Licensing: The appropriate Microsoft Intune license is required if a user or device benefits directly or indirectly from the Microsoft Intune service, including access to the Microsoft Intune service through a Microsoft API. For more information, see Microsoft Intune licensing. 
 
 > [!NOTE]
 > If you're joining session hosts to Azure Active Directory Domain Services, you can't manage them using Intune.
diff --git a/memdocs/intune/fundamentals/filters-device-properties.md b/memdocs/intune/fundamentals/filters-device-properties.md
@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 02/10/2022
+ms.date: 08/08/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: fundamentals
@@ -39,6 +39,8 @@ This article describes the different [device properties](#device-properties) and
 
 ## Device properties
 
+You can use the following device properties in your filter rules:
+
 - **Device Name**: Create a filter rule based on the Intune device name property. Enter a string value for the device's full name (using `-eq`, `-ne`, `-in`, `-notIn` operators), or partial value (using `-startswith`, `-contains`, `-notcontains` operators).
 
   Examples:
diff --git a/memdocs/intune/remote-actions/device-rename.md b/memdocs/intune/remote-actions/device-rename.md
@@ -47,6 +47,9 @@ If a device isn't listed here, it's not supported.
 
 This feature doesn't support renaming hybrid Azure AD Windows devices.
 
+> [!NOTE]
+> Renaming of Android Enterprise devices will only change the name in Intune and not on the device itself. The Device name in Intune is a friendly name that users are free to change.
+
 ## Rename a device
 
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
diff --git a/memdocs/intune/remote-actions/devices-wipe.md b/memdocs/intune/remote-actions/devices-wipe.md
@@ -34,9 +34,6 @@ ms.collection:
 
 By using the **Retire** or **Wipe** actions, you can remove devices from Intune that are no longer needed, being repurposed, or missing. Users can also issue a remote command from the Intune Company Portal to devices that are enrolled in Intune.
 
-> [!NOTE]
-> Before you remove a user from Azure Active Directory (Azure AD), use the **Wipe** or **Retire** actions for all devices that are associated with that user. If you remove users that have managed devices from Azure AD, Intune can no longer wipe or retire those devices.
-
 ## Wipe
 
 The **Wipe** action restores a device to its factory default settings. The user data is kept if you choose the **Retain enrollment state and user account** checkbox. Otherwise, all data, apps, and settings will be removed.
diff --git a/memdocs/intune/remote-actions/remote-help.md b/memdocs/intune/remote-actions/remote-help.md
@@ -191,10 +191,13 @@ To configure your tenant to support remote help, review and complete the followi
 
 2. On the **Settings** tab:
    1. Set **Enable remote help** to **Enabled** to allow the use of remote help. By default, this setting is *Enabled*.
-   2. Set **Allow remote help to unenrolled devices** to **Enabled** if you want to allow this option. By default, this setting *Disabled*.
+   2. Set **Allow remote help to unenrolled devices** to **Enabled** if you want to allow this option. By default, this setting is *Disabled*.
 
 3. Select **Save**.
 
+> [!NOTE] 
+> When you purchase licenses or start a trial, it could take a while to become active (anywhere between 30 minutes to 8 hours). 
+> When you try to create a Remote help session you may continue to see messages indicating that Remote help isn't enabled for the tenant even if you enabled Remote help in the tenant after activation. 
 ### Task 2 – Configure permissions for remote help
 
 The following Intune RBAC permissions manage the use of the remote help app. Set each to *Yes* to grant the permission:
diff --git a/windows-365/enterprise/TOC.yml b/windows-365/enterprise/TOC.yml
@@ -29,8 +29,12 @@ items:
     href: customer-permissions.md  
   - name: Device configuration with MEM
     href: device-configuration.md
-  - name: Encryption
-    href: encryption.md
+  - name: Security
+    items:
+    - name: Windows 365 security
+      href: security.md
+    - name: Encryption
+      href: encryption.md
   - name: Privacy and personal data
     href: privacy-personal-data.md
 - name: How-to guides
diff --git a/windows-365/enterprise/known-issues-enterprise.md b/windows-365/enterprise/known-issues-enterprise.md
@@ -53,6 +53,13 @@ Upgrading an existing Cloud PC from Windows 10 to Windows 11 using the Settings
 1. Edit the related provisioning policy to change the gallery image to Windows 11.
 2. Reprovision the Cloud PC.
 
+## In-place Windows updgrade may change computer name
+
+Upgrading an existing Cloud PC between release versions of Windows 10 to Windows 11 may cause the computer name to be changed to a name with a prefix of "pps" while leaving the Intune device name unchanged.
+
+**Troubleshooting steps**: Find and manage the Cloud PC in Microsoft Endpoint Manager by using the unchanged Intune device name, either through the **Devices > All devices** list or the **Devices > Windows 365 > All Cloud PCs** list.
+
+
 ## Windows 365 provisioning fails<!--38483005-->
 
 Windows 365 provisioning failures may occur because both:
diff --git a/windows-365/enterprise/media/report-remoting-connection/device-history.png b/windows-365/enterprise/media/report-remoting-connection/device-history.png
diff --git a/windows-365/enterprise/report-remoting-connection.md b/windows-365/enterprise/report-remoting-connection.md
@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 08/30/2021
+ms.date: 08/08/2022
 ms.topic: overview
 ms.service: cloudpc
 ms.subservice:
@@ -49,21 +49,21 @@ To get to the **Remoting connection** report, sign in to [Microsoft Endpoint Man
 
 ## Remoting connection tab
 
-The **Remoting connection** tab lists the following information: 
+The **Remoting connection** tab lists the following information:
 
-**Round Trip Time (ms)** is the speed and reliability of network connections from the user location. Times are given for the most recent time (p95 (Last)) and the Median time. The times for the ratings are:
+**Round Trip Time (ms)** is the time taken for traffic from users' devices to reach Cloud PC and return. This metric is an indicator of the quality of the connection and can be used to determine the user’s experience. Values displayed are for the median time of the most recent reading of the metric’s 95th percentile value (p95 (Last)). A rating is provided for these values based on the criteria below.
 
 - Good = 0-100 milliseconds
 - Average = 100-200 milliseconds
 - Poor = more than 200 milliseconds
 
-**Sign in time (sec)** is the total time users take to connect to the Cloud PC. Times are given for the most recent sign in time (p95 (Last)) and the Median sign in time. The times for the ratings are:
+**Sign in time (sec)** is the total time taken for users to connect to the Cloud PC. Values displayed are for the median time of the most recent reading of the metric’s 95th percentile value (p95 (Last)). A rating is provided for these values based on the criteria below.
 
 - Good = 0-30 seconds
 - Average = 30-60 seconds
 - Poor = more than 60 seconds
 
-**Insights and recommendations** suggests actions that you can take to improve your scores.
+**Insights and recommendations** provide information about the actions that you can take to improve scores for specific Cloud PCs that have poor or average ratings.
 
 ![Screenshot of using the remoting connection tab](./media/report-remoting-connection/remoting-connection-tab.png)
 
@@ -75,13 +75,16 @@ You can review the **Round trip time** and **Sign in time** for each Cloud PC mo
 
 ## Device performance tab
 
-You can review the **Round trip time** and **Sign in time** for each Cloud PC device in your organization.
+You can review a list of the **Round trip time** and **Sign in time** values for all the Cloud PC devices in your organization.
 
 ![Screenshot of using the device performance tab](./media/report-remoting-connection/device-performance-tab.png)
 
 ## Device history
 
-When you select on a particular device in one of the reports, you'll see specific information for that device.  
+Select a device in one of the reports to see a daily aggregate bar chart for that device over the last 14 days. Days that have no values are excluded from the chart. Hover over individual days to see values at the bottom of the chart.
+
+> [!NOTE]
+> There may be days when users have signed in but the graph does not display a value. This is caused by the method the graph uses to calculate some edge cases than can result in incorrect data.
 
 ![Screenshot of using the device history](./media/report-remoting-connection/device-history.png)
 
diff --git a/windows-365/enterprise/requirements.md b/windows-365/enterprise/requirements.md
@@ -81,7 +81,7 @@ Windows 365 manages the capacity and availability of underlying Azure resources
 - US Central
 - US East
 - US East 2
-- US West 2
+- US West 2 (Restricted, contact support)
 - US West 3
 - US South central
 - Asia Southeast
diff --git a/windows-365/enterprise/security.md b/windows-365/enterprise/security.md
diff --git a/windows-365/enterprise/whats-new.md b/windows-365/enterprise/whats-new.md
