Conversation
|
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughDocumentation formatting update to Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Merge activity
|
🧪 Test Suite AvailableThis PR can be tested by a repository admin. |
Confidence Score: 3/5Not safe to merge as-is — the permission type change would break user onboarding by making Step 5 impossible to follow. A P1 documentation bug was introduced: the OIDC scopes listed in Step 5 do not exist as Application permissions in Microsoft Graph, so the guide now gives incorrect instructions that users cannot follow. Two additional P2 stale Okta references also remain unfixed. docs/enterprise/setting-up-entra.mdx — Step 5 permission type and residual Okta references need correction. Important Files Changed
Reviews (1): Last reviewed commit: "fix entra documentation" | Re-trigger Greptile |
| 2. Click **Add a permission** | ||
| 3. Select **Microsoft Graph** | ||
| 4. Choose **Delegated permissions** | ||
| 4. Choose **Application permissions** |
There was a problem hiding this comment.
Incorrect permission type for OIDC scopes
The instruction was changed to "Application permissions," but the scopes listed immediately after — openid, profile, email, and offline_access — do not exist as Application permissions in Microsoft Graph. They are Delegated-only scopes tied to user sign-in (authorization code flow). A user following this guide will not find those scopes in the Application permissions picker and will be unable to complete the setup.
The OIDC scopes should be added under Delegated permissions, while the directory-read scopes (User.Read, User.Read.All, GroupMember.Read.All, Group.Read.All) can be added as Application permissions (or Delegated, depending on the intended token flow).
| 4. Choose **Application permissions** | |
| 4. Choose **Delegated permissions** |
| <img src="/media/user-provisioning/entra-form.png" alt="Create token dialog in Okta" /> | ||
| <img | ||
| src="/media/user-provisioning/entra-form.png" | ||
| alt="Create token dialog in Okta" |
|
|
||
| ### Attribute Mappings | ||
|
|
||
| Attribute mappings let you translate Okta claim values into Bifrost roles, teams, or business units without restructuring your Okta claims. Bifrost supports three mapping types: |
There was a problem hiding this comment.
Stale Okta references in Attribute Mappings section
This paragraph still says "Okta claim values" and "Okta claims" twice, despite being inside the Microsoft Entra setup guide.
| Attribute mappings let you translate Okta claim values into Bifrost roles, teams, or business units without restructuring your Okta claims. Bifrost supports three mapping types: | |
| Attribute mappings let you translate Entra claim values into Bifrost roles, teams, or business units without restructuring your Entra claims. Bifrost supports three mapping types: |

Summary
Fixes formatting inconsistencies in the Microsoft Entra ID setup guide to improve readability and ensure consistent MDX rendering.
Changes
<img>tags to use multi-line JSX style<Tip>,<Warning>, and<Note>block content to use proper indentationoptionalClaimsJSON blockType of change
Affected areas
How to test
Review the rendered documentation page for the Microsoft Entra setup guide and verify:
<Tip>,<Warning>,<Note>) display with correct indentationBreaking changes
Related issues
Security considerations
None.
Checklist
docs/contributing/README.mdand followed the guidelines