Hi Wayne Herbert,
Thank you for posting your question in the Microsoft Q&A forum.
First, I would clarify with you whether the goal is to use the organization’s custom domain for user accounts to sign in to Office apps (especially Microsoft Teams) while continuing to use Google Workspace as the email service provider.
If that is the case, I would like to add the following:
You can still follow the steps outlined in Emily’s answer; however, in this scenario, you only need to verify domain ownership by pointing a TXT record to Microsoft to pass the Domain Verification Process. After verification, you can change the user accounts so they use the verified domain for login on Office apps.
Please note that anything related to email will not function in Microsoft 365 if the MX record remains pointing to Google.
For example:
- Teams functionality: Chat, calls, and meetings will work because identity is based on Azure AD/Microsoft 365 accounts.
- Calendar and meeting experience in Teams: Scheduling meetings directly in Teams is tied to having an Exchange mailbox. If you continue using Gmail (no Exchange Online), some integrated calendar features in Teams/Outlook will be limited.
However, there is an option for organizations that want to keep Google as the email provider but use Teams for meetings:
- Microsoft Teams meeting add-on for Google Workspace: This allows users to schedule and join Teams meetings directly from Google Calendar/Gmail. Microsoft provides guidance for this scenario, including domain verification and calendar sync steps. You can review the article here: Set up calendar syncing with Google Workspace
I hope this additional information is helpful and gives you more clarity to decide on the next steps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.