What is Microsoft Azure? #
Microsoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through a global network of Microsoft-managed data.
Why Should You use the Microsoft Azure Connector? #
Lucidum uses the Microsoft Azure connector to retrieve data from Microsoft Azure virtual machines and Azure services, including Azure Active Directory, Azure Blob Storage, Azure Cosmos DBs, and Azure SQL DBs.
-
ensure virtual machines and services are managed per your security policies
-
monitor each endpoint and its status
How Does This Connector Work? #
Lucidum executes read-only requests to the REST API for Microsoft Azure and ingests only meta-data about Azure instances and services. Lucidum does not retrieve any data stored on your systems.
Prerequisite: Creating an Azure Application #
Before configuring the Microsoft Azure connector in Lucidum, you must a create a read-only application in Azure Active Directory that allows Lucidum to retrieve information from Azure.
Creating a Client in Microsoft Azure (5 minutes) #
1. Log in to the Azure Portal (https://portal.azure.com/ ) with an Azure AD global administrator account. |
|
2. Click Home > Microsoft Entra ID. |
|
3. In Overview page: |
|
4. In the Register an application page: |
|
5. In the <app name> page |
|
6. In the <app name> | Certificates & secrets page: |
|
7. In the <app name> | API permissions page: |
|
8. Click Home > Subscriptions. | |
9. In the Subscriptions page: |
|
10.In the Main pane <azure subscription>: |
|
11. In the Add role assignment page: |
|
12. In the Add role assignment page: |
|
13. In the Add role assignment page: |
|
14.In the Main pane <azure subscription>: |
|
15. In the Add role assignment page: |
|
16. In the Add role assignment page: |
|
17. In the Add role assignment page: |
|
Optional Prerequisite: Creating a Role for Azure Blob Storage #
NOTE: If the Azure connector ingests data from Azure Blob storage, ensure that your firewall safe-lists include the IP address of your Lucidum instance.
To access data about Microsoft Azure Blob Storage, you must define an additional role, Storage Blob Data Reader, and add it to the Lucidum read-only application in Azure Active Directory. To do this:
1. Log in to the Azure Portal (https://portal.azure.com/ ) with an Azure AD global administrator account. |
|
2. Click Home > Subscriptions. |
|
3. In the Main pane <azure subscription>: |
|
4. In the Add role assignment page: |
|
5. In the Add role assignment page: |
|
6. In the Add role assignment page: |
|
7. In the Main pane <azure subscription>: |
|
Troubleshooting Azure Blob Storage #
NOTE: If the Azure connector ingests data from Azure Blob storage, ensure that your firewall safe-lists include the IP address of your Lucidum instance.
If you see the error:
Exception:Not authorized to perform list blobs for any container!"
you must safe-list the IP address of your Lucidum instance.
Configuring the Microsoft Azure Connector #
To configure Lucidum to retrieve data from Azure:
-
Log in to Lucidum.
-
In the left pane, select Connector.
-
In the Connector page, select Add Connector.
-
Scroll until you find the Connector for Microsoft Azure. Click Connect. The Settings page appears.
Field | Description | Example |
---|---|---|
Azure AD API Version | This is an optional parameter. Specify the version of the Azure AD API you are using with your Azure AD instance. | 2021-08-01 |
Client ID | Enter the Client ID for the Lucidum application in Azure AD. Client ID is the unique identifier for the Lucidum application in Azure Active Directory. Client ID is also called Application ID. You captured this value in step #5 in the section above. If you select the KMS checkbox, Lucidum will use the URL specified in Settings > System Settings, in the Key Management page. | 5dab08ad-3948-4605-aa68-948333ee64819 |
Client Secret | Enter the Client Secret ID for the Lucidum application in Azure AD. You captured this value in step #6 the section above. If you select the KMS checkbox, Lucidum will use the URL specified in Settings > System Settings, in the Key Management page. | ************ |
Tenant ID | Enter the tenant ID. Tenant ID is a unique identifier for your instance of Azure AD You captured this value in step #5 in the section above. If you select the KMS checkbox, Lucidum will use the URL specified in Settings > System Settings, in the Key Management page. | 30930e4c-6cea-4c29-89d8-81e55978da47 |
Subscription ID | This is an optional parameter. Subscription ID represents your account with Microsoft. You captured this value in step #5 in the section above. If you specify a value in this field, Lucidum will fetch data only from the specified subscription. The default behavior is for Lucidum to fetch data from all subscriptions associated with the specified Tenant ID. | d25c1387-a93e-4a8e-a45a-8ed1298932c5 |
Services | Select one or more Azure services from which you want to ingest data. Services include:
|
|
To test the configuration, click Test.
-
If the connector is configured correctly, Lucidum displays a list of services that are accessible with the connector.
-
If the connector is not configured correctly, Lucidum displays an error message.
Source Documentation #
Creating an Application in Azure #
Required Permissions are:
-
User > User.Read.All
-
Directory > Directory.Read.All
-
AuditLog> AuditLogs.Read.All.
-
UserAuthenticationMethod > UserAuthenticationMethod.Read.All
API Documentation #
-
https://learn.microsoft.com/en-us/graph/api/resources/users?view=graph-rest-1.0
-
https://learn.microsoft.com/en-us/graph/api/resources/user?view=graph-rest-1.0
-
https://learn.microsoft.com/en-us/graph/api/resources/directoryobject?view=graph-rest-1.0
-
https://learn.microsoft.com/en-us/graph/api/resources/directoryaudit?view=graph-rest-1.0
-
https://learn.microsoft.com/en-us/graph/api/resources/authenticationmethod?view=graph-rest-1.0