Skip to content

Commit 4f82771

Browse files
committed
Post-edit changes
1 parent 4de5877 commit 4f82771

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/mem/configmgr/discovery/ad-group-not-discovered.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Delta AD Group Discovery Doesn't Detect Group Membership Changes in Nested OUs
3-
description: Troubleshoot an issue in which AD Delta Discovery doesn't detect group membership changes in child organizational units.
3+
description: Troubleshoot an issue in which the delta discovery process of AD Group Discovery doesn't detect group membership changes in child organizational units.
44
ms.date: 01/12/2025
55
ms.reviewer: kaushika, jarrettr, brianhun, payur
66
ms.custom: sap:Boundary Groups, Discovery and Collections\Active Directory Discovery (all types)
@@ -19,7 +19,7 @@ This article helps you identify this issue in your environment, and provides wor
1919

2020
You set up discovery scopes for AD Group Discovery to target specific Active Directory Domain Services (AD DS) groups, as described in [Configure Active Directory Group Discovery](/intune/configmgr/core/servers/deploy/configure/configure-discovery-methods#bkmk_config-adgd). The initial full discovery cycle correctly discovers groups in all the in-scope OUs.
2121

22-
After the delta discovery cycle runs, you notice that changes in particular group memberships are missed. However, if you force a full discovery cycle to run, the issue resolves as the full discovery cycle discovers changes in all groups in the in-scope OUs.
22+
Some time after the initial full discovery cycle finishes, the delta discovery cycle runs. After the delta discovery cycle finishes, you notice that changes in particular group memberships are missed. However, if you force a full discovery cycle to run, the issue resolves as the full discovery cycle discovers changes in all groups in the in-scope OUs.
2323

2424
In particular, the issue occurs when you define scopes that resemble the following example:
2525

0 commit comments

Comments
 (0)