Merge pull request #16312 from MicrosoftDocs/main

Publish main to live, Wednesday 5:00 PM IST, 10/09
MicrosoftDocs · Oct 9, 2024 · 235de17 · 235de17
2 parents 73d90b5 + 52ebc49
commit 235de17
Show file tree

Hide file tree

Showing 4 changed files with 32 additions and 23 deletions.
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -1,5 +1,15 @@
 {
   "redirections": [
+    {
+      "source_path": "memdocs/intune/enrollment/chrome-enterprise-device-details.md",
+      "redirect_url": "/mem/intune/remote-actions/chrome-enterprise-device-details",
+      "redirect_document_id": true
+    },    
+    {
+      "source_path": "memdocs/intune/enrollment/chrome-enterprise-remote-actions.md",
+      "redirect_url": "/mem/intune/remote-actions/chrome-enterprise-remote-actions",
+      "redirect_document_id": true
+    },
     {
       "source_path": "memdocs/intune/user-help/you-need-to-resolve-a-threat-found-by-zips-android.md",
       "redirect_url": "/mem/intune/user-help/set-up-mobile-threat-defense",

diff --git a/...lment/chrome-enterprise-device-details.md → ...tions/chrome-enterprise-device-details.md b/...lment/chrome-enterprise-device-details.md → ...tions/chrome-enterprise-device-details.md
@@ -40,17 +40,17 @@ You can view synced devices in the **Devices** > **All devices** list and throug
 
 ## Prerequisites  
 
-To view ChromeOS devices and device details, you must be assigned a role that has read permission for *Chrome Enterprise*.  
+To view ChromeOS devices and device details, you must be assigned a role with *read* permission for *Chrome Enterprise*.  
 
 Devices must be enrolled before you can see them in the admin center. Enrollment for ChromeOS devices is done in the Google Admin center. You can create the connection before or after you enroll devices. For more information, see [Enroll ChromeOS devices](https://support.google.com/chrome/a/answer/1360534) (opens Chrome Enterprise and Education Help).
 
 ## View ChromeOS devices  
-Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and go to **Devices** > **All devices** to view an aggregated list of all devices in Intune, including those running ChromeOS.  The following information is shown for ChromeOS devices: 
+Sign in to the [Microsoft Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431) and go to **Devices** > **All devices** to view an aggregated list of all devices in Intune, including those running ChromeOS. The following information is shown for ChromeOS devices: 
 
 * **Device name**: Device names for ChromeOS devices appear as `Chrome- {serialNumber}`. 
 * **Managed by**: ChromeOS devices are managed by **Intune**. 
 * **Ownership**: ChromeOS devices are always marked as **Corporate**.  
-* **Compliance**: Compliance policies are not supported with ChromeOS devices in Intune so they'll appear in this column as **Not evaluated**.  
+* **Compliance**: Compliance policies aren't supported with ChromeOS devices in Intune, so they appear in this column as **Not evaluated**.  
 
 Select **Filter** to filter the device list by platform. You can also go to the navigation menu and select **ChromeOS** for an exclusive view of ChromeOS devices.    
 
@@ -78,15 +78,15 @@ You can create dynamic device groups based on a [Google Admin organizational uni
    1. For **Membership type**, select **Dynamic Device**.
    2. Select **Add a dynamic query**.   
    3. For **Property**, select **enrollmentProfileName**. Select the **Operator**, depending on how you want the rule to work. For **Value**, enter the name of a Google Admin organizational unit.  
-2. Create a scope tag for an Intune RBAC role. The scope tag determines the level of access for the Intune role.  When you get to **Assignments**, include the dynamic device group you previously created. For more information, see [Use role-based access (RBAC) and scope tags for distributed IT](../fundamentals/scope-tags.md#to-create-a-scope-tag).  
+2. Create a scope tag for an Intune RBAC role. The scope tag determines the level of access for the Intune role. When you get to **Assignments**, include the dynamic device group you previously created. For more information, see [Use role-based access (RBAC) and scope tags for distributed IT](../fundamentals/scope-tags.md#to-create-a-scope-tag).  
 
-After you save the scope tag, it's applied to every device that's part of the dynamic device group. The organizational unit's information syncs with the *enrollmentProfileName* device object property in Microsoft Entra ID, using the full path format that's shown in [System info](#system-info). 
+   After you save the scope tag, it applies to every device that's part of the dynamic device group. The organizational unit's information syncs with the *enrollmentProfileName* device object property in Microsoft Entra ID, using the full path format shown in [System info](#system-info). 
 
-For example: `/OU Level1/OU Level2`. 
+   For example: `/OU Level1/OU Level2`. 
 
-The maximum length of the string is 255 characters. Intune truncates the first part of the string if it exceeds the max number of characters. 
+   The maximum length of the string is 255 characters. Intune truncates the first part of the string if it exceeds the max number of characters. 
 
-For example:  `/OU Level1/OU Level2/.../OU Level18` becomes `evel1/OU Level2/.../OU Level18`.  
+   For example:  `/OU Level1/OU Level2/.../OU Level18` becomes `evel1/OU Level2/.../OU Level18`.  
 
 
 ## Next steps  

diff --git a/...lment/chrome-enterprise-remote-actions.md → ...tions/chrome-enterprise-remote-actions.md b/...lment/chrome-enterprise-remote-actions.md → ...tions/chrome-enterprise-remote-actions.md
@@ -37,20 +37,20 @@ Remotely run device actions on ChromeOS devices synced with Microsoft Intune. Th
 * Wipe  
 * Restart (only for kiosk devices and managed guest session devices)  
 
-To access remote actions, select a device in your **Chrome Enterprise (preview)** list or go to **Devices** > **All devices** and select a device. This article describes the remote actions, and provides information about required permissions and known issues.  
+To access remote actions, select a device in your **Chrome Enterprise** list or go to **Devices** > **All devices** and select a device. This article describes the remote actions, and provides information about required permissions and known issues.  
 
 ## Prerequisites     
-[Set up the Chrome Enterprise connector](chrome-enterprise-connector-configure.md) with Microsoft Intune, and enroll devices using the Google Admin console. 
+[Set up the Chrome Enterprise connector](../enrollment/chrome-enterprise-connector-configure.md) with Microsoft Intune, and enroll devices using the Google Admin console. 
 
 Permission requirements are provided in the sections that follow.  
 
 ## Deprovision  
 Select **Deprovision** to remove Google Admin policies from devices your organization no longer uses. To deprovision a ChromeOS device, you must be assigned a role that has the *Remote tasks: Retire* permission.  
 
-After you deprovision a device, it remains in the Intune admin center and the Google Admin console. Then on the admin center **System info** page, the device status changes to **DEPROVISIONED**. The device can't be enrolled again until it's restored to factory settings. For more information about the deprovision action, such as how to select the best reason for deprovisioning, see the [Chrome Enterprise and Education Help documentation](https://support.google.com/chrome/a/answer/3523633?).  
+After you deprovision a device, it remains in the Intune admin center and the Google Admin console. Then on the admin center **System info** page, the device status changes to **DEPROVISIONED**. The device can't be enrolled again until you restore it to factory settings. For more information about the deprovision action, such as how to select the best reason for deprovisioning, see the [Chrome Enterprise and Education Help documentation](https://support.google.com/chrome/a/answer/3523633?).  
 
 ## Lost mode  
-Select **Lost mode** to prevent people from using a ChromeOS device that's lost or stolen. Devices in lost mode display the contact information and message you configured in the Google Admin console. To deprovision a device, you must be assigned a role that has the following permissions:  
+Select **Lost mode** to prevent other people from using a lost or stolen ChromeOS device. Devices in lost mode display the contact information and message you configured in the Google Admin console. To deprovision a device, you must be assigned a role that has the following permissions:  
 
 * *Remote tasks: Enable lost mode*     
 * *Remote tasks: Disable lost mode*        
@@ -72,10 +72,10 @@ Select **Restart** to restart a device. To restart a device, you must be assigne
 >[!IMPORTANT]
 > Device users aren't automatically notified of restarts, and might lose unsaved work if you don't tell them about it ahead of time. 
 
-Restart is only available for kiosk devices and managed guest session devices. The restart will fail on any other type of device. For more information, see [Kiosk apps, managed guest sessions, and smart cards](https://support.google.com/chrome/a/topic/6128720?) (opens Google Chrome Enterprise Help).  
+Restart is only available for kiosk devices and managed guest session devices. The restart fails on any other type of device. For more information, see [Kiosk apps, managed guest sessions, and smart cards](https://support.google.com/chrome/a/topic/6128720?) (opens Google Chrome Enterprise Help).  
 
 ## Bulk device actions   
-You can issue all of these remote actions as part of a bulk device action. For more information about how to do that, see [Use bulk device actions](../remote-actions/bulk-device-actions.md).  
+You can issue all of these remote actions as part of a bulk device action. For more information about how to do that, see [Use bulk device actions](bulk-device-actions.md).  
 
 ## Known issues  
-In some cases, device commands remain in a pending state even if they’ve already completed or failed. 
+In some cases, device commands remain in a pending state, even if they’ve already completed or failed. 
diff --git a/memdocs/intune/toc.yml b/memdocs/intune/toc.yml
@@ -1476,6 +1476,9 @@ items:
         - name: Get Apple MDM push certificate   
           href: ./enrollment/apple-mdm-push-certificate-get.md
           displayName: digital; certificates; notifications; token; PEM; automated device enrollment; user enrollment; device enrollment  
+        - name: Configure Chrome Enterprise connector 
+          href: ./enrollment/chrome-enterprise-connector-configure.md 
+          displayName: chrome os; connector; device management; google admin       
         - name: Add corporate identifiers
           href: ./enrollment/corporate-identifiers-add.md
           displayName: COD; corporate owned; IMEI; device ownership; serial   
@@ -1506,14 +1509,6 @@ items:
             href: ./enrollment/create-device-platform-restrictions.md  
           - name: Create device limit restrictions  
             href: ./enrollment/create-device-limit-restrictions.md  
-        - name: Configure Chrome Enterprise connector
-          items: 
-          - name: Configure Chrome Enterprise connector
-            href: ./enrollment/chrome-enterprise-connector-configure.md 
-          - name: View ChromeOS device information in Intune
-            href: ./enrollment/chrome-enterprise-device-details.md              
-          - name: Remote device actions for ChromeOS  
-            href: ./enrollment/chrome-enterprise-remote-actions.md  
 
       - name: Set up Windows enrollment
         items:  
@@ -1711,6 +1706,8 @@ items:
           href: ./remote-actions/find-primary-user.md
       - name: Other actions
         items:
+        - name: Remote actions for ChromeOS
+          href: ./remote-actions/chrome-enterprise-remote-actions.md
         - name: Locate device
           href: ./remote-actions/device-locate.md
         - name: Rename device
@@ -1723,6 +1720,8 @@ items:
           href: ./remote-actions/device-sync.md
         - name: Examine device inventory
           href: ./remote-actions/device-inventory.md
+        - name: View ChromeOS device information
+          href: ./remote-actions/chrome-enterprise-device-details.md
         - name: Collect diagnostics
           href: ./remote-actions/collect-diagnostics.md
         - name: Remove apps and configuration