Export (0) Print
Expand All

After your transition

Exchange 2013

Applies to: Exchange Online Protection

Topic Last Modified: 2014-07-07

After your transition from Forefront Online Protection for Exchange (FOPE) to Exchange Online Protection (EOP) is complete, you can become more familiar with administering your EOP service. The following video illustrates the steps contained in this topic.

Your browser does not support video. Install Microsoft Silverlight, Adobe Flash Player, or Internet Explorer 9.

We recommend that you view the migration report that details all the changes that were made to your settings when moving them from FOPE to EOP.  If at any time during the transition an error was encountered, and we were not able to transition a setting or policy, this information will appear in the report. To access your report click View your Migration Report. You will be redirected to sign in to the Office 365 admin center. The migration report is located under the service overview.

If you currently use the FOPE Directory Sync Tool to synchronize your user’s information from your on-premises Active Directory to FOPE, you should uninstall that tool after your transition to EOP. EOP uses the same directory synchronization tool as Office 365: the Windows Azure Active Directory Sync tool. If your user’s UPN or SMTP addresses are using a domain that’s not verified for your tenant in Office 365, then we will:

  • Replace the UPN with an @yourdomain.onmicrosoft.com address

  • Remove the SMTP addresses for the missing domains

To set up directory synchronization, see "Use directory synchronization to manage mail users" in Manage mail users in EOP.

If you receive a directory synchronization report that contains an "incompatible object type" error, see the following article: Directory synchronization report contains an "incompatible object type" error in Office 365 or Exchange Online Protection.
EOP does not support uploading a user list by using the Secure File Transfer Protocol (SFTP). However, FOPE tenants who used SFTP to upload users and manage virtual domains can use remote Windows PowerShell in EOP to upload users and add users to distribution groups. For more information, see Use remote Windows PowerShell to manage users by using FOPE SFTP files.

If you want to use Directory Based Edge Blocking (DBEB) feature, which lets you reject messages for invalid recipients at the service network perimeter, after you’ve been transitioned and synchronized your users, you can enable DBEB by setting your domain to Authoritative. For more information about how to do this, see Manage Accepted Domains in EOP.

EOP features an enhanced administration experience built on the same platform as Office 365. To understand how to perform common FOPE tasks in this new environment, see Accomplishing common FOPE administrative tasks in EOP.

After your transition is complete, there will be an extended period of time when you can continue to sign in to the FOPE Admin Center to reference your FOPE settings. For example, you may want to reference a particular FOPE policy rule that was changed to an Exchange Transport rule. For more information, see Sign in to the FOPE Admin Center after your service upgrade.

If your MX record currently points to FOPE, you’ll need to update your MX record to point to the new service so that your inbound email flows through EOP rather than FOPE. Examples of MX records that point to FOPE that you’ll need to change are as follows:

  • Mail.global.frontbridge.com

  • Mail.messaging.microsoft.com

  • Mail.global.sprint.com

  • Mail.us.messaging.microsoft.com

Transition update: As we approach the completion of the FOPE transition we want to make sure that you’re aware of the following update. If you’ve already been transitioned, please follow the guidance in your transition email communication to update your MX records. For those of you who are unable to update your MX records according to the deadlines stated in your transition communication, Microsoft will automatically redirect your mail flow through EOP to preserve continuity of your mail delivery and filtering. Automatic redirects can occur any time between your communicated deadline and July 2014.

  • You should not go through the following steps if your MX record is not pointing to the FOPE service.

  • Until your MX record and smart host information are updated, your email messages will continue to route through FOPE and be protected by the FOPE service.

  • Do not change your Autodiscover record when updating your MX record.

To update your MX record, perform the following steps:

  1. Sign in to the Office 365 admin center.

  2. On the left pane of the Office 365 admin center click Domains.

  3. Select the domain for which you would like to set up your MX record.

  4. Click Active. You will be redirected to the DNS Management Page.

  5. Under DNS records, click View DNS records.

  6. Update your DNS hosting provider with the new MX record information shown in the required setting table.

For more information, you can also read Create DNS records for Office 365.

To ensure that outbound email from your on-premises email system is routed through EOP instead of FOPE, you need to update your on-premises smart host information by using the same Fully Qualified Domain Name (FQDN) that is used in your domain’s MX record. The correct FQDN can be found by following the first 5 steps in the previous procedure.

For more information about how to set this up, see Set Up an On-Premises Connector to Send Outbound Email to EOP.

Depending on how you configured spam messages to be handled in FOPE, you may want to educate your users about changes they will see after moving to EOP.

If you have configured FOPE to send spam messages to users’ Junk Email folders:

In this case, users will not experience any changes to the way they manage spam. Before and after your transition, junk email messages will be delivered to users’ Junk Email folders in Outlook and Outlook Web App.

If you have configured FOPE to place spam messages in the quarantine:

After transition, users will stop managing spam messages in the FOPE quarantine, because no new spam messages will arrive there. Instead, spam messages will be quarantined in EOP.

If enabled, users will begin to receive end-user spam notifications from EOP shortly after your transition is complete. End-user spam notifications in EOP look similar to FOPE spam notifications. End users can use end-user spam notification messages to release their own spam-quarantined messages and optionally report them as not junk to Microsoft. For more information, see Use end-user spam notifications to release and report spam-quarantined messages.

End users with a valid Office 365 user ID and password can also manage their own spam-quarantined messages from the Exchange admin center (EAC) web-based user interface. For more information, see Find and release quarantined messages as an end user.

Emails in the FOPE quarantine will be available until they expire based on the quarantine retention policy set in FOPE. FOPE quarantined messages will not be transitioned to EOP.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft