---
title: "Microsoft Defender for Cloud Apps"
slug: "microsoft-defender-for-cloud-apps"
updated: 2025-07-01T15:58:45Z
published: 2025-07-01T15:58:45Z
canonical: "docs.databee.buzz/microsoft-defender-for-cloud-apps"
---

> ## 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 Apps

Microsoft Defender for Cloud Apps helps secure your cloud applications across Microsoft 365 and other SaaS providers. Defender for Cloud Apps was previously known as Microsoft Cloud App Security. For more information refer to the [Microsoft product page](https://learn.microsoft.com/en-us/defender-cloud-apps/).

**Integration Method:** API

**Tables:** Account Change (3001), Authentication (3002), Detection Finding (2004), Entity Management (3004), File System Activity (1001)

This integration supports the following events.

| **Event** | **Description** |
| --- | --- |
| Entities | Get a list of users & accounts for your organization |
| Activities | Get a list of activities regarding access and password changes |
| Alerts | Get a list of alerts that requires immediate attention |

This integration supports the following versions.

| Microsoft Defender for Cloud Apps API Version | v1 |
| --- | --- |

> [!NOTE]
> **Note**:
> 
> Microsoft Defender for Cloud Apps 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-cloud-apps/release-notes).

## Prerequisites

- The user should have access to the [Azure](https://portal.azure.com/) portal with an account that has the **Global Administrator** privilege.
- The user should have access to the DataBee console.

## Configuration Overview

1. Create an application with required permissions to fetch the data.
  1. [Create an Application](/user-manual/docs/microsoft-defender-for-cloud-apps#create-an-application)
  2. [Add Endpoint Access](/user-manual/docs/microsoft-defender-for-cloud-apps#add-endpoint-access)
  3. [Create the Client Secret](/user-manual/docs/microsoft-defender-for-cloud-apps#create-the-client-secret)
2. Add the [Microsoft Defender for Cloud Apps data feed](/user-manual/docs/microsoft-defender-for-cloud-apps#databee-configuration) in the DataBee console with the below parameters.

| **DataBee Parameters** | **Azure Parameters** |
| --- | --- |
| API Base URL <instance> | [API URL](/user-manual/docs/microsoft-defender-for-cloud-apps#get-api-url) |
| Client Key | [Application (client) ID](/user-manual/docs/microsoft-defender-for-cloud-apps#create-an-application) |
| Client Secret | [Client Secret Value](/user-manual/docs/microsoft-defender-for-cloud-apps#create-the-client-secret) |
| Token URL <tenant_id> | [Directory (tenant) ID](/user-manual/docs/microsoft-defender-for-cloud-apps#create-an-application) |

## Azure Configuration

### Create an Application

1. Log on to [Azure](https://portal.azure.com/) portal with an 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-apps-changed-default-values-image-lytee5sx.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%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-apps-changed-default-values-image-9kd31ja1.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%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-apps-changed-default-values-image-q56w2yvb.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%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-apps-changed-default-values-image-s1z37e94.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)

### Add Endpoint Access

Once the application is created, permissions should be provided to get data. This section details how to configure and add permission to the required endpoints.

#### Add Permissions

1. Select the application registered in the [previous step](/user-manual/docs/microsoft-defender-for-cloud-apps-june25#create-an-application).
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-apps-changed-default-values-image-g85emav9.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
3. Click on **APIs my organization uses** and then search for **Microsoft Cloud App Security**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-68wbr0m7.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
4. Select **Microsoft Cloud App Security** and then click on **Application permissions**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-xsiiwpic.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
5. The following permission needs to be granted, which is common for below events:

| **Event** | **Type** | **Permission** |
| --- | --- | --- |
| Entities | Application | Investigation.read |
| Activities | Application | Investigation.read |
| Alerts | Application | Investigation.read |
6. In the **Select permissions** search bar, enter the **investigation.read** permission as shown below, and check the box to include them and click on **Add permissions** button.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-8tyrbpsq.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
7. On the “API permissions” page, click on the **Grant Admin Consent for <tenant>**, and then click on **Yes** button on the consent confirmation. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-z2oby88m.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
8. The required permissions are now added for the endpoints. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-7iualaq0.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)

### Create the Client Secret

The final step to accessing the APIs is creating a Client Secret. To create it from the Azure Portal:

1. Select the application created in the [previous step](/user-manual/docs/microsoft-defender-for-cloud-apps-june25#create-an-application).
2. Under **Manage**, click **Certificates & secrets**, and then click on **Client secrets**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-gy0s1ooa.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
3. Click **New client secret**. The “Add a client secret” window appears. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-mjxnm4mb.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
4. In “Add a client secret” window:

> [!NOTE]
> **Note**:
> 
> The user needs to re-create the client secret when it expires
  - Enter a ‘Description’ for this client secret and select the desired expiry period from the ‘Expires’ drop-list.
  - Then click on **Add** to create the client secret.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-3fi2bnyo.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
5. Copy the **Value** fields for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-vsz37t73.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)

### Get API URL

1. Open [Microsoft Defender Portal](https://security.microsoft.com/) and navigate to **Settings** and select **Cloud Apps**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-xkpquxt6.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
2. Go to **System** > **About** and copy the **API URL** value for later use. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-mc8mbg7x.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%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-apps-changed-default-values-image-hlscbyep.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
2. Search for **Microsoft Defender for Cloud Apps** and click it as shown below.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-23i38gac.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%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-apps-changed-default-values-image-3a0h1e1u.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
4. Enter feed contact information and click **Next**. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-w8ekdwhz.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
5. In the configuration page, enter the following:
  - **API Base URL:** This is the base URL that DataBee will interact with. Replace <instance> value based on the API URL value.
  - **Authorization Method**: OAuth2
  - **Client Key:** Paste the Client ID generated earlier in the Azure portal.
  - **Client Secret**: Paste the Client Secret value generated earlier in the Azure portal.
  - **Token URL:** Replace <tenant_id> with your Directory (Tenant) ID.
  - **Event Types:** Preselected for all the Event Types the integration pulls. ![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-22zo9tkm.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
  - Before submitting the data source, click on the **Test Connection** to verify that the credentials are valid and the connection is successful.

> [!NOTE]
> **Note**:
> 
> If the test connection fails, the Submit button will remain disabled. Onboarding cannot proceed until the issue is resolved and the test connection is successful.

![](https://cdn.document360.io/04e48772-4346-44a4-aa69-043eca42257c/Images/Documentation/microsoft-defender-for-cloud-apps-changed-default-values-image-4palaagn.png?sv=2026-02-06&spr=https&st=2026-11-15T00%3A04%3A51Z&se=2026-11-15T01%3A04%3A51Z&sr=c&sp=r&sig=xyDVUee%2BXzvhaS449HSUVakul17hKvQbH3VIB%2BR08%2F8%3D)
6. 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 a response code – **403** error**,** this might be possibly due to missing permission. Ensure that all the required permissions are granted correctly as per the above-mentioned steps.

#