We are currently looking at deploying Office 365 with Exchange 2010 in Hybrid mode. One of the deployment question i have is the specific MX record configuration. If we configure the Primary MX to point to the On-Premise Exchange implementation then all mail will route throught here to Office 365.....fine If we have a problem with out on-Premise solution i would like to have a secondary MX record that points to Office 365 (FOPE) and will queue the mail for delivery untill the on-premise solution comes back on line. Is this possible? Thanks for the help Tony

On Fri, 4 Nov 2011 17:50:55 +0000, flipper1974 wrote: > > >We are currently looking at deploying Office 365 with Exchange 2010 in Hybrid mode. One of the deployment question i have is the specific MX record configuration. If we configure the Primary MX to point to the On-Premise Exchange implementation then all mail will route throught here to Office 365.....fine > >If we have a problem with out on-Premise solution i would like to have a secondary MX record that points to Office 365 (FOPE) and will queue the mail for delivery untill the on-premise solution comes back on line. > >Is this possible? Thanks for the help It's certainly a service the MS sells. It's not part of Office 365, though. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

It may be possible but I;m quite aure that it's not supported, there's 2 scenarios, a shared or split namespace. Other's I know of who have a hybrid solution dont have this setup. http://technet.microsoft.com/en-us/library/hh134171.aspxSukh

Thanks for the replies, In our planned hybrid deployment we will have some of our users (40) in the cloud and the majority on-premise (around 80)...... We plan to have the MX (its a shared domain for the hybrid deployment ) pointing at the on-premise solution. If for what ever reason the on-premise solution goes down the users in Office 365 will not be able to receive inbound mail? What i would like to do is have a second MX pointing at the Office 365 solution so in the event of loss of the on-premise solution half the users can still function? Does this make sense? Thanks for the help Regards T

Thanks for the replies, In our planned hybrid deployment we will have some of our users (40) in the cloud and the majority on-premise (around 80)...... We plan to have the MX (its a shared domain for the hybrid deployment ) pointing at the on-premise solution. If for what ever reason the on-premise solution goes down the users in Office 365 will not be able to receive inbound mail? What i would like to do is have a second MX pointing at the Office 365 solution so in the event of loss of the on-premise solution half the users can still function? Does this make sense? Thanks for the help Regards T yes it makes sense and it is possible, but like i said, i dont hink this is supported. I'll try and find out for you. Alternative is to make your gateway/edge/hub HA. Make sure your on prem is HA/DR. This will work As for the 2nd MX, it would me O365 will have to have an accepted domain for your onprem namespace, which yu have to do nayway, but this will have to be an internal relay domain. This is where i dont think it is supported. Also, even if yu could do this, say if an email isnt to the one of hte 80 users and FOPE cant get to on prem coz of the issues, I'm quite sure FOPE will send on an DSN/NDR depending on the issue. Email will only go to the 40. Nice thought but I htink you should invest in your on prem (HA/DR).Sukh

