@YesimNuman
I want to take the time to document all this nicely, but I never find the time. So here is a brief, I cannot be sure if it is the same issue as yours, nor have I time to carefully verify all this, but I thought I’d share it anyway in case it is helpful. Please let me know!
If my assumptions are correct, I believe that this issue arises because of a bug in the "Teams Meeting add-in for Microsoft Outlook".
How it happens
It occurs when you schedule a meeting using the Outlook desktop calendar, and in Outlook desktop you have more than one Microsoft 365 Organization account (Exchange Online “EO” account). You also have the Teams desktop app installed, and signed into your primary account. You have a default EO account, but you create a Teams calendar meeting in a secondary account (or any other than your default).
Symptoms
When you create a meeting in this way, you create what I “technically” call a “dud meeting”. With a dud meeting:
- If you try to join it at any time you will get the message “When the meeting starts, we’ll let people know you’re waiting.” – even though you may be the meeting host.
- If you try to change the dud meeting “meeting options” you will get the message “Only meeting organisers can make changes” – even though you may be the meeting organiser. It will even state there the correct username.
Workaround
The workaround is, to avoid the use of the “Teams Meeting add-in for Microsoft Outlook”. A simple way to do this is to only create Teams meetings using the calendar within Teams itself (when logged in to the relevant account), using Teams web app, or perhaps the desktop app.
Why it happens (maybe)
I believe this issue occurs due to account-specific data that is transacted and compiled between the Teams desktop app and the “Teams Meeting add-in for Microsoft Outlook” at the point it attempts to schedule the meeting. Somewhere there is an assumption that connects the identity information to your default Outlook org / EO account. Even if you have a secondary EO calendar set up in Outlook desktop and you create the Teams meeting in that Outlook desktop calendar, the Teams meeting that is created in that secondary EO calendar has some kind of identity meta data that is from your primary account, not the secondary account. Thus “primary account” is the “organiser” (regardless of what it says). That account does not belong in this secondary organisation, so it is invalid. You can’t join that meeting, or administrate it.
