Update Azure Deployment Configuration to Prepare for Upgrade
Periodically, Alert Logic updates the policy corresponding to the RBAC roles required for Azure deployments. These updates, which Alert Logic announces in Alert Logic Console Release Notes, support new features and ensure your deployments continue to monitor your Azure assets.
Prior to your upgrade to Managed Detection and Response, ensure your Azure deployments are configured properly.
Check for and fix Azure credential problems
The most common issue with Azure deployments prior to upgrade is lack of credentials. For each of your Azure deployments, ensure that Role-Based Access Control (RBAC) is configured correctly with an app registration.
To check for this issue, browse to the Deployments page in the Alert Logic console, click an Azure deployment tile, and then click Azure Subscription. If the Active Directory ID and/or Application ID field is blank, you need to configure app registration and RBAC for the deployment.
To fix this issue, see the instructions in Configure App Registration and RBAC for Microsoft Azure Resources.
If you complete the configuration as described in Configure App Registration and RBAC for Microsoft Azure Resources, your Azure deployments should be ready to upgrade. You can optionally check for the following problems to prevent permission errors that can occur if your Azure deployment is not configured correctly.
If the migration precheck finds permission errors in your deployments, Alert Logic notifies you and advises you to check one or both of the following items. You must fix permission errors prior to upgrade.
To perform CIS benchmark checks, Alert Logic must have permission to access Microsoft Graph. If the correct permissions are not configured, the migration precheck reports a permission error that you must resolve.
To check for permissions to access Microsoft Graph:
- In the Azure portal, click Azure Active Directory.
- On the left panel, click App registrations, and then select your app registration.
- On the left panel, click API permissions.
- Check that your configured permissions look like this:
If permissions are missing, you must grant them.
To grant permissions to access Microsoft Graph:
- On the API permissions page in the Azure console, click + Add a permission.
- On the Request API permissions blade, click Microsoft Graph.
- Click Application permissions, and then in the list, select the following permissions:
- Click Application to see permissions in this category, and then select Application.Read.All.
- Click Group to see permissions in this category, and then select Group.Read.All.
- Click RoleManagement to see permissions in this category, and then select RoleManagement.Read.Directory.
- Click User to see permissions in this category, and then select User.Read.All.
- Click Add permissions, and then on the API permissions pane, click Grant admin consent for Default Directory.
- In the pop-up window, click Yes to allow the changes you made on the permissions.
To prevent or fix permission errors, another item to check is that an RBAC role is assigned to your app registration.
The following procedures assume the RBAC role is created already, as described in Configure App Registration and RBAC for Microsoft Azure Resources.
To check that the role is assigned to the app registration:
- In the Azure portal, click Subscriptions.
- In the Subscriptions blade, select the subscription you want Alert Logic to protect, and then click Access control (IAM).
- Click the Role assignments tab.
- Check that the RBAC role you created is assigned to the app registration.
If a role is not assigned to your app registration, you must assign it.
To assign the role to the app registration:
- On the Role assignments tab in the Azure portal, click +Add, and then click Add role assignment.
- Select the RBAC role you created.
- From the list, click the app you registered earlier.
- Click SAVE.