On Sat, 5 Nov 2011 13:10:04 +0000, flipper1974 wrote: >Thanks for the replies, In our planned hybrid deployment we will have some of our users (40) in the cloud and the majority on-premise (around 80)...... That's a lot of work for such a small number of mailboxes! Why'd you make the decision to use a hybrid configuration? >We plan to have the MX (its a shared domain for the hybrid deployment ) pointing at the on-premise solution. If for what ever reason the on-premise solution goes down the users in Office 365 will not be able to receive inbound mail? They won't be able to SEND e-mail to anyone except those in your domain with mailboxes on O365, either. If you're setting up rich co-existence and single sign-on they won't even be able to log on to O365 if your AD FS proxies (or AD FS servers) aren't accessible. As I said, for such a small number of mailboxes you seem to be willing to expend money for additional servers and server licenses, and time to configure this to work correctly, for what is probably not a lot of benefit if all you're going to use it for is e-mail. >What i would like to do is have a second MX pointing at the Office 365 solution so in the event of loss of the on-premise solution half the users can still function? Does this make sense? To you it makes sense. To the way Office 365 works with a hybrid configuration it doesn't. You're responsible for all e-mail inflow and outflow in a hybrid configuration. Office 365 talks only to your co-existence servers (HT and CAS). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Sat, 5 Nov 2011 13:10:04 +0000, flipper1974 wrote: >Thanks for the replies, In our planned hybrid deployment we will have some of our users (40) in the cloud and the majority on-premise (around 80)...... That's a lot of work for such a small number of mailboxes! Why'd you make the decision to use a hybrid configuration? >We plan to have the MX (its a shared domain for the hybrid deployment ) pointing at the on-premise solution. If for what ever reason the on-premise solution goes down the users in Office 365 will not be able to receive inbound mail? They won't be able to SEND e-mail to anyone except those in your domain with mailboxes on O365, either. If you're setting up rich co-existence and single sign-on they won't even be able to log on to O365 if your AD FS proxies (or AD FS servers) aren't accessible. As I said, for such a small number of mailboxes you seem to be willing to expend money for additional servers and server licenses, and time to configure this to work correctly, for what is probably not a lot of benefit if all you're going to use it for is e-mail. >What i would like to do is have a second MX pointing at the Office 365 solution so in the event of loss of the on-premise solution half the users can still function? Does this make sense? To you it makes sense. To the way Office 365 works with a hybrid configuration it doesn't. You're responsible for all e-mail inflow and outflow in a hybrid configuration. Office 365 talks only to your co-existence servers (HT and CAS). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi flipper1974, Any udpate for your issue? Regards! Gavin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hello Rich, Thanks for the replies, It may seem not worth it but, due to a merging of two companies the users are spread across two offices and continents, with the on-premise solution already up and running and MX pointing to it (didnt want to complicate the matter on initial post!). We are looking at the options for cloud based email for the second office, but would like to have some cross site resilience (Multiple MX) in the event of the On-Premise going down. We will have to implement domain controllers at the new office so could have implemented a HT and CAS to cater for resilience? If its only possible to have the MX pointing at Office 365 OR On-Promise with no secondary record then so be it. I will highlight this when we evaluate the cost / benefit. Thaks again for the replies T

On Mon, 7 Nov 2011 09:16:55 +0000, flipper1974 wrote: > > >Hello Rich, > >Thanks for the replies, It may seem not worth it but, due to a merging of two companies the users are spread across two offices and continents, with the on-premise solution already up and running and MX pointing to it (didnt want to complicate the matter on initial post!). We are looking at the options for cloud based email for the second office, but would like to have some cross site resilience (Multiple MX) in the event of the On-Premise going down. We will have to implement domain controllers at the new office so could have implemented a HT and CAS to cater for resilience? > >If its only possible to have the MX pointing at Office 365 OR On-Promise with no secondary record then so be it. I will highlight this when we evaluate the cost / benefit. If you're going to go the hybrid route then the ONLY place your MX can direct e-mail is to your on-prem location(s). If you want to have a primary and secondary on-prem that's fine, but you'll need co-existence servers in multiple locations. The people in your on-prem system won't have access to mail if that site is down. If you're going to use rich co-existence you'll also need single sign-on (in multiple locations if you want to remain in operation if one site is inaccessible!) and directory synchronization. My advice would be to abandon your on-prem Exchange and simply migrate to O365 (or some other hosted provider). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Mon, 7 Nov 2011 09:16:55 +0000, flipper1974 wrote: > > >Hello Rich, > >Thanks for the replies, It may seem not worth it but, due to a merging of two companies the users are spread across two offices and continents, with the on-premise solution already up and running and MX pointing to it (didnt want to complicate the matter on initial post!). We are looking at the options for cloud based email for the second office, but would like to have some cross site resilience (Multiple MX) in the event of the On-Premise going down. We will have to implement domain controllers at the new office so could have implemented a HT and CAS to cater for resilience? > >If its only possible to have the MX pointing at Office 365 OR On-Promise with no secondary record then so be it. I will highlight this when we evaluate the cost / benefit. If you're going to go the hybrid route then the ONLY place your MX can direct e-mail is to your on-prem location(s). If you want to have a primary and secondary on-prem that's fine, but you'll need co-existence servers in multiple locations. The people in your on-prem system won't have access to mail if that site is down. If you're going to use rich co-existence you'll also need single sign-on (in multiple locations if you want to remain in operation if one site is inaccessible!) and directory synchronization. My advice would be to abandon your on-prem Exchange and simply migrate to O365 (or some other hosted provider). --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hybrid Routing - Pointing your MX record to the Cloud http://community.office365.com/en-us/w/exchange/514.aspxEnzo Pierfelice - LinkedIn