In Microsoft Azure, a resource represents any managed entity, such as a virtual machine, a storage account, or a database, that you create and manage within the Azure environment. These resources are grouped into Resource Groups, which provide a way to manage them collectively. Azure Resource Manager is the platform that enables you to deploy and manage these resources. For more information, refer to Microsoft’s official documentation.
Integration Method: API
Tables: Device Inventory Info (5001), Cloud Resource Inventory (5023)
This integration supports the following events.
Event | Description |
---|---|
Virtual Machines | Gets a list of all the virtual machines in the subscription. |
Virtual Machine Scale Sets | Gets a list of all VM Scale Sets in the subscription, regardless of the associated resource group. |
Cloud Services | Gets a list of all cloud services in the subscription, regardless of the associated resource group. |
This integration supports following versions.
Azure Resource Logs API version | VMs and VM Scale Sets – 2024-07-01 Cloud Service – 2022-09-04 |
Note:
Azure Resource doesn’t support traditional versioning system. Instead, it is a continuously updated cloud service. As for this document preparation, the latest release was on 1st April 2025.
Prerequisites
The user should have access to Azure portal with an account that has Global Administrator privileges.
The user should have access to the DataBee platform.
Configuration Overview
Create an application with required permissions to fetch the data.
Add the Azure Resource Logs feed in the DataBee console with the required Client credentials.
DataBee Parameters
Azure Resource Parameters
Client Key
Client Secret
Token URL (<tenant_id>)
Subscription ID
Azure Configuration
Create an application
Log on to Azure portal with an account that has the Global Administrator privilege.
In the search bar, search for App Registrations and select it.
On the “App registrations” page, select New registration, then “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.
Assign Reader Role to Subscription
Login on to Azure portal with an account that has the Global Administrator privilege. In the search bar check for subscriptions and select it.
Select the Subscription name as shown below.
On the Overview page, copy the Subscription ID for later use.
Assigning a Reader Role to the Subscription. Click on Access Control and select Add
Permission Name: Reader
Type: RBAC
Scope: Subscription
Under Role select the Reader role and click Next.
Under Members, click on Select members to add members and add the application created in previous step and click on Select.
Once a member is added click on Review + Assign to add reader role to subscription for accessing the APIs.
Create the Client Secret
The final step in accessing the APIs is creating a Client Secret. To create it from the Azure Portal:
Select the application created above.
Under Manage, Click Certificates & Secrets, and then Client Secrets.
Click New client secret. Then “Add a client secret” window appears.
On “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.
DataBee Configuration
Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Source button.
Search for the Azure Resource Logs and click it as shown below.
Click on the API Ingest option for collection method.
Enter feed contact information and click Next.
In the configuration page, confirm the following:
API Base URL: this is the base URL that DataBee will interact with
Authorization Method: OAuth2
Client Key: paste the Application (client) ID
Client Secret: paste the client secret Value.
Token URL: replace <tenant_id> placeholder with the Directory (Tenant) ID generated earlier.
Subscription ID: paste the subscriptionId.
Event types: preselected for all the events types the integration pulls.
Click Submit.
Troubleshooting Tips
Ensure the token is pasted correctly. Since you cannot view the token after the 1st time, re-create the token, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.
Ensure that permissions are added correctly, and the subscription is assigned reader role in order to make API calls.