You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: memdocs/configmgr/core/get-started/2022/includes/2202/9708999.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,10 +20,11 @@ A new **Details** window shows more information about the relationship types, an
20
20
21
21
There are several reasons why the site can't delete a dependent collection:
22
22
23
-
- Assigned to user <!-- is this AAD sync? https://docs.microsoft.com/en-us/mem/configmgr/core/clients/manage/collections/create-collections#bkmk_aadcollsync -->
24
-
- Used by cloud attach
25
-
- Use for upload to Microsoft Endpoint Manager
26
-
<!-- need clarity on specifically what settings these apply to -->
23
+
-**Assigned to user**: For more information, see [Modify the administrative scope of an administrative user](../../../../servers/deploy/configure/configure-role-based-administration.md#modify-the-administrative-scope-of-an-administrative-user).
24
+
25
+
-**Used by cloud attach**: For more information, see [Enable cloud attach for Configuration Manager](../../../../../cloud-attach/enable.md).
26
+
27
+
-**Use for upload to Microsoft Endpoint Manager**: For more information, see [Make Configuration Manager collections available to assign Endpoint security policies](../../../../../tenant-attach/endpoint-security-get-started.md#bkmk_collections).
27
28
28
29
The details window lists collections that can't be deleted with the reason why.
0 commit comments