Merge pull request #8387 from MicrosoftDocs/main

OOB publish for 2207 FR catchup

Author: mestew

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
@@ -561,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/hotfix/2207/14959905.md

@@ -0,0 +1,72 @@
+---
+title: Update for Microsoft Endpoint Configuration Manager version 2207, early update ring
+titleSuffix: Configuration Manager
+description: Configuration Manager 2207 early update ring
+ms.date: 09/07/2022
+ms.prod: configuration-manager
+ms.technology: configmgr-core
+ms.topic: reference
+ms.assetid: e415b202-887a-4ad1-ade3-182e9a4ca03a
+author: bhuney
+ms.author: brianhun
+manager: dougeby
+---
+# Update for Microsoft Endpoint Configuration Manager version 2207, early update ring
+
+*Applies to: Configuration Manager (current branch, version 2207)*
+## Summary of KB14955905 
+An update is available to administrators who opted in through a PowerShell script to the early update ring deployment for Microsoft Endpoint Configuration Manager current branch, version 2207. You can access the update in the Updates and Servicing node of the Configuration Manager console.
+
+This update addresses important, late-breaking issues that were resolved after version 2207 became available globally. This article summarizes the most significant changes.
+This update does not apply to sites that downloaded version 2207 on August 26, 2022, or a later date. Therefore, it will not be listed in the Configuration Manager console for those sites.
+
+## Issues that are fixed
+<!-- 15295866 -->
+- Administrators with tenant attached devices are not able to manage software updates when Intune role-based access control (RBAC) is used.
+<!-- 15169634 -->
+- The Configuration Manager console terminates unexpectedly when resuming from sleep or standby.
+<!-- 15208086 -->
+- An Automatic Deployment Rule (ADR) may not be visible after moving it to a folder in the Configuration Manager console.
+
+## Update information for Microsoft Endpoint Configuration Manager, version 2207 early update ring
+This update is available in the Updates and Servicing node of the Configuration Manager console for environments that were installed by using the publicly available early update ring builds of version 2207. These builds were available for download between August 13 and August 26, 2022.
+
+To verify which build is installed, look for a package GUID by adding the Package GUID column to the details pane of the Updates and Servicing node in the console. This update applies to first wave installations of version 2207 from packages that have the following GUIDs:
+
+- 91959D25-96B7-47FA-A36E-E958F2454CE3
+
+### Restart information
+This update does not require a computer restart but will initiate a [site reset](../../core/servers/manage/modify-your-infrastructure.md#bkmk_reset) after installation.
+
+### Update replacement information
+This update does not replace any previously released update.
+
+### Additional installation information
+After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, select Administration -> Site Configuration -> Sites -> Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files. Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
+
+Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
+   ```code
+   select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
+   ```
+If the value 1 is returned, the site is up to date with all the hotfixes applied on its parent primary site.
+
+If the value 0 is returned, the site has not installed all the fixes that are applied to the primary site, and you should use the Recover Secondary Site option to update the secondary site.
+
+## Version information
+The following major components are updated to the versions specified:
+
+|Component |Version |
+|---|---|
+| Configuration Manager console | 5.2207.1048.1700 |
+| Client | 5.0.9088.1010|
+
+## File information
+File information is available in the downloadable [KB14955905_FileList.txt](https://aka.ms/KB14955905_FileList) text file.
+
+## Release history
+- September 7, 2022: Initial hotfix release
+
+## References
+[Updates and servicing for Configuration Manager](../../core/servers/manage/updates.md)
+
+[Summary of changes in 2207](../../hotfix/2207/14840616.md)

memdocs/configmgr/hotfix/TOC.yml

@@ -5,6 +5,8 @@ items:
   items:
   - name: KB 14840616  Summary of changes in 2207
     href: 2207/14840616.md
+  - name: KB 14959905  Early update ring
+    href: 2207/14959905.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

@@ -23,6 +23,9 @@ landingContent:
         links:
           - text: KB 14840616 Summary of changes in 2207
             url: 2207/14840616.md
+          - text: KB 14959905 Early update ring
+            url: 2207/14959905.md
+
   - title: Configuration Manager 2203
     linkLists:
       - linkListType: overview

memdocs/intune/configuration/android-zebra-mx-overview.md

@@ -7,7 +7,7 @@ keywords:
 author: MandiOhlinger
 ms.author: mandia
 manager: dougeby
-ms.date: 04/15/2021
+ms.date: 09/07/2022
 ms.topic: how-to
 ms.service: microsoft-intune
 ms.subservice: configuration
@@ -67,7 +67,7 @@ If Google Play isn't available, download the [Microsoft Intune Company Portal fo
 
 "Sideloading" is when you don't use Google Play to install an app. To sideload the Company Portal app, use StageNow.
 
-The following steps provide an overview. For specific details, see Zebra's documentation. [Enroll in an MDM using StageNow](http://techdocs.zebra.com/stagenow/3-1/Profiles/enrollmdm/) (opens Zebra's web site) may be a good resource.
+The following steps provide an overview. For specific details, see Zebra's documentation. [Enroll in an MDM using StageNow](https://techdocs.zebra.com/stagenow/5-7/Profiles/enrollmdm/) (opens Zebra's web site) may be a good resource.
 
 1. In StageNow, create a profile for **Enroll in an MDM**.
 2. In **Deployment**, choose to download the MDM agent file.
