Microsoft Defender for Cloud Apps
Cloud and workloads

Best Practices

In brief

The page metadata was refreshed, and the guidance now refers to Microsoft Defender instead of Defender for Cloud Apps when describing app-permission monitoring and banning risky apps.

What Defender admins need to know

No administrator action is indicated; use the updated product naming when referencing this guidance.

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.

Best practice: Manage OAuth apps that are authorized by your usersDetail: Many users casually grant OAuth permissions to third-party apps to access their account information and, in doing so, inadvertently also give access to their data in other cloud apps. Usually, IT has no visibility into these apps making it difficult to weigh the security risk of an app against the productivity benefit that it provides.

Microsoft Defender for Cloud Apps provides you with the ability to investigate and monitor the app permissions your users granted. You can use this information to identify a potentially suspicious app and, if you determine that it is risky, you can ban access to it.

For more information: