The BAA agreement HIPAA requires is a signed contract between a medical practice and an outside vendor that handles its patient data, such as an IT provider. It limits what the vendor may do with the data and requires safeguards.
A BAA looks like paperwork. It’s also the contract that decides what an IT provider may do with your patient data. Whether the company running your network has to sign one is a fair question to settle early.
This piece is the buyer’s view. It covers when an IT provider has to sign, what the agreement has to say, and how to tell a provider that understands it from one that doesn’t. VJNetworks started in 2004 and supports businesses across Rockland, Westchester and Bergen counties, and our page on IT support for healthcare practices covers the wider work.

What a BAA Agreement Under HIPAA Actually Is
A business associate agreement is the written contract HIPAA requires between a covered entity, such as a clinic or doctor’s office, and an outside company that handles protected health information for it. The contract sets what the company may do with the data, requires it to protect the data, and requires it to report problems.
The legal test sits in 45 CFR 164.504(e) and the definition in 45 CFR 160.103. A business associate is a company that “creates, receives, maintains, or transmits protected health information” on your behalf. Notice what it leaves out. Nothing in it requires the company to read a single record.
Two things a BAA is not. It isn’t a certificate. Microsoft’s own HIPAA compliance page says there is currently no certification standard that HHS approves to show a business associate complies with HIPAA, so a “HIPAA certified” badge is not an HHS credential. And it isn’t a finish line either. The agreement promises safeguards. It doesn’t build them.
When Your IT Provider Has to Sign a BAA
If the work gives the provider a way to create, receive, maintain or transmit your patient data, plan on it being a business associate. Access is the test. HHS’s own examples include a CPA firm whose accounting services involve access to protected health information. A managed IT company with administrator access to your servers, your email and your backups is in a comparable position. It isn’t a postal service.
The postal comparison is HHS’s. In its cloud computing guidance, HHS describes the conduit exception as limited to transmission-only services, with any storage only temporary and incident to the transmission. The same guidance goes further. A cloud provider that stores only encrypted data, and holds no key to read it, is still a business associate. Lacking the key changes nothing.
Never looking at the files doesn’t change the answer. HHS said as much about cloud storage that the provider can’t even read.
Mike Stoveken on how VJNetworks handles it.
“It’s built into all of our contracts that we sign with any healthcare provider.”
Mike Stoveken, VJNetworks
The chain doesn’t stop at your provider, either. When a business associate hires a subcontractor that handles your patient data, the rule requires an agreement between them as well. Picture a backup service that stores copies of your records for your IT company. That service is a subcontractor. Your provider needs its own agreement with it. Remote-support tools can land in the chain as well. It turns on what they can reach.

Your cloud platform is a separate agreement again. Microsoft says its HIPAA BAA is available through the Online Services Data Protection Addendum, by default, to customers that are covered entities or business associates, and that it covers a list of in-scope Microsoft services. Microsoft also says that having a BAA with it does not ensure an organization’s HIPAA compliance. That agreement covers Microsoft’s side. The company that administers your Microsoft 365 tenant is its own question.
What a BAA Agreement Has to Say Under HIPAA
The regulation lists what the contract must contain. Here are the main terms. The table puts them in plain English. The regulation also covers carrying out any of the practice’s own duties that the provider takes on.
| The contract must | In plain English | Where it comes from |
|---|---|---|
| Limit how the data is used | The provider may use patient data only as the contract and the law allow. | 45 CFR 164.504(e)(2)(i) and (ii)(A) |
| Require safeguards | Appropriate protections, and for electronic records, compliance with the Security Rule. | 164.504(e)(2)(ii)(B); 164.314(a)(2)(i)(A) |
| Require reporting | Tell you about disallowed uses, security incidents the provider learns of, and breaches of unsecured records. | 164.504(e)(2)(ii)(C); 164.314(a)(2)(i)(C) |
| Bind subcontractors | Anyone the provider brings in to handle your data agrees to the same restrictions. | 164.504(e)(2)(ii)(D) |
| Support patient rights | Make records available so you can answer access, amendment and accounting requests. | 164.504(e)(2)(ii)(E) to (G) |
| Open its books to HHS | Make its internal practices and records on this data available to the Secretary of HHS. | 164.504(e)(2)(ii)(I) |
| Handle the end of the contract | At termination, if feasible, return or destroy the data and keep no copies. | 164.504(e)(2)(ii)(J) |
| Let you terminate | You can end it if the provider violates a material term. | 164.504(e)(2)(iii) |
Breach timing deserves a second look, because people misread it. Under 45 CFR 164.410, a business associate must notify the covered entity without unreasonable delay and in no case later than 60 calendar days after discovering a breach of unsecured records, with a narrow exception when law enforcement asks for a delay (45 CFR 164.412). That is the outer limit. It is not a target. HHS’s sample language notes that the parties may add a stricter timeframe, so read what your agreement says.
HHS publishes sample provisions for these terms, and it says plainly that using them isn’t required, that they may not satisfy state law, and that they don’t replace a lawyer. HHS also says the terms can sit inside a services agreement or in a separate document. Either form works.
How to Choose an IT Provider That Will Sign One
Start with the test Mike Stoveken applies when he puts himself on the buyer’s side of the table.
“If I was a customer and I was looking at IT companies, and they didn’t talk about it at all on their website, and I asked them about it, and they didn’t really know what it was, or really talk about how they manage their HIPAA compliance, or track their compliance… it would be a red flag, right, if they didn’t know what it was.”
Mike Stoveken, VJNetworks
That’s a good first screen. A provider that can’t say what a BAA is has told you most of what you need to know. After that, five questions will do the rest.

