--- title: "Azure Security Score" slug: "azure-security-score" updated: 2026-04-27T17:42:01Z published: 2026-04-27T17:42:01Z canonical: "docs.databee.buzz/azure-security-score" --- > ## 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 Security Score Azure Security Score provides a centralized view of an organization’s security posture by measuring how well Azure resources follow Microsoft’s recommended security best practices. These logs help track overall security improvements and identify areas that need attention. Common use cases include secure scores and secure score controls. For more details refer to [Microsoft’s official documentation](https://learn.microsoft.com/en-us/rest/api/defenderforcloud/?view=rest-defenderforcloud-2020-01-01). **Integration Method**: API **Tables**: Assessment Finding (99402001), Cloud Resources Inventory Info (5023) This integration supports the following events. | **Event(s)** | **Description** | | --- | --- | | Subscriptions | List all the subscriptions available in Azure tenant | | Secure Scores | List secure scores for all your Microsoft Defender for Cloud initiatives within your current scope. | | Secure Score Controls | Get all security controls within a scope | | Assessments | List security assessments for all your Microsoft Defender for Cloud resources for subscriptions retrieved by the Subscription event. | | Assessments Metadata | List metadata for security assessments across your Microsoft Defender for Cloud initiatives for subscriptions retrieved by the Subscription event. | This integration supports the following versions. | Azure Security Score API version | 2020-01-01 | | --- | --- | ## Prerequisites - The user should have access to the [Azure portal](https://portal.azure.com/) with an account that has the **Global Administrator** privileges. - The user should have access to the DataBee console. ## Configuration Overview 1. Create an application with required permissions to fetch the data. 2. Create [Azure Security Score Data Feed](/user-manual/docs/azure-security-score#databee-configuration) in the DataBee console with the required Client credentials. | **DataBee Parameter** | **Azure Parameter** | | --- | --- | | Client Key | [Application (client ID)](/docs/azure-security-score#clientid) | | Client Secret | Client [secret](/docs/azure-security-score#secret) Value | | Token URL() | [Directory (Tenant) ID](/docs/azure-security-score#tenantid) | ## Azure Configuration ### Create an application 1. Log on to [Azure portal](https://portal.azure.com/) with an account that has the **Global Administrator** role. In the search bar, search for **App registrations** and select it. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-g4b9d8tq.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 2. 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-security-score-image-1r8gpbnf.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 3. 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-security-score-image-ykhplyav.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) ### Add Endpoint Access Once the application is created, permission should be provided to fetch data. The appropriate permission for the application are needed to access these endpoints. The following section details how to configure and add permissions to the required endpoints. **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-security-score-image-w5xihf0h.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%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-security-score-image-71ga1vdy.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 4. Click on **Application permissions** and search **SecurityEvents.Read.All** and select it. Click on **Add permissions**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-m6vcodij.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 5. The following permissions need to be granted for the endpoint to function properly: | **Permission Name** | **Type** | | --- | --- | | SecurityEvents.Read.All | Application | ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-143n9dg4.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 6. In the search bar, check for **Subscriptions** and select your **Subscription name**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-eoi4igdr.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 7. Assign the Reader Role to the Subscription. Click on **Access Control (IAM)** and select **Add**. Role : Security Reader Scope: Subscription ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-4apyfpo2.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 8. Under **Role**, search **security reader** and select it. Click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-kq6ty2vc.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 9. Under **Members**, select member to be added. Click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-cpm2r8x6.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 10. Under **Assignment type**, Click **Review + assign** and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-v4x7a4cf.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 11. Under **Review + assign**, verified the details (role, member etc.) and click on **Review + assign**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-uphahywt.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) **Action:** Grant the Reader role to the Subscription for the App Registration to enable read-only access to subscription-level resources. ### Create the Client Secret The final step in accessing the APIs is creating a Client Secret. To create it from the Azure Portal: 1. Select the application created above. 2. Under **Manage**, Click **Certificates & secrets**, and then **Client secrets**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-ygtw3va1.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 3. Click **New client secret**. Then “Add a client secret” window appears. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-v80y373h.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 4. On “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-security-score-image-6620utkt.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) > [!NOTE] > **Note**: > > The user needs to re-create the client's secret when it expires. 5. Copy the **Value** fields for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-w7umifmw.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) This completes the setup for Azure Security Score API integration. ## DataBee Configuration 1. Login to the DataBee UI, navigate to **Data** > **Data Feeds** and click the **Add New Data Feed** button. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-ai5d5vdk.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 2. Search for the **Azure Security Score** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-p5ziams1.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 3. Click on the **API Ingest** option for collection method. ![A screenshot of a computer AI-generated content may be incorrect.](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-jou3ud0v.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 4. Enter feed contact information, keep Entity Resolution checkbox checked if you want it, else uncheck it and scroll down. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azure-security-score-image-uxs91zb7.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 5. In the configuration page, confirm the following: ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/azsecscore1.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) - **Client Key:** Paste the [Application (Client) ID](/docs/azure-security-score#clientid) generated previously. - **Client Secret:** Paste the [Client Secret](/docs/azure-security-score#secret) generated previously. - **Token URL**: Replace placeholder with your [Directory (Tenant) ID](/docs/azure-security-score#tenantid). - **Subscription ID:** Paste the [Subscription ID](/docs/azure-security-score#subscriptionid) noted earlier. - **Event Types**: Preselected for all the event types that integration pulls. - **Fetch Subscription Owner ID:** Enable this option to fetch the additional Subscription Owner ID for the User type. > [!NOTE] > NOTE > > The Subscriptions event type is mandatory for configuring all other event types (i.e. Secure Score, Secure Score Control, Assessments and Assessment Metadata) and is therefore non-editable in the UI. 1. Click on the **Test Connection** button once details are added. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/Screenshot 2026-01-22 at 10.36.36 AM.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A35%3A29Z&se=2026-10-30T12%3A35%3A29Z&sr=c&sp=r&sig=QTjgM7uD0e4BDFT6OI5xx48FVSboYZa%2F03lqsCKUyBs%3D) 2. Click on the **Submit** button once Test Connection is successful. ## 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 response code - 403 this might be possibly due to missing permissions. Ensure that all the required permissions are granted correctly as per the above-mentioned steps.