m365-entra-attack

Validate credentials and enumerate users in Microsoft 365 and Entra ID environments.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill m365-entra-attack-uphiago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: m365-entra-attack
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/m365-entra-attack
Command: npx skills add https://github.com/uphiago/recon-skills --skill m365-entra-attack-uphiago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of conducting safe, effective authorized red team operations against Microsoft 365 and Entra ID environments, including credential validation, user enumeration, and Conditional Access assessment, while avoiding accidental account lockouts, false positive validations, and unnecessary detection risk.

Core Features & Use Cases

  • AADSTS Error Code Reference: Quickly distinguish between invalid credentials, valid credentials blocked by MFA/Conditional Access, locked accounts, and non-existent users to avoid wasted effort and false positives.
  • Smart Lockout Discipline: Built-in attempt caps and state tracking ensure password sprays never trigger Microsoft's Smart Lockout policies, preventing accidental disruption of production user accounts.
  • Lockout Differential Detection: Identify active external password spray campaigns targeting the tenant by analyzing pre-existing locked accounts during your engagement.
  • Use Case: For an authorized engagement testing a client's M365 environment, use this Skill to safely validate leaked credentials from stealer logs, identify functional accounts that may be exempt from MFA, and detect if an external attacker is already actively targeting the tenant.

Quick Start

Use the m365-entra-attack skill to safely validate a list of corporate email addresses against a known password list for an authorized M365 red team engagement, tracking per-user attempt counts to avoid triggering Smart Lockout policies.

Frequently Asked Questions about m365-entra-attack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely execute a password spray against Entra ID without triggering Smart Lockout?

To safely execute a password spray against Entra ID without triggering Smart Lockout, you need built-in attempt caps and per-user state tracking to ensure password sprays never exceed Microsoft's Smart Lockout thresholds and disrupt production accounts.

What do AADSTS error codes mean during M365 credential validation?

AADSTS error codes during M365 credential validation distinguish between invalid credentials, valid credentials blocked by MFA or Conditional Access, locked accounts, and non-existent users, helping you avoid wasted effort and false positives during red team engagements.

Can I detect an active external password spray campaign targeting my M365 tenant?

You can detect an active external password spray campaign targeting an M365 tenant by analyzing pre-existing locked accounts using lockout differential detection, identifying accounts already locked by external attackers during your engagement.

How do I test Conditional Access bypass for cloud-only Microsoft identity tenants?

Testing Conditional Access bypass for cloud-only Microsoft identity tenants involves assessing credential validation responses to identify functional accounts that may be exempt from MFA and evaluating access policy enforcement during authorized red team operations.

Does this approach support ROPC and SAML SSO credential validation?

Yes, this approach supports ROPC and SAML SSO credential validation, enabling you to safely validate leaked credentials from stealer logs and identify functional accounts exempt from MFA during authorized M365 red team engagements.