Remote domains in Exchange Online
There are many reasons why you might want to control the types and the format of messages that your users send from Exchange Online to recipients in external domains. For example:
You don't want to let your users forward messages to recipients in other domains.
You work with an organization that you don't want to receive automatic messages from (for example, non-delivery reports and out-of-office replies).
You have a business partner that's outside your organization, and you'd like that partner to receive the same out-of-office replies as those received by people inside your organization.
Your users frequently send email to a company that supports limited email formats, and you'd like to make sure all emails sent to that organization are sent in a format that they can read.
To accomplish this, you use what's called a remote domain. The remote domain settings override settings that your users might configure in Outlook or Outlook on the web (formerly known as Outlook Web App), or that you configure in the Exchange admin center (EAC) or Exchange Online PowerShell. For example, users might have an out-of-office reply set up for people outside the organization, but if a sender from a remote domain sends mail to them, and the remote domain isn't set to receive out-of-office replies, no out-of-office reply is sent. To change the settings, you can:
Create a remote domain for a specific domain, and set unique properties for emails sent to that domain.
Modify the settings for the default remote domain. If you have no other remote domains set up, changes to the default remote domain apply to all external domains. If you have other remote domains set up, changes to the default remote domain apply to all other external domains.
For instructions on how to create and configure remote domains, see Manage remote domains in Exchange Online.
Reducing or increasing information flow to another company
When a message comes from outside your organization, there are several types of replies that are automatically generated. Some types of replies are set up by users in Outlook or Outlook on the web, and others are set up by admins. Because the remote domain settings override settings configured by users, as well as mail user and mail contact settings configured by admins, you can choose which types of automatic replies are sent to everyone on a remote domain.
If a remote domain configuration blocks a specific type of reply, like a non-delivery report, from being sent to recipients in that domain, the reply is generated, but then it's deleted before it's sent. No error message is sent. For example, if you turn off automatic forwarding on the default remote domain, when users try to automatically forward email to another domain, they can change their settings or create the Inbox rule, but their messages won't be forwarded.
The following table shows the types of replies you can control in a remote domain and the settings that each remote domain setting overrides.
|Type of reply
|Per-user settings that this remote domain setting overrides
|Specify whether an out-of-office message should be sent to people on the remote domain, and if so, which message to use. You can select either the reply that the user on your domain set up for people outside your organization, or the one for people inside your organization. The default is to send the out-of-office reply for people outside your organization.
|This setting overrides out-of-office reply settings specified by individual users in Outlook or Outlook on the web.
|Allow or prevent automatic replies to senders on the remote domain. The default is to allow automatic replies.
|This setting overrides automatic replies set up by admins using the Set-MailboxAutoReplyConfiguration cmdlet.
|Allow or prevent automatically forwarded messages to be sent to people on the remote domain. The default is to allow automatic forwarding.
|When users configure automatic forwarding to recipients on a remote domain, the remote domain settings override users' automatic forwarding settings (messages are blocked if automatic forwards are disabled for the remote domain). Users can configure automatic forwarding by using these methods:
Note: When admins use other methods to configure automatic forwarding for users, the forwarded messages aren't affected by the remote domain settings (messages are forwarded to recipients on the remote domain even if automatic forwards are disabled for the remote domain). For example:
|Allow or prevent a delivery receipt to be sent to people on the remote domain. The default is to allow sending delivery reports.
|An email sender on the remote domain can request a delivery receipt on a message. This remote domain setting can override the sender's request for a delivery receipt and prevent the delivery receipt from being sent. For more information about requesting a delivery receipt, see Add delivery receipt to track an e-mail message.
|Allow or prevent non-delivery reports (also known a NDRs or bounce messages) to be sent to people on the remote domain. The default is to allow sending non-delivery reports.
|This remote domain setting is the only way to prevent non-delivery reports from being sent when a message can't be delivered.
|Meeting forward notifications
|Prevent or allow meeting forward notifications to be sent to people on the remote domain. The default is to prevent sending meeting forward notifications.
|Meeting forward notifications are automatically created and sent to the meeting organizer when a meeting participant forwards a meeting. Typically, they're sent to meeting organizers only on domains that are part of your Exchange Online organization. Admins can enable them to be sent to meeting organizers on the remote domain.
Specifying message format
To make sure that email sent from your Exchange Online organization is compatible with the receiving messaging system in the remote domain, you can specify the message format and character set to use for all email messages sent to that remote domain. For example, if you know that the remote domain isn't using Exchange, you can specify to never use Rich Text Format (RTF). The following table describes the message format settings.
|Settings that this overrides
|Rich Text Format (RTF)
|Choose how to format messages:
The default is to follow the user's settings.
|Message format can be defined in several places: Outlook or Outlook on the web, and the admin can also use the Set-MailContact or Set-MailUser cmdlets to modify settings per recipient.
Remote domain settings override settings specified by a user or by the admin. For more information about the message formats and the order of precedence of message format settings, see Message format and transmission in Exchange Online.
|MIME character set and Non-MIME character set
By default, no character sets are specified.
|These settings are used only if the message doesn't include a character set. For a complete list of supported character sets, see Supported character sets for remote domains.
If you specify a particular message format for the remote domain, the format of the headers and message content sent to the domain are modified.
You can configure other message settings for remote domains by using Exchange Online PowerShell. For a complete list of settings, see Set-RemoteDomain.
You can't remove the default remote domain.
You can specify all subdomains when you create a remote domain.