--- title: "Microsoft Defender For Cloud" slug: "microsoft-defender-for-cloud" updated: 2025-03-18T22:53:00Z published: 2025-03-18T22:53:00Z canonical: "docs.databee.buzz/microsoft-defender-for-cloud" --- > ## 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. # Microsoft Defender For Cloud Microsoft Defender For Cloud is a cloud-native application protection platform (CNAPP) protects cloud-based applications from cyber threats and vulnerabilities. For more information, refer to [official documentation](https://learn.microsoft.com/en-us/azure/defender-for-cloud/defender-for-cloud-introduction). **Integration Method:** API **Tables**: Detection Finding (2004), Incident Finding (2005) This integration supports the following events. | **Event** | **Description** | | --- | --- | | Alerts | Retrieve a list of alerts data objects. | | Incidents | Retrieve a list of incidents data objects. | This integration supports the following versions. | Microsoft Graph REST API | v1.0 | | --- | --- | > [!NOTE] > **Note:** > > Microsoft Defender for Cloud is a continuously updated cloud service. As for this document preparation, the latest release was in [**February 2025**](https://learn.microsoft.com/en-us/defender-office-365/defender-for-office-365-whats-new#february-2025). ## Prerequisites - The user should have access to the [Azure portal](https://portal.azure.com/#home) with an account that has Global Administrator privileges. - The user should have access to the DataBee console. ## Configuration Overview 1. Generate client credentials with the required scopes. 2. Add the [Microsoft defender for Cloud data feed](/user-manual/docs/microsoft-defender-for-cloud#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 privileges. 2. In the search bar, search for **App Registrations** and select it. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-eggtmmv0.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-xvx2rwtx.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-6pqpf8dj.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-3er0lkx1.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) ### Add Endpoint Access Once the application is created, two 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 - [Alerts](https://graph.microsoft.com/beta/security/alerts_v2) - [Incidents](https://graph.microsoft.com/beta/security/incidents) #### 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/microsoft-defender-for-cloud-mar2025-image-vi36p6e0.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-j83c5tzy.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 4. Click on **Application permissions.** ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-p0dap1b9.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 5. The following permissions need to be granted for the one endpoint to function properly: | **Event** | **Permission** | **Permission Type** | | --- | --- | --- | | Alerts | SecurityEvents.Read.All | Application | | Incidents | SecurityIncident.Read.All | Application | 1. 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/microsoft-defender-for-cloud-mar2025-image-uqqm7zho.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 2. On the “API permissions page”, click **Grant admin consent** **for **. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-v4xp3lv5.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 3. Click the **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-sxk2sbyb.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 4. The required permissions are now added for the endpoints. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-er2ehguv.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-yuc2z5pw.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 3. Click on **New client secret**. Then “Add a client secret” window appears. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-cdir143o.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-ogrk8m8r.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) > [!NOTE] > Note: > > The user needs to re-create the client secret when it expires. 5. Click **Add**. Copy the Secret **Value** field for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-vxt7xy9x.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%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/microsoft-defender-for-cloud-mar2025-image-0oxby61r.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 2. Search for the **Microsoft Defender For Cloud** and click it as shown below. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-kiwmo9kf.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 3. Click on the **API Ingest** option for collection method. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-m92v42bo.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-8uu5yjfb.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 5. In the configuration page, confirm the following: - Authorization Method: OAuth2 - Client key: paste **Application (client) ID.** - Client secret: paste the **Secret value.** - Token URL: replace placeholder with the **Directory (Tenant) ID** generated earlier. - Event Types: preselected for all the event types that integration pulls. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-mar2025-image-29e8v4ez.png?sv=2026-02-06&spr=https&st=2026-10-30T11%3A33%3A22Z&se=2026-10-30T12%3A33%3A22Z&sr=c&sp=r&sig=melzkqnIbNRF8XdluT5h4M0AQz1UO24medqoxb5u0%2FE%3D) 1. Click **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 response code - **403** this might be possibly due to missing permission. Ensure that all the required permissions are granted correctly as per the above-mentioned steps.