New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downloading pst files - Forbidden error #966
Comments
Sorry, missed the download differentiation. |
@chellooo20 what permissions does your SAS URI have? Let me know if you need help figuring it out. |
The SAS URL is the one I receive from the Office 365 Admin Console. How can I tell what permissions it comes with? |
You'll need to look for the query parameter That SAS URI has read and list permissions, because it only has an |
https://------.blob.core.windows.net/ingestiondata?sv=2015-04-05&sr=c&si=IngestionSasForAzCopy201810221206071580&sig=---- This is the one I have to work with. |
Ok, that SAS URI is getting it's permissions from an ACL. We can use Storage Explorer to find out what those permissions are then! To do so, right click on your container and click "Manage Access Policies...", then look for the policy with the Id |
I don't have the permissions to check any policies. The container is accessible from the Office 365 admin console but was not set up by us. When I right click on the container no 'Manage Access Policies' shows up. |
We'll try to start a ticket with Microsoft. We don't have an Azure subscription either. |
@chellooo20 , were you able to make progress on this? |
Closing due to lack of reply. Please open a new issue if you still have problems. |
Storage Explorer Version: 1.5.0.
Platform/OS: Windows
Architecture: ia32
Bug description
Trying to download pst files uploaded with azure copy tool I am getting a forbidden error message.
Steps to Reproduce
Expected Experience
Expected outcome would be file being downloaded to local drive.
Actual Experience
Download doesn't start. REceive this error message
Additional Context
I connected to container using a SAS URL provided by the Office 365 console.
The text was updated successfully, but these errors were encountered: