Share via

MS Team plugin for Google calendar no longer allowing us to login using a 'onmicrosoft' account

Greg Nutley 20 Reputation points
2026-03-11T10:01:21.1266667+00:00

Hi,

We are a Small to Medium Business (SMB) that primarily operates within a Google Workspace environment. However, our users also have Microsoft 365 Business licenses, with licensed accounts associated with an 'x.onmicrosoft.com' domain.

For several years, we successfully used the Microsoft Teams for Google Calendar plugin to add Teams meeting links to our Google Calendar events, authentically linking these meetings to our licensed 'onmicrosoft.com' accounts. Recently, the plugin's authentication appears to have changed, now only allowing us to authenticate using our default Google Workspace account/domain.

This is problematic, as most of our users' Teams licenses are tied to their 'onmicrosoft.com' credentials, not their Google Workspace email addresses.

We are aware of the workaround—creating the meeting in the Teams app separately and then manually copying the invite details into Google Calendar—but this is significantly less efficient than the previous direct integration.

Has the functionality to select which credentials are used to authenticate the Teams plugin been removed, or is there an alternative solution available to address this licensing/authentication conflict?"

Microsoft Teams | Microsoft Teams for business | Calendar | Other
Answer accepted by question author
  1. Q&A Assist
    2026-03-11T10:01:49.94+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The Teams Meeting add-on for Google Calendar now authenticates against a single Microsoft work or school account and does not support choosing different Microsoft identities per Google account or per event. The add-on also does not sync with other Microsoft calendars and is designed to work with the Microsoft account that is connected to the business email/domain configuration.

    From the current behavior and documentation:

    1. The Teams Meeting add-on is tied to the signed-in Microsoft work or school account
      • In Google Calendar, the add-on flow is:
        1. Open the Teams add-on.
        2. Select Sign in and use the Microsoft work or school account used to access Teams.
        3. Select Authorize Access.
      • The add-on then uses that account for creating Teams meetings from Google Calendar.
      • There is no documented option to switch between multiple Microsoft identities (for example, an onmicrosoft.com account vs. another account) within the add-on UI.
    2. The add-on does not sync with other Microsoft calendars
      • Meetings scheduled with the add-on “will only appear on your Google calendar. They don't sync with other Microsoft calendars.”
      • This reinforces that the add-on is a lightweight way to generate Teams meeting links from Google Calendar, not a full multi-identity/calendar integration.
    3. For organizations using Google Workspace as primary email
      • If Google Workspace is the primary email/calendaring system, the supported approach is to connect the business domain and enable calendar syncing between Google Workspace and Teams, using the admin setup wizards:
        • Connect the business domain and email to Teams via the Integrating your business email with Microsoft Teams process.
        • If using Google Workspace with a custom domain, enable bidirectional calendar syncing via Set up calendar syncing between Google Workspace and Microsoft Teams for your business.
      • This model expects users to sign into Teams with the same business email identity that is used in Google Workspace, not a separate x.onmicrosoft.com identity.
    4. Personal Gmail/Google Calendar vs. Google Workspace
      • Personal Gmail/Google Calendar cannot be synced with Teams; only Google Workspace with a custom domain is supported for bidirectional sync.
      • For personal use, the add-on can still be used to create Teams meetings directly from Google Calendar, but again with a single Microsoft account sign-in.

    Given the above, there is no documented way in the current add-on to:

    • Select or switch between multiple Microsoft identities for the add-on per Google user, or
    • Force the add-on to use x.onmicrosoft.com identities when the organization is configured around a different primary business email/domain.

    Supported alternatives for the described scenario are:

    1. Align identities and domains
      • Connect the existing business domain (the one used in Google Workspace) to Microsoft 365/Teams using the Integrating your business email with Microsoft Teams guidance.
      • Assign Teams licenses to those business email identities instead of (or in addition to) separate x.onmicrosoft.com accounts.
      • Then sign into the Teams add-on in Google Calendar with the same business email identity that users use in Google Workspace.
    2. Use full calendar sync instead of relying solely on the add-on
      • For organizations whose primary email is Google Workspace, use the Set up calendar syncing between Google Workspace and Microsoft Teams for your business process.
      • This enables bidirectional sync between Google Calendar and Teams for users on the same business domain and avoids the need to manage separate onmicrosoft.com identities for scheduling.
    3. Continue the manual workaround where necessary
      • Where identities cannot be aligned or licenses cannot be moved to the business domain accounts, the only documented option remains to:
        • Create the meeting in Teams/Outlook using the licensed onmicrosoft.com account, and
        • Copy the meeting details into Google Calendar.

    In summary, the current documented model expects a single Microsoft work/school identity per user that matches the business email domain, and there is no supported mechanism in the add-on to choose or override which Microsoft credentials are used per event. The recommended path is to connect the business domain to Teams and/or enable Google Workspace–Teams calendar sync so that the same identity is used across both systems.

    References:

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.