microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Recommended way to secure Application Hosted Media bot

Open
#342 6 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

I have an application hosted media bot that only places calls into Teams - it doesn't listen for incoming Teams calls.

Given the application's HTTPS endpoint and media socket are open to the internet, what is the recommended way to ensure they call only be accessed by Teams? I have tried using "AzureBotService" service tag on the inbound firewall rules, but didn't receive any Teams traffic. Is there another service tag I should be using?

Also, how does this advice change for bots that are not hosted in Azure?

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 with issue #342 and its questions about the AzureBotService inbound firewall rule, Teams access, and non-Azure hosting. Done means documenting an authoritative access-control recommendation for both Azure-hosted and non-Azure application-hosted media bots.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
networking, security
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.