Connection Filters

Avanan creates Connection Filters to prevent the blocking of emails sent to users.

Connection filter name: Connection filter policy (Default)

Journal Rules

Avanan creates a Journal rule that configures Microsoft 365 to send a copy of all scoped emails to the journaling mailbox used by Avanan for inspection.

Avanan uses this Journal rule only for policies in Detect and Detect and Remediate protection modes.

Journal rule name: Avanan - Monitor

Journal Reports

Avanan configures the Journal rule to send the Journal reports to [portal]@[portal]-mail.avanan.net

It also configures a mailbox for undeliverable journal reports, if the mailbox was not configured yet for the Avanan tenant.

Avanan sends the undeliverable journal reports to these mailboxes when they are not deliverable to the email address specified in the journal rule:

Avanan Tenant Region	Undeliverable Journal Report Mailbox
United States	[portal name]@mt-prod-3-journal-error.avanan.net
Europe	[portal name]@mt-prod-av-1-journal-error.avanan.net
Canada	[portal name]@mt-prod-av-ca-2-journal-error.avanan.net

Groups

Avanan creates groups to protect the specific users and groups selected in the policies for Prevent (Inline) protection mode.

When administrators configure Scope for a policy in Prevent (Inline) protection mode, it gets updated to the relevant group so that only those specific users are protected inline.

Avanan creates these groups:

• avanan_inline_incoming

• avanan_inline_outgoing

Avanan Inline Incoming Group

This group allows Avanan to protect only the incoming emails sent to users protected by an incoming policy in Prevent (Inline) protection mode.

Group name: avanan_inline_incoming

Group email address: avanan_inline_incoming@[portal domain]

Avanan Inline Outgoing Group

This group allows Avanan to protect only the outgoing emails sent by users protected by an outgoing policy in Prevent (Inline) protection mode.

Group name: avanan_inline_outcoming

Group email address: avanan_inline_outcoming@[portal domain]

Distribution Lists

Avanan creates a distribution list to support the protection of group mailboxes for policies in Prevent (Inline) protection mode.

Distribution list name: avanan_inline_groups

Spoofed Senders Allow List

To route emails from protected users and send emails on behalf of the protected domain, Avanan adds spoofed sender exceptions to Tenant Allow/Block List in Microsoft 365.

For example, Avanan adds these infrastructure values for Avanan tenants residing in the United States region.

User	Sending Infrastructure	Spoof Type	Action
*	us.cloud-sec-av.com	Internal	Allow
*	us.cloud-sec-av.com	External	Allow

Sending infrastructure for Avanan tenants residing in different regions:

Region	Country	Sending Infrastructure
Americas	USA	us.cloud-sec-av.com
	Canada	ca.cloud-sec-av.com
EMEA (Europe, Middle East and Africa)	Ireland	eu.cloud-sec-av.com
	United Arab Emirates	mec.cloud-sec-av.com
APAC (Asia Pacific)	Australia	au.cloud-sec-av.com
	India	aps.cloud-sec-av.com
United Kingdom	-	euw2.cloud-sec-av.com

Trusted ARC Sealers

To ensure email authentication remains valid even after routing emails, Avanan adds a Avanan domain to the list of Authentication Received Chain (ARC) trusted sealers.

Avanan adds this to the list of trusted ARC sealers: avanan.net

Reported Phishing Emails

To present all phishing reported emails from end users using the Microsoft Report Message Add-in, reports must be configured to be sent to Microsoft and to an internal phishing reporting mailbox.

If your Microsoft 365 account is configured to send reported emails to an internal mailbox, Avanan monitors that internal mailbox for phishing reports, and the configuration does not change.

If your Microsoft 365 account is not configured to send emails to an internal mailbox, the system creates a shared mailbox with report-phishing-checkpoint@<your domain> email address and configures it to receive these reports.

Note - The system creates only a shared mailbox and it does not consume a Microsoft license from your account.

Delegated Token

To complete the required actions during automatic onboarding, such as creating groups and assigning a Global Admin role to the Avanan application, Avanan uses a delegated token from the authorizing user who approved the permissions.

If you choose to disconnect Avanan from Microsoft 365, Avanan executes the reverse actions, including deleting groups and disassociating roles. To do that, the Avanan Azure application must periodically refresh and maintain a valid delegated token.

The system initiates the refresh action on behalf of the authorizing user, and you can observe these activities in your Microsoft 365 audit log:

• Periodic logins by the Avanan application on behalf of the user to refresh the token.

• Failed login attempts in case the user no longer exists or the password has changed.

  Note - These failed logins do not affect security or email delivery. However, when disconnecting Avanan from Microsoft 365, manual actions are necessary to eliminate its footprint. To resolve this issue, re-authorize the Microsoft 365 application with the same or another Microsoft administrator credentials. Click Security Settings > SaaS Applications. Click Configure for Office 365 Mail. Click Re-Authorize Avanan Office 365 Email App. Follow the onscreen instructions and authorize the Microsoft 365 application.

PowerShell Scripts

Avanan uses PowerShell scripts to perform various tasks in the Microsoft 365 environment, such as:

• Create / edit / delete Mail Flow rules, Connectors, Journal rules, Connection Filter, and Distribution List.

• Configuring a mailbox for undeliverable Journal Reports (if the mailbox was not configured yet for the tenant).

  This mailbox will be used to receive Journal Reports when they are not deliverable to the email address specified in the Journal rule.

• Reading the Hosted Content Filter Policy to get the tenant’s policy actions.

• Allowing Avanan domain, so emails will not be blocked when going through Avanan’s security engines.

• In case a policy that triggers Microsoft Encryption is created, a script will read the IRM Encryption to configure an Encryption rule.

• Creating a new shared mailbox and configuring the system to forward reported phishing emails to the mailbox using the Microsoft Report Message Add-in.

  Note - If the Microsoft account is already configured to forward reported phishing emails to an internal mailbox, this configuration will not be performed.