Skip to content

Commit 12f4288

Browse files
authored
Merge pull request #49874 from Potapy4/patch-22
Fix markdown
2 parents b44dc1a + f94a970 commit 12f4288

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/hybrid/how-to-connect-fix-default-rules.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ If the extensions don't work for you, try adding two new sync rules, described i
6868
#### Add an inbound sync rule
6969
An inbound sync rule means the source for the attribute is a connector space, and the target is the metaverse. For example, to have a new attribute flow from on-premises Active Directory to Azure Active Directory, create a new inbound sync rule. Launch the **Synchronization Rules Editor**, select **Inbound** as the direction, and select **Add new rule**.
7070

71-
!Synchronization Rules Editor](media/how-to-connect-fix-default-rules/default3a.png)
71+
![Synchronization Rules Editor](media/how-to-connect-fix-default-rules/default3a.png)
7272

7373
Follow your own naming convention to name the rule. Here, we use **Custom In from AD - User**. This means that the rule is a custom rule, and is an inbound rule from the Active Directory connector space to the metaverse.
7474

0 commit comments

Comments
 (0)