Merge pull request #8029 from MicrosoftDocs/main

jborsecnik · web-flow · commit 3166aa0b6954 · 2022-07-18T10:42:30.000-07:00
Monday 10:30 merge main to live
diff --git a/memdocs/autopilot/known-issues.md b/memdocs/autopilot/known-issues.md
@@ -30,7 +30,7 @@ This article describes known issues that can often be resolved by configuration
 
 ### Autopilot profile not being applied when assigned 
 
-In Windows 10 April (KB5011831) release, there is an issue where the Autopilot profile may fail to apply to the device. As a result, any settings made in the profile may not be configured for the user such as device renaming. To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device.
+In Windows 10 April and some May update releases, there is an issue where the Autopilot profile may fail to apply to the device and the hardware hash may not be harvested. As a result, any settings made in the profile may not be configured for the user such as device renaming. To resolve this issue, the May (KB5015020) cumulative update needs to be applied to the device.
 
 ### DefaultuserX profile not deleted
 
diff --git a/memdocs/configmgr/develop/compliance/how-to-assign-configuration-baselines.md b/memdocs/configmgr/develop/compliance/how-to-assign-configuration-baselines.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how to assign a configuration baseline to a collection by creating an assignment instance, populated with a minimum set of required values, and saving.
 
 
 ---
diff --git a/memdocs/configmgr/develop/core/servers/configure/how-to-list-the-maintenance-windows-and-properties-for-a-specific-collection.md b/memdocs/configmgr/develop/core/servers/configure/how-to-list-the-maintenance-windows-and-properties-for-a-specific-collection.md
@@ -11,7 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
-
+description: Learn how to list the maintenance windows and properties for a specific collection with provided examples and links.
 
 ---
 # How to List the Maintenance Windows and Properties for a Specific Collection
