Share via

Teams link not being generated

Rita Rita 115 Reputation points
2025-09-01T16:35:53.3966667+00:00

Hello

Please i need your help on this issue.

Teams link not being generated.

We programmatically generate calendar invitations of online teams' meetings for the last few years, running without any problems.

Its suddenly stopped working the last few days and the API is not returning the Teams meeting link to join.

 I read this issue and its almost identical:

Issue ID: TM1142501User's image

I was wondering if I can also have the workaround that was provided to users so I can get our system working again.

Microsoft Teams | Microsoft Teams for business | Calendar | Other

3 answers

Sort by: Most helpful
  1. Ryan-N 12,995 Reputation points Microsoft External Staff Moderator
    2025-09-18T19:12:26.87+00:00

    Hi @Rita Rita,

    Thank you for your response. I truly appreciate your cooperation.

    Based on the information you provided, I’d like to share the following:

    The appearance of the Teams Meeting button after adding the First Name and Last Name to the info@ account profile suggests that there may have been a recent change on Microsoft’s side, causing the system to rely on these fields to activate the Teams meeting feature.

    There is no official Microsoft documentation that explicitly states that the “First Name” and “Last Name” fields must be filled in for the Teams Meeting button to appear. These fields are primarily used for identity display purposes, not for authentication or authorization. Therefore, in theory, an account without a first/last name (but with a valid Teams license and access rights) should still be able to schedule Teams meetings.

    The issue may stem from a system-level issue.

    In this case, I recommend that you raise a support ticket with Microsoft’s technical team to request a deeper investigation into the system. As a moderator, I lack the tools to perform such in-depth checks. Once you raise the ticket, a live agent will proactively reach out to you and conduct a remote session to help identify the root cause: https://admin.microsoft.com/#/homepage.

    Since this is a relatively rare case, I also suggest visiting the following link: https://feedbackportal.microsoft.com/. After accessing the portal, please create a post describing this issue. This action will help Microsoft become aware of the problem and may prompt the product development team to investigate and potentially fix the issue.

    In the meantime, I recommend keeping temporary values in the First Name/Last Name fields to ensure the Teams Meeting feature continues to function properly.

     If I receive any information regarding this issue, I will update it immediately in this post. If you have any questions or concerns, feel free to share them with me. I’m here to support you.


    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. 

    User's image

    Was this answer helpful?

    0 comments No comments

  2. Ryan-N 12,995 Reputation points Microsoft External Staff Moderator
    2025-09-04T19:16:06.72+00:00

    Hi @Rita Rita,

    Thank you for your response. Based on the information you provided, I’d like to share the following guidance and details to help resolve the issue effectively.

    1. Check Teams License Status

    Although the account info@ has been assigned a Business Standard license, the Microsoft Teams service might not be enabled in the license configuration.

    Action:

    • Go to Microsoft 365 Admin Center
    • Navigate to Users > info@... > Licenses and Apps
    • Check whether Microsoft Teams is selected (enabled) under the Business Standard license
    • If not enabled, activate it and save. Then, sign in to the Teams app using the info@ account to complete activation.
    1. Check Mailbox Type

    The info@ account may have originally been set up as a shared mailbox. By default, shared mailboxes do not have Teams licenses and cannot create Teams meeting links.

    Action:

    • Ensure the info@ mailbox has been converted to a user mailbox and assigned Business Standard + Exchange Online Plan 2
    • If the conversion was recent, it may take 24–48 hours for the system to fully recognize and activate Teams features
    1. Check Teams Meeting Policy

    Microsoft Teams may apply restrictive policies to certain accounts, especially general-purpose ones like info@. If the assigned policy disables the Outlook add-in, the Teams Meeting button will not appear in Outlook.

    Action:

    • Go to Teams Admin Center
    • Navigate to Users > info@... > Policies
    • Check the meeting policy assigned to this account
    • Ensure that Allow scheduling from Outlook (Outlook add-in) is enabled
    • If not, switch to the Global policy or create a custom policy that allows this feature
    1. Check Outlook Application

    Action:

    • Open Outlook using the info@ account
    • Go to File > Options > Add-ins
    • Check if Microsoft Teams Meeting Add-in for Office is listed under Disabled Add-ins
    • If so, re-enable it via Manage COM Add-ins, then restart Outlook
    1. Sign in to Microsoft Teams App

    To ensure Outlook recognizes info@ as a valid Teams account, sign in to the Microsoft Teams app (desktop or web) using info@ at least once.

    1. Check via Outlook Web App (OWA)

    OWA reflects license changes faster than the desktop Outlook. After completing the steps above, sign in to OWA using info@ and try creating a new meeting to see if the Teams Meeting button appears.

    1. Temporary Workaround (if needed)

    If full activation for info@ is not yet possible, you can use a delegation method:

    • Grant Full Access and Send As permissions to a personal account (e.g., tony@...) for the info@ mailbox
    • Add info@ as an additional account in Outlook (not just auto-mapped)
    • Create meetings from the info@ calendar — the Teams Meeting button will appear if your account has a Teams license

    Summary

    The main reasons why the Teams Meeting button is not showing for info@ are:

    • Teams service is not enabled in the license
    • Teams meeting policy blocks Outlook integration
    • The mailbox was recently converted from shared and needs time to activate

    Following all the steps above will help resolve the issue and enable Teams meeting functionality for the info@ account in Outlook.

     If you have any updates regarding the issue, feel free to share them with me. In case you have any other questions or concerns, please let me know and I’ll support you.


    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. 

    User's image

    Was this answer helpful?


  3. Ryan-N 12,995 Reputation points Microsoft External Staff Moderator
    2025-09-01T17:12:24.45+00:00

    Hi @Rita Rita,

    Thank you for reaching out. I understand the severity of the issue you're experiencing with the inability to generate Microsoft Teams meeting links via API, and I appreciate you referencing incident code TM1142501 — your situation fully matches the service issue confirmed by Microsoft.

    Microsoft has provided a temporary workaround while they work on deploying a permanent fix:

     Use the Microsoft Teams mobile app (iOS/Android) to schedule meetings. The mobile app uses a different scheduling logic that is not affected by the license verification bug. You can:

    • Create a new meeting directly from the mobile app.
    • Or open and edit a draft meeting (created from desktop/web) using the mobile app — simply saving it from the mobile device will automatically add the Teams join link.

     This workaround has been confirmed to work reliably and does not require any changes to your API configuration or user account settings.

     

    Current Status As of September 1, 2025, Microsoft is actively deploying a fix to restore normal functionality. The issue is still ongoing, but there are no reports of data loss, and the problem is limited to the meeting scheduling process.

    Once the fix is fully deployed, meetings created via API or desktop/web apps will automatically include the join link as expected.

     

    Additional Information You can click the link "Are you experiencing this issue?" This action helps Microsoft identify users affected by the same issue. When the latest update is available, they will prioritize delivering it to you.

     User's image

    If you have any updates regarding the issue, feel free to share them with me. In case you have any other questions or concerns, please let me know and I’ll support you.


    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. 

    User's image

    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.