Forum Discussion
Create directory in Azure Storage-different experience in Azure Storage Explorer vs Window ISE app
Hi
I observer different outcomes when attempting to create a directory on a container in ADLS Gen2.
My current permissions here are Reader and Contributor.
Azure Storage Explorer: I am authenticating using SSO. I am able to create directory in the storage container.
Windows ISE app: I have a script to create directory on the same storage container but I get a 403 error. I authenticate using SSO.
It is perplexing to me why I can perform this action in Azure Storage Explorer but not using a script in Windows ISE. I have the same permissions.
In another instance, I requested to be granted the role Storage Blob Data Contributor and then the same script worked.
Are there any differences when performing these actions in Azure Storage Explorer vs Windows ISE app.
4 Replies
- Have you tried Visual Studio Code (Free in the MS App Store)? I have left the ISE in the dust for this exact reason, when you use ISE not all commands execute the same way, it can be very annoying. I might be wrong, but once I moved to VSC I haven't had those issues. Every script I have authored in VSC has executed as expected on other hosts... barring any other PowerShell versioning quirk...
- Hi
I wanted to provide an update on this issue. Though I thought I was doing exactly the same thing in Storage Explorer and when running the script, it turned out that I was not. My authentication in the Explorer was at the storage accounts level. My authentication had the context of my access at storage account and blob container. When I set up a stand alone connection at only the blob container level, I noticed that I am not able to perform the operations.
The resolution was to modify my script. I provided the entire context that I was using in the explorer. Storage account> Container> directory
Both are set to authenticate against my official account . I authenticate using SSO
