Microsoft Defender for Cloud Apps
Cloud and workloads

Investigate Risky Oauth

In brief

The article’s date, metadata, taxonomy links, and terminology were updated. Several references to Defender for Cloud Apps now use Microsoft Defender or Defender.

What Defender admins need to know

Administrators reviewing or sharing this guidance should use the updated terminology. No administrator action is stated.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

OAuth phishing google.

As a security admin, you need visibility and control over the apps in your environment and that includes the permissions they have. You need the ability to prevent use of apps that require permission to resources you wish to revoke. Therefore, Microsoft Defender for Cloud Apps provides you with the abilitySaaS security capabilities to investigate and monitor the app permissions your users granted. This article is dedicated to helping you investigate the OAuth apps in your organization, and focus on the apps that are more likely to be suspicious.

Our recommended approach is to investigate the apps by using the abilities and information provided in Defender for Cloud Apps to filter out apps with a low chance of being risky, and focus on the suspicious apps.

In this tutorial, you'll learn how to:

How to remediate suspicious OAuth apps

After you determine that an OAuth app is risky, Defender for Cloud Apps provides the following remediation options: