From 413c24fc953f7abab2b36be50f56fc8f6db5fbc1 Mon Sep 17 00:00:00 2001 From: Reinaldy Rafli Date: Sun, 5 Jul 2026 16:56:26 +0700 Subject: [PATCH] fix(azure): Azure SSO installation setup for stuck self-hosted installation Closes https://github.com/getsentry/self-hosted/issues/4244 --- docs/organization/authentication/sso/azure-sso.mdx | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/organization/authentication/sso/azure-sso.mdx b/docs/organization/authentication/sso/azure-sso.mdx index 290b24c49e512..3743ab17a9a8e 100644 --- a/docs/organization/authentication/sso/azure-sso.mdx +++ b/docs/organization/authentication/sso/azure-sso.mdx @@ -81,6 +81,19 @@ If you change your organization slug, you'll need to make the same update in the - If you made changes, click "Save Settings" to complete your setup. +### Self-Hosted Installation + +If you created an account in Sentry using the same email as your Azure/Entra ID account before configuring SSO, the invitation email may not arrive (for non-public instances), leaving the account unlinked. This process requires a colleague (User B) who can log in via SSO and temporarily take over ownership. + +1. Log in to your self-hosted Sentry instance using your existing account — we'll call this User A. +2. Ask someone else to log in through SSO and confirm it creates a new account for them — we'll call this User B. +3. User A needs to assign the "Owner" role to User B. +4. User B needs to remove User A's account from the Sentry instance. +5. User A logs in through SSO. If prompted to merge accounts, choose "No, thanks". The new account should now be properly created and linked to the Azure account. You may need to use incognito mode, or clear all browser cookies and session data, before logging in. +6. User B can re-assign the "Owner" role back to User A. + +Credits to [Adamar_Work on Discord](https://discord.com/channels/621778831602221064/796028405833007104/1483484392239398954) for the solution. + ## SCIM Integration