FOPE to EOP transition FAQ
Applies to: Exchange Online Protection
Topic Last Modified: 2014-06-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’s your turn to be transitioned.
Q. I can’t wait for the transition, is it possible for me to self-migrate?
A. 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. 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. My transition started more than 72 hours ago. Why have I not seen an update?
A. If your transition has been proceeding for longer than 72 hours, please contact the FOPE Support team by calling 866.291.SPAM (7726). You may also open a support ticket by choosing the Get Help Now option in the FOPE Admin Center.
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 calling 866.291.SPAM (7726) 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. I received an email stating that you won’t transition my FOPE settings because we’re self-migrating. We’re not self-migrating; how do we get Microsoft to transition us to EOP?
A. If you received an email notice informing you that you won’t be transitioned, and you want us to transition your settings from EOP to FOPE, please contact the FOPE Support team by calling 866.291.SPAM (7726). Please provide them with your customer name and Office 365 tenant name (your tenant name is the *.onmicrosoft.com domain name) and instructions that you would like Microsoft to transition your settings into the existing Office 365 tenant.
Q. I was recently transitioned from FOPE to EOP and I would like to change my *.onmicrosoft.com domain name. How can I do that?
A. As of May 15 2014, we are no longer taking any requests to change any *.onmicrosoft.com domain names. We apologize for any inconvenience this may cause.
Q. My FOPE is currently locked and I’m not ready to switch my MX record. Can you unlock me?
A. At this time we won’t be able to unlock your FOPE Admin Center console. If you need to make any policy updates please switch your MX record to EOP. From there you’ll be able to update any filtering policies.
Q. I was transitioned over 45 days ago and I was told I needed to switch my MX record now or else my mail flow will stop. Can I get it extended?
A. If you’ve already been transitioned and you still need to change your MX records, please do so immediately. 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.
Q. When do I have to update my MX record?
A. 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.
Q. How long do I have until the legacy FOPE MX records are no longer supported?
A. We will continue to support the legacy FOPE MX records, but to take advantage of all the features that EOP has to offer, such as regional routing for those who are located outside of the Americas, you’ll still be required to switch your MX record to point to EOP.
Q. Why should I switch my MX record if Microsoft is going to do the work for me?
A. We’re encouraging all customers to switch their MX record to point to EOP. By not switching your MX record, you won’t able to take advantage of all the new features of EOP (for example, regional routing will be disabled).
Q. My company is located outside of the Americas, what happens if I don’t switch over my MX record?
A. If you don’t switch your MX record according to the deadline indicated in your transition communications, we’ll automatically route your mail through the EOP data centers in the Americas. If you’re located outside of the Americas, you must change your MX record in order to take advantage of regional routing and have your mail routed through data centers outside of the Americas.
Q. I’m not using an MX record and instead have hard-coded IP addresses to point to FOPE. Will the IP addresses be redirected to EOP?
A. No, Microsoft is only redirecting the fully qualified domain names (FQDN) used in FOPE MX records (for example, mail.global.microsoft.com). Microsoft does not recommend or support configurations that use hard-coded IP addresses, and you must change such configurations to use the same FQDN as the EOP MX record to avoid service disruption when the FOPE service is no longer in operation.
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.
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?
Your MX records should all be routed to Office 365 for any domains provisioned in Office 365.
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.
All recipient addresses must be present in Office 365 for all domains configured as “Authoritative” in the service.
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.
All mail-enabled users must have a valid route path for delivery:
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.
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.
Q. I’m a reseller and I need to manage my customer’s tenants; how does this work?
A. For details, see Delegated administration FAQ.