Staff keep connecting new apps to their work accounts: finding them and setting a rule people follow
Every 'Sign in with Microsoft' or 'Sign in with Google' can hand a third-party app access to mail and files. How to see what is connected, decide what stays, and set an approval rule.
A test account and an old app
In January 2024, Microsoft published an account of how a state-backed group it calls Midnight Blizzard got into its corporate email. The attackers did not need a new vulnerability. They used password spraying against a legacy test account that did not have multifactor authentication, then found an old test OAuth application that had elevated access to Microsoft’s corporate environment. From there they created more malicious applications, granted them consent, gave them a role that allows access to mailboxes, and read corporate email.
Most small organizations will never face that adversary. They do have the same ingredients: old accounts nobody owns, and a growing list of third-party apps that staff connected to their work accounts with a single click. A scheduling tool, a PDF signer, a browser add-on that “summarizes your inbox.” Each one asked for permission to read mail, calendars or files, and someone said yes.
The leadership problem is not that staff are careless. They are trying to get work done, and the tools make connecting an app easy. The problem is that nobody decided who may grant that access, so everyone can.
Why this is hard
- It is out of sight unless someone looks. An app connected through “Sign in with Microsoft” or “Sign in with Google” does not show up on an invoice if it is free, and it does not install anything on a company laptop.
- The permissions outlive the person. Microsoft notes that changing consent settings affects only future consent. Grants that users already made stay in place until someone reviews and revokes them.
- A password change is not the same as a review. Microsoft’s guidance for a compromised mailbox lists reviewing and revoking consented apps as its own step, separate from resetting the password.
- A flat ban fails. If staff cannot get any tool approved, they use personal accounts instead, and the company loses sight of the data entirely.
Step 1: see what is already connected
Both major platforms show the list. It is usually longer than anyone expects.
Microsoft 365. In the Microsoft Entra admin center, the enterprise applications list shows apps that have been granted access in your tenant, and each app’s permissions page shows what it can do and who consented. Microsoft documents how to review and revoke those permissions.
Google Workspace. In the Admin console under Security, Access and data control, API controls, the Manage App Access page has an “Accessed apps” section listing apps that have accessed Google data, with user counts and the services each requested. Google notes that details typically appear 24 to 48 hours after authorization.
Export the list. For each app, note four things: what it does, what it can access, how many people use it, and whether anyone in the business would miss it.
Step 2: sort the list into three groups
| Group | What goes in it | Action |
|---|---|---|
| Keep | Apps with a clear business use, a known publisher and permissions that match the job | Mark as approved, name an owner |
| Replace | Apps with a real use but too much access, or a duplicate of a tool you already pay for | Move users to the approved tool, then revoke |
| Remove | Apps nobody can explain, apps used by one departed employee, apps asking for full mailbox or full drive access for a minor feature | Revoke now |
Pay attention to scope, not only to the name. An app that reads a calendar to book meetings is a different risk from one that can read and send mail as the user.
Step 3: set the rule in the platform, not only in a policy
A written policy helps people understand the rule. The platform setting is what makes it hold.
Microsoft Entra ID. By default, Microsoft says, all users can consent to apps for permissions that do not require administrator consent, such as access to their own mailbox. Microsoft recommends allowing user consent only for apps from verified publishers, and only for permissions you classify as low impact. That is the built-in “Allow user consent for apps from verified publishers, for selected permissions” option. Turn on the admin consent workflow at the same time, so a user who hits a block can request the app and an administrator can approve it. Without that workflow, a block feels like a dead end, and people route around it.
Google Workspace. Google lets admins set each app as Trusted, Limited, Specific Google data or Blocked, per organizational unit, and choose what happens with apps nobody has configured yet: allow sign-in to any app, only to apps requesting basic profile information, or to none. Admins can also let users request access to unconfigured apps for review. Google also lets you mark services such as Gmail and Drive as restricted, so only apps you mark Trusted or give Specific Google data access can reach them.
For most small organizations, a reasonable starting point is: users may connect apps that only read their basic profile; anything that wants mail, files or calendars goes through a request; a named person reviews requests within two business days.
Step 4: make approval easy and quick
This is where efforts often stall. If the request takes three weeks, people stop asking.
- Publish the approved list where staff can find it, with what each tool is for.
- Keep the request short: what the app is, what it will be used for, and what data it needs.
- Answer fast, even if the answer is “use this approved tool instead.”
- Say yes when you can. An approved app with an owner is better than an unapproved one nobody knows about.
Step 5: review on a schedule
Put the connected-apps review on the calendar quarterly, and tie it to two events: an employee leaving, and a vendor contract ending. When someone leaves, check which apps they consented to and whether anyone else depends on them. Also look for old test or service accounts that have no owner and no MFA, because that combination is exactly what started the Microsoft incident.
Who does what
| Role | Responsibility |
|---|---|
| Owner or executive sponsor | Agrees the rule and backs it when someone senior wants an exception |
| IT administrator or MSP | Runs the export, changes the consent settings, handles requests |
| Department leads | Explain what their teams use and why |
| Staff | Request apps through the workflow instead of connecting them directly |
When to get help
If the first export shows dozens of apps and no one knows where to start, an outside review can sort them, set the consent rules and leave you with a request process that people will use.
Want to talk it through? Book a free 30-minute call with Security Medic Consulting.
Sources
- Microsoft Security Blog, Midnight Blizzard: Guidance for responders on nation-state attack, January 25, 2024 (accessed 2026-11-05).
- Microsoft Learn, Configure how users consent to applications, updated June 24, 2025 (accessed 2026-11-05).
- Microsoft Learn, Respond to a compromised cloud email account, last updated July 17, 2026 (accessed 2026-11-06).
- Google Workspace Admin Help, Control which third-party and internal apps access Google Workspace data (accessed 2026-11-05).