Need assistance troubleshooting Teams meeting creation issue

Dustin 0 Reputation points
2026-11-11T18:35:19.11+00:00

We have a user who is unable to create Teams meetings from:

  • Teams Desktop
  • Teams Web
  • Outlook on the Web (OWA)
  • New Outlook

However, the user can successfully create Teams meetings from Classic Outlook.

We captured a HAR log and observed that the createOnlineMeeting request is failing with:

  • HTTP 401 Unauthorized
  • WWW-Authenticate: error="invalid_token"

We have already tested:

  • InPrivate/Incognito browser session
  • Multiple clients (Teams Web, Teams Desktop, OWA, New Outlook)We have a user who is unable to create Teams meetings from:
    • Teams Desktop
    • Teams Web
    • Outlook on the Web (OWA)
    • New Outlook
    However, the user can successfully create Teams meetings from Classic Outlook. We captured a HAR log and observed that the createOnlineMeeting request is failing with:
    • HTTP 401 Unauthorized
    • WWW-Authenticate: error="invalid_token"
    We have already tested:
    • InPrivate/Incognito browser session
    • Multiple clients (Teams Web, Teams Desktop, OWA, New Outlook)
      Since Classic Outlook works, licensing and basic mailbox functionality appear to be intact. Any guidance on the root cause and resolution would be appreciated. Please let us know how to fix this issue.
Microsoft Teams | Microsoft Teams for business | Meetings and calls | Schedule meetings
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. BabybooHN 3,895 Reputation points Independent Advisor
    2026-11-11T18:42:51.4066667+00:00

    Dear @Dustin

    The 401 invalid_token response points to authentication of the meeting-creation request, but it does not establish the underlying cause. Classic Outlook working is useful evidence; however, it does not fully rule out differences in policy or the authentication path used by the other clients. Microsoft documents that a 401 can result from a missing, expired, or invalid access token. Please refer to this document: Resolve Microsoft Graph authorization errors

    Since you have already tested multiple clients and InPrivate sessions, I recommend these administrator checks:

    1. Identify the failing endpoint. Capture the request hostname/path, complete WWW-Authenticate response, UTC timestamp, and request/correlation IDs. The name createOnlineMeeting alone does not identify which service rejected the token. Do not post authorization headers, tokens, cookies, or an unredacted HAR publicly.
    2. Review Microsoft Entra sign-in logs. Under Entra ID > Monitoring & health > Sign-in logs, check both interactive and non-interactive events for the user around the failure time. Review the resource, failure reason, authentication details, and Conditional Access results. A successful initial sign-in does not necessarily establish that every dependent service request succeeded. If a policy failure appears, investigate that specific result rather than disabling Conditional Access broadly.
    3. Check the user’s effective Teams meeting policy. Confirm Private meeting scheduling and Outlook add-in are enabled, and compare the assignment with a working user. These are separate scheduling controls; a policy difference should be investigated, although it would not by itself explain the token rejection. Manage who can start instant meetings and schedule

    If no configuration or sign-in failure explains it, I recommend opening a Microsoft 365 support case for service-side investigation. Provide the sanitized trace, IDs, timestamps, affected user, and the client comparison you already completed. Continue using classic Outlook as the temporary workaround.

    Which hostname/path receives the 401, and do the corresponding Entra sign-in events show Success, Failure, or Interrupted? Please share only sanitized details.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-11-11T18:37:24.6533333+00:00

    Classic Outlook uses the Teams COM add-in, while new Outlook uses native meeting functionality, so first inspect the affected mailbox’s DefaultOnlineMeetingProvider and set it to TeamsForBusiness only if it is missing, Unknown, or incorrect.^1^

    Check and repair the mailbox calendar configuration

    Connect to Exchange Online PowerShell with an account assigned the Organization Management or Recipient Management role, or equivalent cmdlet permissions. Microsoft documents that these roles can configure calendar settings for users.^2^

    Connect-ExchangeOnline

