Microsoft 365 and Google Workspace have become the operational foundations of virtually every home health agency in the country — hosting email, scheduling documents, care coordination notes, billing correspondence, staff communications, and increasingly, clinical reference materials that contain patient information. They are also the two most consistently misconfigured systems I encounter when I assess home health agencies for the first time. Both platforms ship with default settings optimised for ease of deployment, not for HIPAA compliance. The gap between those defaults and what HIPAA actually requires is significant, consistent, and entirely closable — but only if someone takes the time to close it.
The assumption that a cloud platform subscription equals HIPAA compliance is one of the most expensive misconceptions in home health administration. Microsoft and Google maintain the infrastructure that runs their platforms. They do not configure the security settings that protect your agency's specific use of those platforms. That configuration is your responsibility — and the 2026 HIPAA mandatory requirements have made several previously optional configurations legally mandatory.
What Neither Platform Configures For You By Default
Before examining platform-specific settings, it is worth establishing what both Microsoft 365 and Google Workspace leave unconfigured in their standard deployments that directly affects HIPAA compliance:
- Multi-factor authentication: Both platforms support MFA. Neither enforces it by default. Every user can log in with username and password alone until an administrator configures enforcement — which is now a 2026 HIPAA mandatory requirement.
- Data Loss Prevention: Both platforms include DLP capabilities that can scan outbound email for PHI patterns and block or quarantine messages containing unencrypted patient information. Neither configures DLP rules by default.
- Email encryption for PHI: Neither platform automatically encrypts outbound email containing patient information. Encryption must be configured through DLP rules, transport rules, or sensitivity labels.
- External sharing restrictions: Both platforms allow file sharing with external parties by default. Without configuration, a care coordinator can share a patient file with anyone using a shareable link — no authentication required from the recipient.
- Audit log retention: Both platforms generate audit logs of user activity. Default retention periods may be shorter than HIPAA's six-year documentation requirement without specific configuration.
Microsoft 365: The Critical Configuration Items
Conditional Access and MFA Enforcement
Microsoft Entra ID (formerly Azure Active Directory) Conditional Access is the mechanism through which MFA is enforced in Microsoft 365 environments. The default configuration does not include a Conditional Access policy requiring MFA. You must create one — and it must cover every user with ePHI access, with no exceptions for any user, device type, or location. The policy should be configured to require MFA on every login from every location — not just from outside the office network, which is a common but inadequate configuration that leaves office workstations without MFA protection.
Microsoft Authenticator with number matching enabled is the recommended MFA method for home health deployments. Number matching — which requires the user to enter a number displayed on the login screen into the authenticator app before approving — eliminates the MFA fatigue attack vector that basic push notifications are vulnerable to. Configure number matching in the Microsoft Authenticator settings within the Entra ID admin portal.
Microsoft Defender for Office 365 — Safe Links and Safe Attachments
Standard Microsoft 365 Business Basic and Business Standard subscriptions include basic email filtering. They do not include Safe Links (which rewrites URLs in emails and checks them at click time in real time, not just at delivery) or Safe Attachments (which detonates email attachments in a sandbox environment before delivering them). Both require Microsoft 365 Business Premium or Microsoft Defender for Office 365 Plan 1. For home health agencies where phishing email is the primary attack vector — which it is — the upgrade from standard to Business Premium is the single most impactful licensing change you can make.

