The service account just needs to exist. The permissions are based on the Modern Auth via the App Registration. It allows an account to impersonate for the purposes of attaching, but in the interest of security the service account cannot actually see the data. Ping me at mark@thecloudgeezer.com if you want to head deeper into that little rabbit hole.
That is a tough question because both have merits and obviously it depends on the migration you are performing. However, I do lean towards MigWiz because the Ms tools are no longer free. Meaning that when the costs are the same, the toolsets can be compared on technical ability rather than cost. Remember that the Ms tools do destroy the source mailbox, which is the major difference. This can be both good or bad depending on your migration and this is why I made my initial comment. Please feel free to email at mark@thecloudgeezer.com if you want a deep dive conversation into what might be best for you. Have a good day. Mark.
Yes, I agree, the initial setup is semi-automated inside the Migration Manager console of M365. It also does some other things around the setup of the forwarding domains etc. on the Google side. Basically a few different migration concepts in play there in how they perform the migration itself. MigrationWiz looks to just drop the data content from one live account to another and then you perform the cutover yourself. This approach can often be a simpler one but it does depend on your actual situation and needs. Drop me a note to mark@thecloudgeezer.com if you need any thoughts or guidance in what you are doing.
You are too good man.❤
And you are too kind. :-) I am just helping out my fellow IT nerds out there.
beautifully done video. question, what permissions did you assign your service account on the destination tenant?
The service account just needs to exist. The permissions are based on the Modern Auth via the App Registration. It allows an account to impersonate for the purposes of attaching, but in the interest of security the service account cannot actually see the data. Ping me at mark@thecloudgeezer.com if you want to head deeper into that little rabbit hole.
Which method would you recommend, Migration Wiz or Built in Microsoft ?
That is a tough question because both have merits and obviously it depends on the migration you are performing. However, I do lean towards MigWiz because the Ms tools are no longer free. Meaning that when the costs are the same, the toolsets can be compared on technical ability rather than cost. Remember that the Ms tools do destroy the source mailbox, which is the major difference. This can be both good or bad depending on your migration and this is why I made my initial comment. Please feel free to email at mark@thecloudgeezer.com if you want a deep dive conversation into what might be best for you. Have a good day. Mark.
Also MigrationWiz can migrate Google Groups while MS Tools cannot. It's right?@@thecloudgeezer
MigrationWiz is more complicated than the automation process from MS365 and Google API
Yes, I agree, the initial setup is semi-automated inside the Migration Manager console of M365. It also does some other things around the setup of the forwarding domains etc. on the Google side. Basically a few different migration concepts in play there in how they perform the migration itself. MigrationWiz looks to just drop the data content from one live account to another and then you perform the cutover yourself. This approach can often be a simpler one but it does depend on your actual situation and needs. Drop me a note to mark@thecloudgeezer.com if you need any thoughts or guidance in what you are doing.