Avanan now introduces infrastructure enhancements to further support inline inspection for Microsoft 365 Emails, including updates to Avanan’s footprint within customers’ Microsoft 365 and Microsoft Azure environments.

As part of ongoing investments to support the growing scale of Avanan customers, the infrastructure responsible for inline inspection for Microsoft 365 Emails is being upgraded to ensure continued alignment with Microsoft platform requirements and service architecture.

The update includes several modifications within Microsoft environments – a new connector, new Avanan sending infrastructure added to the customer’s Tenant Allow/Block List (TABL), and exclusions from certain Avanan transport rules and TABL entries. In addition, new Avanan IP addresses will be excluded from transport rules created by Avanan and from the default connection filter. Together, these changes update Avanan’s service footprint in Microsoft 365 and Microsoft Azure while maintaining seamless inline inspection and policy enforcement for Microsoft 365 Emails.

What This Means for Customers

For customers who have already enabled inline inspection for Microsoft 365 Emails and are deployed in Automatic Mode, Avanan will apply the required modifications automatically over the next 2 – 3 months. Audit logs reflecting these changes will appear in Microsoft 365, and some monitoring systems may generate alerts. These alerts can be safely ignored. Customers who prefer not to have these updates applied automatically can contact Avanan Support and follow the manual instructions provided in the knowledgebase article:
https://support.checkpoint.com/results/sk/sk184699

For customers who have not yet enabled inline inspection for Microsoft 365 Emails, the required infrastructure changes will be applied automatically once inspection is enabled.

For new customers, these updates will be incorporated into the automatic onboarding process going forward.

Customers who deployed Avanan manually are encouraged to follow the step-by-step guidance outlined in the same knowledgebase article to ensure alignment with the updated infrastructure.