AZURE BLOB STORAGE / MEET YOUR DESKTOP
Your containers.
A little closer.
MountMe brings private Azure Blob Storage to Windows with a read-only drive and a separate upload desk that keeps you in the loop.
A Windows drive for your Azure blobs.
Explore containers, open files, and seek through large objects without downloading the entire account first. The mounted drive uses a bounded memory cache and stays read-only. Choose one container or browse the containers your credential can access.
An opt-in write preview, too.
For one container, a separate staged write preview supports copy-in and editing files in place. Choose a local staging folder and hard limit; the Writeback Desk shows cloud confirmation after the local save. Confirmed staged copies are retained and count toward the limit. Rename/delete, temporary-file replacement saves, and live-provider writable validation remain future work.
Uploads with somewhere to look.
Use the separate Transfer Desk to send files, folders, or a drive's readable contents to an existing container. See the active file, accepted progress, committed totals, average useful speed, and active elapsed time. Uploads read from the original file without a second full-size staging copy.
Cancel now. Reconcile before continuing.
Cancellation stops local work and retains originals, completed blobs, and recovery records. Resume checks which blocks Azure still holds before sending more. If uncommitted blocks have expired, missing data has to be uploaded again. Keep source files at their original paths for recovery.
Existing blob? You choose.
Skip existing names, ask at each conflict, or choose conditional overwrite. Apply-to-all decisions make a large queue easier to handle. Replacement protects against a destination that changed after it was inspected. Skipping a name doesn't imply that its contents were compared.
Your account. Your access.
Connect with an Azure storage account key or SAS token. A container-scoped SAS can limit access to one container; its permissions determine whether you can browse, read, or upload. Keys and tokens stay in the app's session and aren't included in saved connection settings. Microsoft Entra sign-in isn't part of this milestone.
What has been tested?
A small live Azure test cancelled after an accepted block, resumed from saved recovery state, and independently verified all three synthetic files through complete SHA-256 readbacks. The large test file also matched when read through an actual Windows mount. Local failure tests cover interrupted replies and destination races. Sustained large-volume reliability is still being evaluated.
Portable, with one drive prerequisite.
MountMe runs from an extracted Windows folder with its .NET runtime included. Mounting requires the separately installed Dokan runtime. Browsing and direct uploads work without that driver. Standard Hot-tier block blobs are the initial tested configuration; archive rehydration, append/page blobs, and full writable application compatibility aren't included.