Merge branch 'MicrosoftDocs:main' into main

Author: Banreet

README.md

@@ -3,48 +3,54 @@
 This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
 For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
 
-# Docs.microsoft.com GitHub repository
+# GitHub repository for Microsoft technical documentation
 
-You've found one of the GitHub repositories that houses the source for content published to [https://docs.microsoft.com](https://docs.microsoft.com/.), home of all technical content for Microsoft's Cloud and Enterprise Division.
+You've found one of the GitHub repositories that houses the source for content published to [Microsoft Docs](https://docs.microsoft.com/), home of all technical content for Microsoft's Cloud and Enterprise Division.
 
 ## Contribute to your documentation
+
 We **want and encourage contributions** from our community (users, customers, partners, friends on other planets) and Microsoft employees to improve your documentation. Here are some tips:
 
-* **Create a GitHub account**: Sign up is free at [GitHub.com](https://www.github.com).
+* **Create a GitHub account**: Sign up for free at [GitHub](https://www.github.com).
+
+* **Use your browser**: There are two options:
 
-* **Use your browser**: There are two options: 
+    **Option 1: Edit directly from Microsoft Docs**
 
-    **Option 1: Edit directly from docs.microsoft.com**  
-    1. Go to the topic, such as [https://docs.microsoft.com/mem/intune/protect/troubleshoot-policies-in-microsoft-intune](mem/intune/protect/troubleshoot-policies-in-microsoft-intune.md). 
+    1. Browse to the [InTune](/mem/intune) article you want to edit.
     2. Select **Edit** (top right). This shows the markdown file in the GitHub repository.
-    3. Select the pencil icon. When you hover over the pencil icon, you'll see the **Edit this file** tooltip. 
-    4. Make your changes, and then **commit** your changes. 
+    3. Select the pencil icon. When you hover over the pencil icon, you'll see the **Edit this file** tooltip.
+    4. Make your changes, and then **commit** your changes.
     5. Create the pull request.
-    
-    **Option 2: Find the article in this repository, and update**  
-    1. Most topics are in `https://github.com/MicrosoftDocs/memdocs/tree/master/memdocs/intune`. In this folder, search for the topic name, such as `troubleshoot-policies-in-microsoft-intune`. 
-    2. Select the link, and click the pencil icon. When you hover over the pencil icon, you'll see the **Edit this file** tooltip. 
-    3. Make your changes, and then **commit** your changes. 
-    4. Create the pull request. 
+
+    **Option 2: Find the article in this repository, and update**
+
+    1. Most topics are in `https://github.com/MicrosoftDocs/memdocs/tree/master/memdocs/intune`. In this folder, search for the topic name, such as `troubleshoot-policies-in-microsoft-intune`.
+    2. Select the link, and click the pencil icon. When you hover over the pencil icon, you'll see the **Edit this file** tooltip.
+    3. Make your changes, and then **commit** your changes.
+    4. Create the pull request.
 
   When you make an update, you may be prompted to sign a license agreement. This is a one-time task. So any future updates by your GitHub username won't need to sign again. 
 
   The value in the `author` metadata (at the top of every topic) lists the GitHub author. In the `troubleshoot-policies-in-microsoft-intune` example, you'll see `MandiOhlinger`. In your pull request, you can also mention (@*authorValue*) the author if you like.
 
-* **MSFT Employees**: After you create a GitHub account, link it to your Microsoft email address. When your account is linked, you don't have to sign a license agreement to make an update. Steps:
+* **MSFT Employees**: After you create a GitHub account, link it to your Microsoft email address. When your account is linked, you don't have to sign a license agreement to make an update. Follow these steps:
 
-  1. On a device with corpnet, go to [GitHub account setup](https://review.docs.microsoft.com/en-us/help/contribute/contribute-get-started-setup-github?branch=master). If you're not on corpnet, this link returns a 404.
+  1. On a device with access to corpnet, go to [GitHub account setup](https://review.docs.microsoft.com/en-us/help/contribute/contribute-get-started-setup-github?branch=master). If you're not on corpnet, this link returns a 404.
 
-    Creating a GitHub account, and linking to your Microsoft account is a one-time thing. When your account is linked, you don't have to sign a license agreement to make an update. 
+     Creating a GitHub account, and linking to your Microsoft account is a one-time thing. When your account is linked, you don't have to sign a license agreement to make an update.
 
-  2. In your browser, go to the article, and select **Edit**. Switch to the private repo (IntuneDocs-pr):  
-    **From**: https://github.com/MicrosoftDocs/memdocs/...  
-    **To**: https://github.com/MicrosoftDocs/memdocs-pr/...
+  2. In your browser, go to the article, and select **Edit**. Switch to the private repo (`IntuneDocs-pr`):
+
+     **From**: `https://github.com/MicrosoftDocs/memdocs/...`
+
+     **To**: `https://github.com/MicrosoftDocs/memdocs-pr/...`
 
-  3. Select the pencil icon, and make your changes. 
+  3. Select the pencil icon, and make your changes.
 
 ## Use markdown to format your topic
-All the articles in this repository use GitHub-flavored markdown. Here's a list of resources to get started:
+
+All the articles in this repository use GitHub-flavored Markdown. Here's a list of resources to get started:
 
 * [Markdown basics](https://help.github.com/articles/basic-writing-and-formatting-syntax/)
 * [Printable markdown cheatsheet](https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf)

memdocs/cloud-native-windows-endpoints.md

@@ -9,7 +9,7 @@ author: scottbreenmsft
 
 ms.author: brenduns
 manager: dougeby
-ms.date: 06/01/2022
+ms.date: 09/07/2022
 ms.topic: conceptual
 ms.service: mem
 ms.subservice: fundamentals
@@ -28,6 +28,7 @@ ms.custom: intune-azure
 ms.collection:
   - M365-identity-device-management
   - highpri
+  - highseo
 ---
 
 # Tutorial: Set up and configure a cloud-native Windows endpoint with Microsoft Endpoint Manager
@@ -560,6 +561,12 @@ Following are some settings available in the settings catalog that might be rele
   - Microsoft App Store
     - Require Private Store Only - **Only Private store is enabled**
 
+      > [!NOTE]
+      > This setting applies to Windows 10. On Windows 11, this setting blocks access to the public Microsoft store. A private store is coming to Windows 11. For more information, go to:
+      > 
+      > - [Update to Endpoint Manager integration with the Microsoft Store on Windows](https://techcommunity.microsoft.com/t5/windows-it-pro-blog/update-to-endpoint-manager-integration-with-the-microsoft-store/ba-p/3585077)
+      > - [FAQ: Supporting Microsoft Store experiences on managed devices](https://techcommunity.microsoft.com/t5/windows-management/faq-supporting-microsoft-store-experiences-on-managed-devices/m-p/3585286)
+
 - **Block Gaming**  
   Organizations might prefer that corporate endpoints can't be used to play games. The Gaming page within the Settings app can be hidden entirely using the following setting.
   For additional information on the settings page visibility, go to the [CSP documentation](/windows/client-management/mdm/policy-csp-settings#settings-pagevisibilitylist) and the ms-settings [URI scheme reference](/windows/uwp/launch-resume/launch-settings-app#ms-settings-uri-scheme-reference).

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/comanage/workloads.md

@@ -15,9 +15,9 @@ ms.collection: highpri
 
 # Co-management workloads
 
-You don't have to switch the workloads, or you can do them individually when you're ready. Configuration Manager continues to manage all other workloads, including those workloads that you don't switch to Intune, and all other features of Configuration Manager that co-management doesn't support.
+You don't have to switch any of the workloads. When you're ready, you can switch them individually, several at once, or all at the same time. However, until you switch the workloads over to Intune, Configuration Manager continues to manage the workloads that you don't switch to Intune, along with all other features of Configuration Manager that co-management doesn't support.
 
-If you switch a workload to Intune, but later change your mind, you can switch it back to Configuration Manager.
+If you switch a workload to Intune, but later change your mind, you can switch it back to Configuration Manager, although there might be an impact. For example, Windows and Office versions will remain at a later version if installed by Intune.
 
 Co-management supports the following workloads:
 
@@ -45,6 +45,9 @@ For more information on the Intune feature, see [Use compliance policies to set
 
 Windows Update for Business policies let you configure deferral policies for Windows 10 or later feature updates or quality updates for Windows 10 or later devices managed directly by Windows Update for Business.
 
+> [!NOTE]
+> To use Windows Autopatch with these devices, this workload needs to be managed by Intune. For more information, see [Prerequisites for Windows Autopatch](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites).
+
 For more information on the Intune feature, see [Manage Windows software updates in Intune](../../intune/protect/windows-update-for-business-configure.md).
 
 ## Resource access policies
@@ -96,6 +99,8 @@ The device configuration workload includes settings that you manage for devices
 
 You can still deploy settings from Configuration Manager to co-managed devices even though Intune is the device configuration authority. This exception might be used to configure settings that your organization requires but aren't yet available in Intune. Specify this exception on a [Configuration Manager configuration baseline](../compliance/deploy-use/create-configuration-baselines.md). Enable the option to **Always apply this baseline even for co-managed clients** when creating the baseline. You can change it later on the **General** tab of the properties of an existing baseline.
 
+To use Windows Autopatch with these devices, this workload needs to be managed by Intune. For more information, see [Prerequisites for Windows Autopatch](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites).
+
 For more information on the Intune feature, see [Create a device profile in Microsoft Intune](../../intune/configuration/device-profile-create.md).
 
 > [!NOTE]
@@ -125,6 +130,9 @@ Updates can be managed using either of the following features:
 - [Use Update Channel and Target Version settings to update Microsoft 365 with Microsoft Intune Administrative Templates](../../intune/configuration/administrative-templates-update-office.md)
 - [Manage Microsoft 365 Apps with Configuration Manager](../sum/deploy-use/manage-office-365-proplus-updates.md).
 
+> [!NOTE]
+> To use Windows Autopatch with these devices, this workload needs to be managed by Intune. For more information, see [Prerequisites for Windows Autopatch](/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites).
+
 For more information on the Intune feature, see [Add Microsoft 365 apps to Windows devices with Microsoft Intune](../../intune/apps/apps-add-office365.md).
 
 ## Client apps

memdocs/configmgr/core/TOC.yml

@@ -285,16 +285,16 @@ items:
     items:
     - name: Technical Preview overview
       href: get-started/technical-preview.md
+    - name: 2208 features
+      href: get-started/2022/technical-preview-2208.md
     - name: 2207 features
       href: get-started/2022/technical-preview-2207.md       
     - name: 2206 features
       href: get-started/2022/technical-preview-2206.md           
     - name: 2205 features
       href: get-started/2022/technical-preview-2205.md       
     - name: 2204 features
-      href: get-started/2022/technical-preview-2204.md       
-    - name: 2203 features
-      href: get-started/2022/technical-preview-2203.md 
+      href: get-started/2022/technical-preview-2204.md        
   - name: Migrate data between hierarchies
     items:
     - name: Migration overview

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/get-started/2020/includes/2011/7774961.md

@@ -11,7 +11,7 @@ ms.date: 11/23/2020
 
 <!--7774961-->
 
-You can now use the [Update-Help](/powershell/module/microsoft.powershell.core/update-help) cmdlet to get the latest information for the Configuration Manager PowerShell module. This content is the same as what's published on docs.microsoft.com for the [ConfigurationManager module](/powershell/module/configurationmanager/).
+You can now use the [Update-Help](/powershell/module/microsoft.powershell.core/update-help) cmdlet to get the latest information for the Configuration Manager PowerShell module. This content is the same as what's published for the [ConfigurationManager module](/powershell/module/configurationmanager/).
 
 The computer on which you run this cmdlet needs internet access, specifically `pshelpprod.blob.core.windows.net`. Then run the following command:
 

memdocs/configmgr/core/get-started/2022/includes/2208/13879970.md

@@ -0,0 +1,19 @@
+---
+author: Banreet
+ms.author: banreetkaur
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 08/29/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_fixedIssues "></a> Issues that are fixed
+
+<!--13879970 -->
+
+If the osdinjection.xml file is directly modified, it isn't correctly preserved updating to a new Configuration Manager version.
+Example modifications include adding support for more binaries or for an alternate content provider (ACP). When this issue occurs, operating system deployment task sequences fail to resolve required dependencies. The smsts.log file contains the following error.
+
+```Failed to load TSCore.dll Code (0x8007007E).```
+

memdocs/configmgr/core/get-started/2022/includes/2208/14917369.md

@@ -0,0 +1,17 @@
+---
+author: Banreet
+ms.author: banreetkaur
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 08/29/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_improvements-to-the-dark-theme"></a> Dark theme is now extended to more dashboards
+
+<!--14917369, 14959592, 14969236-->
+
+In this release we've extended the dark theme to more dashboards, which previously didn't display the dark theme correctly. For example, the O365 Updates Dashboard, PCM Dashboard, and Health Attestation dashboard will now display according to the dark theme, when it's enabled.
+
+Enable this pre-release feature to experience the dark theme. For more information, see [Dark theme for the console.](../../../../../core/servers/manage/admin-console.md)

memdocs/configmgr/core/get-started/2022/includes/2208/8126836.md

@@ -0,0 +1,17 @@
+---
+author: Banreet
+ms.author: banreetkaur
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: include
+ms.date: 08/29/2022
+ms.localizationpriority: medium
+---
+
+## <a name="bkmk_enable-intune"></a> Intune role-based access control (RBAC) for tenant attached devices
+
+<!--8126836-->
+
+You can now use Intune role-based access control (RBAC) when interacting with tenant attached devices from the Microsoft Endpoint Manager admin center. 
+For example, when using Intune as the role-based access control authority, a user with Intune's [Help Desk Operator role](../../../../../../intune/fundamentals/role-based-access-control.md#built-in-roles) doesn't need an assigned security role or additional permissions from Configuration Manager.
+For more information, see [Intune role-based access control for tenant attached clients.](../../../../../cloud-attach/use-intune-rbac.md)