@cR0w Sorry no. We found this issue internally in early November. We couldn't resolve it internally so escalated to MS. After a lot of back-and-forth they emailed to say that they had confirmed the issue we were experiencing was a "known bug". It looks like they are going to roll the fix into the next update for Purview, they gave us a date of 6th Jan 25 but advised that it can take up to 2 weeks for changes to propagate world-wide.