Microsoft 365 domains can now be onboarded through the Graph API

Cloudflare has opened a public beta that lets Cloudflare Area 1 email security be deployed on Microsoft 365 domains through the Microsoft Graph API. Domains onboarded this way take less configuration and less waiting than established deployment models, while keeping the same Area 1 protection.

Phishing remains the usual entry point for most threat campaigns: stolen employee credentials are then used for data exfiltration, money transfer or other malicious activity. Moving mailboxes to a provider such as Microsoft 365 or Google Workspace does not remove that exposure. Area 1 analyzes every inbound message against Cloudflare's threat models and blocks malicious mail before it reaches the recipient's inbox.

Where this fits among the existing deployment options

Area 1 already supports several deployment paths: Journaling + BCC, where a copy of each message goes to Area 1; Inline/MX records, which add a hop; and Secure Email Gateway Connectors, where Area 1 interacts directly with a SEG. MX records have always been the recommended option.

API-based email scanning

Being the first hop lets the service sinkhole malicious messages so they never hit the destination inbox. The drawback is organizational rather than technical: repointing MX records often needs sign-off from other teams, which adds cycles, and the change is then subject to DNS propagation time. Operations teams want protection in place while those adjustments work through the process.

How API scanning works

With Graph API onboarding, Area 1 reads the messages associated with a domain and evaluates them, removing much of the setup work and delay. Once authorized to read incoming messages from Microsoft 365, the service processes email and fires detections on suspected messages. The workflow is a few clicks: select the domain, open Domains & Routing in settings, add the domain and choose API scan, then follow the setup wizard to authorize read access. Protection is active within minutes of authorization.

BLOG-1586 Embedded Image - PtxkgT

The speed matters most where domains appear faster than first-hop DNS changes can be made. A customer in a sector with heavy M&A activity uses API onboarding to cover newly acquired domains immediately, while new access rights, ownership handovers and the rest of the integration work are still in progress. Under the previous process, acquired mailboxes stayed unprotected for the duration.

BLOG-1586 Embedded Image - LmX3eS
BLOG-1586 Embedded Image - Buz0fu

Roadmap

  • Retroactive scanning of messages sent before Area 1 was installed, so new customers can clean up older mail that still poses risk.
  • UI controls to designate which mailboxes have inbound mail scanned.
  • Hybrid deployments combining API and MX records. Today each domain is limited to a single deployment type, either MX or API; the combined approach is intended to give both maximum flexibility and maximum coverage.

These capabilities are scheduled for 2023, and the open beta is the foundation for building them. Any customer can join the beta and onboard a new domain using the steps above.