Forum Discussion
Default Sensitivity Label to be added to migrated files (from Local Network Server)
Hi Experts,
We are migrating our file-sharing services from a local network file server to MS Teams/SPO.
The requirement is to enable and give default sensitivity labels from the migrated files. Manually assigning sensitivity labels in over a TB of files is hectic and could be prone to error as well.
MS Purview MIP labels and label policies are configured, however, at present, only new documents and/or revised files are only having the sensitivity labels assigned.
Any suggestions, guide, and tips will be highly appreciated.
Thanks,
Rhey
5 Replies
We did used AvePoint Fly Migration, in case you're asking.
- I'm new to Purview, but I guess you could configure the default label on your SPO document libraries? I believe it should apply on the files migrated by Sharegate?
I would personally, but this might not work for you, use the most restrictive label that's suitable on the DL.- I tried dumping a few hundred test docs using ShareGate from a shared drive into the library with the default sensitivity label applied and the label didn't get applied (as expected) until I actually edited the docs. I'll see if a metadata change will trigger the label application.
Ellya_Gold Thanks for the input.
This is pretty much the case, although default sensitivity label is applied, the document/s must actually be edited, the saved for this label to kick-in.Guess, this will and still the way forward.
- We're looking at exactly the same scenario, using ShareGate to migrate Finance file share docs to Teams, a lot of which will need to be labelled as 'restricted' with encryption set on the label(s).
I'm wondering if Power Automate could change the file metadata to force labelling?
