Dec 08 2020
- last edited on
May 24 2021
I'm in the process of migrating a client from a file share to Microsoft 365. Part of the migration includes applying sensitivity labels. So far, we did an inventory and know what labels should be applied to which file.
What is the best way to apply labels at such a granular level? I tried using the Set-AIPFileLabel PowerShell cmdlet in a loop, but found it to be very unstable. It crashes over 50% of the time, taking down the entire PowerShell session. When it doesn't crash, it uses up a very large amount of memory that is not being released until the entire script ends.
Any feedback is much appreciated.
Dec 11 2020 07:41 AM
@Haniel Croitoru If your data is already migrated, you can use MCAS for automatic labeling.
Mar 24 2021 09:44 PM
Apr 07 2021 07:21 AM
Aug 01 2021 08:58 PM
Has anyone found anything from MS on this?
We too are receiving these random crashes. Initially we thought it was due to some complex hash tables we used to reset labels.
We made some minor mods but still randomly get these errors.
TRY/CATCH did not help. Any fixes found on your end?
Aug 06 2021 05:56 AM
We noticed this was worse when deleting files during the labeling process. Our workaround is to leave the files around until we've labeled them all, and then delete them. My guess is that there is some issue where the powershell commands are holding onto file handles and breaking if those files disappear.