- Will they sign before they touch anything? Raise it while you’re still comparing proposals, not at onboarding. The rule is about the data moving, so the signature comes first.
- Can they explain their own agreement in plain words, without a script?
- Who else reaches your records on their behalf? Ask about the backup service and any other outside tool, and whether the provider has an agreement with each.
- What happens when something goes wrong? Who reports what, to whom, and how soon. Remember the 60-day ceiling and ask whether the agreement sets a shorter one.
- What happens to your data when the relationship ends? “If feasible” is in the regulation. Ask what that would look like for you.
Two lines are worth listening for. The first is “we don’t look at your data, so we don’t need a BAA.” We covered that one. The second is “we’re HIPAA certified.” As noted above, there is no HHS-approved certification for business associates. A provider may well have had a security audit by an outside firm, and that’s worth something, but it’s a different thing from the agreement the regulation requires.
What Skipping a BAA Has Cost Healthcare Organizations
The cases are not hypothetical. HHS’s Office for Civil Rights announced that Raleigh Orthopaedic Clinic of North Carolina agreed to a $750,000 settlement of charges that it potentially violated HIPAA by failing to execute a business associate agreement before turning over the protected health information of 17,300 people to a potential business partner. The announcement ties the penalty to a missing contract, and the settlement also carried a corrective action plan.
The cloud guidance describes a second case in which OCR entered a resolution agreement with a covered entity that stored the information of more than 3,000 individuals on a cloud-based server without a BAA with the provider.
The exposure runs both ways. Since the HITECH Act and OCR’s 2013 final rule, business associates are directly liable for compliance with parts of the HIPAA rules, which HHS lays out in its fact sheet on direct liability. The paperwork isn’t one-sided.
One more thing. HHS proposed a rewrite of the Security Rule that would also apply to business associates, published in the Federal Register on January 6, 2025 (90 FR 898). We searched the Federal Register on November 11, 2026 and found the proposal but no final rule, so the rules described here are the ones in force today. This is general information, not legal advice, and your own counsel or compliance advisor decides what your practice must do.
For the wider checklist, what HIPAA requires of your IT provider goes further. If you’re weighing providers more generally, how to evaluate an MSP before you sign is the companion piece, and our page on cybersecurity for healthcare practices covers the security side. The services behind all of it are described under managed IT services.
Things Practices Ask About BAAs
Does our IT company really have to sign a BAA?
When does the BAA need to be signed?
Is a BAA the same as a HIPAA certification?
We already have a BAA with Microsoft. Does that cover our IT provider?
Can the BAA sit inside the main service agreement?
Will the proposed Security Rule rewrite change any of this?
Talk with our team about business associate agreements and what to expect from an IT provider. No cost, no obligation.
