- 28 Apr 2025
- 4 Minutes to read
- Print
- DarkLight
Azure Resources (Blob Ingest)
- Updated on 28 Apr 2025
- 4 Minutes to read
- Print
- DarkLight
Azure Compute Services are the core set of cloud computing services that allow you to deploy and manage workloads on Microsoft Azure. These services provide the infrastructure, tools, and platforms for computing and storage needs. For detailed information, please refer to the Microsoft’s official documentation.
Integration Method: Azure Blob
Tables: Device Inventory Info (5004), Cloud Resources Inventory Info (5023)
Event | Description |
---|---|
VM | Get the list of Virtual Machines configured in Azure Compute |
VM Scaleset | Get the list of VM ScaleSets configured in Azure Compute |
CloudServices | Get the list of Cloud services configured in Azure Compute |
Note:
Microsoft Azure is a continuously updated cloud service. As of this document preparation, the latest release was in September 2025.
Prerequisites
The user should have access to the Azure portal with an account that has the Global Administrator privilege.
The user should have access to the DataBee console.
Configuration Overview
Generate client credentials with the required scopes.
Add the Azure Resource Log data feed in the DataBee console with the below parameters.
DataBee Parameter
Azure Resource Logs Parameter
Client ID
Application (client) ID
Client Secret
Client Secret Value
Tenant ID
Directory (Tenant) ID
Blob Account Name
Storage Account Name
Blob Container Name
Container Name
Azure Queue Name
Queue Name
Azure Resource Logs Configuration
To create an Azure Blob storage, need to follow below steps.
Create an application
Log on to Azure with a user account that has the Global Administrator privilege.
In the search bar, search for App Registration and select it.
On the “App registrations” page click on the New registration. The “Register an application” window will appear.
On the “Register an application” window:
Under ‘Name’ enter your Application Name then click on Register to create the application.
On the app Overview page, copy the Application (client) ID and Directory (tenant) ID for later use.
Create client secret
Select the application created above.
Under Manage, click Certificates & secrets, and then click on Client secrets.
Click New client secret. “Add a client secret” window appears.
In “Add a client secret” window:
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.
Note:
The user needs to re-create the client secret when it expires.
Copy the Value fields for later use.
Create Storage Account
Navigate to the home page and search for the Storage accounts.
To create a new storage account, ensure the user has the necessary permissions to create one and follow the steps outlined here. To use an existing storage account, proceed to step 3.
Open the Storage accounts, locate and select the desired storage account. Copy the Storage Account Name for future reference.
Assign Role to Application
In storage account, assign the created Azure AD App to a Role that grants access to the storage blob.
Navigate to Access Control (IAM) under the Storage accounts and click on Add.
Assign the appropriate role for the Application.
Role
Description
Storage Blob Data Contributor
Allows read/write/delete access to blob objects.
Storage Queue Data Contributor
Allows to send/read/delete messages in queues.
Storage Account Contributor
Provides full control over the storage account.
In the “Add role assignment” page, use the search bar to type the desired role and select it from the list. Once selected, click Next.
Select the member for the role assignment.
Click on Select members.
Search for the application created during the app registration process and click on Select.
Click Next to continue.
Click Next to continue.
Click Review + Assign to finalize the role assignment.
To verify the role assignment
Navigate to Access Control (IAM) > Role assignments.
Search for the application and assigned role for storage blob would be visible.
Creating a Queue for Blob Storage
To read the data from blob storage we need a queue.
In the storage account, Click on Data storage > Queues.
Go to Queues and click on + Queue to create a new queue.
Enter a queue name and click on OK.
To set up event notification, go to the Events tab and click on + Event Subscription.
Provide EVENT SUBSCRIPTION DETAILS, TOPIC DETAILS and EVENT TYPES:
Enter the event name.
Choose Event Grid Schema as event schema.
Add System Topic Name if not added already.
Select Blob Created as the Filter to Event Types.
Select Storage Queue as the Endpoint Type.
Provide ENDPOINT DETAILS to configure the endpoint:
Click on Configure an endpoint option.
Select the appropriate ‘Subscription’ and ‘Storage account’ values.
Select the Select existing queue option and choose the queue created previously.
Click Select.
Click Create to finalize the event subscription.
Forwarding the Administrative logs to Blob Storage
To forward the Azure Activity logs of the administrative category to the blob storage account that you created, follow below steps.
Navigate to the home page and search for the Monitor App.
Navigate to the Activity log tab and click on Export Activity Logs.
Click on Add diagnostic setting.
Select the Administrative category and choose the Archive to a storage account. Fill the below details. Click on Save.
A new container will be created in your storage account, which will be used in the DataBee configuration.
DataBee Configuration
Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
Search for Azure Resource Logs and click it as shown below.
Click on the Azure Blob option.
Enter feed contact information and click Next.
In the configuration page, confirm the following:
Client ID: paste the Application ID.
Client Secret: paste the Secret Value.
Tenant ID: paste the Directory ID.
In the configuration page, confirm the Azure Blob Storage details:
Blob Account Name: paste the Storage Account name.
Blob Container Name: paste the Storage Container name.
Compression: none
Content Type: JSON Lines
Azure Queue Name: paste the Queue name.
Click Submit.
Troubleshooting Tips
In case of any permission errors, ensure that proper roles are assigned to the application in the storage created.