> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kobble.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Azure AD (Microsoft)
> Configure Azure AD OAuth for your Customer Portal.
## Overview
Offering a sign in with Azure AD in your Customer Portal may be a good idea for businesses that already use Microsoft services. It allows your users to sign in with their Microsoft account, which is convenient and secure.
To support Sign in with Azure AD you need to configure the Azure AD provider in the Kobble dashboard for your project.
Once configured, the Azure AD sign-in button will automatically be added on your Kobble Customer Portal.
## Configuration
1. Navigate to the [Authentication](https://app.kobble.io/p/authentication) section and choose the Azure AD provider.
2. Copy the provided Redirect URI. Note this URI will change if you configure a custom domain later.
3. Open your [Azure Portal](https://portal.azure.com/) and navigate to the Azure Active Directory section.
4. Click on App registrations and then New registration.
5. Fill the OAuth form on your Azure Portal. Choose a Web platform and paste the Redirect URI provided by Kobble.
6. Save your app.
7. On the app page, create a new Client Secret by clicking on Add a certificate or secret
8. Select an expiration date that fits your needs and save the secret.
9. Copy/paste the Client Id and Client Secret into your Kobble settings, turn on the Enabled switch and save.
10. Go to API Permissions in the left menu of your Azure Portal.
11. Click on Add a permission
12. In the slider, click on Microsoft Graph and choose Delegated permissions
13. Select the following permissions: **email**, **openid**, **profile** and save.
Don't forget to add the following permissions to your Azure configuration: **email**, **openid**, **profile**.
🎉 Et voilà ! Your customer can now use Azure AD to sign-in in your authentication portal. No further action is required on your end.
In case you change your Customer Portal domain later, you will have to go through this process again and update your Authorized Redirect URI in your Azure Client ID.