> For the complete documentation index, see [llms.txt](https://docs.nanocorp.ai/n.scope-v2.0-english/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nanocorp.ai/n.scope-v2.0-english/ressources/integrations/single-sign-on/azure-ad-sso.md).

# Azure AD SSO

## n.Scope Azure SSO Feature

## 1. Configuring SSO

### 1.1 Pre-Requisites

To successfully configure Azure SSO integration with n.Scope, the following pre-requisites must be dealt with :

* [ ] The n.Scope platform must be able to communicate with Azure Servers
* [ ] An Azure Application must be created following Nano Corp instructions.

### 1.2 Configuring Azure SSO

Follow these steps to integrate n.Scope with Azure SSO.

#### 1.2.1 Retrieve Azure SSO Applications details

Retrieve the Application ID & Tenant ID from the Azure AD application page.

<figure><img src="/files/dDyiaBP7HDpF38mJfbx6" alt=""><figcaption></figcaption></figure>

Note that information aside as they will be required later.

#### 1.2.2 Configure Single Page Application Callback

n.Scope requires a SPA callback from Azure SSO. Create one from Azure SSO

<figure><img src="/files/yJW2bReXfXROAFKRRT5T" alt=""><figcaption></figcaption></figure>

Set the redirect URI for the callback to the IP address or FQDN of the n.Scope deployed on your network, on the `/ssoazure` path.

{% hint style="info" %}
Example Callback URI: \`https\://{N.SCOPE IP ADDRESS}/ssoazure\`
{% endhint %}

Set the logout URL to the `/api/logout_sso` path.

{% hint style="info" %}
&#x20;Example Logout URI: \`https\://{N.SCOPE IP ADDRESS}/api/logout\_sso\`
{% endhint %}

Check the API permissions parameters. The following permissions must be granted:

* [ ] email
* [ ] offline\_access
* [ ] OpenID
* [ ] profile
* [ ] User.Read
* [ ] User.ReadBasic.All

<figure><img src="/files/E0rIZ3SZAfzNJ5CUf7G5" alt=""><figcaption></figcaption></figure>

### 1.3 Configuring n.Scope for Azure SSO

This section will detail the steps required to enable Azure SSO on n.Scope.

#### 1.3.1 Activate Azure SSO

Connect to n.Scope using the default admin login and password (admin/admin).

⚠️ You will be required to change the admin password on the first login, don’t forget to write down the updated password.

Navigate to n.Scope configuration from the left navigation menu:

<figure><img src="/files/ucBT45LPxAQsCabX6jnM" alt="" width="375"><figcaption></figcaption></figure>

Select the Single Sign-On tab:

<figure><img src="/files/ojTx8HQxNfFzn96hPl4o" alt=""><figcaption></figcaption></figure>

Register the SSO service by selecting Azure and providing the Application ID & Tenant ID you noted from the first step.

<figure><img src="/files/ZU7KL0mISMsib2wGoMGN" alt=""><figcaption></figcaption></figure>

Click on the + Add button to register the SSO service.

{% hint style="info" %}
You can give any meaningful name you wish to this SSO integration (we recommend Azure SSO)
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nanocorp.ai/n.scope-v2.0-english/ressources/integrations/single-sign-on/azure-ad-sso.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.