Fix AzCopy HTTP 403 Errors When Uploading PST Files to Microsoft 365
Question details
The user needs to upload PST files for a Microsoft 365 network import after AzCopy returns HTTP 403.

- Product
- Microsoft 365 network import with AzCopy
- Device & OS
- not provided
- Scenario
- A new batch of PST files is being uploaded using a newly generated shared access signature (SAS) URL.
- Observed behavior
- AzCopy uploads fail with an HTTP 403 response.
Have the source PST path and the SAS URL from the Microsoft 365 import workflow ready, and check which AzCopy version you are using. Treat the SAS URL as a credential and do not share it in support requests.
Verify the SAS URL and AzCopy upload command
Use this approach when a new PST upload batch fails after a SAS URL is generated.
Confirm that the source path contains the PST files, then return to the Microsoft 365 import workflow and copy the complete SAS URL for the destination.
In the import workflow, verify that the SAS URL is current and intended for uploading to the destination. If it may have expired or was copied incorrectly, generate and copy a new URL.
For AzCopy v10, run a command such as azcopy copy "C:\PST" "<full SAS URL>" --recursive=true. For the older AzCopy version, use its supported syntax, such as AzCopy.exe /Source:"<PST location>" /Dest:"<SAS URL>" /V:"<log location>" /Y.
Check the AzCopy output and log for the failed request. If HTTP 403 continues with a current URL, test the upload from another network and ask your administrator to check network or storage access restrictions.

Use WPS Office for Everyday Document Work
WPS Office is a free, lightweight alternative for working with Office documents in a familiar interface. Its format compatibility helps you move everyday document work across from Microsoft Office; it does not fix AzCopy errors or perform Microsoft 365 PST imports.

Frequently Asked Questions
What does HTTP 403 mean during an AzCopy upload?
HTTP 403 means the destination refused the request. Check the complete SAS URL, its validity and upload access, and any network or storage restrictions.
How do I replace an expired SAS URL?
Return to the Microsoft 365 import workflow, generate or obtain a current SAS URL, and use the complete new URL as the destination in your AzCopy command.
Which AzCopy command should I use for PST files?
Use azcopy copy with the PST source and full SAS destination for AzCopy v10. Older AzCopy versions use different syntax, including /Source and /Dest switches, so check your installed version before running the command.
What should I do if a new SAS URL still returns HTTP 403?
Review the AzCopy output and log, confirm that the destination URL was copied in full, and test from another network. If the error persists, ask your administrator to check access restrictions.




