microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Going from a joinUrl to a call

Open
#458 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Given a joinUrl e.g. https://teams.microsoft.com/l/meetup-join/19%3ameeting_M2VlNTYwZTUtODdjNC00M2NlLTgzNDctOWIxYzRjZTczYWMy%40thread.v2/0?context=%7b%22Tid%22%3a%2210a9973c-4935-429e-a061-6082fb749d0d%22%2c%22Oid%22%3a%22e71220b2-1e43-44f6-a9e3-b7d06166052a%22%7d how is one supposed to match up the IDs available in the bot (scenarioId, callChainId, resourceId etc).

We have tried via Graph: Calendar Events and Online Meeting endpoints do not seem to have much in common.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the joinUrl with the identifiers exposed by the bot, then review the Microsoft Graph Calendar Events and Online Meeting endpoints mentioned in the issue. Done would be a documented, reliable mapping between the joinUrl and the relevant bot identifiers, or a clear explanation that no such mapping is available.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.