Governed access to Azure Blob Storage for your teams and partners
Collaboration, access control and visibility on the containers you already have
Share containers with colleagues, partners and customers, each with a permission, an end date and a reason. People work in a web explorer without an Azure role, nobody receives a storage key, and every file operation is attributed to a person. Your files stay in your containers.
Microsoft Entra ID No Azure roles or storage keys to hand out Free plan, no credit card
Blob Web Explorer: your teams and partners work on your Azure Blob containers in a familiar web explorer.
Why teams switch
Azure Blob Storage is built for applications, not for people.
When people need the files, access gets improvised. Blob Web Explorer adds the access and collaboration layer on top of your containers, while IT keeps control.
Today Access is improvised
Each request for files becomes an Azure role to grant or a ticket for IT
Storage keys and SAS links travel by email, with no owner and no end date
Partners get an SFTP server someone has to maintain
Nobody can say who has access to what, or who downloaded what
With Blob Web Explorer
Each access has an owner, a permission and an end date
Partners and business users work in a browser, without an Azure role
Shares never go beyond the owner's own access: their Azure RBAC rights, or the SAS URL or connection string they hold
File and sharing operations attributed to a person
How it works
Up and running in three steps.
No data migration: Blob Web Explorer works with the containers you already have.
Connect your containers
Link existing containers with your Azure account, a SAS URL or a connection string, or discover them directly from Azure.
Give the right access
Share each container by email with read or write access and an end date. With Enterprise, also assign Administrator, Contributor or Reader roles from Microsoft Entra ID.
Work and keep oversight
People search, preview, upload and download in their browser. You review who has access, follow the activity log and see storage usage.
What you get
Collaboration, access control and oversight, in one web explorer.
Collaboration
Work with partners without handing out keys
Share a container by email with read or write access, start and end dates and a reason. Recipients need no Azure account or role and never receive the SAS URL or connection string. A share never outlives the access of its container, and you can disable one recipient without affecting the others.
People who only need the files get them without a role on your storage accounts. With Enterprise, they sign in with Microsoft Entra ID and receive the Administrator, Contributor or Reader role you assign from your tenant, and people who already have Azure access find their containers and link them in a few clicks.
Know who has access, who did what, and what you store
Every share shows its owner, permission, dates and reason, which keeps access reviews simple. File and sharing operations are recorded with user, action, outcome, time and IP address, with CSV export. Usage & costs shows container sizes, inactive data and indicative costs.
Search by file name or folder path across every container you can access, even in different storage accounts. Then preview images, PDF, video and text, upload by drag and drop (up to 195 GiB per file with Enterprise) and download several files as a ZIP. Search uses an index refreshed on demand; it does not read file contents.
No. Blob Web Explorer connects to your existing Azure Blob containers. Your files stay where they are.
Can our team use Microsoft Entra ID?
Yes. With Enterprise, your users sign in with your Microsoft Entra ID, and you assign the Administrator, Contributor and Reader roles from your own tenant.
Do the people we share with need Azure permissions?
No. Recipients sign in to Blob Web Explorer and open the containers shared with them, without any Azure role. A share covers a whole container and uses the SAS URL or connection string the owner linked it with; recipients never receive that credential. Sharing is bounded by the owner's access: what they can do through Azure RBAC or the SAS URL or connection string they provide. Containers linked with a personal Azure account follow that person's Azure permissions and cannot be shared. How access works.
How is this different from Azure Storage Explorer or the Azure portal?
Blob Web Explorer works alongside them. Azure Storage Explorer and the Azure portal remain the tools to administer storage. Blob Web Explorer serves the people who use the files and the owners who share them: named, time-bound container shares, application roles that need no Azure role on your storage accounts, a search by file name and path across containers and activity attributed to each person, in a browser. See which tool fits which audience.
Can we review who has access to our containers?
Yes. Each share shows its recipient, permission, start and end dates and optional reason, and the owner can disable it at any time. Activity records show who uploaded, downloaded, deleted or shared what. They are operational records for oversight and access reviews, not an immutable compliance archive. Access reviews.
Does it work with Azure Data Lake Storage Gen2?
Yes, through the Blob endpoint with a virtual folder model. Native directory ACL management is not provided in the interface.
Can we try it before buying?
Yes. Start with the free plan on your own containers. For Enterprise, contact us and we can give you access to an enterprise demo environment for a week.
Get started
Try Blob Web Explorer on your own containers.
Create your free account and link your first container in minutes. A question about Enterprise or pricing? Write to us.
