API regression: BadRequest error on /beta/copilot aiInsights endpoint after 2025/09/22
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reproducing the request against the beta /copilot/users/:user_id/onlineMeetings/:meeting_id/aiInsights endpoint with the shown Python SDK code and filter. Compare behavior before and after 2025/09/22 if possible, then determine whether the API contract changed and whether migration documentation is required.
Written by the indexing model from the issue text.
Description
Problem
The following API endpoint stopped working as expected after 2025/09/22:
https://graph.microsoft.com/beta/copilot/users/:user_id/onlineMeetings/:meeting_id/aiInsights
After 2025/09/22, requests now return:
{
"error": {
"code": "BadRequest",
"message": "Value cannot be null. (Parameter 's')",
"innerError": {
"date": "2025-09-25T02:21:05",
"request-id": "8e2a3b90-24ac-4a05-ad77-50d3ade65aba",
"client-request-id": "8e2a3b90-24ac-4a05-ad77-50d3ade65aba"
}
}
}
# My code snippet:
graph_client = get_graph_client_beta(auth_code)
me = await graph_client.me().get()
user_id = me.id
graph_client.request_adapter.base_url = "https://graph.microsoft.com/beta/copilot"
query_params = AiInsightsRequestBuilder.AiInsightsRequestBuilderGetQueryParameters(
filter=f"contentCorrelationId eq '{correlation_id}'"
)
request_configuration = RequestConfiguration(query_parameters=query_params)
result = await graph_client.users.by_user_id(user_id).online_meetings. \
by_online_meeting_id(meeting_id) \
.ai_insights. \
get(request_configuration=request_configuration)
Impact
- This appears to be an API issue rather than an SDK bug, but it directly affects SDK behavior.
- The same code worked until 2025/09/22, so this looks like a regression in the API backend.
Request
- If this is an expected change, please update the documentation and communicate any required migration steps for SDK usage.
- Dominant language
- Python
- Stars
- 44
- Forks
- 16
- Avg merge
- 20h 39m
- 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-beta-sdk-python
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
type:bug type:investigation
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoftgraph/msgraph-beta-sdk-python#1033 · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 42/100
microsoftgraph/msgraph-beta-sdk-python#1006 · 1 comment ·
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
microsoftgraph/msgraph-beta-sdk-python#987 · 2 comments ·
All issues in microsoftgraph/msgraph-beta-sdk-python
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AiursoftWeb/AnduinOS-2#19 ·