In August 2021, the security firm UpGuard published research showing that websites built with Microsoft Power Apps portals had been exposing personal information to anyone who knew where to look. UpGuard’s report explained that the portals could publish data through OData feeds, a kind of web interface for retrieving records, and that unless the developer also turned on table permissions for a list, anonymous visitors could read the list data freely. UpGuard first found an exposed portal on May 24, 2021, and later identified others with the same configuration.
CNN reported that the exposed information included employee details and data from COVID-19 vaccination, contact tracing and testing appointment systems. After UpGuard notified Microsoft and the affected organizations, the exposures were closed, and UpGuard reported that Microsoft changed Power Apps portals so that table permissions are enabled by default.
Nobody broke in. The data was available because of how the software was set up. That is what makes the incident a useful lesson for any business: a leak can come from settings rather than from attackers.
Leak or breach: why the difference matters
A breach usually means someone got in who should not have: a stolen password, malware, an exploited vulnerability. A leak means data was left where outsiders could reach it, often through a setting nobody realized was on. The defenses overlap, but leaks need their own attention, because a perfectly patched system with strong passwords can still publish data if it is configured to.
Common places data leaks from:
- file-sharing links that work for anyone who has the URL
- cloud storage set to public, often during testing
- web forms, portals and booking pages that store what people submit
- email forwarding rules that copy messages to outside addresses
- old exports and spreadsheets left in shared folders
- accounts that former employees or contractors can still use
How to prevent leaks
Know where sensitive data lives
You cannot protect data you have not found. List the systems that hold customer, employee, financial or health information, including the small ones: a form tool, a shared spreadsheet, a scheduling app.
Check the defaults on every new tool
The Power Apps exposures came from default behavior that people did not realize applied to them. When you deploy a platform, find every setting that controls anonymous or external access and decide on it deliberately. Microsoft’s SharePoint sharing documentation, for example, explains the organization-level and site-level settings that control “Anyone” links, which allow sharing without signing in.
Test like an outsider
After setting up a portal, form or shared folder, open it in a private browser window without signing in. If you can see data that way, so can everyone else.
Review sharing regularly
Sharing that made sense for one project often outlives it. Run the sharing and external access reports your platforms provide, remove links nobody needs, and give links an expiry date where the platform supports it.
Use data loss prevention where it fits
Data loss prevention (DLP) tools look for sensitive information, such as account or ID numbers, and can warn, block or log when it is shared. Microsoft describes how Purview DLP policies identify, monitor and automatically protect sensitive information across its services.
Give people only the access they need
Least privilege limits how far a mistake can spread. Remove access promptly when someone changes roles or leaves, and review admin accounts in particular.
Watch for changes, and plan the response
Alerts on new forwarding rules, new public links and changes to sharing settings catch problems early. Decide in advance who investigates a possible leak, how you confirm what was exposed, and who decides whether customers or regulators need to be told.
What to do next
Start with one system that holds sensitive data and check its sharing and anonymous-access settings, then open anything public in a private browser window to see what an outsider sees. Our Microsoft 365 services cover sharing and DLP setup, and our cybersecurity page explains the wider controls. You can also request a Blind Spot Scan for an outside look at your exposure.