Detect risky OAuth application consent grants in Azure AD / Microsoft Entra ID using Microsoft Graph API, audit logs, and permission analysis to identify illicit consent grant attacks.
Start a fresh conversation. Replace the highlighted placeholders.
Use detecting-suspicious-oauth-application-consent to analyze [Entra tenant] for suspicious OAuth consent grants during [timeframe], using my explicitly authorized [Microsoft Graph access], and produce a risk report with remediation recommendations.
Required inputs
[Entra tenant]
[timeframe]
[Microsoft Graph access]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: detecting-suspicious-oauth-application-consentdescription: Detect risky OAuth application consent grants in Azure AD / Microsoft Entra ID using Microsoft Graph API, audit logs, and permission analysis to identify illicit consent grant attacks.domain: cybersecuritysubdomain: cloud-securitytags: - OAuth- Azure-AD- Entra-ID- Microsoft-Graph- illicit-consent- cloud-security- application-permissionsversion: '1.0'author: mahipallicense: Apache-2.0nist_csf: - PR.IR-01- ID.AM-08- GV.SC-06- DE.CM-01mitre_attack: - T1528- T1550.001- T1098.001- T1566.002
Detecting Suspicious OAuth Application Consent
Overview
Illicit consent grant attacks trick users into granting excessive permissions to malicious OAuth applications in Azure AD / Microsoft Entra ID. This skill uses the Microsoft Graph API to enumerate OAuth2 permission grants, analyze application permissions for overly broad scopes, review directory audit logs for consent events, and flag high-risk applications based on publisher verification status and permission scope.
When to Use
When investigating security incidents that require detecting suspicious oauth application consent
When building detection rules or threat hunting queries for this domain
When SOC analysts need structured procedures for this analysis type
When validating security monitoring coverage for related attack techniques
Prerequisites
Azure AD / Entra ID tenant with Global Reader or Security Reader role
Microsoft Graph API access with Application.Read.All, AuditLog.Read.All, Directory.Read.All
Python 3.9+ with msal, requests
App registration with client secret or certificate for authentication
Steps
Authenticate to Microsoft Graph using MSAL client credentials flow
Enumerate all OAuth2 permission grants via /oauth2PermissionGrants
List service principals and their assigned application permissions
Query directory audit logs for Consent to application events
Flag applications with high-risk scopes (Mail.Read, Files.ReadWrite.All, etc.)
Check publisher verification status for each application
Generate risk report with remediation recommendations
Expected Output
JSON report listing all OAuth apps with granted permissions, risk scores, unverified publishers, and suspicious consent patterns
Audit trail of consent grant events with user and IP details