--- title: "Azure AD Sign-in" slug: "azure-ad-signin" updated: 2026-04-15T21:25:04Z published: 2026-04-15T21:25:04Z canonical: "docs.databee.buzz/azure-ad-signin" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.databee.buzz/llms.txt > Use this file to discover all available pages before exploring further. # Azure AD Sign-in Azure AD Sign-in is an identity and access management solution from Microsoft that helps organizations secure and manage identities for hybrid and multi-cloud environments. For more information, refer to [Azure's official documentation](https://learn.microsoft.com/en-us/azure/azure-monitor/getting-started). **Integration Method:** API **Tables**: Authentication (3002) This integration supports the following events. | **Event** | **Description** | | --- | --- | | Authentication | Retrieve a list of users sign-in and authentication data objects. | This integration supports the following versions. | Microsoft Graph REST API | v1.0 | | --- | --- | ## Prerequisites - The user should ensure scopes are properly assigned to the API token for successful data retrieval. - The user should have access to the DataBee console. ## Configuration Overview 1. Generate client credentials with the required scopes. 2. Add the [Azure Ad Sign-In data feed](/user-manual/docs/azure-ad-sign-in#databee-configuration) in the DataBee console with the below parameters. | **DataBee Parameter** | **Azure Parameter** | | --- | --- | | Client Key | Application (client) ID | | Client Secret | Client Secret Value | | Token URL() | Directory (Tenant) ID | ## Azure Configuration ### Create an application 1. Log on to [Azure](https://portal.azure.com/) with a user account that has the Global Administrator role. 2. In the search bar, search for **App Registrations** and select it. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-ocy7r7v1.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 3. On the “App registrations” page, select **New registration,** the **“**Register an application**”** window will appear. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-8cz5yjaa.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 4. On the “Register an application” window: 1. Under **Name** enter your Application Name then click on **Register** to create the application. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-y7uw5tv9.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 5. On the app **Overview** page, copy the **Application (client) ID** and **Directory (tenant) ID** for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-siuoa4q7.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) ### Add Endpoint Access Once the application is created, permissions should be provided to get data. The appropriate permissions for the application are needed to configure these endpoints. The following section details how to configure and add permissions to the sign-in endpoint. Endpoint needed for Microsoft Entra **-** [Microsoft Entra Endpoint](https://graph.microsoft.com/v1.0/auditLogs/signIns). #### Add Permissions From the Azure Active Directory portal: 1. Select the application registered in the previous step. 2. Under **Manage,** click “API permissions” and then click **Add a permission,** the “Request API permissions” window will appear. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-ild5zzd9.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 3. On “Request API permissions” window, Click on **Microsoft APIs** then on **Microsoft Graph.** ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-1oqcy98g.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 4. Click on **Application permissions.** ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-2kgsiod9.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 5. The following permissions need to be granted for the one endpoint to function properly: | **Endpoint** | **Permission** | | --- | --- | | /v1.0/auditLogs/signIns | AuditLog.Read.All | | /v1.0/auditLogs/signIns | Directory.Read.All | 6. In the **Select permissions** search bar, enter the permission shown above, and check the box to include it. If you run into any problems, check [Microsoft's official document](https://learn.microsoft.com/en-us/graph/api/user-list?view=graph-rest-1.0&tabs=http#permissions). Click the **Add permissions** button after selecting all required permissions. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-zyjkb5gs.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 7. On the **API permissions** page, click **Grant admin consent** **for **. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-tw3ugnzy.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 8. Click the **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-8ohixc7p.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 9. The required permissions are now added for the endpoints. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-5bjye2cf.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) ### Create the Client Secret The final step in configuring the Graph API is creating a **Client ID** and **Client Secret**. To create these items, from the Azure Portal: 1. Select the application created above. 2. Under **Manage**, Click **Certificates and Secrets**, and then **Client Secrets**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-i9gnpvud.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 3. Click on **New client secret**. The “Add a client secret” window appears. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-pa4vxs8z.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 4. In the “Add a client secret” window: 1. Enter a ‘Description’ for this client secret and select the desired expiry period from the ‘Expires’ drop-list. 2. Then click on **Add** to create the client secret. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-66pmb4ym.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) > [!NOTE] > **Note:** > > The user needs to re-create the client secret when it expires. 5. Click **Add**. Copy the **Value** fields for later use. ![Inserting image...](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-zxm50jm2.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) ## DataBee Configuration 1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-r1cg8fux.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 2. Search for the **Azure AD Sign-in** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-vedevsyw.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-ad-sign-in-feb-2025-image-15trgpuy.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/image(474).png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 5. In the configuration page, confirm the following: - Authorization Method: OAuth2 - Client key: paste **Application (client) ID.** - Client secret: paste **Application (client) secret.** - Token URL: replace < tenant_id> placeholder with the **Directory (Tenant) ID** generated earlier. - Event Types: preselected for all the event types that integration pulls. - API Version: Select the API version - Buffer Time: In Graph API some events may become available after a delay. The buffer time defines how far back the system queries data to capture delayed events and prevent missing records. By default, it will take as a 30m buffer. Note: Add Buffer Time in minutes ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/Screenshot%202026-04-15%20at%202.20.48%E2%80%AFPM.png?sv=2026-02-06&spr=https&st=2026-10-30T12%3A22%3A39Z&se=2026-10-30T13%3A22%3A39Z&sr=c&sp=r&sig=pXbVkwumOLnqIASWnZ5AHIyuZq2HAG%2FB%2FqZ2NLhaXG0%3D) 6. Click on Submit ## Troubleshooting Tips - If you are facing an **invalid client** or **unauthorized client** error this might be possibly due to incorrect credentials. Ensure the client key, client secret and Tenant ID are pasted correctly. Since you cannot view the client secret after the 1st time, re-create it, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed. - If you are facing a **403**-response code this might be possibly due to missing permission. Ensure that all the required permissions are granted correctly as per the above-mentioned steps.