Error: Consent not found

If you have been using Microsoft Graph Data Connect for a while, you might have configured a recurring pipeline that has been running for several months. In that case, you might run into this error:

Operation on target <name> failed:
ErrorCode=UserErrorOffice365DataLoaderError,
'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,
Message=Office365 data loading failed to execute.
office365LoadErrorType: PermanentError.
Consent not found.
The consent for application [xx] was either never granted or expired.
Learn more at https://aka.ms/mgdcdocs/appconsent.,
Source=Microsoft.DataTransfer.ClientLibrary,'

The main error is really " The consent for application [x] was either never granted or expired.” If this is the first time you are running this pipeline, you could be missing the consent in Azure (it was not yet approved by your Microsoft 365 Administrator). If this was working before, it has likely been more than 6 months since it was approved, and the consent has expired.

The solution is simple, done in just 2 steps:

1. In the Azure Portal, go to the Microsoft Graph Data Connect application and update it.
2. In the Microsoft 365 Admin Center, approve the application update.

To update the application, search for the “Microsoft Graph Data Connect” service in the Azure Portal at https://portal.azure.com or navigate directly to https://aka.ms/MGDCinAzure to get started. Once there, click on the MGDC Application your created previously (that is the request for consent), click on Properties on the left navigation bar and then click on the “Update Properties” button. You do not need to change any of the properties.

After you update the consent request, you need to approve the update in the Microsoft 365 Admin Center. This process is described in item “1h. Approve the Microsoft Graph Data Connect Application” in the step-by-step guide.

Before you update the application properties in the Azure Portal, it will show in the list in the Microsoft 365 Admin Center as “Expired”. After you update the properties, it will show in the list as “Update Available”. Once you approve and everything is ready, it will show as “Approved.”

Just click on the app and follow the steps to approve it.

That is it! Now you can just run the pipeline again and everything will work as before. Until it is time to update the consent again in 6 months…

You can avoid this issue completely by keeping track of the MGDC Application consent date and updating it ahead of time. You can update the application and continue to use the earlier consent until the Microsoft 365 Administrator approves the new one, allowing for this consent rotation to be done proactively.

For more about MGDC for SharePoint, visit the main article at https://aka.ms/SharePointData.