Forum Discussion
Solved
[Exchange Online - Address Book] What to do with OAB when wrapping up local infra after migration?
Hey there guys, I am really near to a point where I will wrap up local exchange infrastructure (leaving only one server for management) and fully move to O365 Exchange Online. Thing is I got ...
- if all of your users have migrated to Exchange Online then you don't need to worry about your address book as no one uses it when all mailboxes are in the cloud. They get their address book from Exchange Online.
Here is an article that should help:
"How and when to decommission your on-premises Exchange servers in a hybrid deployment"
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx
Depending upon the size of your organization and the criticality of mail flow, I usually recommend people leave behind one or two lightweight Exchange VM's to perform the role of SMTP relay to Exchange Online. Some people use IIS SMTP servers for that, which is fine, but for managing user objects when Azure AD Connect is syncing accounts, you'll still benefit from at least one Exchange server to perform that user management. Therefore, the case I make is, if you are going to have at least one server for user management, why not continue to use that for SMTP relay? That way you don't have to change your scanners/copiers/applications to point to a new SMTP relay server?
At the Microsoft Ignite conference, Microsoft announced that they will be making improvements to the Hybrid configuration so that in the future you will be able to perform user management directly in the cloud interface even if you have Azure AD Connect enabled, which means you then won't need those Exchange management servers on prem (at that time you would then need to transition to an SMTP Relay server).
Here is a good ignite video you may want to watch:
https://myignite.microsoft.com/sessions/55014?source=sessions
if all of your users have migrated to Exchange Online then you don't need to worry about your address book as no one uses it when all mailboxes are in the cloud. They get their address book from Exchange Online.
Here is an article that should help:
"How and when to decommission your on-premises Exchange servers in a hybrid deployment"
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx
Depending upon the size of your organization and the criticality of mail flow, I usually recommend people leave behind one or two lightweight Exchange VM's to perform the role of SMTP relay to Exchange Online. Some people use IIS SMTP servers for that, which is fine, but for managing user objects when Azure AD Connect is syncing accounts, you'll still benefit from at least one Exchange server to perform that user management. Therefore, the case I make is, if you are going to have at least one server for user management, why not continue to use that for SMTP relay? That way you don't have to change your scanners/copiers/applications to point to a new SMTP relay server?
At the Microsoft Ignite conference, Microsoft announced that they will be making improvements to the Hybrid configuration so that in the future you will be able to perform user management directly in the cloud interface even if you have Azure AD Connect enabled, which means you then won't need those Exchange management servers on prem (at that time you would then need to transition to an SMTP Relay server).
Here is a good ignite video you may want to watch:
https://myignite.microsoft.com/sessions/55014?source=sessions
Here is an article that should help:
"How and when to decommission your on-premises Exchange servers in a hybrid deployment"
https://technet.microsoft.com/en-us/library/dn931280(v=exchg.150).aspx
Depending upon the size of your organization and the criticality of mail flow, I usually recommend people leave behind one or two lightweight Exchange VM's to perform the role of SMTP relay to Exchange Online. Some people use IIS SMTP servers for that, which is fine, but for managing user objects when Azure AD Connect is syncing accounts, you'll still benefit from at least one Exchange server to perform that user management. Therefore, the case I make is, if you are going to have at least one server for user management, why not continue to use that for SMTP relay? That way you don't have to change your scanners/copiers/applications to point to a new SMTP relay server?
At the Microsoft Ignite conference, Microsoft announced that they will be making improvements to the Hybrid configuration so that in the future you will be able to perform user management directly in the cloud interface even if you have Azure AD Connect enabled, which means you then won't need those Exchange management servers on prem (at that time you would then need to transition to an SMTP Relay server).
Here is a good ignite video you may want to watch:
https://myignite.microsoft.com/sessions/55014?source=sessions
Hey Joe,
Thanks for clarifying the case, we do leave one server to be SMTP relay and to use it for management - anyway the license is free. Thanks for the link to the ignite as well.
By the way you just reminded me one thing - we got this one Exchange 2016 with one free license (we obtained hybrid license) on-premise, however we use edge server to connect it to our O365 tennant - we do not publish out hybrid server directly to the o365 (And if I am not wring we use normal license for Edge server). Is license for such edge also free and we can apply same license on Edge as has been applied on a hybrid server?
Thanks for clarifying the case, we do leave one server to be SMTP relay and to use it for management - anyway the license is free. Thanks for the link to the ignite as well.
By the way you just reminded me one thing - we got this one Exchange 2016 with one free license (we obtained hybrid license) on-premise, however we use edge server to connect it to our O365 tennant - we do not publish out hybrid server directly to the o365 (And if I am not wring we use normal license for Edge server). Is license for such edge also free and we can apply same license on Edge as has been applied on a hybrid server?
- According to the licensing FAQ, Exchange 2016 does not require a license, so I would take that to include an Exchange 2016 edge server too but you can/should clarify with your license reseller.
https://products.office.com/en-us/exchange/microsoft-exchange-licensing-faq-email-for-business
Another similar question was asked here:
https://social.technet.microsoft.com/Forums/exchange/en-US/155170dc-faee-43c6-9d60-0cf0e97bd7d9/license-for-2010-edge-transport-?forum=exchange2010
My question for you is why not just point your MX records at EOP and avoid the need to maintain an edge server altogether? seems like that would eliminate the single point of failure on-prem and reduce your security exposure (less servers for you to patch and maintain,etc).