when created Teams schedule with Graph api as a "Online meeting", but it was created "personal schedule"
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Start with the Microsoft Graph application-post-onlinemeetings documentation linked in the reproduction steps, then inspect the Python requests.post() payload and its allowNewTimeProposals, isOnlineMeeting, and onlineMeetingProvider values. Reproduce the request with the stated Teams account setup and determine whether the response creates an online meeting or a personal schedule. Done means the cause is confirmed and the issue has a documented correction or is shown to be expected behavior.
Written by the indexing model from the issue text.
Description
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
```</details>
### Configuration
- OS : Windows10 , 11
- environment : Browser and client app
### Other information
_No response_
- Dominant language
- Python
- Stars
- 630
- Forks
- 96
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoftgraph/msgraph-sdk-python
-
status:waiting-for-triage type:bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
microsoftgraph/msgraph-sdk-python#1570 ·
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoftgraph/msgraph-sdk-python#1563 ·
-
Needs: Attention :wave: type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoftgraph/msgraph-sdk-python#1287 · 2 comments · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
microsoftgraph/msgraph-sdk-python#1578 ·
-
status:waiting-for-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-python#1557 ·
All issues in microsoftgraph/msgraph-sdk-python
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·