Merge pull request #6172 from MicrosoftDocs/master

11/18/2021 PM Publish

Author: Taojunshen

memdocs/autopilot/add-devices.md

@@ -161,8 +161,8 @@ You can delete Windows Autopilot devices that aren't enrolled into Intune:
 
 Completely removing a device from your tenant requires you to delete the Intune device, the Azure Active Directory device, and the Windows Autopilot device records. These deletions can all be done from Intune:
 
-1. First, delete the devices from Windows Autopilot at **Devices** > **Windows** > **Windows enrollment** > **Devices** (under **Windows Autopilot Deployment Program**). Choose the devices you want to delete, then choose **Delete**. Windows Autopilot device deletion can take a few minutes to complete.
-2. If the devices are enrolled in Intune, you must [delete them from the Intune All devices blade](../intune/remote-actions/devices-wipe.md#delete-devices-from-the-intune-portal).
+1. First if the devices are enrolled in Intune, you must [delete them from the Intune All devices blade](../intune/remote-actions/devices-wipe.md#delete-devices-from-the-intune-portal).
+2. Once device is not enrolled in Intune, delete the devices from Windows Autopilot at **Devices** > **Windows** > **Windows enrollment** > **Devices** (under **Windows Autopilot Deployment Program**). Choose the devices you want to delete, then choose **Delete**. Windows Autopilot device deletion can take a few minutes to complete.
 3. Delete the devices in Azure Active Directory devices at **Devices** > **Azure AD devices**.
 
 ## Next steps

memdocs/configmgr/comanage/overview.md

@@ -118,9 +118,6 @@ Enabling co-management itself doesn't require that you onboard your site with Az
 
 Upgrade your devices to Windows 10, version 1709 or later. For more information, see [Adopting Windows as a service](../core/understand/configuration-manager-and-windows-as-service.md#key-articles-about-adopting-windows-as-a-service).
 
-> [!IMPORTANT]
-> Windows 10 mobile devices don't support co-management.
-
 ### Permissions and roles
 
 <!--SCCMDocs issue #667-->

memdocs/intune/apps/intune-management-extension.md

@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 07/15/2021
+ms.date: 11/18/2021
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -54,7 +54,7 @@ The Intune management extension supplements the in-box Windows 10 MDM features.
 
 - End users aren't required to sign in to the device to execute PowerShell scripts.
 
-- The Intune management extension agent checks with Intune once every hour and after every reboot for any new scripts or changes. After you assign the policy to the Azure AD groups, the PowerShell script runs, and the run results are reported. Once the script executes, it doesn't execute again unless there's a change in the script or policy. If the script fails, the Intune management extension agent retries the script three times for the next three consecutive Intune management extension agent check-ins.
+- The Intune management extension agent checks after every reboot for any new scripts or changes. After you assign the policy to the Azure AD groups, the PowerShell script runs, and the run results are reported. Once the script executes, it doesn't execute again unless there's a change in the script or policy. If the script fails, the Intune management extension agent retries the script three times for the next three consecutive Intune management extension agent check-ins.
 
 - For shared devices, the PowerShell script will run for every new user that signs in.
 
@@ -225,7 +225,6 @@ To see if the device is auto-enrolled, you can:
     > The **Microsoft Intune Management Extension** is a service that runs on the device, just like any other service listed in the Services app (services.msc). After a device reboots, this service may also restart, and check for any assigned PowerShell scripts with the Intune service. If the **Microsoft Intune Management Extension** service is set to Manual, then the service may not restart after the device reboots.
 
 - Be sure devices are [joined to Azure AD](/azure/active-directory/user-help/user-help-join-device-on-network). Devices that are only joined to your workplace or organization ([registered](/azure/active-directory/user-help/user-help-register-device-on-network) in Azure AD) won't receive the scripts.
-- The Intune management extension client checks once per hour for any changes in the script or policy in Intune.
 - Confirm the Intune management extension is downloaded to `%ProgramFiles(x86)%\Microsoft Intune Management Extension`.
 - Scripts don't run on Surface Hubs or Windows 10 in S mode.
 - Review the logs for any errors. See [Intune management extension logs](#intune-management-extension-logs) (in this article).

memdocs/intune/configuration/group-policy-analytics.md

@@ -8,7 +8,7 @@ author: MandiOhlinger
 
 ms.author: mandia
 manager: dougeby
-ms.date: 09/23/2021
+ms.date: 11/18/2021
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -107,7 +107,7 @@ Be sure the file is less than 4 MB and has a proper unicode encoding. If the exp
 
     - **CSP Mapping**: Shows the OMA-URI path for the on-premises policy. You can use the OMA-URI in a [custom device configuration profile](custom-settings-configure.md). For example, you may see `./Device/Vendor/MSFT/BitLocker/RequireDeviceEnryption`.
 
-## Supported CSPs
+## Supported CSPs and Group Policies
 
 Group Policy analytics can parse the following CSPs:
 
@@ -116,8 +116,9 @@ Group Policy analytics can parse the following CSPs:
 - [BitLocker CSP](/windows/client-management/mdm/bitlocker-csp)
 - [Firewall CSP](/windows/client-management/mdm/firewall-csp)
 - [AppLocker CSP](/windows/client-management/mdm/applocker-csp)
+- [Group Policy Preferences](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn581922(v=ws.11)#group-policy-preferences-1)
 
-If your imported GPO has settings that fall outside of the above supported CSPs, they may be included the **Unknown Settings** column to acknowledge that were identified in your GPO.
+If your imported GPO has settings that aren't in the supported CSPs and Group Policies, then the settings may be listed in the **Unknown Settings** column. This behavior means the settings were identified in your GPO.
 
 ### Known Issues
 

memdocs/intune/fundamentals/licenses.md

@@ -73,7 +73,7 @@ For more information about giving administrators access to Microsoft Endpoint Ma
 A Microsoft Intune license is created for you when you sign up for the Intune free trial. As part of this trial, you'll also have a trial Enterprise Mobility + Security (EMS) subscription. An Enterprise Mobility + Security (EMS) subscription includes both Azure Active Directory Premium and Microsoft Intune.
 
 > [!NOTE]
-> If you are unable to access this portal using the step below, or if you don't have an Intune license, you can sign up now for the [Intune free trial](/mem/intune/fundamentals/free-trial-sign-up). When setting up Intune, you can give an administrators access to Microsoft Endpoint Manager [without them requiring an Intune license](/mem/intune/fundamentals/unlicensed-admins).
+> If you are unable to access this portal using the step below, or if you don't have an Intune license, you can sign up now for the [Intune free trial](./free-trial-sign-up.md). When setting up Intune, you can give an administrators access to Microsoft Endpoint Manager [without them requiring an Intune license](./unlicensed-admins.md).
 
 To confirm your Microsoft Intune license or trial, use the following steps:
 
@@ -97,4 +97,4 @@ If you don't have a license for Azure AD Premium, see [Sign up for Azure Active
 
 For the latest information about product editions, product licensing updates, volume licensing plans, and other information related to your specific use cases, see the [Microsoft Licensing](https://www.microsoft.com/licensing/default) page.  
 
-For information about how user and device licenses affect access to services, as well as how to assign a license to a user, see the [Assign Intune licenses to your user accounts article](licenses-assign.md).
+For information about how user and device licenses affect access to services, as well as how to assign a license to a user, see the [Assign Intune licenses to your user accounts article](licenses-assign.md).

memdocs/intune/fundamentals/surface-management-portal.md

@@ -71,6 +71,6 @@ If a Surface device isn’t working properly, the Microsoft Surface Diagnostic T
 
 ## Next steps
 
-* Harness the power of Surface, Windows, and Office connected together through the cloud. To learn how to plan, deploy, and manage Microsoft Surface and Surface Hub devices, see [Microsoft Surface for IT professionals](https://docs.microsoft.com/surface/).   
+* Harness the power of Surface, Windows, and Office connected together through the cloud. To learn how to plan, deploy, and manage Microsoft Surface and Surface Hub devices, see [Microsoft Surface for IT professionals](/surface/).   
 
-* To get set up in Microsoft Intune quickly, step through the Intune guided scenarios. If you're new to Intune, set up your Intune tenant by following the [free trial quickstart](free-trial-sign-up.md).  
+* To get set up in Microsoft Intune quickly, step through the Intune guided scenarios. If you're new to Intune, set up your Intune tenant by following the [free trial quickstart](free-trial-sign-up.md).

memdocs/intune/includes/intune-notices.md

@@ -83,7 +83,7 @@ If you want users to have access to developer settings moving forward, you will
 
 ### Plan for change: Announcing end of support for the existing Use Locations (network fence) feature in Intune<!-- 9492223  -->
 
-Intune is announcing end of support for the [network fence feature](../protect/use-network-locations.md) for use only in devices enrolled through Android device administrator. Google has reduced support for devices enrolled using device administrator and Intune customers have provided feedback leading to a re-envisioning of the location based fencing to better meet customer needs across multiple Android enrollment options.
+Intune is announcing end of support for the [network fence feature](../protect/create-compliance-policy.md) for use only in devices enrolled through Android device administrator. Google has reduced support for devices enrolled using device administrator and Intune customers have provided feedback leading to a re-envisioning of the location based fencing to better meet customer needs across multiple Android enrollment options.
 
 #### How does this affect me?
 
@@ -222,4 +222,4 @@ Notify your helpdesk, if applicable, of this upcoming change in support. You als
 2. Here’s how you can block devices on versions below Android 6.0:
     - Set enrollment restrictions to prevent devices on Android 5.x from enrolling
     - Utilize a device compliance policy for Android device administrator or Android Enterprise to make devices on Android 5.x non-compliant.
-    - Configure an app protection policy Conditional launch setting with a Min OS version requirement to block users from app access.
+    - Configure an app protection policy Conditional launch setting with a Min OS version requirement to block users from app access.

memdocs/intune/protect/certificate-connector-overview.md

@@ -221,13 +221,6 @@ Updates for the Certificate Connector for Microsoft Intune are released periodic
 
 New updates for the connector can take a week or more to become available for each tenant.
 
-### November 17, 2021
-
-Version **6.2111.4.0**. This update includes:
-
-- Bug fix for high memory usage under certain conditions.
-- Bug fix to allow removal of proxy server from within the configuration tool.
-
 ### October 11, 2021
 
 Version **6.2110.201.0**. This update includes:

windows-365/overview.md

@@ -34,8 +34,8 @@ Windows 365 is a cloud-based service that automatically creates a new type of Wi
 
 Windows 365 is available in two editions:
 
-- **Windows 365 Business** is made specifically for use in smaller companies (up to 300 seats) who want ready-to-use Cloud PCs with simple management options. For more information, see [Getting started with Windows 365 Business and Cloud PCs](/windows-365/business/get-started-windows-365-business).
-- **Windows 365 Enterprise** is for larger companies who want unlimited seats for creating Cloud PCs. It includes options to create custom Cloud PCs based on device images that you create, more management options, and full integration with Microsoft Endpoint Manager. For more information, see [What is Windows 365 Enterprise?](/windows-365/enterprise/overview).
+- **Windows 365 Business** is made specifically for use in smaller companies (up to 300 seats) who want ready-to-use Cloud PCs with simple management options. For more information, see [Getting started with Windows 365 Business and Cloud PCs](./business/get-started-windows-365-business.md).
+- **Windows 365 Enterprise** is for larger companies who want unlimited seats for creating Cloud PCs. It includes options to create custom Cloud PCs based on device images that you create, more management options, and full integration with Microsoft Endpoint Manager. For more information, see [What is Windows 365 Enterprise?](./enterprise/overview.md).
 
 To learn about the differences between the two versions, see [Compare Windows 365 Business and Enterprise](business-enterprise-comparison.md).
 
@@ -52,8 +52,8 @@ Managed Server Providers (MSPs) can manage Cloud PCs in Microsoft 365 Lighthouse
 <!-- ########################## -->
 ## Next steps
 
-[Learn more about Windows 365 Business](/windows-365/business/get-started-windows-365-business).
+[Learn more about Windows 365 Business](./business/get-started-windows-365-business.md).
 
-[Learn more about Windows 365 Enterprise](/windows-365/enterprise/overview).
+[Learn more about Windows 365 Enterprise](./enterprise/overview.md).
 
-[Read the Windows 365 service description](/office365/servicedescriptions/windows-365-service-description/windows-365-service-description).
+[Read the Windows 365 service description](/office365/servicedescriptions/windows-365-service-description/windows-365-service-description).