Forum Discussion

lsuryadevara's avatar
lsuryadevara
Icon for Microsoft rankMicrosoft
Feb 20, 2025

Purview not picking up Sensitivity Labels built from Information Protection layer

One of my customers has inquired about the visibility of sensitivity labels in the Purview Portal, as they are not appearing for any of their data sources. They attempted to propagate it from the Information Protection layer and could see them in their Fabric Lakehouse but not in Purview. Has anyone faced a similar issue or have any inputs?

5 Replies

  • Thank you so much luchete ! I will help them try Dataverse, as their alternative storage layer and will let you know!

    • luchete's avatar
      luchete
      Iron Contributor

      Great, keep me updated please!

      Regards!

  • luchete's avatar
    luchete
    Iron Contributor

    Hi lsuryadevara,
    I’ve had a similar issue before. It’s possible that the sensitivity labels aren’t being fully synchronized between the Information Protection layer and Purview. One thing to check is whether the labels have been published and are correctly assigned to the data sources in Purview. Sometimes it takes a bit of time for the labels to appear in Purview after being set up in Information Protection. If everything is configured properly, try syncing again or verify that the right permissions are set for the labels to be visible in Purview.

    Regards!

    • lsuryadevara's avatar
      lsuryadevara
      Icon for Microsoft rankMicrosoft

      Hi luchete Thank you so much for responding. Customer has been waiting for a long time. We also tried giving the users admin permissions on both Information Protection layer and the data layer to see if that would help, but nothing seems to work. Should we consider Data verse as a storage layer to receive these changes?

      • luchete's avatar
        luchete
        Iron Contributor

        lsuryadevara,

        Since you’ve already tried admin permissions and it hasn’t resolved the issue, as you've said, it may be worth looking at alternative storage layers, such as Dataverse. If your customer’s data sources are compatible with Dataverse, it could be a good idea to consider it as a potential storage layer for sensitivity labels.

        Dataverse might offer more seamless support for these types of changes. If you're still experiencing issues after considering this, it could also help to check if there are any specific configurations or settings that need to be aligned between the layers for full synchronization.

        Regards!

Resources