We finished moving to Microsoft 365 and now have about 120 legacy PST files from old machines to bring into user mailboxes. I looked at the AzCopy network upload route and got a 403 error on the SAS URL before even starting. Is there a saner path?
How to perform PST to Office 365 migration?
Solved Cloud & Migration
AJ
Andrew Jackson October 10, 2019
2 replies
9,460 views
Reviewed by moderators
The 403 on AzCopy usually means an expired or region-mismatched SAS key from the compliance portal, and honestly the whole network upload flow is fiddly. Options ranked:
1
Small batches: Outlook import per user works but does not scale to 120 files.
2
Microsoft network upload: regenerate the SAS key fresh, upload with AzCopy v10 and map files in the CSV. Free but slow to babysit.
3
SysTools Office 365 Import: point it at the PST folder, map files to mailboxes and it uploads directly with resume support. For 120 files this is the route that finishes the same week.
Went with option 3 after the SAS key failed a second time. All 120 mapped and imported over two nights. Solved.