Skip to content

Commit 80df771

Browse files
Merge pull request #4246 from anunesms/docs-editor/remove-replication-permissions-1750141568
Update image in ISPM to match steps
2 parents e1e6fbb + 836e224 commit 80df771

File tree

4 files changed

+5
-1
lines changed

4 files changed

+5
-1
lines changed
672 KB
Loading
652 KB
Loading
680 KB
Loading

ATPDocs/remove-replication-permissions-microsoft-entra-connect.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,11 @@ Smart attackers are likely to target Microsoft Entra Connect in on-premises envi
3030

3131
1. Take appropriate action on those accounts and remove their 'Replication Directory Changes' and 'Replication Directory Changes All' permissions by unchecking the following permissions:
3232

33-
![Screenshot of the replication permissions.](media/remove-replication-permissions-microsoft-entra-connect/permissions.png)
33+
[![Screenshot that shows Replicationconfiguration](media/remove-replication-permissions-microsoft-entra-connect/replicationconfiguration.png)](media/remove-replication-permissions-microsoft-entra-connect/replicationconfiguration.png#lightbox)
34+
35+
36+
37+
3438

3539
> [!IMPORTANT]
3640
> For environments with multiple Microsoft Entra Connect servers, it’s crucial to install sensors on each server to ensure Microsoft Defender for Identity can fully monitor your setup. It has been detected that your Microsoft Entra Connect configuration does not utilize Password Hash Sync, which means that replication permissions are not necessary for the accounts in the Exposed Entities list. Additionally, it’s important to ensure that each exposed MSOL account is not required for Replication Permissions by any other applications.

0 commit comments

Comments
 (0)