Skip to content

SCIM doc updates #3229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
x-cubed merged 3 commits into from
Jul 2, 2026
Merged

SCIM doc updates #3229

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aee6e44
Update known limitations for SCIM for Entra
aneita-octo Jul 2, 2026
0336be9
Update pubDate and modDate
aneita-octo Jul 2, 2026
09dc728
Merge remote-tracking branch 'origin/main' into aneita-scim-updates
aneita-octo Jul 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion src/pages/docs/security/authentication/scim/configuring-microsoft-entra.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -179,4 +179,3 @@ Entra ID will now reach out to Octopus Deploy regularly via the SCIM API wheneve
- Octopus Deploy does not support nested groups. Any requests from Entra ID to add a group as a member of another group will be ignored.
- Any groups provisioned by Entra ID will be global teams, rather than space-scoped teams, because Azure AD authentication applies to the whole Octopus Deploy instance. You can still apply space-scoped permissions to these teams, but the teams will be visible to all spaces.
- Octopus Deploy only supports a single email address for each user, whereas Entra ID supports many. Octopus Deploy will ignore any email addresses other than the **Work** email address, ie: `emails[type eq "work"].value`.
- Entra ID has a [Provisioning Expression builder](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/expression-builder) feature in preview, which depends on APIs that are not yet implemented in Octopus Deploy. As such, you may see errors if you try to use the Provisioning Expression builder in the Azure Portal.