Merge pull request #7652 from MicrosoftDocs/main

Publish 05/19/2022 3:30 PM PT

Author: Angela Fleischmann

.openpublishing.redirection.json

@@ -1154,6 +1154,10 @@
             "redirect_document_id": false
         },
         {
+            "source_path": "windows-365/get-users-started.md",
+            "redirect_url":"/windows-365/end-user-access-cloud-pc",
+            "redirect_document_id": false
+        }, {
             "source_path": "memdocs/intune/remote-actions/remote-assist-mobile-devices.md",
             "redirect_url": "/mem/intune/remote-actions/remote-help",
             "redirect_document_id": false

memdocs/autopilot/enrollment-autopilot.md

@@ -65,7 +65,7 @@ ms.collection:
 
       When creating expressions:
 
-      - To create a group that includes all of your Autopilot devices, enter: `(device.devicePhysicalIDs -any (_ -contains "[ZTDId]"))`.
+      - To create a group that includes all of your Autopilot devices, enter: `(device.devicePhysicalIDs -any (_ -contains "[ZTDID]"))`.
       - Intune's group tag field maps to the `OrderID` attribute on Azure AD devices. To create a group that includes all Autopilot devices with a specific group tag (the Azure AD device `OrderID`), enter: `(device.devicePhysicalIds -any (_ -eq "[OrderID]:179887111881"))`.
       - To create a group that includes all your Autopilot devices with a specific Purchase Order ID, enter: `(device.devicePhysicalIds -any (_ -eq "[PurchaseOrderId]:76222342342"))`
 

memdocs/configmgr/apps/deploy-use/uninstall-applications.md

@@ -80,7 +80,7 @@ Many customers have lots of collections because for every application they need
 
 Starting in version 2107, you can enable an application deployment to support implicit uninstall. If a resource is in a collection, the application installs. Then when you remove the resource from the collection, the application uninstalls.
 
-Starting in version 2111, this behavior also supports [application groups](create-app-groups.md#app-approval).<!-- 10479618 --> When this article refers to an _application_, it also applies to app groups.
+Starting in version 2111, this behavior also supports [application groups](create-app-groups.md).<!-- 10479618 --> When this article refers to an _application_, it also applies to app groups.
 
 > [!NOTE]
 > In version 2111 and later, this behavior applies to deployments to device or user collections.<!--10393847--> In version 2107, this behavior only applies to deployments to device collections.

memdocs/configmgr/core/plan-design/hierarchy/log-files.md

@@ -246,7 +246,6 @@ The following table lists the log files that are on the Configuration Manager si
 |CertMgr.log|Records certificate activities for intrasite communication.|Site system server|  
 |chmgr.log|Records activities of the client health manager.|Site server|  
 |Cidm.log|Records changes to the client settings by the Client Install Data Manager (CIDM).|Site server|  
-|CollectionAADGroupSyncWorker.log | Log file for synchronization of collection membership results to Azure Active Directory. | Site server|
 |colleval.log|Records details about when collections are created, changed, and deleted by the Collection Evaluator.|Site server|  
 |compmon.log|Records the status of component threads monitored for the site server.|Site system server|  
 |compsumm.log|Records Component Status Summarizer tasks.|Site server|  
@@ -387,6 +386,7 @@ The following table lists the log files that contain information related to the
 |Log name|Description|Computer with log file|  
 |--------------|-----------------|----------------------------|  
 |CertMgr.log|Records certificate and proxy account information.|Site server|  
+|CollectionAADGroupSyncWorker.log | Log file for synchronization of collection membership results to Azure Active Directory. |Computer with the service connection point|
 |CollEval.log|Records details about when collections are created, changed, and deleted by the Collection Evaluator.|Primary site and central administration site|  
 |Cloudusersync.log|Records license enablement for users.|Computer with the  service connection point|  
 |Dataldr.log|Records information about the processing of MIF files.|Site server|  

memdocs/configmgr/core/servers/manage/cmpivot.md

@@ -138,6 +138,8 @@ The CMPivot window contains the following elements:
 
    - The available columns vary based upon the entity and the query.  
 
+   - The color saturation of the data in the results table or chart indicates if the data is live or from the last hardware inventory scan stored in the site database.  For example, black is real-time data from an online client whereas grey is cached data.
+
    - Select a column name to sort the results by that property.  
 
    - Right-click on any column name to group the results by the same information in that column, or sort the results.  

memdocs/configmgr/sum/deploy-use/third-party-software-update-catalogs.md

@@ -25,7 +25,7 @@ To make it easier to find custom catalogs, we're providing a list of links as a
 |</br></br>Custom catalog provider|</br></br> URL|
 |--|--|
 |Adobe | Multiple catalogs are available from Adobe. </br>  https://www.adobe.com/devnet-docs/acrobatetk/tools/DesktopDeployment/sccm.html |
-|Centero Software Manager| https://centero.fi/centero-software-manager/ |
+|Centero Software Manager| https://centero.fi/centero-software-manager/product-editions/#csm-for-mecm |
 |Dell| *Partner catalog* available in the **Third-Party Software Update Catalogs** node </br> https://www.dell.com/support/article/sln311138/ </br></br> https://downloads.dell.com/Catalog/DellSDPCatalogPC.cab </br></br>ftp://ftp.dell.com/catalog/DellSDPCatalog.cab |
 |Fujitsu| https://support.ts.fujitsu.com/GFSMS/globalflash/FJSVUMCatalogForSCCM.cab |
 |HP| *Partner catalog* available in the **Third-Party Software Update Catalogs** node <br> https://hpia.hpcloud.hp.com/downloads/sccmcatalog/HpCatalogForSms.latest.cab</br></br> `http://ftp.hp.com/pub/softlib/software/sms_catalog/HpCatalogForSms.latest.cab` |

memdocs/intune/apps/manage-microsoft-office.md

@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 01/12/2022
+ms.date: 05/19/2022
 ms.topic: conceptual
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -111,14 +111,15 @@ This configuration scenario only works with enrolled devices. However, any UEM p
 
 ## General app configuration scenarios
 
-Office for iOS and Android offers administrators the ability to customize the default configuration for several in-app settings.  This capability is offered for both enrolled devices via any UEM provider and for devices that are not enrolled when Office for iOS and Android has an Intune App Protection Policy applied.
+Office for iOS/iPadOS and Android offers administrators the ability to customize the default configuration for several in-app settings using either [iOS/iPadOS](../apps/app-configuration-policies-use-ios.md) or [Android](../apps/app-configuration-policies-use-android.md) app configuration policies.  This capability is offered for both enrolled devices via any UEM provider and for devices that are not enrolled when Office for iOS and Android has an Intune App Protection Policy applied.
 
 > [!NOTE]
 > If an App Protection Policy is targeted to the users, the recommendation is to deploy the general app configuration settings in a **Managed Apps** enrollment model. This ensures the App Configuration Policy is deployed to both enrolled devices and unenrolled devices. 
 
 Office supports the following settings for configuration:
 
 - Manage the creation of Sticky Notes
+- Set add-ins preference
 
 ### Manage the creation of Sticky Notes
 
@@ -128,6 +129,21 @@ By default, Office for iOS and Android enables users to create Sticky Notes. For
 |-------------------------------------------------------------------|-------------|
 |    com.microsoft.office.NotesCreationEnabled    |    **true** (default) enables Sticky Notes creation for the work or school account<br>**false** disables Sticky Notes creation for the work or school account    |
 
+### Set add-ins preference
+
+For iOS/iPadOS devices running Office, you (as the admin) can set whether Office add-ins are enabled. These app settings can be deployed using an [app configuration policy](../apps/app-configuration-policies-use-ios.md) in Intune.
+
+|    Key    |    Value    |
+|-------------------------------------------------------------------|-------------|
+|    com.microsoft.office.OfficeWebAddinDisableAllCatalogs    |    **true** (default) disables the entire add-in platform<br>**false** enables the add-in platform    |
+
+If you need to enable or disable the Office Store portion of the platform for iOS devices, you can use the following key.
+
+|    Key    |    Value    |
+|-------------------------------------------------------------------|-------------|
+|    com.microsoft.office.OfficeWebAddinDisableOMEXCatalog    |    **true** (default) disables only the Office Store portion of the platform<br>**false** enables the Office Store portion of the platform<br>**NOTE:** Sideloaded will continue to work.    |
+
+For more information about adding configuration keys, see [Add app configuration policies for managed iOS/iPadOS devices](../apps/app-configuration-policies-use-ios.md).
 
 ## Data protection app configuration scenarios
 

memdocs/intune/enrollment/device-enrollment.md

@@ -70,8 +70,8 @@ Enrollment options vary by operating system (OS). When selecting a method, choos
     * **No**: Devices aren't associated with a user during enrollment, which is a typical configuration for kiosk, point of sale (POS), or shared-utility devices. 
     * **Optional**: Microsoft Intune makes this setting available for you to configure on your own.   
 * MDM profile removable: Tells you if users can remove the MDM profile from an enrolled device. Options: 
-    * **Yes**: Device users cannot unenroll devices.  
-    * **No**: Device users can unenroll devices. 
+    * **Yes**: Device users can unenroll devices.  
+    * **No**: Device users cannot unenroll devices. 
     * **Configurable via policy** (Android Enterprise): There's a setting in Intune that lets you block factory resets on devices, which prevents users from unenrolling their devices, but it is not configured by default. 
 
 ### iOS/iPadOS enrollment methods 
@@ -85,11 +85,11 @@ You can use the following methods to enroll iOS/iPadOS devices in Intune:
 
 | **Method** | **Reset required** | **User affinity** | **MDM profile removable** | 
 |:---:|:---:|:---:|:---:|
-|BYOD| No| Yes | No | 
-|Device enrollment manager| No |No |No | 
+|BYOD| No| Yes | Yes | 
+|Device enrollment manager| No |No |Yes | 
 |Automated Device Enrollment| Yes | Optional | Optional|
-|Setup Assistant enrollment via USB| Yes | Optional | No| 
-|Direct enrollment via USB| No | No | No|
+|Setup Assistant enrollment via USB| Yes | Optional | Yes| 
+|Direct enrollment via USB| No | No | Yes|
 
 For more information about the iOS/iPadOS enrollment methods supported in Intune, see [Enroll iOS/iPadOS devices](ios-enroll.md).  
 
@@ -102,8 +102,8 @@ You can use the following methods to enroll macOS devices in Intune:
 
 | **Method** |  **Reset required** |  **User affinity** | **MDM profile removable** |
 |:---:|:---:|:---:|:---:|
-|BYOD| No| Yes | No | 
-|Device enrollment manager| No |No |No  | 
+|BYOD| No| Yes | Yes | 
+|Device enrollment manager| No |No |Yes  | 
 |Apple Automated Device Enrollment| Yes | Optional | Optional|
 
 For more information about the macOS enrollment methods supported in Intune, see [Set up enrollment for macOS devices](macos-enroll.md).    
@@ -121,13 +121,13 @@ You can use the following methods to enroll Windows devices in Intune:
 
 | **Method** | **Reset required** | **User affinity** | **MDM profile removable** |
 |:---:|:---:|:---:|:---:|
-|BYOD| No | Yes | No | 
-|Device enrollment manager| No |No |No |
-|Automatic enrollment via MDM | No |Yes |No | 
-|Automatic enrollment via Group Policy|No |Yes |No | 
-|Windows Autopilot |Yes |Yes |No | 
-|Bulk enrollment |No |No |No | 
-|Co-management |No |Yes |No | 
+|BYOD| No | Yes | Yes | 
+|Device enrollment manager| No |No |Yes |
+|Automatic enrollment via MDM | No |Yes |Yes | 
+|Automatic enrollment via Group Policy|No |Yes |Yes | 
+|Windows Autopilot |Yes |Yes |Yes | 
+|Bulk enrollment |No |No |Yes | 
+|Co-management |No |Yes |Yes | 
 
 For more information about the Windows enrollment methods supported in Intune, see [Enrollment methods for Windows devices ](windows-enrollment-methods.md).  
 
@@ -147,8 +147,8 @@ In the table, this data is shown in the Enrollment type column.
 
 | **Enrollment type** | **Enrollment method** | **Reset required** | **User affinity** | **MDM profile removable** | 
 |:---:|:---:|:---:|:---:|:---:|
-|Android Device Admin|User-initiated via Company Portal | No | Yes | No | 
-|Android Enterprise, personal-owned with work profile|User-initiated via Company Portal| No | Yes | No |  
+|Android Device Admin|User-initiated via Company Portal | No | Yes | Yes | 
+|Android Enterprise, personal-owned with work profile|User-initiated via Company Portal| No | Yes | Yes |  
 
 #### Corporate-owned Android devices    
 Intune supports the following device management configurations on corporate-owned devices: 
@@ -173,9 +173,9 @@ In the table, this data is shown in the Enrollment type column. You can use the
 |:---:|:---:|:---:|:---:|:---:|
 |Android (AOSP) user-associated|QR code|Yes|Yes|Configurable via policy|
 |Android (AOSP) userless|QR code|Yes|No|Configurable via policy|  
-|Android Device Admin|DEM-initiated via Company Portal| No | No | No |
-|Android Device Admin|User-initiated via Company Portal with predeclared IMEI or serial number | No | Yes | No | 
-|Android Device Admin with Zebra Mobility Extensions|User or DEM-initiated via Company Portal| No | Yes if user-initiated; no if DEM-initiated | No | 
+|Android Device Admin|DEM-initiated via Company Portal| No | No | Yes |
+|Android Device Admin|User-initiated via Company Portal with predeclared IMEI or serial number | No | Yes |Yes | 
+|Android Device Admin with Zebra Mobility Extensions|User or DEM-initiated via Company Portal| No | Yes if user-initiated; no if DEM-initiated | Yes | 
 |Android Enterprise dedicated|NFC, token, QR code, Google zero-touch| Yes | No | Configurable via policy | 
 |Android Enterprise fully managed|NFC, token, QR code, Google zero-touch| Yes | Yes | Configurable via policy | 
 |Android Enterprise corporate-owned with work profile| NFC, token, QR code, Google zero-touch | Yes | Yes | Configurable via policy | 

windows-365/TOC.yml

@@ -17,8 +17,6 @@ items:
   href: enterprise/index.yml
 - name: End-user experience
   items:  
-  - name: Get users started
-    href: get-users-started.md
   - name: End-user hardware requirements
     href: end-user-hardware-requirements.md
   - name: Access a Cloud PC

windows-365/end-user-access-cloud-pc.md

@@ -2,7 +2,7 @@
 # required metadata
 title: Accessing Cloud PCs
 titleSuffix:
-description: Learn how end-users can access their Cloud PC.
+description: Learn how users can access their Cloud PC.
 keywords:
 author: ErikjeMS  
 ms.author: erikje
@@ -30,29 +30,51 @@ ms.collection: M365-identity-device-management
 
 # Access a Cloud PC
 
-End users can access their Cloud PCs in two different ways:
+Users can access their Cloud PCs in two different ways:
 
 - [windows365.microsoft.com](https://Windows365.microsoft.com)
 - Microsoft Remote Desktop
 
 For information on hardware requirements, see [End user hardware requirements](end-user-hardware-requirements.md).
 
-## Windows365 web site
+## Windows 365 web site
 
-End users can navigate to [windows365.microsoft.com](https://windows365.microsoft.com) to access their Cloud PCs.  
+Users can navigate to [windows365.microsoft.com](https://windows365.microsoft.com) to access their Cloud PCs.  
 
 ### Software requirements
 
-To access their Cloud PC from this website, the end user's device must meet the following requirements:
+To access their Cloud PC from this website, the user's device must meet the following requirements:
 
 - Supported operating systems: Windows, macOS, ChromeOS, Linux
 - A modern browser like Microsoft Edge, Google Chrome, Safari, or Mozilla Firefox (v55.0 and later).
 
-### End-user actions
+### Home page
 
-While on windows365.microsoft.com, end users can perform actions on their Cloud PCs by selecting the gear icon on a Cloud PC card.
+On their Windows 365 home page, users see the Cloud PCs they have access to in the **Your Cloud PCs** section.
+
+![Windows 365 home.](business/media/get-started-windows-365-business/cloud-pc-home.png)
+
+Users can select **Open in browser** to open their Cloud PC.
+
+> [!NOTE]  
+> Mobile devices aren’t currently supported for using a browser to open Cloud PC. The Remote Desktop app is supported.
+
+### User actions
+
+While on windows365.microsoft.com, users can take actions on their Cloud PCs by selecting the gear icon on a Cloud PC card.
+
+![Card menu.](business/media/get-started-windows-365-business/cloud-pc-gear.png)
+
+- **Rename**: Changes the name of the Cloud PC shown to the user on the web site. This action won’t affect any name in Microsoft Endpoint Manager, Azure Active Directory, on the device, or in the Remote Desktop Apps.
+- **Reset**:
+  - Reinstalls Windows (with the option to choose between Windows 11 and Windows 10).
+  - Removes your personal files.
+  - Removes any changes you made to settings.
+  - Removes your apps.
+
+    > [!IMPORTANT]  
+    > Before resetting your Cloud PC, make sure to back up any important files you need to keep to a cloud storage service or external storage. Resetting your Cloud PC will delete these files.
 
-- **Rename**: Changes the name of the Cloud PC shown to the user on the web site. This action won’t affect any name in Microsoft Endpoint Manager, Azure Active Directory, on the device, or in the Remote Desktop Apps.  
 - **Restart**: Restarts the Cloud PC.
 - **Troubleshoot**: Troubleshoot and attempt to resolve any issues that may be preventing a user from connecting to their Cloud PC. The checks run include:
     - Check whether any files or agents required for connectivity are correctly installed.
@@ -63,7 +85,20 @@ While on windows365.microsoft.com, end users can perform actions on their Cloud
   | No issues detected | None of the checks discovered an issue with the Cloud PC. |
   | Issues resolved  | An issue was detected and fixed. |
   | Can’t connect to Cloud PC. We’re working to fix it, try again later. | A Microsoft service required for connectivity is unavailable. Try connecting again later. |
-  | We couldn’t fix issues with your Cloud PC. Contact your administrator. | An issue was detected but it couldn't be fixed. This issue exists because of an ongoing Windows update or another issue. If this error persists for an extended period of time, the Cloud PC may need to be reprovisioned. |
+  | We couldn’t fix issues with your Cloud PC. Contact your administrator. | An issue was detected but it couldn't be fixed. This issue exists because of an ongoing Windows update or another issue. If this error persists for an extended period of time, the Cloud PC may need to be reset. |
+- **System Information**: Displays information about the Cloud PC specification.
+
+### User feedback
+
+Users can provide feedback about their Cloud PC experience by using the feedback icon in the upper right corner.
+
+### Collect user logs
+
+Users can collect logs of their Cloud PC sessions. The logs are collected from the browser and the user can choose the save location.
+
+To turn on log collection, in the client, select the gear icon > **Capture logs**.
+
+   ![Capture logs.](media/get-users-started/settings-logs.png)
 
 ## Remote Desktop