After verifying your records on the primary domain in the Admin center, modify your TXT SPF record to include both the M365 as well as keeping the GSuite include syntax and change to a soft fail (~all, instead of -all).If you have more users than that it may be quite the undertaking, but not terrible and I believe that can be scripted with PowerShell fairly easily. These forwarding address would point to This was the trick and what the migration tool was trying to do for me but couldn't. Fully sync'd mailboxes on the M365 sideĪt this point I realized that all I really needed to do was change my primary domain's public DNS MX records over to M365 and manually setup forwarding (with the retain copies in the M365 mailbox option enabled) for each of my clients' users (24 users).Working MX records for said domains in public DNS.Verified domains in GSuite and M365/Azure AD.You can see now that what we have here is a slightly different environment implementation then the above document is referencing - it's not wrong, seamless sign-on should be embraced for everyone, but not fully compatible with the GSuite migration tool's expectations. I would be able to remove all my synchronized on-premes users from Azure, create corresponding Mail Contacts for GSuite import, but than my Azure AD connect sync would likely fail on those user objects because of the AAD Mail Contacts utilizing the same UPN. Had this been a hybrid exchange environment, it would likely have worked, but that was not my case. Let me break to explain that a bit: Because I had all my on-premise user objects already sync'd and then subsequently given Exchange Online licenses which makes them mailboxes, I would not be able to add a proxyAddress. I started a support ticket with Microsoft, who as extremely helpful and, after two days, was able to come back to me and inform me that the documentation is really geared for Mail Contacts, not for Mailboxes, which is what all my users were provisioned as already. I mean, the data was there, but new emails are not going to both places, even with all my public DNS subdomains and entries working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |