Accessing blob storage using storage Explorer over a PE (SFTP Enabled )

Question

Hi,

I have a storage account (Blob) I'm able to access the storage account using azure storage explorer but I'm unable to delete files or create folders.

error

{ "error": { "code": "AuthorizationFailure", "message": "This request is not authorized to perform this operation.\nRequestId:6ea5241c-801f-0061-0d84-37f85e000000\nTime:2024-11-15T17:31:32.7577840Z" } }

---

Stranger still if I enable All networks on the Public network access. I can delete files. May not be a bug but for the life of me I cannot understand this behaviour.

Answer 1

Hi @weasle

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Issue: I'm able to access the storage account using azure storage explorer but I'm unable to delete files or create folders.

 

Solution: When you delete a file, it tries to connect via dfs.core.windows.net this Private DNS zone needs to be linked to the PE.

If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.

Please let us know if you have any further queries. I’m happy to assist you further. 

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members. 

Answer 2

Found what i think is the answer. When you delete a file it tries to connect via dfs.core.windows.net this Private DNS zone needs to be linked to the PE. Apologies been pulling my hair out over the weekend and went through the logs again and again till i noticed this. My bad.