@@ -108,7 +108,7 @@ After completing the first two steps, the Company Portal app is installed on the
 
 ## Step 4: Create a device management profile in StageNow
 
-Use StageNow to create a profile that configures the settings you want to manage on the device. For specific details, see Zebra's documentation. [Profiles](http://techdocs.zebra.com/stagenow/3-2/stagingprofiles/) (opens Zebra's website) may be a good resource.
+Use StageNow to create a profile that configures the settings you want to manage on the device. For specific details, see Zebra's documentation. [Profiles](https://techdocs.zebra.com/stagenow/5-7/stagingprofiles/) (opens Zebra's website) may be a good resource.
 
 When you create the profile in StageNow, on the last step, select **Export to MDM**. This step generates an XML file. Save this file. You need it in a later step.
 

memdocs/intune/fundamentals/whats-new.md

@@ -60,7 +60,7 @@ You can use RSS to be notified when this page is updated. For more information,
 ### Role-based access control
 ### Scripts
 -->
-
+  
 ## Week of September 05, 2022
 
 ### Device management

memdocs/intune/remote-actions/remote-help.md

@@ -373,3 +373,4 @@ Version 4.0.0.0 - GA release
 ## Next steps
 
 [Get support in Microsoft Endpoint Manager admin center](../../get-support.md)
+  

windows-365/enterprise/requirements.md

@@ -71,7 +71,7 @@ You must use [Microsoft Endpoint Manager admin center](https://admin.microsoft.c
 
 ## Role and identity requirements
 
-- Admin role: You must be an [Intune Administrator in Azure AD](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#intune-administrator) or [Windows 365 Administrator](/azure/active-directory/roles/permissions-reference#windows-365-administrator) to provision Cloud PCs.
+- Admin role: You must be an [Intune Administrator in Azure AD](/azure/active-directory/users-groups-roles/directory-assign-admin-roles#intune-administrator) or [Windows 365 Administrator](/azure/active-directory/roles/permissions-reference) to provision Cloud PCs.
 - User identity: Cloud PC users must be configured with [hybrid identities](/azure/active-directory/hybrid/whatis-hybrid-identity) so that they can authenticate with resources both on-premises and in the cloud.
 
 ## Supported Azure regions for Cloud PC provisioning
@@ -87,15 +87,15 @@ Windows 365 manages the capacity and availability of underlying Azure resources
 - Asia Southeast
 - Australia East
 - Canada Central
-- East Asia Regions
-- East Korea Central
+- East Asia
+- Korea Central
 - Europe North
 - Europe West
 - France Central
 - Germany West Central
 - India Central
 - Japan East
-- Norway
+- Norway East
 - Switzerland North
 - UK South
 

windows-365/enterprise/whats-new.md

@@ -65,9 +65,9 @@ You can now review connectivity health checks and errors in the Microsoft Endpoi
 <!-- vvvvvvvvvvvvvvvvvvvvvv -->
 ### Provisioning
 
-#### New supported Azure regions: East Asia Regions, East Korea Central, Norway, Switzerland North<!--37678838-->
+#### New supported Azure regions: East Asia, Korea Central, Norway East, Switzerland North<!--37678838-->
 
-New Azure regions are now supported for Windows 365 Cloud PC provisioning: East Asia Regions, East Korea Central, Norway, and Switzerland North.
+New Azure regions are now supported for Windows 365 Cloud PC provisioning: East Asia, Korea Central, Norway East, and Switzerland North.
 
 For more information about supported Azure regions, see [Supported Azure regions for Cloud PC provisioning](requirements.md#supported-azure-regions-for-cloud-pc-provisioning).