Skip to content

Correct plan availability for Azure Entra ID SSO #3153

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

Closed
claude wants to merge 2 commits into from
Closed

Correct plan availability for Azure Entra ID SSO #3153

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
15129b8
Correct plan availability for Azure Entra ID SSO
claude Aug 14, 2026
d8d5e4a
Rename Azure Active Directory to Azure Entra ID in SSO docs
claude Aug 14, 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
2 changes: 1 addition & 1 deletion data/llm_descriptions.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -386,7 +386,7 @@
platform/cli/reference/update: "CLI reference for bk update: update the installed bk CLI or print update instructions, handling Homebrew, mise, and standalone binary installations."
platform/cli/reference/user: "CLI reference for bk user: invite users to your organization."
platform/cli/reference/version: "CLI reference for bk version: display the installed CLI version."
platform/sso: "Overview of SSO support, listing providers (Okta, ADFS, GitHub, Google, Azure AD, OneLogin, custom SAML)."
platform/sso: "Overview of SSO support, listing providers (Okta, ADFS, GitHub, Google, Azure Entra ID, OneLogin, custom SAML)."
platform/sso/okta: "Configuring Okta as an SSO provider with SAML and optional SCIM user provisioning."
platform/sso/adfs: "Step-by-step setup of Active Directory Federation Services (ADFS) as an SSO provider."
platform/sso/google-workspace: "Setting up Google Workspace (G Suite) as an SSO provider using OpenID."
Expand Down
2 changes: 1 addition & 1 deletion data/nav.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -977,7 +977,7 @@
path: "platform/sso/github-sso"
- name: "OneLogin"
path: "platform/sso/onelogin"
- name: "Azure AD"
- name: "Azure Entra ID"

@buildsworth-bk-app buildsworth-bk-app Bot Aug 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: The renamed product is Microsoft Entra ID, not "Azure Entra ID"; the guide's H1 and Microsoft link already use the official name. Please use "Microsoft Entra ID" consistently in this nav entry, the overview, the LLM description, and the warning in the guide.

path: "platform/sso/azure-ad"
- name: "Custom SAML"
path: "platform/sso/custom-saml"
Expand Down
2 changes: 1 addition & 1 deletion pages/platform/sso.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Buildkite supports the following SSO providers:
* [GitHub](/docs/platform/sso/github-sso)
* [Google Workspace](/docs/platform/sso/google-workspace)
* [Google Workspace (SAML)](/docs/platform/sso/google-workspace-saml)
* [Azure Active Directory](/docs/platform/sso/azure-ad)
* [Azure Entra ID](/docs/platform/sso/azure-ad)

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use the official Microsoft Entra ID product name

The provider is named Microsoft Entra ID, not “Azure Entra ID,” as confirmed by the linked guide’s title and introduction (pages/platform/sso/azure_ad.md:1-6) and the existing Azure OIDC documentation (pages/pipelines/security/oidc/azure.md:24-28). This rename makes the provider list inconsistent with its destination page, while the same incorrect hybrid name is also introduced in the navigation and LLM description; use “Microsoft Entra ID” in all three labels.

AGENTS.md reference: AGENTS.md:L319-L320

Useful? React with 👍 / 👎.

@buildsworth-bk-app buildsworth-bk-app Bot Aug 14, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: The generic "Pro or Enterprise" note above this list still reads as if every provider here is available on both plans. A Pro customer can therefore still choose Azure from this overview without seeing that it requires Enterprise, while the PR description says this list will show per-provider availability. Please add the plan availability to the relevant provider entries here.

* [OneLogin](/docs/platform/sso/onelogin)
* [Custom SAML](/docs/platform/sso/custom-saml)

Expand Down
5 changes: 4 additions & 1 deletion pages/platform/sso/azure_ad.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,9 @@

You can use [Microsoft Entra ID](https://www.microsoft.com/en-us/security/business/identity-access/microsoft-entra-id#Overview) (formerly known as Azure Active Directory) as an SSO provider for your Buildkite organization. To complete this tutorial, you need admin privileges for both Azure and Buildkite.

> 📘 Enterprise plan feature
> Microsoft Entra ID (Azure AD) SSO is only available to Buildkite customers on the [Enterprise](https://buildkite.com/pricing) plan.

> 📘 You can also set up SSO providers manually with GraphQL.
> See the <a href="/docs/platform/sso/sso-setup-with-graphql">SSO setup with GraphQL guide</a> for detailed instructions and code samples.

Expand Down Expand Up @@ -53,7 +56,7 @@ Then, on your [Buildkite organization **Settings**](https://buildkite.com/organi
Once you've [performed a test login](#step-4-perform-a-test-login) you can enable your SSO provider using the **Enable** button. Enabling the SSO provider will not force a log out of any signed in users, but will cause all new or expired sessions to authorize through Azure AD before accessing any organization data.

> 🚧
>If you need to edit or update your Azure Active Directory provider settings, you will need to <a href="/docs/platform/sso#disabling-and-removing-sso">disable the SSO provider</a> first.
>If you need to edit or update your Azure Entra ID provider settings, you will need to <a href="/docs/platform/sso#disabling-and-removing-sso">disable the SSO provider</a> first.

## Using SCIM to provision and manage users

Expand Down