> For the complete documentation index, see [llms.txt](https://docs.agentnoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agentnoon.com/technical-documentation/authentication-and-identity-security/single-sign-on-sso/microsoft-sso-integration-azure-ad.md).

# Microsoft SSO Integration (Azure AD)

Agentnoon supports Single Sign-On (SSO) via Microsoft Azure Active Directory using the SAML 2.0 protocol, allowing users to securely access the platform

#### 1. Consent Link for Microsoft SSO Integration

1. Shared a link for the Customer integration with Microsoft SSO.
2. Customer’s IT Admin will need to approve the app via the consent link below
   1. Consent link: please email us at <SupportSWP@dayforce.com> and we will send over the consent link for SSO for admins
3. Other parameters the IT admin will need.
   1. Redirect URI: <https://auth.agentnoon.com/__/auth/handler>
   2. Logout URL: <https://app.agentnoon.com/logout>

#### 2. Documentation Reference

1. Reference to Microsoft Learn documentation for granting tenant-wide admin consent.
2. **Link:** [Microsoft Learn - Grant tenant-wide admin consent](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/grant-admin-consent?pivot=portal)

#### 3. Testing Account

1. We will request a test account to validate the integration setup.

#### 4. Post-Approval Actions

1. No further actions are required after the admin approval, as the configuration supports all organizational users by default.

**Action Items:**

1. Ensure the Customer’s IT Admin approves the consent link.
2. Confirm that the integration functions correctly using the provided test account.


---

# 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.agentnoon.com/technical-documentation/authentication-and-identity-security/single-sign-on-sso/microsoft-sso-integration-azure-ad.md?ask=<question>&goal=<user_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.