Configuration management

The “Configuration management” page provides a comprehensive overview of all the permissions available in the CoreView Configuration Manager App. From this section, you can monitor the status of each permission and manage any required actions.

All permissions linked to the app are listed along with their current status, which will be either:

• Granted
• Permission required

What to do if a permission shows as “Permission required”

If you notice a permission labeled as “Permission required” instead of “Granted,” it usually means that the permission has been newly added or recently updated in the CoreView Configuration Manager App.

In these cases, refer to this article for step-by-step instructions on how to add and grant the required permission. This ensures the app continues to function correctly and all Configuration Manager features remain fully operational.

Permissions can be:

• Application permissions: granted during the onboarding process and mandatory to use the Service Principal 
• Delegated permissions: if you see a “Permission required” message for a delegated permission, you have two options:
  • If you intend to use only the Service Principal: you can click “Ignore alert.” This will remove the banner.
  • If you want to use User Account Authentication: follow the steps below to grant the permission.

View permissions list

This page will display the permissions once the Configuration Manager App has been created.
If you don’t see the permissions, you can find all the steps to create the Configuration Manager App in this article. If any permissions are still required, you'll be notified. 

For example, a red box labeled “Permission required” will indicate missing permissions.

Alert banners

You automatically receive an in-app banner alert if any “Configuration management” consent is missing or needs configuration. 

Grant missing permissions

If permissions are missing and the “Required permission” status appears, follow the procedure explained below to grant them.

Assign required permissions

Step 1: access the Configuration Manager App section on the Azure Portal 

1. Go to Azure Active Directory > App registrations
2. Search for and select the application CoreView Configuration Manager

3. In the left menu, select API permissions

Step 2: click “Add a permission”

1. Open the “Request API permissions” page. 
2. Select the needed workload widget. 

To identify the needed workload, follow this procedure:

• In the column “Permissions” in the “Configuration management” page, search for the needed permission. 
• Now, view the “category” the permission belongs to. For example, “AccessReview.ReadWrite.All” belongs to the Microsoft Graph category. 

Step 3: select permission type

You can view the permission type in the “Type” column: 

1. Select the correct permission according to the type. For example, if the missing permission is of the “Delegated” type,  click “Delegated permissions”.

Step 4: search for and add the permission

• Use the search bar to find the required permission by pasting the name of the permission (such as AdvancedHunting.Read), which you can view in the “Permission” column in the “Configuration management” page:

• Select the permission using the checkbox.
• Click “Add permissions” to add it.

Step 5: grant permissions in bulk

Before granting admin consent, ensure that you have added all required permissions. For example, if CoreView identifies three required permissions, add all missing permissions first, and then use the bulk apply option by clicking “Grant Admin Consent for [Your Organization]”.

Although it may take until the next day for the permission status to change from “Permission required” to “Granted”, user account authentication is available for use immediately after permissions are applied.