Reconsent for sensitivity label scanning

Last updated Aug 17, 2026 Consent Scanning

AI summary

Microsoft changed the sensitivity labels API that Rencore Governance uses, requiring a switch to a new endpoint with different permissions. Every connected Microsoft 365 tenant must reconsent or sensitivity label scanning will fail and your data will become stale. You only need to redo the existing consent you already granted through Environment Settings.

Microsoft recently changed the API that Rencore Governance uses to collect the Microsoft 365 connector inventory for Sensitivity Labels. To keep scanning this area, Rencore Governance is switching to a different endpoint. The new endpoint needs permissions that your existing consent does not cover, so every connected Microsoft 365 tenant must reconsent, or scans for this area may fail and stop once the change is live.

Info: This change only affects the Microsoft 365 connector and specifically the Sensitivity Label scanning. It does not require you to set up anything new. You only need to redo a consent you have already granted.

Do you need to take action?

Yes. This reconsent is required for every Microsoft 365 tenant connected to Rencore Governance, regardless of whether you have noticed scan failures yet. Depending on what you originally consented to, reconsent to one of the following, whichever you already have in place:

Global Consent
Security and Compliances

To reconsent, you will need to:

Go to “Environment Settings”.
Click on the “Ellipses Menu” ([…]).
Click on “Manage Consent”.
Locate the consent you originally granted, either “Global Consent” or “Security and Compliance”.
Reconsent using the same option you already had in place. There is nothing new to configure.

Questions about this change

Why is this happening now?

Microsoft changed an API endpoint. Switching to the new endpoint ensures Rencore Governance continues to collect accurate, up-to-date Sensitivity Label data.

What happens if I do not reconsent?

Microsoft 365 scans for Sensitivity Labels will not work as expected, and sensitivity label data will not be updated; however he rest of M365 data will be updated.

Will I lose any data?

No. Your existing data is not lost, but it will become stale until you reconsent and scanning resumes.

Does this affect anything else?

Yes. Any connected feature that relies on Sensitivity Label inventory data, such as policies and reports, will be affected by the stale data until you reconsent.

Warning: Until you reconsent, connected policies and reports that depend on Sensitivity Label inventory data will continue to operate on stale data.

Frequently asked questions

Do I need to reconsent my Microsoft 365 tenants for sensitivity label scanning?

Yes. Every Microsoft 365 tenant connected to Rencore Governance must reconsent, even if you have not seen scan failures yet. The new endpoint needs permissions that your existing consent does not cover.

How do I reconsent for sensitivity label scanning?

Go to Environment Settings, click the Ellipses Menu, and click Manage Consent. Locate your original consent, either Global Consent or Security and Compliance, and reconsent using the same option. There is nothing new to configure.

What happens if I do not reconsent for sensitivity label scanning?

Microsoft 365 scans for Sensitivity Labels will not work as expected, and Sensitivity Label data will not be updated. The rest of the Microsoft 365 data will still be updated.

Will I lose existing sensitivity label data if I do not reconsent?

No. Your existing data is not lost, but it becomes stale until you reconsent and scanning resumes.

Which policies and reports are affected until I reconsent?

Any connected feature that relies on Sensitivity Label inventory data, such as policies and reports, keeps operating on stale data until you reconsent.

Was this page helpful?