Awesome information and great video, please kindly upload more videos related to all kinds of technical issues and scenarios related to Office 365 and Email and Exchange Server
Great video! Thanks! I have a coworker who is against going hybrid before migration due to potential issues hybrid may cause, but personally, I don't see the drawbacks of going hybrid while in the migration process? We're currently running on-prem 2016 Exchange and will be moving to Exchange Online. Do you have any thoughts on why you would not want to go hybrid before migraiton?
Hello Bill, thanks for your comments. One of the disadvantages of a Hybrid Migration and using Azure AD Connect requires you to keep an Exchange Server in your environment because Azure AD Connect locks objects in your Active Directory. Therefore with it you would be unable to change or manage user attributes in Office 365. Third-party management tools such as ADSIEDIT are not supported. You could turn this into an advantage, as keeping an Exchange on-premises server could be used as a local SMTP service or gives you the option to migrate back from Exchange Online in the future if required.
Hi Hossein. Yes use a Cloudinspired lab with VMware Virtual Machines - DC, AD Connect and Exchange Servers location either On-Premise or IaaS VMs in the Azure Cloud in a hybrid environment, together with Office 365 tenant. It works really well for testing purposes, migrations, training and demos.
How can you describe the difference of this mailboxes consolidation and migration on premise to exchange to office 365 with Quest on demand migration tools, if you could explain a little bit about the benefit
What about Autodiscover and all the other stuff, is any configuration required there? Also what about Federation, is any federation required for hybrid exchange? or all of this handled by the Hybrid Agent?
Hi Rujoi, It used to be the case where orgainisations must have a running Exchange server in the environment for recipient management activities. You couldn`t manage most attributes from Exchange Online. Instead, you used to have to manage those attributes from on-premises. This was a requirement but is no longer the cae with 2022 H1 Cumulative Update, therefore with a view to shut down the last Exchange server(s) and use Windows PowerShell for recipient management. More information here: techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026
Great video! Have one question though: CompanyA has an Exchange on-prem and O365 hybrid configuration like in your video as they want to migrate all mailboxes to O365. CompanyA acquires CompanyB, that has Exchange on-prem only. What do you suggest? A) Migrate CompanyB to Company Exchange on-prem and them migrate mailboxes to O365 B) Set up another hybrid between CompanyB on-prem and CompanyAs O365 tenant Thanks in advance!
Hi Douglas - Thanks for the comments. For option B - Having more than one Azure AD Connect sync server connected to a single Azure AD tenant is not supported. Supported topologies for Azure AD Connect are covered in this article which should help you for different scenarios. docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies%C2%A0
Hi! Thanks for your video. I'm planning hybrid with Exchange 2013. Do you think it's a problem using a third party connector for email download. Should I change this to direct download via the Exchange and change the MX Record?
Hi. Author: I don't see where in your steps of configuration Quest Migration Manager was configured to play a role in the migration. The migration you configured just include all of Microsoft's migration tools: AAD Connect, the Exchange Hybrid migration wizard, O365 Admin center, and the O365 Exchange Admin Center for migration. Did I missed something?
Hi Harrison, Quest Migration Manager wasn`t used in this video for the Exchange on-premise migration to Exchange Online. Microsoft tools were only used.
My client don't want to use Exchange Online, but wants to stay on his own Exchange On-prem 2016. Mainly because of Microsoft Teams, as the Teams calendar currently doesn't work with his mailbox. He do however pay for a 365 license without Exchange. Is it possible to combine the 2 without migrating?
Great video !!! i have an Query. My organization has been running in a hybrid configuration I need to manage my users from on-premises and also need for directory synchronization or password synchronization to access for the application in on premises and O365 I have planned to move all of my mailboxes alone to Exchange Online. please let me know, if i can decommission the on premises exchange server alone once i move all the mailbox to O365.
Hi Senthil, thanks for your comment. One of the disadvantages of a Hybrid Migration and using Azure AD Connect requires you to keep an Exchange Server in your environment because Azure AD Connect locks objects in your Active Directory. if you are still using Azure AD Connect to sync your accounts to the cloud then the only supported way to manage recipients is with a local Exchange Server. Therefore without it you would be unable to change or manage user attributes in Office 365. Third-party management tools such as ADSIEDIT are not supported. You could turn this into an advantage, as keeping an Exchange on-premises server could be used as a local SMTP service or gives you the option to migrate back from Exchange Online in the future if required.
This is great video for Hybrid mode thanks. I’m after the same detail but for just straight migration from Exchange on prem to M365 and shutting down the on prem stuff immediately after mailbox migration. Do you have a Step-By-Step for that one?
Hello, Thanks both for your comments. After directory synchronization (user is synced from on-premise) most of the attributes cannot be managed from Exchange Online and must be managed from on-premises. In the article below it explains why you may not want to decommission Exchange servers from on-premises after a hybrid configuration. The other migrations possible are cutover, staged exchange migration etc. I`ll note these for future videos! How and when to decommission your on-premises Exchange servers in a hybrid deployment docs.microsoft.com/en-us/exchange/decommission-on-premises-exchange
Thanks for the guide but the way you explained some things, like virtual directories, if I understood eveything you just said there then I wouldn't need this guide in the first place.
can you help me? when i installed the HCW, it has some error regarding the migration endpoint couldn’t be created and no EWS service was listening on the specified endpoint. couldn’t detect the MRS proxy server automatically
Hello, there is a article here to troubleshooting issues where the hybrid migration endpoint cannot be created learn.microsoft.com/en-gb/archive/blogs/exovoice/troubleshooting-issues-where-the-migration-endpoint-cannot-be-created-in-hybrid-scenarios .Please also check your firewall it must allow the incoming connections on URL containing /ews/mrsproxy.svc, in case it is using URL filtering, or if possible, you can allow all the incoming traffic on port 443. If you are using an IP filtering configuration in the firewall, you should make sure that you have the updated Exhange Online IP list in the firewall configuration, you can find IP ranges list for Exchange Online in that article. Also using the Test-MigrationServerAvailability command you can test access to the MRSProxy. Hope that helps.
Do you have a video that is post this that explains how to get the asure AD or 365 Tenant first or whatever else one might need to do to get this this step?
Hi Andrew, you would need to create a new Azure tenant/subscription, can start here azure.microsoft.com/en-gb/free/. For the hybrid synchronize on-premise Active Directory users to Azure Active Directory (Entra ID) there are are videos below in the Cloud Inspired channels covering this setup. How to setup & install, from start to finish using Azure AD Connect to synchronize on premise Active Directory users to Azure Active Directory in a hybrid model. ruclips.net/video/898r84nVqaA/видео.html Azure AD Connect V2 | Step by Step Installation Upgrade ruclips.net/video/NPD3Idgo1LA/видео.html
Thanks for the video. Is it possible to do an ultra minimal migration using this method? I have a client using Exchange 2013 with a local AD and a 365 Azure AD tenant that are wholly separate. I think I would prefer to keep them separate - their local security practices aren't good and I do not have time to fight them over it. Their 365 tenant is under the same domain. I would like to simply migrate their mailboxes to their existing 365 user accounts then cut over to Cloud Exchange, leaving the local AD untouched with no sync other than mailbox data.
Take a look at "decide on a migration path in Exchange Online" Microsoft article below which includes a Express migration to see if it meets your requirements. learn.microsoft.com/en-us/exchange/mailbox-migration/decide-on-a-migration-path
Hi Ashish, for a Exchange hybrid deployment, you need to use a certificate from a trusted third-party CA. docs.microsoft.com/en-us/exchange/certificate-requirements
Hi Hossein, The Microsoft 365 or Office 365 Exchange license can be allocated after the migration is complete. There is a grace period of 30 days to assign the license. docs.microsoft.com/en-us/exchange/hybrid-deployment/move-mailboxes
Recently I subscribe m365 business basic, my exist email service provider is rackspace. All user's email configured in I map. Can you pl help me how to migration wil work
Hi Kumar, This video is about migrating from Exchange on-premise to Office 365. First I would check with Rackspace to see if they have any migration documentation to migrate from their platform.
Technically fine, but pathetic use of English... "Premises" are a location or site. "Premise" are the assumptions upon which other inferences are made. If you really can't manage the two extra syllables and can't say, for example, "on site", which is equally valid, you could muster the ugly "on-prem". But the continued use of "on premise"? This is just butchering English and it makes the speaker look uneducated and lazy. Were English a second language, making the same mistake as a lot of other people is one thing, but a native English speaker? Not someone I will trust to tell me the weather let alone technical migration strategies. Can't get past the grade 7 vocabulary, sorry.
Andrew, as you state in your comment "on-site" is equally as vaild as "on-premise". Throughout this video the term "on-premise" is used, this is a commonly referred and referenced across Microsoft documentation. Which for clarity, refers to IT infrastructure hardware and software applications that are hosted on-site. Therefore the use of this term is correct and has nothing to do with your disrespectful comments on the speakers use of English.
Excellent demonstration
Glad it was helpful!
The most Perfekt Guide
Thank you.
You're very welcome!
Awesome information and great video, please kindly upload more videos related to all kinds of technical issues and scenarios related to Office 365 and Email and Exchange Server
Thanks Suprito, noted for future videos!
@@CloudInspired Thanks waiting for the same
Great video! Thanks! I have a coworker who is against going hybrid before migration due to potential issues hybrid may cause, but personally, I don't see the drawbacks of going hybrid while in the migration process? We're currently running on-prem 2016 Exchange and will be moving to Exchange Online. Do you have any thoughts on why you would not want to go hybrid before migraiton?
Hello Bill, thanks for your comments.
One of the disadvantages of a Hybrid Migration and using Azure AD Connect requires you to keep an Exchange Server in your environment because Azure AD Connect locks objects in your Active Directory.
Therefore with it you would be unable to change or manage user attributes in Office 365. Third-party management tools such as ADSIEDIT are not supported.
You could turn this into an advantage, as keeping an Exchange on-premises server could be used as a local SMTP service or gives you the option to migrate back from Exchange Online in the future if required.
Thanks Great video. Please upload more
Thanks Hossein, will do. Glad you liked the video!
@@CloudInspired Do you have a Lap for home training? Like few DC`s and a exchange On-Promise and AAD+Office365 etc....
Hi Hossein. Yes use a Cloudinspired lab with VMware Virtual Machines - DC, AD Connect and Exchange Servers location either On-Premise or IaaS VMs in the Azure Cloud in a hybrid environment, together with Office 365 tenant.
It works really well for testing purposes, migrations, training and demos.
Thanks, it was awesome
You're welcome KG
How can you describe the difference of this mailboxes consolidation and migration on premise to exchange to office 365 with Quest on demand migration tools, if you could explain a little bit about the benefit
What about Autodiscover and all the other stuff, is any configuration required there? Also what about Federation, is any federation required for hybrid exchange? or all of this handled by the Hybrid Agent?
very useful thank you
You are welcome Hamza
Great video! Many thanks! Do I still need to keep the Exchange On-Premise or I could start decommissioning? Thanks again.
Hi Rujoi, It used to be the case where orgainisations must have a running Exchange server in the environment for recipient management activities. You couldn`t manage most attributes from Exchange Online. Instead, you used to have to manage those attributes from on-premises. This was a requirement but is no longer the cae with 2022 H1 Cumulative Update, therefore with a view to shut down the last Exchange server(s) and use Windows PowerShell for recipient management. More information here:
techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/ba-p/3285026
Great video! Have one question though:
CompanyA has an Exchange on-prem and O365 hybrid configuration like in your video as they want to migrate all mailboxes to O365. CompanyA acquires CompanyB, that has Exchange on-prem only. What do you suggest?
A) Migrate CompanyB to Company Exchange on-prem and them migrate mailboxes to O365
B) Set up another hybrid between CompanyB on-prem and CompanyAs O365 tenant
Thanks in advance!
Hi Douglas - Thanks for the comments.
For option B - Having more than one Azure AD Connect sync server connected to a single Azure AD tenant is not supported.
Supported topologies for Azure AD Connect are covered in this article which should help you for different scenarios.
docs.microsoft.com/en-us/azure/active-directory/hybrid/plan-connect-topologies%C2%A0
@@CloudInspired Thank you!
Do you have video or webinar to how migrate exchange mailbox user with archive enabled to office 365 with the archive?
Hi! Thanks for your video. I'm planning hybrid with Exchange 2013. Do you think it's a problem using a third party connector for email download. Should I change this to direct download via the Exchange and change the MX Record?
Hi. Author: I don't see where in your steps of configuration Quest Migration Manager was configured to play a role in the migration. The migration you configured just include all of Microsoft's migration tools: AAD Connect, the Exchange Hybrid migration wizard, O365 Admin center, and the O365 Exchange Admin Center for migration. Did I missed something?
Hi Harrison, Quest Migration Manager wasn`t used in this video for the Exchange on-premise migration to Exchange Online. Microsoft tools were only used.
My client don't want to use Exchange Online, but wants to stay on his own Exchange On-prem 2016. Mainly because of Microsoft Teams, as the Teams calendar currently doesn't work with his mailbox.
He do however pay for a 365 license without Exchange.
Is it possible to combine the 2 without migrating?
Great video !!! i have an Query. My organization has been running in a hybrid configuration I need to manage my users from on-premises and also need for directory synchronization or password synchronization to access for the application in on premises and O365
I have planned to move all of my mailboxes alone to Exchange Online.
please let me know, if i can decommission the on premises exchange server alone once i move all the mailbox to O365.
Hi Senthil, thanks for your comment. One of the disadvantages of a Hybrid Migration and using Azure AD Connect requires you to keep an Exchange Server in your environment because Azure AD Connect locks objects in your Active Directory. if you are still using Azure AD Connect to sync your accounts to the cloud then the only supported way to manage recipients is with a local Exchange Server.
Therefore without it you would be unable to change or manage user attributes in Office 365. Third-party management tools such as ADSIEDIT are not supported.
You could turn this into an advantage, as keeping an Exchange on-premises server could be used as a local SMTP service or gives you the option to migrate back from Exchange Online in the future if required.
This is great video for Hybrid mode thanks. I’m after the same detail but for just straight migration from Exchange on prem to M365 and shutting down the on prem stuff immediately after mailbox migration. Do you have a Step-By-Step for that one?
The scenario would be very interesting! I would also like to migrate without hybrid and work only with MS365 Cloud. Is there a video @cloudInspired?
Hello, Thanks both for your comments. After directory synchronization (user is synced from on-premise) most of the attributes cannot be managed from Exchange Online and must be managed from on-premises.
In the article below it explains why you may not want to decommission Exchange servers from on-premises after a hybrid configuration. The other migrations possible are cutover, staged exchange migration etc. I`ll note these for future videos!
How and when to decommission your on-premises Exchange servers in a hybrid deployment
docs.microsoft.com/en-us/exchange/decommission-on-premises-exchange
ty:)
Thanks Romit
Thanks for the guide but the way you explained some things, like virtual directories, if I understood eveything you just said there then I wouldn't need this guide in the first place.
Glad it helped!
can you help me? when i installed the HCW, it has some error regarding the migration endpoint couldn’t be created and no EWS service was listening on the specified endpoint. couldn’t detect the MRS proxy server automatically
Hello, there is a article here to troubleshooting issues where the hybrid migration endpoint cannot be created
learn.microsoft.com/en-gb/archive/blogs/exovoice/troubleshooting-issues-where-the-migration-endpoint-cannot-be-created-in-hybrid-scenarios .Please also check your firewall it must allow the incoming connections on URL containing /ews/mrsproxy.svc, in case it is using URL filtering, or if possible, you can allow all the incoming traffic on port 443. If you are using an IP filtering configuration in the firewall, you should make sure that you have the updated Exhange Online IP list in the firewall configuration, you can find IP ranges list for Exchange Online in that article.
Also using the Test-MigrationServerAvailability command you can test access to the MRSProxy.
Hope that helps.
Do you have a video that is post this that explains how to get the asure AD or 365 Tenant first or whatever else one might need to do to get this this step?
Hi Andrew, you would need to create a new Azure tenant/subscription, can start here azure.microsoft.com/en-gb/free/.
For the hybrid synchronize on-premise Active Directory users to Azure Active Directory (Entra ID) there are are videos below in the Cloud Inspired channels covering this setup.
How to setup & install, from start to finish using Azure AD Connect to synchronize on premise Active Directory users to Azure Active Directory in a hybrid model.
ruclips.net/video/898r84nVqaA/видео.html
Azure AD Connect V2 | Step by Step Installation Upgrade
ruclips.net/video/NPD3Idgo1LA/видео.html
I cant even get the hybrid application proxy to install. Met all prerequisites and it fails to even install
Hi, what error were you getting?
Thanks for the video. Is it possible to do an ultra minimal migration using this method? I have a client using Exchange 2013 with a local AD and a 365 Azure AD tenant that are wholly separate. I think I would prefer to keep them separate - their local security practices aren't good and I do not have time to fight them over it. Their 365 tenant is under the same domain. I would like to simply migrate their mailboxes to their existing 365 user accounts then cut over to Cloud Exchange, leaving the local AD untouched with no sync other than mailbox data.
Take a look at "decide on a migration path in Exchange Online" Microsoft article below which includes a Express migration to see if it meets your requirements. learn.microsoft.com/en-us/exchange/mailbox-migration/decide-on-a-migration-path
@@CloudInspired Thanks, Express sounds like what I want to do, minus synchronising the passwords.
Thanks
Your welcome Eric
I have a question you have not configured certificate error in exchange on premise and proceeded for hybrid migration will this will cause any issue ?
Hi Ashish, for a Exchange hybrid deployment, you need to use a certificate from a trusted third-party CA.
docs.microsoft.com/en-us/exchange/certificate-requirements
Do i have to get an Office 365 E3 license for JUST moving a test mailbox On-Prem to Office365?
Hi Hossein, The Microsoft 365 or Office 365 Exchange license can be allocated after the migration is complete. There is a grace period of 30 days to assign the license.
docs.microsoft.com/en-us/exchange/hybrid-deployment/move-mailboxes
Recently I subscribe m365 business basic, my exist email service provider is rackspace. All user's email configured in I map. Can you pl help me how to migration wil work
Hi Kumar, This video is about migrating from Exchange on-premise to Office 365.
First I would check with Rackspace to see if they have any migration documentation to migrate from their platform.
++
Thanks Yury!
Technically fine, but pathetic use of English... "Premises" are a location or site. "Premise" are the assumptions upon which other inferences are made. If you really can't manage the two extra syllables and can't say, for example, "on site", which is equally valid, you could muster the ugly "on-prem". But the continued use of "on premise"? This is just butchering English and it makes the speaker look uneducated and lazy. Were English a second language, making the same mistake as a lot of other people is one thing, but a native English speaker? Not someone I will trust to tell me the weather let alone technical migration strategies. Can't get past the grade 7 vocabulary, sorry.
Andrew, as you state in your comment "on-site" is equally as vaild as "on-premise".
Throughout this video the term "on-premise" is used, this is a commonly referred and referenced across Microsoft documentation. Which for clarity, refers to IT infrastructure hardware and software applications that are hosted on-site.
Therefore the use of this term is correct and has nothing to do with your disrespectful comments on the speakers use of English.