Microsoft Office Tutorials and References
In Depth Information
Changing an MX record
INSIDE OUT Enable centralized mail transport: yes or no?
The reason most organizations enable centralized mail transport is because of special
compliance requirements such as on-premises Data Leakage Prevention (DLP).
However, with DLP now available in the latest release of Office 365, the reasons for enabling
centralized mail transport are further reduced. Furthermore, this adds additional hops
and latency to email delivery, not to mention your on-premises Exchange environment
might be at risk of becoming a single point of failure. Therefore, unless you have
specific compliance requirements that can be met only by having to route Internet-bound
emails through your on-premises Exchange environment, the recommendation is that
you should not enable centralized mail transport.
Enabling and disabling centralized mail transport
Before you change your MX record, decide whether to enable centralized mail transport.
Remember, too, that centralized mail transport is not enabled by default. If you need to
turn centralized mail transport on or off, you can do so with the EMC or through Windows
PowerShell.
Enabling and disabling centralized mail transport with EMC
Follow these steps and refer to Figure 11-94 to enable or disable centralized mail transport
with the EMC:
1. Start the EMC, expand the Microsoft Exchange On-Premises node, and click
Organization Configuration.
2. On the main EMC pane, select the Hybrid Configuration tab.
3. On the Actions pane, click Manage Hybrid Configuration.
4. Because you are not changing anything else except for centralized mail transport,
click Next on each page of the Manage Hybrid Configuration Wizard until you get to
the Mail Flow Security page, as shown in Figure 11-94.
5. Under Mail Flow Path, choose to route email directly using DNS settings or route all
Internet-bound email through your on-premises Exchange environment.
6. Click Next.
7. Click Manage.
Search JabSto ::




Custom Search