Overview
Setup
Inline
Setup
Office 365 - Area 1 as MX Record
Use cases
1 - Junk email and Area 1 Admin Quarantine
2 - Junk email and user managed quarantine
3 - Junk email and administrative quarantine
4 - User managed quarantine and administrative quarantine
5 - Junk email folder and administrative quarantine
Google Workspace - Area 1 as MX Record
Cisco - Area 1 as MX Record
Cisco - Cisco as MX record
Reference
Egress IPs
API
Setup
Gmail BCC setup
Exchange BCC setup
Office 365 journaling setup
Office 365 Graph API setup
Account setup
Manage account members
Escalation contacts
Manage parent permissions
SSO integration
Generic SSO guide
Okta guide
Azure guide
Permissions
Email configuration
Domains and routing
Domains
Alert Webhooks
Partner Domains TLS
Email policies
Text add-ons
Link actions
Allow and block lists
Allowed patterns
Trusted domains
Block lists
Enhanced detections
Business email compromise (BEC)
Office 365 directory integration
Google Workspaces directory integration
Added Detections
Retract settings
Gmail retraction
Office 365 retraction
Phish submissions
PhishNet for Office 365
PhishNet for Google Workspace
Admin Quarantine
Reporting
Search
Unified Search
Detection search
Available parameters
Mail Trace
Phish reports
SIEM integration
Splunk
Sumo Logic
Audit Logs
API
Service accounts
Channel and Alliance Partners
Reference
How we detect phish
Dispositions and attributes
Language support
Cloudflare SSO

Setup

When you configure Area 1 Email Security to protect your organization, you can choose between two main setup architectures: Inline and API.

With an Inline deployment, Area 1 evaluates email messages before they reach a user’s inbox. When you choose an API deployment, email messages only reach Area 1 after they have already reached a user’s inbox.

Select a deployment method to get started.