hipaa.systems
Tool category

HIPAA compliant cloud storage? Services that sign a BAA

Cloud storage services that sign a BAA — on which plans, how you put the agreement in place, and what you must configure before storing patient files.

Products 4Criteria 2Commissions None

Cloud storage and file sharing at a glance

Cloud storage can hold patient files under HIPAA when the provider signs a BAA for your plan and you control sharing links, synced copies on computers and who can sign in. We compare 4 products in Cloud storage and file sharing. 3 sign a Business Associate Agreement (Dropbox, Google Drive (Google Workspace), OneDrive for Business (Microsoft 365)). 1 signs one only for certain plans or products (Box). Every value links to the vendor's own documentation and shows when it was checked.

Sign a BAADropbox, Google Drive (Google Workspace), OneDrive for Business (Microsoft 365)
Only some plans or productsBox
Products compared4
3 more facts
Compared onBAA without a sales process, BAA on entry-level team plans
CommissionsNone — no vendor pays us
Facts checked since2026-10-06

Compare the providers ↓

Comparison

Alphabetical. No vendor pays us for listings, rankings or referrals — methodology.

ProductSigns a BAABAA without a sales processBAA on entry-level team plans
BoxConditionalPartialNo
DropboxYesYesYes
Google Drive (Google Workspace)YesYesNot verified
OneDrive for Business (Microsoft 365)YesYesYes
Found an outdated or wrong fact? Report it

Do not include patient information. Vendors are welcome — we check every report against the source before changing anything. Corrections policy.

What to check before you choose

A BAA on the plan, for the services you use
Storage is often covered while some add-ons are not. Check the plan and the list of covered services before uploading patient files (164.502(e)).
Sharing links
Turn off public "anyone with the link" sharing, set link expiry, and limit sharing to your own domain where you can.
Synced copies on computers
Desktop sync puts PHI on every computer that syncs, so those devices come under your device rules (164.310(d)). Encryption is an addressable specification (164.312(a)(2)(iv)); we recommend encrypting them and using a screen lock — or turning sync off.
Access, sign-in and logs
HIPAA requires access control, audit controls and person authentication (164.312(a), (b), (d)). Our recommended way to meet them: one account per person, multifactor sign-in, and activity logs you can review.
Version history and recovery
HIPAA requires a data backup plan and a way to restore lost data (164.308(a)(7)). Version history and a tested restore make that real after ransomware or accidental deletion.
Getting data back at the end
At the end of the contract the BAA must require the vendor to return or destroy PHI where feasible — and, where that is not feasible, to keep protecting it and limit further uses (164.504(e)(2)(ii)(J)). Check export before you commit.

Common mistakes

How we compare

BAA without a sales process
You can put the BAA in place yourself — it is included in standard terms or accepted in account settings — rather than requesting it and waiting for approval.
BAA on entry-level team plans
The BAA is available on the vendor's entry-level business or team plan, not only on enterprise tiers.

Requirements behind these criteria

Relevant for