> For the complete documentation index, see [llms.txt](https://docs.sled.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sled.so/sso.md). # Single Sign-On Authenticate with your existing identity provider Sled supports Single Sign-On (SSO), allowing your users to authenticate using their existing identity provider credentials instead of managing separate passwords. ## Supported Providers * [Azure Active Directory](/sso/azure-active-directory.md) - Microsoft Entra ID (OAuth 2.0 / OpenID Connect) ## How SSO Works in Sled When SSO is enabled, users see a **"Sign in with Microsoft"** button on the login page. Clicking it redirects them to your identity provider for authentication. After successful login, users are automatically created in Sled and assigned a role based on their group memberships. ### Key Features * **Automatic user provisioning** - Users are created in Sled on first login, no manual setup needed * **Group-based access control** - Map identity provider groups to Sled roles (Admin, Editor, Viewer) * **Default viewer access** - All authenticated users get read-only access without any extra configuration * **MFA support** - Works with your identity provider's Multi-Factor Authentication policies * **Optional password fallback** - Keep password login enabled alongside SSO during transition --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sled.so/sso.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.