Multiple tenants can't create meeting links

Question

Multiple tenants can't create meeting links

Martin Tranberg 0

We're a MSP, and we have multiple tenants with the same issue. They can not create Teams meetings with meeting links. It's across Teams online, desktop app, mobile app and Outlook integration (both web and app). It's affecting all users in these tenants.

When trying to access meeting options is just shows a placeholder image: User's image

When trying to create a meeting they get an error that the link could not be created:

User's image

Using the meet now feature also gives an error:

User's image

We've tried to report the error using the feedback option, and it's just rejected. We've been in contact with Microsoft support, and documented the issue - but they are just sending us in all directions.

We've tried disabling and reenabling the licenses, running all checks and checked all default settings for meeting options, and compared the setup to working tenants using PS - but we're not seeing any direct indications on why they encounter this issue.

Any idea on how we can resolve this issue?

0 comments

2 answers

Your answer

Answer 1

Dear @Martin Tranberg,

Good day! Welcome to Microsoft Q&A forum!

Based on your description, I understand that as an MSP managing multiple tenants, you're encountering an issue where users are unable to create Microsoft Teams meeting links across all platforms (Teams web, desktop, mobile, and Outlook integration). This problem affects all users within those tenants, including failures when accessing meeting options, scheduling meetings, or using the “Meet Now” feature. You’ve already performed several troubleshooting steps, such as license resets, configuration checks, and comparisons with working tenants but haven’t identified the root cause.

Regarding this matter, I’ve also noticed similar reports from other users experiencing the same behavior, which suggests this may not be isolated but could require deeper investigation from Microsoft Support.

Just to confirm, I understand you’ve already been in contact with Microsoft Support. Could you clarify whether a formal support ticket (service request) has been created and is actively being tracked?

If not, I would strongly recommend doing so, as this type of cross-tenant and all-user impact will require backend investigation from Microsoft.

If no ticket has been created yet: Please have your Microsoft 365 Global Admin submit a service request via the Admin Center and include:

Affected tenants
Scope (all users, all platforms)
Screenshots/errors you’ve captured
Troubleshooting steps already performed
For more details, you could refer to this article: Get support for Microsoft 365 for business

A Microsoft Technical Support Engineer will be able to:

Perform a remote session to analyze the issue directly
Validate backend configurations and services tied to Teams meeting creation
Run synchronization or diagnostic tools not available externally
Escalate the case to a specialized engineering team if needed

In the meantime, I did notice that another user has reported experiencing the same issue and shared a temporary workaround that seems to help in certain cases. While this won’t address the root cause, it could be useful to keep operations moving while Microsoft continues investigating.

Kindly let me know when there are updates or if you need further assistance. Any updates you’re able to share would be really helpful. I appreciate your time and look forward to hearing how things are going!

Thank you for your time and patience.

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.

Martin Tranberg 0 Reputation points

2026-06-16T15:32:06.2466667+00:00

Hi,

Thank you for reaching out.

We have filed a official support ticket to MS - but it has been closed with a information that we need to contact Partner Support for further support - but Partner Support does not work with technical issues. We have also reported the issue using the feedback function and those reports has been closed with "No findings".

TrackingID#****[Moderator note: Personally Identifiable Information removed]

The ticket contains web debug logs, recordings of the issue, teams debug logs and screenshots etc. It's quite well documented in the ticket.
Julie Huynh 1,530 Reputation points Independent Advisor

2026-06-17T12:54:29.3233333+00:00

Dear @Martin Tranberg,

Thank you for the detailed update and for sharing the background of your previous support experience.

Based on the information provided (specifically that this is related to a partner tenant), the request needs to be handled through your partner organization.

I understand that you’ve already attempted to reach out to Partner Support. The recommended next step would be to continue working with your partner so they can further investigate on their side.

If they are unable to identify the root cause, they have a dedicated escalation path through Partner Center support channels, which is separate from regular technical support and allows them to raise the issue internally with Microsoft.

Thank you for your patience and understanding!
Martin Tranberg 0 Reputation points

2026-06-18T05:27:59.25+00:00

But we are the MSP (Partner) - It's our client tenants that has the issues.
Anyway - it's simply unacceptable as a partner, it's not possible to raise a ticket to resolve issues with this magnitude. We've been using now almost 3 weeks to get someone at MS to take some kind of action on this issue. Raising a ticket by it self is almost impossible as a partner, and as the tenant it's completely impossible.
Daniel-Vo 6,175 Reputation points Microsoft External Staff Moderator

2026-06-19T11:34:33.7833333+00:00

Hi @Martin Tranberg,

Based on your ticket number, I checked and have some information, please help me check in private message.

Answer 2

Joël Kikkert 0

We have the same issue since an hour or so, the only work around is creating a teams meeting with the add-in in Classic Outlook, that still seems to be working, every other way gives the same error as in your screenshot.

Martin Tranberg 0 Reputation points

2026-06-16T13:54:04.8966667+00:00

We have one tenant that have had the issue for almost 3 weeks now, and one for 12 days. But happy to see that it's not just us at least. I'll check the Classic outlook WA.
Martin Tranberg 0 Reputation points

2026-06-16T14:02:11.2566667+00:00

I can confirm that the Teams integration in outlook Classic is still working here too.
Then we have a WA for now - Thanks! 😊👍

But I really would like MS to acknowledge there's a general issue and fix the underlaying cause.
Joël Kikkert 0 Reputation points

2026-06-16T14:04:32.7666667+00:00

Good to hear you can also use the WA, i've also reported the problem with high impact to Microsoft, wishing for the best!
Martin Tranberg 0 Reputation points

2026-06-16T14:13:04.2466667+00:00

Hope you get though to someone who can do something. We've been documenting and testing for a week now - and just got ditched, and ignored. It's frustrating to say the least. 😒