Categories

This article covers the requirements to give consent for partial imports as well as activation for the Azure AD reports feature.  

 

I. Overview 

Because CoreView serves as a reporting and administrative proxy for Office 365, there may be times when a Tenant Administrator or Operator may be prompted to grant access to the resources, such as the one below. 

 

Graphical user interface, text 
Description automatically generated 

       

When this happens, there are two possible areas that need to be addressed. 

  • Attempt a re-consent using the URL supplied below,  
  • Delete CoreView's Application Permission Azure AD and then force a re-consent. 

 

II. Force the Consent Prompt 

A Tenant Admin can force a re-consent by opening an InPrivate browser session and then using an Office 365 account that has Global Admin permissions, pasting the following URL into the browser's address bar and pressing enter. 

 

 

Once you do this, you should be presented with the original consent dialogue. Scroll to the bottom and okay these permissions. Once this has been done, no other user logging into CoreView should receive the Admin Approval notice shown in Section I of this article. 

 

III. CoreView Application Permissions in Azure 

During enrollment, application permissions are created for CoreView in Azure AD. When customers are experiencing ongoing prompts for Admin Approval, then the original permissions need to be deleted and recreated. Below are the instructions on how to perform this action.  

Note: This must be performed by a user with an Office 365 account with Global Admin rights. 

  • Under Admin Centers section available in the left-hand side of the screen, click on Show All button and then on Azure Active Directory > Enterprise Applications > All applications 
  • Set your filters to show all applications, with any Status and any Visibility 
  • Search for CoreView or 4ward365 Microsoft API 
  • Delete the permission. 
  • Execute the step described in Section II. 

It can take up to 24 hours to be activated on the Microsoft side. After that, CoreView can retrieve the audit data during the full import executed once per day.  

 

Note: If the CoreView application was mistakenly added to Azure AD by someone without the Global Admin role, CoreView Operators will not be able to login unless the application is first removed from Azure AD and re-added under the Global Admin credentials.