Updated November 18, 2026
How to find risky OAuth apps in Microsoft 365
Every time someone clicks "Accept" on a Sign in with Microsoft screen, an outside app gets a foothold in your tenant. Most are harmless. A few can read every mailbox or act as an administrator. This guide shows how to find those few.
What makes an app risky
An OAuth app is risky when a breach at the vendor would hand the attacker real power in your tenant. Look for four things:
- A directory role. An app that holds Global Administrator or Privileged Role Administrator can do anything an admin can.
- Application permissions that write. Permissions such as
Mail.ReadWriteorDirectory.ReadWrite.Allgranted as application permissions work without any user signed in. - Admin consent for every user. A delegated permission that an admin approved for the whole organisation, for example to read and send mail.
- A secret or certificate on the app in your tenant. Attackers add their own credentials to an app to keep access after you reset passwords.
An unverified publisher is a fifth, weaker sign. It does not mean the app is bad, but nobody has confirmed who runs it.
Where to look in the Entra admin center
- Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
- Go to Entra ID, then Enterprise apps, then All applications.
- Open an app and select Permissions. The Admin consent tab shows what was granted for the whole organisation. The User consent tab shows what single users granted.
- Go to Roles and admins, open Global Administrator and check whether any member is an app rather than a person.
This works, but you have to open every app one by one. A tenant that has used Microsoft 365 for a few years often has dozens.
The PowerShell way
With the Microsoft Graph PowerShell SDK you can list the outside apps and the organisation-wide consents in one go:
Connect-MgGraph -Scopes "Directory.Read.All"
$tenant = (Get-MgOrganization).Id
$microsoft = "f8cdef31-a31e-4b4a-93e4-5f571e91255a"
# Third-party apps: not owned by your tenant or by Microsoft
$apps = Get-MgServicePrincipal -All | Where-Object {
$_.ServicePrincipalType -eq "Application" -and $_.AppOwnerOrganizationId -and
$_.AppOwnerOrganizationId -notin @($tenant, $microsoft) }
$apps | Select-Object DisplayName, AppId,
@{n="Secrets"; e={ $_.KeyCredentials.Count + $_.PasswordCredentials.Count }}
# Delegated permissions an admin granted for every user
Get-MgOauth2PermissionGrant -All | Where-Object ConsentType -eq "AllPrincipals" |
Select-Object ClientId, Scope
You still need to match the ClientId values to app names, check application permissions with Get-MgServicePrincipalAppRoleAssignment for each app, and check directory role members with Get-MgDirectoryRoleMember.
What to do with a risky app
Do not delete it first. Open the app, select Properties and set "Enabled for users to sign-in?" to No. That blocks it at once and you can undo it if something breaks. Then ask the owner whether it is still needed, review its permissions and delete it when you are sure.
Sources: Microsoft Learn, Review permissions granted to enterprise applications and Disable user sign-in for an application.
Or see the whole list in two minutes
OAuth App Audit signs in read-only, lists every third-party app in your tenant and puts the risky ones first, with the reason for each. Free summary, no PowerShell. We delete our access token when the check ends.
Other guides: How to review app consent in Microsoft Entra ID · After the ConnectWise Cloud Backup breach: what to check in your tenant