No storage access of its own
Blob Web Explorer never reaches your storage with its own identity. Each linked container uses the access you provide: your Azure account, a SAS URL or a connection string.
Security and data protection
Your files stay in your containers. Your Azure rights stay in charge.
Blob Web Explorer gives people a simple way to work with Azure Blob Storage without weakening the controls your IT team already relies on.
No storage identity of its own Microsoft Entra ID roles Private network option Activity records
Access
Access that follows your Azure permissions.
Azure account links stay personal
Containers linked with your Azure account follow your effective Azure permissions, are marked Personal, cannot be shared and show clearly when their access ends.
Microsoft Entra ID roles
In enterprise editions, users sign in with Microsoft Entra ID and receive the Administrator, Contributor or Reader role that you assign from your own tenant. A user without a role gets Reader access.
Time-bound sharing
Shares carry read or write permissions, start and end dates and an optional reason. A share is capped so it never outlives the access of its container, and owners can disable it at any time.
Activity records
File and sharing operations are recorded with user, action, target, outcome, time and IP address. Enterprise administrators review activity across containers.
Private network option
The Azure Marketplace edition (early 2027) can run fully inside your virtual network, reachable only through a private endpoint with private DNS.
Data
What is stored, and where.
| Data | Free and Pro | Enterprise | Enterprise in your Azure 2027 |
|---|---|---|---|
| Your Blob files | Always in the storage accounts you connect. Blob Web Explorer does not copy them to another storage platform. | ||
| Application data (users, linked containers, shares, search index, activity) | Hosted by us on Microsoft Azure | Hosted by us, or in a storage account you control | A storage account you provide in your subscription |
| Application | Shared service on Microsoft Azure | Dedicated instance on Microsoft Azure, in the region you choose | Your Azure subscription (Azure Marketplace) |
| Sign-in | Blob Web Explorer account | Your Microsoft Entra ID (other OIDC / SAML providers on request) | Your Microsoft Entra ID |
Encryption at rest and in transit is provided by Microsoft Azure for the storage and hosting services used. See the Privacy Policy for personal data processing and subprocessors.
Operations
Run by a dedicated publisher, with an exit path.
We operate the Free, Pro and Enterprise plans, monitor them and apply updates. Enterprise maintenance is announced five business days in advance.
- Support requests through the in-app Customer Hub or support@blobexplorer.com.
- Application data can be exported on request.
- Your Blob files never depend on Blob Web Explorer: they remain usable with any Azure tool.
- From early 2027, Enterprise customers can run the application in their own subscription through Azure Marketplace.
Does Blob Web Explorer need access to all our storage accounts?
No. It only works with the containers you link, using the access you provide for each one. With an Azure account link, access is limited to what that user can already do in Azure.
Can a share outlive the container's access?
No. A share's end date is capped to the end of the container's access, and containers linked with an Azure account cannot be shared at all.
Are activity records an immutable compliance archive?
No. They are operational records for oversight and troubleshooting. Review retention, backup and regulatory requirements separately.
How do we report a security issue?
Email support@blobexplorer.com with the details. Please do not include credentials or sensitive data in your message.