Skip to main content
← Back to all posts
email security··8 min read·By Quantm Security Team

AI-Enabled Phishing and Microsoft 365 Email Controls

AI can improve phishing language, personalization, and scale, while QR codes, CAPTCHA pages, and stolen sessions complicate detection. The response is layered Microsoft 365 control, not an AI label.

AI-enabled phishing uses generative tools to improve language, adapt messages to a target, and produce variations quickly. It does not replace the attacker's need to reach an inbox, trigger an action, steal access, or obtain money. That means the practical defence is still layered email, identity, endpoint, and business-process control.

The useful question is not whether a message was written by AI. It is whether your controls can detect suspicious delivery, protect the requested action, and contain the account or device if the message succeeds.

How AI changes phishing

Generative tools can remove obvious grammar errors, imitate a business tone, summarize public information about a target, and create many message versions. Voice and image tools can also support a broader impersonation attempt.

These capabilities make writing quality a weak phishing test. Employees need to inspect sender context, destination, request, and verification path instead.

Evasion techniques that matter now

QR codes can hide a destination from text-based inspection and move the user to a mobile device. CAPTCHA pages can delay the malicious content until after automated analysis. Shared cloud documents and multi-step redirects can make the initial link appear less suspicious.

Microsoft's Q1 2026 email threat review describes active QR-code phishing and CAPTCHA-based evasion. These are vendor-observed trends, not a prediction that every business will see the same mix.

Attackers may also target session tokens or device-code flows. A stolen session can bypass the protection expected from a password change or basic MFA prompt, which is why sign-in and session controls matter alongside inbox filtering.

Microsoft 365 controls by attack stage

Attack stage Control objective Microsoft 365 examples to evaluate
Sender and delivery Authenticate and inspect mail SPF, DKIM, DMARC, anti-phishing, impersonation policies
Link and file Detect or contain content Safe Links, Safe Attachments, quarantine, user reporting
Sign-in Resist stolen credentials Authentication strengths, phishing-resistant methods, Conditional Access
Session Reduce token abuse Sign-in risk, session revocation, token protection where supported
Device Limit unmanaged access Intune compliance, app protection, Defender for Endpoint integration
Response Investigate and contain Explorer or message trace, audit logs, identity and endpoint incidents

Licensing and configuration determine which capabilities are available. Verify the tenant rather than assuming a named Microsoft 365 plan automatically applies every control.

Microsoft's identity protection guidance identifies phishing-resistant authentication and token protection as stronger measures against credential and session theft. Roll out Conditional Access in report-only mode first where Microsoft guidance calls for testing, and maintain emergency access.

Do not automate trust

AI assistants can summarize and act on email, so malicious message content may target the model as well as the user. Microsoft now documents prompt-injection protection in Defender for Office 365 for supported Plan 2 environments.

Treat email content as untrusted input in any workflow that can send messages, retrieve files, change records, or trigger business actions. Limit permissions, require approval for sensitive actions, and retain logs that show what the automation received and did.

A control review for small businesses

Start with four checks:

  1. Confirm domain authentication and anti-phishing policies for every business domain.
  2. Identify users and workflows most exposed to payments, payroll, client data, and administrator access.
  3. Review MFA methods, Conditional Access, unmanaged-device access, and session response steps.
  4. Test one QR-code, fake-share, and account-compromise scenario from user report through containment.

Learn how email filters work before treating any AI feature as a complete solution. The SMB email security control guide covers the full control set, while an M365 Posture Review identifies tenant-specific gaps without promising that one tool will stop every attack.