azure data.md

Microsoft Azure

The Dropzone platform integrates with Microsoft Azure to support investigations with Azure Log Analytics (KQL queries), Azure Activity Log when no Log Analytics workspace is configured, and Azure Resource Management for querying compute, network, container, and monitor resources. This integration is separate from Microsoft Sentinel and Microsoft 365/Defender; you may use both the Sentinel and Azure integrations concurrently.

During investigations, the integration uses the service principal to run KQL against your Log Analytics workspaces (e.g. sign-in logs, alerts, custom tables) and to read Azure Activity Log for configured subscriptions so the assistant can correlate who did what and when. It also calls Azure Resource Manager to list and describe VMs, resource groups, networks, AKS clusters, and other ARM resources. All access is read-only.

Integration Overview

To enable these integrations you will perform the following actions:

See the Microsoft Integrations page for instructions on how to register a new application, locate your Client ID and Tenant ID, and create a Client Secret.

{% hint style="info" %} When registering the application, set the "Supported account types" to "Accounts in this organizational directory only" and leave "Redirect URI" blank. No API permissions are required. {% endhint %}

Assign Azure RBAC Roles

Your service principals must be configured so that Dropzone can query Log Analytics and list resources in your subscriptions. Dropzone AI can access both subscriptions and Log Analytic Workspaces, but each requires different role permissions.

For each Azure subscription you want Dropzone to be able to access, do the following:

Select your subscription

Click on Access control (IAM)

Add a role assignment

The Reader role will allow Dropzone to see all resource metadata, resource groups, and subscription-level Activity Log within the subscription. To limit access, you may use a dedicated app registration, scope Reader to specific resource groups where possible, or exclude highly sensitive subscriptions from the configured list.

Click Select members

Assign members

Click Review + assign

Repeat for each subscription.

For each Log Analytics workspace you want Dropzone to be able to access, do the following:

Navigate to Log Analytics Workspace

Select your workspace

Click on Access control (IAM)

Add a role assignment

Select your role

Click Select members

Assign members

Click Review + assign

Repeat for every Log Analytics workspace you will use.

Locate your Subscription IDs and Workspace IDs

The Dropzone integration requires Subscription and Workspace IDs to enable.

{% hint style="info" %} If you are using the [Dropzone Azure scanner], you will not need a Workspace ID, as it will automatically discover workspaces and table schemas for the configured subscriptions. {% endhint %}

To obtain your Subscription ID, do the following:

To obtain your Workspace ID, do the following:

Copy the Workplace ID

Enable Microsoft Azure

To enable the Data Source integration, you will need the following information:

Dropzone Field Source
Tenant ID The Directory ID copied earlier
Client ID The Application ID copied earlier
Client Secret The Client Secret Value copied earlier
Subscription ID The Subscription/Workspace IDs copied earlier

To enable the Data Source integration, do the following:

Integrations Dropdown

Click Available

The Microsoft Azure Configuration

After saving, run the integration's test connection (or validation) to confirm credentials and permissions. If you use the Azure scanner, run the scanner for this integration so that workspaces and table schemas are discovered. The integration will then use those workspaces for Log Analytics queries.

If you have any errors, contact your Dropzone AI support representative.

Troubleshooting

Symptom Check
"Credentials are incomplete" or auth errors Verify Tenant ID, Client ID, and Client Secret; ensure the secret has not expired.
"Failed to list resource groups" Ensure Reader is assigned on that subscription; role assignment can take a few minutes to propagate.
"Failed to query Azure Log Analytics" or 403 on workspace query Ensure Log Analytics Reader is assigned on that specific workspace; confirm the workspace ID in config matches the workspace.
Activity log query fails Ensure Reader is assigned on the subscription (subscription-level Activity Log is covered by Reader).