Limitations of Azure Storage Explorer: Filtering and Renaming Challenges
Limitations of Azure Storage Explorer: Filtering and Renaming Challenges
Azure Storage Explorer simplifies managing Azure Storage data across Windows, macOS, and Linux platforms. Refer to Get started with Storage Explorer for more info.
However, there are nuances surrounding filtering and renaming functionalities that users should be mindful of.
Filter Functionality
Azure Storage Explorer lacks wildcard support, limiting search capabilities to prefixes only. This limitation can pose challenges when attempting to locate files based on substrings within the blob container.
Search blobs by prefix
Filter by prefix
The version used to test is 1.32.1
Utilising blob tags can aid in blob storage searches. It’s advisable to set blob tags accordingly, as discussed in Use blob index tags to manage and find data with .NET
To overcome these limitations, consider employing Azure AI Search to enable full-text search functionality on blob data. Refer to the post Search over Azure Blob Storage content for insights on indexing files for efficient data retrieval.
Renaming Files and Folders
Renaming files and folders within Azure Storage isn’t supported directly. One workaround involves cloning the file or folder and subsequently deleting the original, although this approach may result in the loss of version history.
Missing rename functionality, with only clone or delete options available for each blob:
An alternative solution is presented by Cerebrata offering a tool for renaming files and folders in Azure Storage. While untested, this tool provides an additional avenue for users encountering renaming challenges.
Conclusion
Despite its utility, Azure Storage Explorer presents limitations in filtering and renaming operations. Users should explore alternative solutions, such as Azure AI Search and external tools, to address these challenges effectively.
References
Enable content on a site to be searchable