For example, xxx.yy.157.139 would be the Data 1 interface IP address for ESA1, and xxx.yy.158.153 would be Data 1 interface IP address of ESA2. Note: The IP addresses that you see in the screen shot above would be proportional to the number of ESA's which are provisioned to your allocation. At a minimum, allow 1 hour for all changes to take effect. Note: It is highly recommended that you test these settings well before any planned production mail cut-over, because settings may take time to replicate in the Microsoft 365 Exchange console. You can use the assigned IPs or hostnames in the Microsoft 365 configuration. The IPs are dedicated to each client and are not likely to change without notification. If you have not received or do not have a copy of the letter, please contact with your contact information, customer name, and domain name under service. In addition to the letter which you see below, you will also receive an encrypted email that provides you with additional details on the number of Cloud Gateway (aka ESA) and Cloud Email and Web Manager (aka SMA) provisioned for your allocation. Your Cisco Secure Email welcome letter includes your Cloud Gateway IP addresses and other pertinent information. If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.
#EMAIL SETTINGS LOOKUP OFFICE365 SOFTWARE#
This document is not restricted to specific software and hardware versions. CLI access to your Cisco Secure Email Cloud Gateway environment:.Cisco Secure Email Gateway or Cloud Gateway.Prerequisites RequirementsĬisco recommends that you have knowledge of these topics: This document covers the steps required to integrate Cisco Secure Email with Microsoft 365 for inbound and outbound email delivery.