microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Microsoft teams recording issues with new bot creation in Australia

Open
#541 1 comment 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

we have 12 Teams recording bot that all work fine (US/UK/Europe/AsiaPAC)

we have built a new service in Australia East comprising of Bot and cloud service and storage with our teams recording code

this is same setup that work in every other region but for some reason when you assign the Australia recording policy to a users

you get below error when trying to make a call

image

the only difference i can see is that you have to user azure bots now and not bot channel registrations as Microsoft got rid of these.

we have test this with a customer multitenant and within our own environment and get same error

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 reproducing the call failure after assigning the Australia recording policy, then compare the Australia East Azure Bot, cloud service, and storage setup with the working US, UK, Europe, and AsiaPAC services. Use the attached error image and verify whether the Australia configuration differs; done means identifying the configuration or regional cause and confirming a successful call or a documented limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.