$user = "[Email]"

Get-MailboxCalendarConfiguration -Identity $user |
    Format-List DefaultOnlineMeetingProvider,
                OnlineMeetingsByDefaultEnabled,
                WorkingHoursStartTime,
                WorkingHoursEndTime,
                WorkingHoursTimeZone

    Get-MailboxCalendarConfiguration returns the specified mailbox’s calendar settings.^3^

    If DefaultOnlineMeetingProvider is not TeamsForBusiness, correct it:

    Set-MailboxCalendarConfiguration `
    -Identity $user `
    -DefaultOnlineMeetingProvider TeamsForBusiness

Get-MailboxCalendarConfiguration -Identity $user |
    Format-List DefaultOnlineMeetingProvider

    This exact correction resolved a closely matching single-user case where Teams and new Outlook could not create Teams meetings because the provider value was unknown.^4^

    Also inspect the returned working-hours values. In that case, malformed working hours accompanied the corrupted provider configuration; do not overwrite valid values merely because meeting creation fails.

    After changing the provider, allow the mailbox configuration to propagate, then create a new meeting in OWA, new Outlook, and Teams. The expected result is that createOnlineMeeting succeeds rather than returning 401 invalid_token.

    If the provider is already correct

    Do not repair or reinstall the classic Outlook add-in. Classic Outlook already works, and Microsoft states that new Outlook does not use the Teams COM add-in.^1^ The Incognito and multi-client tests also make another local cache or browser test low value.

    Check the effective scheduling policy:

    1. Open Teams admin center → Users → Manage users.
    2. Select the affected user and review the assigned meeting policy.
    3. Open Meetings → Meeting policies, select that effective policy, and review Meeting scheduling.
    4. Confirm Private meeting scheduling is enabled. If Outlook scheduling is required, also confirm Outlook add-in is enabled.

    These are per-user scheduling controls; Microsoft documents that they are enabled by default but can be changed by policy.^5^

    Compare the affected user with a working user assigned the same licensing and policies. A policy problem is less likely if both have identical effective settings, but Classic Outlook success alone does not conclusively validate the native OWA/new Outlook path.

    Treat a continuing 401 as a backend/service case

    If the provider and effective policy are correct, the available information does not establish whether the rejected token is malformed, stale, or being rejected because of user provisioning. The response header alone is insufficient to identify the exact root cause.

    1. In Microsoft 365 admin center → Health → Service health, check for active Teams or Exchange Online incidents.
    2. Select Help & Support, describe the issue, identify the affected user, and run the offered Teams/Exchange diagnostics. Microsoft documents this admin-center diagnostic workflow and notes that diagnostics provide findings without changing the tenant.^6^
    3. If no diagnostic resolves it, open a support request and attach:
      • The sanitized HAR file.
      • UTC timestamp of a failed request.
      • request-id, client-request-id, correlation ID, and response headers, where present.
      • The affected user’s provider output and effective meeting policy.
      • Confirmation that Classic Outlook succeeds while Teams, OWA, and new Outlook fail.
      • A working comparison user from the same tenant, if available.

    A similar cross-client meeting-creation case was recognized as service-side and required Service Health monitoring and Microsoft 365 support rather than further client repair.^7^

    Use Classic Outlook as the temporary scheduling workaround while Microsoft Support correlates the failed request with service telemetry.

    References

    1. Fix Teams Meeting add-in problems in Classic Outlook - Microsoft Teams ...
    2. Set-MailboxCalendarConfiguration-Description
    3. Get-MailboxCalendarConfiguration-Syntax
    4. Teams Meeting toggle on new Outlook and Teams upon creating event not available - Microsoft Q&A
    5. Manage who can start instant meetings and schedule meetings
    6. Self-help diagnostics for Microsoft Teams administrators
    7. User Unable to create Teams meetings - Microsoft Q&A
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.