@@ -167,7 +167,7 @@ public void ListMaintenanceWindowsAndPropertiesForASpecificCollection(WqlConnect
 ## .NET Framework Security  
  For more information about securing Configuration Manager applications, see [Configuration Manager role-based administration](../../../../develop/core/servers/configure/role-based-administration.md).  
 
-## See Also  
+## See also  
  [About maintenance windows](about-maintenance-windows.md)
  [Software distribution overview](software-distribution-overview.md)
  [About deployments](about-software-distribution-deployments.md)
diff --git a/memdocs/configmgr/develop/core/servers/console/how-to-create-a-configuration-manager-console-node.md b/memdocs/configmgr/develop/core/servers/console/how-to-create-a-configuration-manager-console-node.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how to create and start a configuration manager console node that displays available collections.
 
 
 ---
diff --git a/memdocs/configmgr/develop/core/understand/how-to-create-a-configuration-manager-object-by-using-managed-code.md b/memdocs/configmgr/develop/core/understand/how-to-create-a-configuration-manager-object-by-using-managed-code.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how to create a configuration manager object by using managed code, with included examples and links.
 
 
 ---
diff --git a/memdocs/configmgr/develop/core/understand/how-to-modify-a-configuration-manager-object-by-using-managed-code.md b/memdocs/configmgr/develop/core/understand/how-to-modify-a-configuration-manager-object-by-using-managed-code.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how to modify a configuration manager object by using managed code with the provided examples and links.
 
 
 ---
diff --git a/memdocs/configmgr/develop/osd/how-to-set-operating-system-deployment-branding-information.md b/memdocs/configmgr/develop/osd/how-to-set-operating-system-deployment-branding-information.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how to set operating system deployment branding information in the configuration manager by changing the property of the client agent component section.
 
 
 ---
diff --git a/memdocs/configmgr/develop/osd/how-to-set-the-pxe-service-point-response-to-all-network-interfaces.md b/memdocs/configmgr/develop/osd/how-to-set-the-pxe-service-point-response-to-all-network-interfaces.md
@@ -11,7 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
-
+description: Learn how to set the PXE service point response to all network interfaces by setting the BindPolicy embedded property.
 
 ---
 # How to Set the PXE Service Point Response to All Network Interfaces
diff --git a/memdocs/configmgr/develop/reference/core/clients/sdk/ccm_requestedapppolicyactivation-client-wmi-class.md b/memdocs/configmgr/develop/reference/core/clients/sdk/ccm_requestedapppolicyactivation-client-wmi-class.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how the CCM_RequestedAppPolicy Activation class represents a requested application policy activation. 
 
 
 ---
diff --git a/memdocs/configmgr/develop/reference/core/clients/sdk/ccm_softwareupdate-client-wmi-class.md b/memdocs/configmgr/develop/reference/core/clients/sdk/ccm_softwareupdate-client-wmi-class.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how enumerating the CCM_SoftwareUpdate Client WMI Class gives all the updates that are applicable and need to be installed.
 
 
 ---
diff --git a/memdocs/configmgr/develop/reference/core/clients/sdk/determineifrebootpending-method-in-class-ccm_clientutilities.md b/memdocs/configmgr/develop/reference/core/clients/sdk/determineifrebootpending-method-in-class-ccm_clientutilities.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how DetermineIfRebootPending is simplified from Managed Object Format code and defines the method.
 ---
 
 # DetermineIfRebootPending Method in Class CCM_ClientUtilities
diff --git a/memdocs/configmgr/develop/reference/core/servers/configure/addsitesystem-method-in-class-sms-defaultboundarygroup.md b/memdocs/configmgr/develop/reference/core/servers/configure/addsitesystem-method-in-class-sms-defaultboundarygroup.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how the AddSiteSystem class method adds one or more site system servers to a default boundary group.
 
 
 ---
diff --git a/memdocs/configmgr/develop/reference/core/servers/configure/ddraddstringarray.md b/memdocs/configmgr/develop/reference/core/servers/configure/ddraddstringarray.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how the DDRAddStringArray function, in Configuration Manager, adds a string array property to the data discovery record.
 
 
 ---
diff --git a/memdocs/configmgr/develop/reference/osd/adddistributionpoints-method-in-class-sms_tasksequencepackage.md b/memdocs/configmgr/develop/reference/osd/adddistributionpoints-method-in-class-sms_tasksequencepackage.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how the AddDistributionPoints Method adds the distribution points for the task sequence package.
 
 
 ---
diff --git a/memdocs/configmgr/develop/reference/osd/exportxml-method-in-class-sms_tasksequence.md b/memdocs/configmgr/develop/reference/osd/exportxml-method-in-class-sms_tasksequence.md
@@ -11,6 +11,7 @@ ms.author: aaroncz
 manager: dougeby
 ms.localizationpriority: null
 ms.collection: openauth
+description: Learn how the ExportXml Method exports task sequence XML in a format that is suitable to use on another site.
 
 
 ---
diff --git a/memdocs/intune/apps/apps-ae-system.md b/memdocs/intune/apps/apps-ae-system.md
@@ -58,6 +58,8 @@ The **Overview** blade of the app you've created is displayed.
 
 > [!NOTE]
 > You will need to work with the OEM of your device to find the package name of the app you would like to enable/disable.
+>
+> You cannot create an Android Enterprise system app when there is the same app in Managed Google Play in Intune.
 
 The app you've created is displayed in the apps list, where you can assign it to the groups that you select. 
 
diff --git a/memdocs/intune/apps/apps-deploy.md b/memdocs/intune/apps/apps-deploy.md
@@ -38,7 +38,7 @@ ms.collection:
 After you've [added an app](apps-add.md) to Microsoft Intune, you can assign the app to users and devices. It is important to note that you can deploy an app to a device whether or not the device is managed by Intune.
 
 > [!NOTE]
-> The **Available for enrolled devices** deployment intent is only supported for **device groups** when targeting Android Enterprise fully managed devices (COBO) and Android Enterprise corporate-owned personally-enabled (COPE) devices.
+> The **Available for enrolled devices** deployment intent is supported for **user groups** and **device groups** when targeting Android Enterprise fully managed devices (COBO) and Android Enterprise corporate-owned personally-enabled (COPE) devices.
 
 The following table lists the various options for *assigning* apps to users and devices:
 
diff --git a/memdocs/intune/apps/apps-supported-intune-apps.md b/memdocs/intune/apps/apps-supported-intune-apps.md
@@ -62,10 +62,10 @@ The below apps support the Core Intune App Protection Policy settings and are al
 |Microsoft Excel|[Android](https://play.google.com/store/apps/details?id=com.microsoft.office.excel)|✔|No settings|✔|N/A|✖|✖|✔|
 |Microsoft Excel|[iOS](https://apps.apple.com/us/app/microsoft-excel/id586683407)|✔|No settings|✔|N/A|✖|✖|✔|
 |Microsoft Launcher|[Android](https://play.google.com/store/apps/details?id=com.microsoft.launcher)|✔|✔ see [Launcher app config](configure-microsoft-launcher.md)|✖|N/A|✖|✖|N/A|
-|Microsoft Lens - PDF Scanner|[Android](https://play.google.com/store/apps/details?id=com.microsoft.office.officelens)|✔|No settings|✖|N/A|✖|✖|N/A|
-|Microsoft Lens - PDF Scanner|[iOS](https://apps.apple.com/us/app/microsoft-lens-pdf-scanner/id975925059)|✔|No settings|✖|N/A|✖|✖|N/A|
+|Microsoft Lens - PDF Scanner|[Android](https://play.google.com/store/apps/details?id=com.microsoft.office.officelens)|✖|No settings|✖|N/A|✖|✖|N/A|
+|Microsoft Lens - PDF Scanner|[iOS](https://apps.apple.com/us/app/microsoft-lens-pdf-scanner/id975925059)|✖|No settings|✖|N/A|✖|✖|N/A|
 |Microsoft Lists|[iOS](https://apps.apple.com/us/app/microsoft-lists/id1530637363)|✔|No settings|✔|N/A|N/A|✔|✔|
-|Microsoft Lists|[Android](https://play.google.com/store/apps/details?id=com.microsoft.lists.public&gl=US)|✔|No settings|✖|N/A|N/A|✖|✖|
+|Microsoft Lists|[Android](https://play.google.com/store/apps/details?id=com.microsoft.lists.public&gl=US)|✖|No settings|✖|N/A|N/A|✖|✖|
 |Microsoft Office|[Android](https://play.google.com/store/apps/details?id=com.microsoft.office.officehubrow)|✔|✔ see [Office app config](manage-microsoft-office.md)|✔|N/A|✖|✖|✔|
 |Microsoft Office|[iOS](https://apps.apple.com/app/microsoft-office/id541164041)|✔|✔ see [Office app config](manage-microsoft-office.md)|✔|N/A|✖|✖|✔|
 |Microsoft OneDrive|[Android](https://play.google.com/store/apps/details?id=com.microsoft.skydrive)|✔|No settings|✔|N/A|✖|✔|N/A|
diff --git a/memdocs/intune/apps/store-apps-company-portal-autopilot.md b/memdocs/intune/apps/store-apps-company-portal-autopilot.md
@@ -1,9 +1,9 @@
 ---
 # required metadata
 
-title: Add and assign the Windows 10 Company Portal app for Autopilot provisioned devices
+title: Add and assign the Windows 10 Company Portal app for Intune managed devices
 titleSuffix: Microsoft Intune
-description: Add and assign the Windows 10 Company Portal app to Intune for Autopilot provisioned devices.
+description: Add and assign the Windows 10 Company Portal app to Intune managed devices.
 keywords:
 author: Erikre
 ms.author: erikre
@@ -32,15 +32,15 @@ ms.collection:
 - highpri
 ---
 
-# Add and assign the Windows 10 Company Portal app for Autopilot provisioned devices
+# Add and assign the Windows 10 Company Portal app for Intune managed devices
 
-To manage devices and install apps, your users can use the Company Portal app. You can assign the Windows 10 Company Portal app directly from Intune. 
+To manage devices and install apps, your users can optionally use the Company Portal app. You can assign the Windows 10 Company Portal app directly from Intune. 
 
 ## Prerequisites
 
-For Windows 10 Autopilot provisioned devices, it is recommended that you associate your Microsoft Store for Business account with Intune. For more information, see [How to manage volume purchased apps from the Microsoft Store for Business with Microsoft Intune](windows-store-for-business.md).
+You can choose to install the **Company Portal (Offline)** app using the steps below. The Company Portal app will be installed in device context when assigned to the Autopilot group and will be installed on the device before the user logs in. Offline apps are updated using Intune, whereas online apps are updated by the store. Use offline apps when you need to install and maintain a specific app version.
 
-You can choose to install the **Company Portal (Offline)** app using the steps below. The Company Portal app will be installed in device context when assigned to the Autopilot group and will be installed on the device before the user logs in. Offline apps are updated using Intune, whereas online apps are updated by the store. When synced from the Microsoft Store for Business and deployed as a Microsoft Store app, the Company Portal (Offline) updates will occur automatically to any required assignments. If you need to maintain a specific version of the Company Portal app, refer to [Manually add the Windows 10 company portal app](./store-apps-company-portal-app.md) for details.
+For Windows 10 Autopilot provisioned devices, it is recommended that you associate your Microsoft Store for Business account with Intune. For more information, see [How to manage volume purchased apps from the Microsoft Store for Business with Microsoft Intune](windows-store-for-business.md).
 
 ## Configure the store settings to show the offline app
 
@@ -71,7 +71,7 @@ You can choose to install the **Company Portal (Offline)** app using the steps b
 1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) with your admin account.
 2. Select **Apps** > **Windows**.
 3. From the list of Windows apps, select **Company Portal (Offline)**.
-4. To [Assign](apps-deploy.md) the Company Portal app as a required app to your selected autopilot device groups, select **Properties** > **Edit** (next to **Assignments**) > **Add Group** (below **Required**) and then select a device group to assign the app. 
+4. To [Assign](apps-deploy.md) the Company Portal app as a required app to your selected device groups, select **Properties** > **Edit** (next to **Assignments**) > **Add Group** (below **Required**) and then select a device group to assign the app. 
 5. As this is an *Offline* app, be sure to change the **License type** to **Device licensing** before selecting **Review + save**. To set the **License type**, click **User** on the row of the group you added (under the **License type** column). 
 6. Select **Device licensing** > **OK** > **Review + save**.
 
diff --git a/memdocs/intune/configuration/device-restrictions-android-for-work.md b/memdocs/intune/configuration/device-restrictions-android-for-work.md
@@ -2,12 +2,12 @@
 # required metadata
 
 title: Android Enterprise device settings in Microsoft Intune
-description: On Android Enterprise or Android for Work devices, restrict settings on the device, including copy and paste, show notifications, app permissions, data sharing, password length, sign in failures, use fingerprint to unlock, reuse passwords, and enable bluetooth sharing of work contacts. Configure devices as a dedicated device kiosk to run one app, or multiple apps.
+description: On Android Enterprise or Android for Work devices, restrict settings on the device. Restrict copy and paste, notifications, app permissions, data sharing, password length, sign in failures, use fingerprint to unlock, reuse passwords, and enable bluetooth sharing of work contacts. Configure devices as a dedicated device kiosk to run one app, or multiple apps.
 keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 07/12/2022
+ms.date: 07/18/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -207,7 +207,7 @@ Use these settings to configure a kiosk-style experience on your dedicated devic
 **Enrollment profile type**: Select an enrollment profile type to start configuring Microsoft Launcher or the Microsoft Managed Home Screen on your devices. Your options:
 
 - **Not configured**: Intune doesn't change or update this setting. By default, users might see the device's default home screen experience.
-- **Dedicated device**: Configure a kiosk-style experience on your dedicated devices. Before you configure these settings, be sure to [add](../apps/apps-add-android-for-work.md) and [assign](../apps/apps-deploy.md) the apps you want on the devices.
+- **Dedicated device**: Configure a kiosk-style experience on your dedicated devices. Before you configure these settings, be sure to [add](../apps/apps-add-android-for-work.md), and [assign](../apps/apps-deploy.md) the apps you want on the devices.
 
   - **Kiosk mode**: Choose if the device runs one app or runs multiple apps. Your options:
 
@@ -320,9 +320,11 @@ Use these settings to configure a kiosk-style experience on your dedicated devic
 
         - **Wi-Fi allow list**: Create a list of valid wireless network names, also known as the service set identifier (SSID). Managed Home Screen users can only connect to the SSIDs you enter.
 
+          Wi-Fi SSIDs are case sensitive. If the SSID is valid but the capitalization you enter doesn't match the network name, then the network isn't shown.
+
           When left blank, Intune doesn't change or update this setting. By default, all available Wi-Fi networks are allowed.
 
-          **Import** a .csv file that includes a list of valid SSIDs.
+          **Import** a .csv file that includes a list of valid SSIDs. 
 
           **Export** your current list to a .csv file.
 
@@ -653,7 +655,7 @@ You can configure the following settings:
 
 - **Short support message**: When users try to change a setting that's managed by the organization, a short message is shown. Use these settings to customize this message. You can enter a different message for different languages. By default, this message is in **English (United States)**.  
 
-  - **All, except when specified**: This message is the Intune default message, and is shown for all languages. If you don't select a locale and don't enter a custom message, then this text is automatically shown, and is automatically translated to the device's default language.
+  - **All, except when specified**: This message is the Intune default message, and is shown for all languages. If you don't select a locale and don't enter a custom message, then this text is automatically shown. This text is also automatically translated to the device's default language.
 
     You can change this message. Any changes aren't translated. If you delete all the text in this message and leave this setting blank, then the following original short Intune default message is used and is translated:
 
diff --git a/memdocs/intune/configuration/device-restrictions-ios.md b/memdocs/intune/configuration/device-restrictions-ios.md
@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 06/23/2022
+ms.date: 07/18/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -212,7 +212,7 @@ You can also **Import** a CSV file with the list of app names and their bundle I
   - iOS 4.0 and newer
   - iPadOS 13.0 and newer
 
-- **Block Find My iPhone**: **Yes** prevents this feature in the Find My app. When set to **Not configured** (default), Intune doesn't change or update this setting. By default, the OS might allow using this Find My app feature to get the approximate location of the device.
+- **Block Find My iPhone**: In the Find My app, **Yes** disables/hides the **Devices** tab. When set to **Not configured** (default), Intune doesn't change or update this setting. By default, the OS might allow using the **Devices** tab in the Find My app to get the approximate location of the device.
 
   This feature applies to:  
   - iOS 13.0 and newer
diff --git a/memdocs/intune/enrollment/enrollment-restrictions-set.md b/memdocs/intune/enrollment/enrollment-restrictions-set.md
@@ -94,12 +94,17 @@ If you block Android Enterprise work profile enrollment on personal devices, onl
 
 #### Blocking personal iOS/iPadOS devices
 By default, Intune classifies iOS/iPadOS devices as personally-owned. To be classified as corporate-owned, an iOS/iPadOS device must fulfill one of the following conditions:
-- [Registered with a serial number](corporate-identifiers-add.md).
-- Enrolled by using Automated Device Enrollment (formerly Device Enrollment Program)
+- [Registered with a serial number or IMEI](corporate-identifiers-add.md).
+- Enrolled by using Automated Device Enrollment (formerly Device Enrollment Program).
 
 > [!NOTE]
 > An iOS User Enrollment profile overrides an enrollment restriction policy. For more information, see [Set up iOS/iPadOS and iPadOS User Enrollment (preview)](ios-user-enrollment.md).  
 
+#### Blocking personal macOS devices
+By default, Intune classifies macOS devices as personally-owned. To be classified as corporate-owned, a macOS device must fulfill one of the following conditions:
+- [Registered with a serial number](corporate-identifiers-add.md).
+- Enrolled by using Automated Device Enrollment (formerly Device Enrollment Program).
+
 #### Blocking personal Windows devices
 If you block personally owned Windows devices from enrollment, Intune checks to make sure that each new Windows enrollment request has been authorized for corporate enrollment. Unauthorized enrollments are blocked.  
 
diff --git a/memdocs/intune/enrollment/ios-ipados-device-compliance-security-configurations.md b/memdocs/intune/enrollment/ios-ipados-device-compliance-security-configurations.md
diff --git a/windows-365/enterprise/in-development.md b/windows-365/enterprise/in-development.md
