Yes, it is recommended to first do a requirement engineering and see what labels and policies are required and then start doing a test with few users internally to perform initial validation and gather more requirements and then go for second sample and make sure include few users from each departments and then continue and add more users.
Azure Information Protection - Starting with 1 label to prevent data loss
Hi y'all,
Hope you are enjoying your weekend!
So please help us with the following:
One of our customer would like to start with Azure Information Protection.
The whole implementation could require months of work.
Is it possible to start with 1 default label to prevent data loss?
In the Microsoft documentation we see the following advice:
Unless you have very strict and concrete requirements for protection already, start
with “All users in my org -> Co-Owner (Full Control)”. It gives you 90% of the
protection with 10% of the effort, and most leaks would be prevented by this policy.
So will this suite our purpose?
How will this work? Is there any encryption involved?
It's about 9000 Microsoft 365 E3 users.