We managed to solve the issue. I don't know if this is a proper solution or a workaround. We were applying the sensitivity policy to Microsoft 365 groups.
The solution was to create a security group and assign the sensitivity policy to that group.
Hope this help people who have the same issue 🙂
1 best response
Accepted Solutions
best response confirmed by
GustavoAA (Brass Contributor)
We managed to solve the issue. I don't know if this is a proper solution or a workaround. We were applying the sensitivity policy to Microsoft 365 groups.
The solution was to create a security group and assign the sensitivity policy to that group.