Merge branch 'main' of https://github.com/microsoftdocs/memdocs-pr into eby0

Author: dougeby

memdocs/configmgr/cloud-attach/use-intune-rbac.md

@@ -59,7 +59,7 @@ To use Intune role-based access control for tenant attach rather than Configurat
 
 To enable Intune to manage user permissions for cloud-attached devices, use the following steps:  
 
-1. Open the [Microsoft Endpoint admin center](https://endpoint.microsoft.com) and sign in.
+1. Open the [Microsoft Endpoint admin center](https://endpoint.microsoft.com) and sign in as a user that has the **Roles/Update** permission. For more information about the permission, see [custom role permissions in Intune](../../intune/fundamentals/create-custom-role.md).
 1. Select **Tenant administration** > **Connectors and tokens** > **Microsoft Endpoint Configuration Manager**.
 1. In the banner, select **You can also manage user permissions from Intune. Click here to learn more about this option.**
 1. The **Use Intune RBAC** flyout appears.

memdocs/configmgr/core/clients/deploy/about-client-installation-properties.md

@@ -404,6 +404,10 @@ Example: `CCMCERTISSUERS="CN=Contoso Root CA; OU=Servers; O=Contoso, Ltd; C=US |
 
 For more information about the certificate issuers list and how clients use it during the certificate selection process, see [Planning for PKI client certificate selection](../../plan-design/security/plan-for-certificates.md#pki-client-certificate-selection).
 
+### `CCMCERTNAMECHECK`
+<!--14846212-->
+Starting in version 2207, this property can be used to skip checking the subject name for the certificate.`CCMCERTNAMECHECK=0` skips checking the subject name of the certificate.
+
 ### `CCMCERTSEL`
 
 If the client has more than one certificate for HTTPS communication, this property specifies the criteria for it to select a valid client authentication certificate.

memdocs/configmgr/core/servers/manage/checklist-for-installing-update-2203.md

@@ -350,7 +350,7 @@ For more information, see [Update distribution points with the boot image](../..
 
 ### Update PowerShell help content
 
-To get the latest information for the Configuration Manager PowerShell module, use the [Update-Help](/powershell/module/microsoft.powershell.core/update-help) cmdlet. Run this cmdlet on all computers with the Configuration Manager console. This help content is the same as what's published on docs.microsoft.com for the [ConfigurationManager module](/powershell/module/configurationmanager/).
+To get the latest information for the Configuration Manager PowerShell module, use the [Update-Help](/powershell/module/microsoft.powershell.core/update-help) cmdlet. Run this cmdlet on all computers with the Configuration Manager console. This help content is the same as what's published for the [ConfigurationManager module](/powershell/module/configurationmanager/).
 
 For more information, see [Configuration Manager PowerShell cmdlets: Update help](/powershell/sccm/overview#update-help).
 

memdocs/configmgr/core/servers/manage/checklist-for-installing-update-2207.md

@@ -350,7 +350,7 @@ For more information, see [Update distribution points with the boot image](../..
 
 ### Update PowerShell help content
 
-To get the latest information for the Configuration Manager PowerShell module, use the [Update-Help](/powershell/module/microsoft.powershell.core/update-help) cmdlet. Run this cmdlet on all computers with the Configuration Manager console. This help content is the same as what's published on docs.microsoft.com for the [ConfigurationManager module](/powershell/module/configurationmanager/).
+To get the latest information for the Configuration Manager PowerShell module, use the [Update-Help](/powershell/module/microsoft.powershell.core/update-help) cmdlet. Run this cmdlet on all computers with the Configuration Manager console. This help content is the same as what's published for the [ConfigurationManager module](/powershell/module/configurationmanager/).
 
 For more information, see [Configuration Manager PowerShell cmdlets: Update help](/powershell/sccm/overview#update-help).
 

memdocs/configmgr/hotfix/2207/14840616.md

@@ -0,0 +1,76 @@
+---
+title: Summary of changes in Configuration Manager current branch, version 2207
+titleSuffix: Configuration Manager
+description: Article listing changes in Configuration Manager current branch, version 2207
+ms.date: 08/30/2022
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: reference
+ms.assetid: 9271169f-2ec2-415c-b3f3-a2293218ada5
+author: bhuney
+ms.author: brianhun
+manager: dougeby
+---
+
+# Summary of changes in Configuration Manager current branch, version 2207
+
+*Applies to: Configuration Manager (current branch, version 2207)*
+
+## Summary of KB14840616
+Release version 2207 of Microsoft Endpoint Configuration Manager current branch contains fixes and feature improvements.
+The "Issues that are fixed" list isn't inclusive of all changes. Instead, it highlights changes the product development team believes are most relevant to the broad Configuration Manager customer base. Many of these changes were made in response to customer feedback about product issues and improvements.
+
+##### Notes
+- Version 2207 is available as an in-console update that can be installed at the top-tier site in a hierarchy.
+- For installation information, see [Checklist for installing update 2207 for System Center Configuration Manager](../../core/servers/manage/checklist-for-installing-update-2207.md).
+- For more information about the changes that are included in version 2207, see [What's new in version 2207 of Configuration Manager current branch](../../core/plan-design/changes/whats-new-in-version-2207.md).
+- This globally available release contains all of the fixes summarized in the following article.
+
+   KB [14244456](../../hotfix/2203/14244456.md): Update rollup for Microsoft Endpoint Configuration Manager current branch, version 2203
+
+## Issues that are fixed
+
+<!-- 13923149 -->
+- The default timeout period for hardware inventory reports is reduced from eight weeks to one week. This reduces the length of time that messages from the client may queue if there is a temporary problem communicating with a management point.
+<!-- 2840033 -->
+- The **Format and Partition Disk** task sequence step incorrectly sets the *Type* value of a recovery partition to 0x7 instead of 0x27.
+<!-- 9421122 -->
+- The *IsVirtual* discovery property can incorrectly toggle from a value of 1 to a value of zero when system discovery runs after heartbeat discovery. The value is set back to a 1 after the next heartbeat discovery cycle. 
+<!-- 10898529 -->
+- Computers with updated BIOS may be duplicated in some collections. This happens because of duplicate information stored in the hardware inventory tables.
+<!-- 12554467 -->
+- Clients may generate excessive traffic to the Management point while downloading the WebView2 installation files. This happens after enabling the **Display custom tabs with Microsoft Edge WebView2 runtime** client setting. This update adds randomization to the WebView2 download process to reduce overall management point load.
+<!-- 1261946 -->
+- Discovery data for computers from untrusted domains may be marked as obsolete when they go through the client re-registration process. 
+<!-- 13177588 -->
+- The **New-CMFolder** PowerShell cmdlet allows invalid characters as input for folder names. This prevents later modification of the folder name in the Configuration Manager console.
+<!-- 13464778 -->
+- The **Get-CMObjectSecurityScope** PowerShell cmdlet doesn't work when run against a folder. The following error is logged by the cmdlet.
+   ```text
+   WARNING: Unrecognized object type 'SMS_ObjectContainerNode'. Could not retrieve object security scope.
+   ```
+<!-- 14022391 -->
+- The legend values in antimalware reports are displayed as placeholders such as "_1", "_2", instead of their correct localized names.
+<!-- 14563799 -->
+- Default hardware inventory classes may be disabled when installing a new Configuration Manager client.
+<!-- 14567825 -->
+- The task sequence *Install application* step now captures the correct executable name - smsappinstall.exe - in the smsts.log file.
+<!-- 14716643 -->
+- Logging for the SMS_Service_Connector component is enhanced for easier troubleshooting. 
+<!-- 14918873 -->
+- The data warehouse process (Microsoft.ConfigMgrDataWarehouse.exe) may terminate unexpectedly in large environments when SQL change tracking is enabled.
+<!-- 15037050 -->
+- Heartbeat discovery data records (DDR files) from Windows 365 Cloud PC clients are rejected. The following error is recorded in the ddm.log file on the site server.
+   ```text
+   CDiscoveryPropertyBase::Validate - Max width of property "CloudPCInfo" exceeds maximum 900 characters
+   ```
+<!-- 14916633 -->
+- If the **Upload to Microsoft Endpoint Manager admin center** option is disabled and re-enabled in Cloud Attach properties, the option for **Role-based Access Control** can't be enabled again. 
+<!-- 14727900 -->
+- The **Native client app** value is blank after completing the Azure Services wizard.
+<!-- 14960789 -->
+- The Search tab disappears from the Configuration Manager console after completing a search on a top level node, or after changing options from *Current Node* to *All Subfolders*.
+
+## Hotfixes that are included in this update
+- KB [14480034](../../hotfix/2203/14480034.md): Registration fails for PKI clients after updating to Configuration Manager current branch, version 2203
+- KB [14244456](../../hotfix/2203/14244456.md): Update rollup for Microsoft Endpoint Configuration Manager version 2203

memdocs/configmgr/hotfix/TOC.yml

@@ -3,6 +3,8 @@ items:
   href: index.yml
 - name: Version 2207
   items:
+  - name: KB 14840616  Summary of changes in 2207
+    href: 2207/14840616.md
   - name: KB 14978429  Connected cache update for Microsoft Endpoint Configuration Manager version 2207
     href: 2207/14978429.md
 - name: Version 2203

memdocs/configmgr/hotfix/index.yml

@@ -17,6 +17,12 @@ metadata:
   ms.localizationpriority: high
 
 landingContent:
+  - title: Configuration Manager 2207
+    linkLists:
+      - linkListType: overview
+        links:
+          - text: KB 14840616 Summary of changes in 2207
+            url: 2207/14840616.md
   - title: Configuration Manager 2203
     linkLists:
       - linkListType: overview

memdocs/intune/apps/apps-add-office365.md

@@ -1,7 +1,7 @@
 ---
 # required metadata
 
-title: Add Microsoft 365 apps to Windows 10/11 devices using Microsoft Intune
+title: Add Microsoft 365 Apps to Windows 10/11 devices using Microsoft Intune
 titleSuffix: 
 description: Learn how you can use Microsoft Intune to install Microsoft 365 apps on Windows 10/11 devices.
 keywords:
@@ -32,7 +32,7 @@ ms.collection:
 - highpri
 ---
 
-# Add Microsoft 365 apps to Windows 10/11 devices with Microsoft Intune
+# Add Microsoft 365 Apps to Windows 10/11 devices with Microsoft Intune
 
 Before you can assign, monitor, configure, or protect apps, you must add them to Intune. One of the available [app types](apps-add.md#app-types-in-microsoft-intune) is Microsoft 365 apps for Windows 10 devices. By selecting this app type in Intune, you can assign and install Microsoft 365 apps to devices you manage that run Windows 10. You can also assign and install apps for the Microsoft Project Online desktop client and Microsoft Visio Online Plan 2, if you own licenses for them. The available Microsoft 365 apps are displayed as a single entry in the list of apps in the Intune console within Azure.
 

memdocs/intune/apps/apps-win32-app-management.md

@@ -124,9 +124,6 @@ Set the app availability based on a date and time for a required app by using th
     - **Allow user to snooze the restart notification**: You can choose **Yes** or **No**.
         - **Select the snooze duration (minutes)**: The default value is 240 minutes (4 hours). The snooze value can't be more than the reboot grace period.
 
-    > [!IMPORTANT]
-    > Restart time is not registered when the user doesn't have admin privileges to the device.
-
 11. Select **Review + save**.
 
 ## Notifications for Win32 apps 

memdocs/intune/apps/configure-microsoft-launcher.md

@@ -77,7 +77,7 @@ The following table lists the Microsoft Launcher available configuration keys, v
 |    Feed Enable User Change Allowed    |    Boolean    |    True    |     Allows you to specify if the **Feed Enable** setting can be changed by the end user.<ul><li>If set to **True**, the feed will only be enforced for the initial deployment. Subsequently, the policy will not be enforced to respect any changes the user may have made.</li><li>If set to **False**, the feed will be enforced on every sync.</li></ul><br>JSON key name:`com.microsoft.launcher.Feed.Enabled.UserChangeAllowed`    |
 |    Search Bar Placement   |    String    |    Bottom    |  Allows you to specify the **placement of search bar** on the home screen. <ul><li>If set to **Bottom**, the search bar will be located on the bottom of the home screen.</li><li>If set to **Top**, the search bar will be located on the top of the home screen.</li><li>If set to **Hidden**, the search bar will be removed from the home screen.</li></ul><br>JSON key name:<br>`com.microsoft.launcher.Search.SearchBar.Placement`    |
 |    Search Bar Placement User Change Allowed   |    Boolean    |    True    |  Allows you to specify if the **Search Bar Placement** setting can be changed by the end user. <ul><li>If set to **True**, the search bar placement will only be enforced for the initial deployment. Subsequently, the policy will not be enforced to respect any changes the user may have made.</li><li>If set to **False**, the placement of search bar will be enforced on every sync.</li></ul><br>JSON key name:<br>`com.microsoft.launcher.Search.SearchBar.Placement.UserChangeAllowed`<p>**NOTE:** For Microsoft Launcher v 6.2 and later, this setting will no longer be enforced. Therefore, setting this value to `True` will have no effect. Your end users will not be able to customize the location of the search bar placement on their device.    |
-|    Dock Mode  |    String    |    Show    | Allows you to enable the dock on the device when the user swipes to the right on the home screen.<ul><li>If set to **Show**, the dock will be enabled.</li><li>If set to **Hidden**, the dock will hide from the home screen, but the user can display it when it is needed.</li><li>If set to **Disabled**, the dock will be disabled.</li></ul><br>JSON key name:<br>`com.microsoft.launcher.Dock.Mode`    |
+|    Dock Mode  |    String    |    Show    | Allows you to enable the dock on the device when the user swipes up from the bottom on the home screen.<ul><li>If set to **Show**, the dock will be enabled.</li><li>If set to **Hidden**, the dock will hide from the home screen, but the user can display it when it is needed.</li><li>If set to **Disabled**, the dock will be disabled.</li></ul><br>JSON key name:<br>`com.microsoft.launcher.Dock.Mode`    |
 |   Dock Mode User Change Allowed   |    String    |    True    |  Allows you to specify if the Dock Mode setting can be changed by the end user.<ul><li>If set to **True**, the dock mode setting will only be enforced for the initial deployment. Subsequently, the policy will not be enforced to respect any changes the user may have made.</li><li>If set to **False**, the dock mode setting will be enforced on every sync.</li></ul><br>JSON key name:<br>`com.microsoft.launcher.Dock.Mode.UserChangeAllowed`    |
 
 ## Enter JSON Data