Reconsent Required for Microsoft 365 Sensitivity Label Scanning

Microsoft recently changed the API that Rencore Governance uses to collect the Microsoft 365 service 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.

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

Reconsent to Security and Compliances or Global Consent

To reconsent, you will need to:

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

Frequently Asked Questions

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 don’t 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.