microsoftgraph / microsoftgraph/msgraph-sdk-python

when created Teams schedule with Graph api as a "Online meeting", but it was created "personal schedule"

未关闭
#906 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

question type:bug
主要语言
Python
星标
630
派生
96
平均合并
15 小时 20 分钟
30 天内合并 PR
3

描述

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_

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

先查看复现步骤中链接的 Microsoft Graph application-post-onlinemeetings 文档,然后检查 Python requests.post() 的 payload 以及 allowNewTimeProposals、isOnlineMeeting 和 onlineMeetingProvider 的值。使用所述的 Teams 账户设置复现该请求,并确定响应创建的是在线会议还是个人日程。完成的标准是确认原因,并且该问题已有记录在案的修正,或已证明这是预期行为。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
api
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
30/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。