AI Security
"The EHR wasn't accessed" isn't the reassurance it sounds like
UCHealth says an intruder in two employee Microsoft cloud accounts may have taken files with names, Social Security numbers, and health information, while the EHR was never touched. The protected health information that leaks is often the copy that lives outside the EHR.
November 17, 2026 · 6 min read

Two employee accounts in a Microsoft cloud tenant were enough to put sensitive data for about 129,000 people in scope, without anyone touching the electronic health record. That is the plain reading of UCHealth's November 13 notice.
I want to stay close to what UCHealth said, because the notice is careful and the lesson does not need embellishment. The useful part for any health system or HealthTech company is the sentence that sounds like good news: "Importantly, UCHealth's electronic health record was not accessed." That sentence is true, and it is also where many teams stop looking.
What UCHealth's notice says
According to the notice, on July 27, 2026, UCHealth discovered that an unauthorized third party had gained access to two employee accounts in its Microsoft cloud system. It launched an investigation, secured the affected accounts and environment, and notified law enforcement. The investigation found the activity was limited to certain services within the cloud system, and that the third party may have acquired certain files stored there.
Some of those files contained personal information. Depending on the person, UCHealth says that may include name, Social Security number, driver's license number, health information, and billing information. UCHealth says its security team and outside experts have monitored for any leak or use of the data and have not found evidence that it was misused or further disclosed. It is mailing letters to about 129,000 individuals, offering a year of identity protection to those whose Social Security or driver's license numbers were involved, and says its review is ongoing.
The notice does not explain the time between discovery in July and letters in November, and I am not going to second-guess it. Anyone who has done a file review after a mailbox compromise knows that kind of work can take months, because the slow part is reading everything the intruder could have read and working out whose data is in it.
Why the EHR is often not where the exposure is
The EHR is the most protected system in most health organizations. It has role-based access, audit logs that compliance teams actually review, and a vendor whose business depends on it. When people picture a health data breach, they picture the EHR.
But protected health information does not stay in the EHR. It gets exported, attached, summarized, and saved for perfectly ordinary reasons:
- A billing analyst downloads a report of denied claims to work through in a spreadsheet
- A quality team keeps a running list of patients for a registry submission
- A manager emails a scheduling export to a colleague
- A clinic saves scanned intake forms to a shared drive while a document workflow is fixed
- Someone keeps a copy of a patient complaint, with details, in their own OneDrive
Each of those files lives in Microsoft 365 or a similar suite, under one person's account, with that person's access controls and that person's MFA. When that account is compromised, the intruder does not need the EHR. The extract is sitting there already, often with more identifiers in one place than any single EHR screen would show.
I do not know what was in UCHealth's files beyond what the notice lists, and I am not guessing. The pattern I am describing is general, and it is why "the EHR was not accessed" answers a narrower question than the one patients are asking.
Map the PHI that lives outside the EHR
The fix starts with knowing where the copies are. This is a mapping exercise, and you can scope it to something manageable.
Pick the places where exports land in your environment. For most organizations on Microsoft 365, that means:
- Mailboxes, especially shared mailboxes used by billing, scheduling, HIM, and patient relations
- OneDrive accounts of people whose jobs involve reports or extracts
- SharePoint sites and Teams channel files for departments that work with patient lists
- File shares and sync folders that predate the move to the cloud
For each, ask three questions. What kinds of identifiers end up here, and why? Who can reach it, including through sharing links that never expire? How long does it stay?
Microsoft 365 has built-in tools for sensitive information types, retention labels, and data loss prevention. Use them to find the files with Social Security numbers and medical record numbers first, because those carry the highest notification cost. Then work on retention: a report exported for a one-time project in 2022 should not still be sitting in someone's OneDrive.
The second fix is on the account side. Two accounts were the way in here, per the notice. Every account with routine access to exported PHI deserves the same scrutiny as an EHR account: phishing-resistant MFA, conditional access, alerting on unusual sign-ins and mass downloads, and a quick path to revoke sessions.
A tabletop for the scenario that actually happens
Most incident response tabletops in health care start with ransomware on the EHR. That is a real scenario, but it trains the team to look in one place.
Try this inject instead: "Security has confirmed an outside party had access to two staff Microsoft 365 accounts for an unknown period. The EHR shows no unusual access."
Then ask the room:
- Which accounts are they, and what were those people's jobs?
- What files and mailboxes could those accounts reach, including shared ones?
- How would you find out which of those files contain PHI, and how long would it take?
- Who decides whether this is a reportable breach, and on what evidence?
- What do you tell patients and the board while the file review is still running?
If the honest answer to the third question is "we would have to open every file," you have found the gap. It is better found in a conference room than in a notice letter.
Where to start this week
Pull the list of accounts in your organization that regularly export or receive patient data outside the EHR. Check their MFA method and whether downloads from them are logged and alerted. Then pick one shared mailbox, scan it for Social Security numbers, and see what you find. That single result will tell you more about your exposure than any statement about the EHR.