> For the complete documentation index, see [llms.txt](https://documentation.astera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.astera.com/astera-data-stack-v10/setting-up/user-roles-and-access-control/azure-authentication.md).
# Azure Authentication
Azure authentication is a security feature that allows users to log into a system using their Microsoft Azure credentials.
Astera Data Stack leverages this authentication method and provides the option to register new users using Azure authentication through its Server Browser interface.
## **Configuring Azure Authentication Credentials**
1. Go to *Server > Cluster > Cluster Settings*
2. Click on Authentication mode tab and select Azure Authentication from dropdown
3. Provide a valid *Client Id, Redirect URI* and *Account type*.
{% hint style="info" %}
**Note:** You can find your *Client ID, Redirect URI* and *Account Type* in you Azure Portal.
{% endhint %}
## **Registering user using Azure Authentication**
1. After Configuring Azure Credentials, navigate to *Server Browser* tool window by pressing ctrl + alt + B*.*
2. Here, in *Security > User*, right-click on *User* and select **Register User**
3. A *Register User* window will open, in the *Registration* drop-down select **Azure Authentication**
4. Once selected, Astera will start retrieving a list of users.
5. Once the users have been retrieved, a search UI will appear.
Now there are two ways to specify the user you want to register
* By clicking on the dropdown given in the search bar, this will show the list of all users which exist in that active directory:
* By just directly searching in the search bar for a specific user and clicking e***nter*** so that user will be selected:
6. Once the user has been selected by one of the methods, the selected email id will be displayed in a *User Email Id* grid.
7. Now Click Register and you can see that selected users are added
8. Now you can [activate them or assign them a role](https://documentation.astera.com/latest/setting-up/user-roles-and-access-control) as you would normally do in Astera
{% hint style="info" %}
**Note:** Users Registered using azure authentication can only be activated, deactivated, or deleted
{% endhint %}
## **Login Using Azure Authentication**
Once users have been registered with Azure authentication, they can login with the same authentication credentials.
To log in, select the *Log In* option from the top right of the client window.
Selecting this will open a new window.
In the authentication Dropdown, there are three options:
1. *Centerprise*: For Users that are created by using a simple/existing registration method.
2. *Windows Authentication:* For users that are created by using the Windows authentication method.
3. *Azure Authentication:* For users that are created using the Azure authentication method
2. By selecting Azure Authentication, the email and password textbox will get locked. Click on *Log In*
3. User would be redirected to the Microsoft sign-in screen where they can sign-in as they would normally do with their email id and password.
This concludes the working of Azure Authentication in Astera Data Stack.
---
# 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://documentation.astera.com/astera-data-stack-v10/setting-up/user-roles-and-access-control/azure-authentication.md?ask=&goal=
```
`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.