docs(email-security): duplicate rule name in M365 MX pre-delivery setup instructions
Maintainers usually reply within 1 day
@akhil9tiet is already working on this.
Since Oct 19, 2026.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown
- Domain
- documentation
Research direction
Open the M365 email security MX pre-delivery setup page linked in the issue and read Section 4, “Create transport rules.” Update step 10’s rule name so it clearly distinguishes the quarantine action from the rule in step 4. Done when the two rules have distinct, action-specific names.
Written by the indexing model from the issue text.
Description
Existing documentation URL(s)
What changes are you suggesting?
In Section 4 ("Create transport rules"), steps 4 and 10 instruct users to create two separate Exchange transport rules with the same rule name ("Email Security Deliver to Junk Email folder").
Having identical rule names in Exchange Online creates confusion during administration, logging, and troubleshooting.
I suggest updating step 10 to give the second rule a distinct name that reflects its action (quarantining), such as:
- Step 4 Name:
Email Security Deliver to Junk Email folder(orEmail Security - Send Bulk to Junk) - Step 10 Name:
Email Security Quarantine Malicious Messages(orEmail Security - Quarantine)
Additional information
Specifically, step 10 currently states:
10. Set the following rule conditions:
- Name: Email security Deliver to Junk Email folder.
- Apply this rule if: [...] MALICIOUS, UCE, SPOOF
- Do the following: Redirect the message to > hosted quarantine.
Differentiating the name in step 10 will prevent administrative confusion when managing rules inside the Exchange Admin Center.
- Dominant language
- MDX
- Stars
- 5.3k
- Forks
- 17.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 571
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudflare/cloudflare-docs
-
effort:medium engineering
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
cloudflare/cloudflare-docs#34464 ·
Maintainers usually reply within 1 day
-
content:edit documentation effort:high
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
cloudflare/cloudflare-docs#34428 ·
Maintainers usually reply within 1 day
-
content:new documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
cloudflare/cloudflare-docs#33929 ·
Maintainers usually reply within 1 day
-
Changelog for https://github.com/cloudflare/workerd/pull/7053May be free again A pull request for this issue was closed without being merged. Opencontent:new documentation product:workers
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cloudflare-docs#32869 · 6 comments ·
Maintainers usually reply within 1 day
-
Artifacts lacks paid subscription requirement warning/mentionPossibly taken @AiAlchemist0 claimed this 62 days ago. Opencontent:edit documentation product:artifacts
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cloudflare/cloudflare-docs#32812 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cloudflare/cloudflare-docs
Similar issues
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ramnes/notion-sdk-py#423 ·
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 89/100
duckdb/duckdb-web#7514 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nxdpro/journeyguard#8 ·