CX-876 Clarify provisioning capabilities for Exchange groups

[luisina-santos]

Updated limitations and instructions for Exchange groups provisioning.

@mindymo please update if you think it needs more clarification.

main change:

• Exchange groups provisioning and sync owners is ONLY available using Client secret auth method. Using OAuth you are not able to manage exchange groups

Summary by CodeRabbit

Documentation

• Updated Microsoft Entra connector documentation to clarify OAuth limitations for Mail Enabled Security groups and Distribution groups provisioning.
• Documented that Client secret-based authentication supports provisioning both owners and members in Exchange groups.
• Removed outdated limitation note regarding owner provisioning.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation update to the Microsoft Entra connector clarifying OAuth limitations for Mail Enabled Security and Distribution groups, and updating Exchange group provisioning details to specify client secret authentication and support for provisioning both owners and members.

Changes

Cohort / File(s)	Summary
Documentation Updates baton/microsoft-entra.mdx	Tightened OAuth provisioning limitations note; renamed Exchange groups provisioning section to indicate "Client secret based auth"; expanded provisioning scope from "members" to "owners and members"; removed limitation about users as owners.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Documentation hops anew,
Clarity shines through and through,
Owners and members dance with glee,
OAuth's limits now we see!
With client secrets held so tight,
Microsoft Entra's burning bright! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: clarifying provisioning capabilities for Exchange groups in the Microsoft Entra documentation, which aligns with the PR's objective to update limitations and instructions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@baton/microsoft-entra.mdx`:
- Around line 147-149: Update the heading and terminology: change the heading
"Optional: Configure Exchange groups provisioning with **Client secret** based
auth" to use the compound modifier "Client secret-based" and replace the phrase
"mailed security groups" in the same paragraph with the correct term
"mail-enabled security groups" so terminology matches line 24's usage; update
the occurrences around the "Configure Exchange groups provisioning" section and
any related sentences referencing mailed security groups to use "mail‑enabled
security groups".

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix grammar and terminology issues.

1. Line 147: Add hyphen to "secret-based" per compound modifier rules.
2. Line 149: "mailed security groups" should be "mail-enabled security groups" to match the terminology used in line 24.

📝 Proposed fix

-## Optional: Configure Exchange groups provisioning with **Client secret** based auth
+## Optional: Configure Exchange groups provisioning with **Client secret**-based auth

-To set up the connector to support provisioning owners and members to Exchange groups, which are distribution lists and mailed security groups, follow these steps:
+To set up the connector to support provisioning owners and members to Exchange groups, which are distribution lists and mail-enabled security groups, follow these steps:

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## Optional: Configure Exchange groups provisioning with **Client secret** based auth
	To set up the connector to support provisioning members to Exchange groups, which are distribution lists and mailed security groups, follow these steps:
	To set up the connector to support provisioning owners and members to Exchange groups, which are distribution lists and mailed security groups, follow these steps:
	## Optional: Configure Exchange groups provisioning with **Client secret**-based auth
	To set up the connector to support provisioning owners and members to Exchange groups, which are distribution lists and mail-enabled security groups, follow these steps:

🧰 Tools

🪛 LanguageTool

[grammar] ~147-~147: Use a hyphen to join words.
Context: ...oups provisioning with Client secret based auth To set up the connector to s...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents

In `@baton/microsoft-entra.mdx` around lines 147 - 149, Update the heading and
terminology: change the heading "Optional: Configure Exchange groups
provisioning with **Client secret** based auth" to use the compound modifier
"Client secret-based" and replace the phrase "mailed security groups" in the
same paragraph with the correct term "mail-enabled security groups" so
terminology matches line 24's usage; update the occurrences around the
"Configure Exchange groups provisioning" section and any related sentences
referencing mailed security groups to use "mail‑enabled security groups".

[mindymo]

Looks great, thank you!