You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to create a teams schedule with Micorosoft Graph api as a "Online Meeting", but now it was created as the "personal schedule".
Microsoft Graph api code is created in Python. Teams schedule info write in json file and call function "requests.post()". To make it an Online meeting, the following code is settings were made. payload 'allowNewTimeProposals' is 'true' payload 'isOnlineMeeting' is 'true' payload 'onlineMeetingProvider' is 'teamsForBusiness'
But it was created as the "personal schedule". I would like to know why I cannot register my schedule in “Online Meeting”.
Expected behavior
I would like you to investigate this issue, whether it's a bug or anything.
Describe the bug
I would like to create a teams schedule with Micorosoft Graph api as a "Online Meeting", but now it was created as the "personal schedule".
Microsoft Graph api code is created in Python. Teams schedule info write in json file and call function "requests.post()". To make it an Online meeting, the following code is settings were made. payload 'allowNewTimeProposals' is 'true' payload 'isOnlineMeeting' is 'true' payload 'onlineMeetingProvider' is 'teamsForBusiness'
But it was created as the "personal schedule". I would like to know why I cannot register my schedule in “Online Meeting”.
Expected behavior
I would like you to investigate this issue, whether it's a bug or anything.
How to reproduce
1 ) Create new Teams account and groupe.
2 ) According to how to implement automatic schedule registration using Graph API
URI : https://learn.microsoft.com/ja-jp/graph/api/application-post-onlinemeetings
3 ) Register a schedule in your newly created Teams account
SDK Version
No response
Latest version known to work for scenario above?
No response
Known Workarounds
No response
Debug output
Click to expand log
```The text was updated successfully, but these errors were encountered: