Blog Post

Microsoft Teams Support
2 MIN READ

New MRCA Diagnostic: Teams Meeting Add-in For Classic Outlook

Carlos Farrica's avatar
Carlos Farrica
Icon for Microsoft rankMicrosoft
Apr 23, 2026

Hi Teams Community,

We're back with another great addition from Christopher Tart​ to Support Diagnostics for Microsoft Teams. We're excited to share that the

Teams Support team has added a new diagnostic to the Microsoft Remote Connectivity Analyzer — the Teams Meeting Add-in For Classic Outlook diagnostic.

If you manage Teams in your organization, you've likely seen this scenario come through your support queue more than once: a user opens classic Outlook to schedule a meeting and the Teams Meeting button is simply nowhere to be found.

This new diagnostic is here to help you quickly pinpoint what's blocking the add-in — whether it's a policy misconfiguration, a licensing gap, or a coexistence mode that's incompatible with the Teams add-in.

 

Some common symptoms this diagnostic helps you troubleshoot:

  • The Teams Meeting button is missing from the Outlook ribbon
  • The Teams add-in doesn't appear in Outlook's list of COM add-ins
  • Users are unable to schedule a Teams meeting directly from Outlook
  • Only the Skype Meeting option appears in Outlook, with no Teams option in sight

 

To access the new diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on Teams Meeting Add-in For Classic Outlook.

You'll need to sign in with a Teams account to run the test. Once authenticated — the diagnostic will then validate that user's configuration end to end.

 

At a high level, the test checks a couple of things:

  • The user is licensed for Microsoft Teams
  • The Teams Outlook add-in policy is enabled (TeamsUpgradePolicy / Teams meeting policies)
  • The user's coexistence and upgrade mode is compatible with the Teams Meeting add-in — users set to Skype for Business Only mode will not see the Teams add-in in Outlook
  • The Teams desktop client is installed and signed in on the user's machine
  • Exchange Online or on-premises connectivity is verified to confirm Outlook can reach Teams for meeting scheduling
  • Admin policies that may be suppressing the add-in are flagged (e.g., Outlook add-in management policies)

For more information, check out these resources:

 

Please give the new diagnostic a try — and let us know if it helped!

Thanks! Microsoft Teams Support

Published Apr 23, 2026
Version 1.0
diagnostics

2 Comments

  • Petri-X's avatar
    Petri-X
    Bronze Contributor
    Apr 23, 2026

    Hi Carlos Farrica​ 

    That looks very nice, but what do you say for people when you are offering like a random web page where people should add their credentials. As you know, many years we have tried to ask users to not put their credentials to the unknown pages. This page, on the other hand is under Microsoft domain, but how do we know how our credentials are used on here?

    This change even a bit more interesting when you are asking to us the GA credentials even:

    Do you see this follows the best practices?

    I haven't tested, but if companies have conditional access policies, will this still work?

    • Carlos Farrica's avatar
      Carlos Farrica
      Icon for Microsoft rankMicrosoft
      Apr 24, 2026

      Hi Petri-X​,
      Thank you for raising this — these are exactly the right questions for any security-conscious IT administrator to ask, and they're worth answering clearly.

      The Microsoft Remote Connectivity Analyzer is a Microsoft-owned and Microsoft-operated tool. It is built, maintained, and documented by Microsoft, and is available at https://testconnectivity.microsoft.com — a Microsoft-owned domain. Official documentation is published on Microsoft Learn: Microsoft Remote Connectivity Analyzer Tool - Connectivity Analyzer | Microsoft Learn 
      As stated in that documentation, MRCA is "a free connectivity test platform for cloud-based services and on-premises technologies" designed specifically to help IT administrators troubleshoot connectivity issues affecting Microsoft 365, Teams, and Exchange. It is not a third-party tool, and it is not affiliated with any external service.

      1. Authentication flow — credentials go to Microsoft's identity platform, not to a custom form When MRCA prompts for credentials, the sign-in flow is handled through login.microsoftonline.com — Microsoft's standard identity platform, the same endpoint used by Outlook, Teams, and every other Microsoft 365 service. You can verify this in your browser's address bar during sign-in. Credentials are not entered into, or handled by, the MRCA tool itself. This is consistent with how Microsoft recommends implementing authentication across its services, using OAuth 2.0 and Modern Authentication. See: Microsoft identity platform and OAuth 2.0

       

      1. Credential storage — credentials are not retained MRCA uses the access token issued by Microsoft's identity platform only for the duration of the diagnostic test session. No credentials are persisted by the tool. The Microsoft Privacy Statement (microsoft.com/en-us/privacy/privacystatement) governs how any associated diagnostic data is handled, and testconnectivity.microsoft.com is a Microsoft-owned and operated property (verifiable via the site's TLS certificate issued to Microsoft Corporation).

       

      1. Global Admin credentials — the sign-in is handled by Microsoft's identity platform We understand why signing in with a Global Administrator account on a web-based tool may feel uncomfortable — and that instinct is the right one to have. The important reassurance here is that when MRCA prompts for credentials, the sign-in occurs through login.microsoftonline.com, which is the same Microsoft identity platform endpoint your admins use to sign into the Microsoft 365 admin center, Microsoft Entra, and every other Microsoft service. Your GA credentials are never entered into or handled by the MRCA tool itself. All of the same protections that apply to any elevated sign-in — MFA, Conditional Access, sign-in risk evaluation — apply here as well. If your tenant requires MFA or a compliant device for privileged accounts, those requirements will be enforced. Reference: Microsoft identity platform and OAuth 2.0 authorization code flow