Creation of events with IsOnlineMeeting=true (Teams Online Meetings) does not work when "[ ] Outlook Add-in" is off
Hello
For corporate environment creation of Teams Online Meeting via POST Event call with IsOnlineMeeting=true flag is broken when in Teams administrative area
https://admin.teams.microsoft.com/policies/meetings/edit/R2xvYmFs
in section Meeting Scheduling setting [ ]Outlook add-in is disabled.
After that if to create OnlineMeetin=true Event with Graph API, response will always have
a. Event.OnlineMeeting == null
b. Event.OnlineMeetingProvider == OnlineMeetingProviderType.Unknown
Steps:
Create user1, assign Microsoft 365 license
Login via user1 in Teams at least once (workaround of sporadic issue of a new user being unable to create via API events in calendar, this needs to be addressed but this issue is not about that)
Create by user1 at least one online meeting (workaround of another sporadic issue of a new user being unable to create via API events in calendar, this needs to be addressed but this issue is not about that)
Go to the Teams administrative area
https://admin.teams.microsoft.com/policies/meetings/edit/R2xvYmFs
in section Meeting Scheduling and disable setting [ ]Outlook add-in is disabled.
Go to Microsoft Graph API Explorer and POST event with IsOnlineMeeting
Actual result:
Event is returned from API call with 2 properties having invalid values
a. Event.OnlineMeeting == null
b. Event.OnlineMeetingProvider == OnlineMeetingProviderType.Unknown
Expected result:
Event is created, OnlineMeetingProvider is TeamsForBusiness, OnlineMeeting is filled with data.
Basically, our support spend month to investigate that case.
Please fix IsOnlineMeeting=true events creation in a way
a) No need to login in Teams at least once
Its really ugly to ask customers to do it.
b) No need to create by user1 at least one online meeting
Its really ugly to ask customers to do it.
c) It does not depend Teams administrative area*Meeting Scheduling* setting [ ]Outlook add-in
This setting is about add-in. Why does it taken into account for graph API calls. It should not.
Thanks