Export (0) Print
Expand All
4 out of 8 rated this helpful - Rate this topic

FOPE to EOP Transition FAQ

Exchange 2013

Applies to: Exchange Online Protection

Topic Last Modified: 2014-03-27

The following section is a list of frequently asked questions about the Forefront Online Protection for Exchange (FOPE) to Exchange Online Protection (EOP) transition. This FAQ applies only to FOPE to EOP standalone customers and not Office 365 upgrades. If you still have unanswered questions or need additional information regarding the transition please contact the FOPE Support team by calling 866.291.SPAM (7726). You can also open a support ticket by choosing the Get Help Now option in the FOPE Admin Center.

Q. When will my FOPE service be transitioned to EOP?

A. We will begin to transition FOPE customers to EOP in the third quarter of 2013. You will receive a notification when it is your turn to be transitioned. You will receive a minimum of 30 days’ notice prior to your transition.

Q. I can’t wait for the transition, is it possible for me to self-migrate?

Some customers have asked if they can self-migrate to EOP ahead of their scheduled upgrade, in order to take advantage of EOP’s new capabilities. We strongly recommend that you wait to be upgraded from FOPE to EOP in order to have the smoothest transition experience. Self-migration involves additional work, complexity, and risk. If you are interested in self-migrating, please see Forefront Online Protection for Exchange to Exchange Online Protection: Self Migration Guidance.

Q. I am not ready to be transitioned, can I push back my transition date?

A. If for any reason you are not ready after we have provided you with a specific transition date, we will provide you with a one-time option to postpone the transition for 30 days. You can request to postpone only after you have received your initial transition email. To postpone you will need to sign in to the FOPE Admin Center. You will notice a message at the top of the portal indicating that your transition has been scheduled. To postpone, click Click here for more options and follow the instructions.

If you don’t see a confirmation message in the FOPE Admin Center within 1 hour after requesting a postponement, please contact the transition team by emailing Move2EOP@microsoft.com.

Q. How long will the transition from FOPE to EOP take?

A. In nearly all cases, the process of migrating your FOPE settings to EOP will take less than 72 hours to complete. On occasion, though, we have a few upgrades that take longer. If this happens to you, don't worry, we haven't forgotten about you, and there isn't anything that you need to do. The service transition team meets daily to look at slower upgrade tasks and make sure we're doing everything that needs to be done. All of your mail will continue to be protected by FOPE until the transition of all of your settings to EOP is completed.

Q. I am currently subscribed to another Office 365 service. Will Microsoft transition my FOPE service to that Office 365 account?

A. We can transition your FOPE settings into your existing Office 365 account, but we ask that you inform us by emailing Move2EOP@microsoft.com prior to the kickoff of the transition. Provide us with your FOPE domain name and your Office 365 tenant domain name and we will take care of the rest.

Q. My FOPE subscription is about to expire and I have not transitioned to EOP, what do I do?

A. If your FOPE agreement expires prior to your transition to EOP, work with your partner or licensing specialist to renew your FOPE subscription. Do not purchase EOP prior to your transition. We will convert your active FOPE subscription to EOP as part of the transition.

Q. When do I have to update my MX record?

A. After we have transferred all of your settings to EOP, and you have received the Welcome to EOP email, you will have up to 45 days to switch your MX record. After 45 days, we cannot guarantee that your mail flow will continue through FOPE.

Q. Does EOP have a communication portal like in FOPE where I can find out about known issues and expected resolutions? What about new features?

A. The Office 365 admin center will have some of this information. If you are impacted by a Service Level Event then you should see a communication alert (typically accompanied by a bell icon) after signing in to the Office 365 admin center. We recommend that you read and act on any items as appropriate.

Regarding new EOP features, in addition to highlighting new features in the FOPE vs. EOP Feature Comparison topic, we’ll also be posting blog articles about new features to the Office Blogs website.

Q. Why are some migrated policy rules listed as version 14?

A. This just means that the rule is based off an Exchange Server 2010 Transport rule format, and is not a cause for alarm. All Exchange Transport rule options will be available for you to choose from.

Q. How can I ensure consistent delivery for my hybrid mail flow? 

  1. Your MX records should all be routed to Office 365 for any domains provisioned in Office 365.

  2. Your smart hosts should all be configured to deliver messages to the MX record for your own domain.onmicrosoft.com. For example: contoso-com.mail.eo.outlook.com.

  3. All recipient addresses must be present in Office 365 for all domains configured as “Authoritative” in the service.

  4. If all recipient addresses are not present in Office 365 then any domain missing recipient addresses must be configured as “Internal Relay” in the service in order to support relay through the service for unknown recipients.

  5. All mail-enabled users must have a valid route path for delivery:

    1. The default, and expected, delivery address specified in Office 365 for an on-premises mailbox is the primary SMTP address of the mailbox. If this is true in your scenario then delivery will follow the path defined for hybrid mail flow.

    2. If there is currently any internal recipient redirection taking place on-premises, that logic will be replicated to Office 365 via directory synchronization. If there is no public MX record for the domain being used as the “External email address” or “TargetAddress” for this redirection then the domain must be configured specifically in an Outbound connector.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
© 2014 Microsoft. All rights reserved.