200ms agents for Teams calling.
Bland's self-hosted voice stack responds in 200 milliseconds and keeps call data off third-party AI providers, reached from Teams through your certified SBC.
Bland + Microsoft Teams
Teams calling connects to Bland through your certified SBC, putting 200ms voice agents on your numbers with warm transfers back to Teams users.
What Bland does inside Microsoft Teams.
Through your certified SBC.
Teams calling connects through your certified session border controller, which peers with Teams on one side and a Bland SIP trunk on the other.
Agents on Teams numbers.
Attach the numbers and DIDs your SBC routes to Bland, and each one is answered by the pathway or persona you assign.
Back to a Teams user.
Transfer Call nodes send callers to a DID or SIP URI through the SBC, with warm transfer to brief the Teams user before the caller joins.
Context in SIP headers.
Pass an x-bland-session-id header with a session token to load caller data, and map call variables to headers on transfers out.
Encrypted both ways.
Bland encrypts every connection, with SIP over TLS on port 5061 and SRTP media, from static regional IPs your SBC can trust.
How it deploys.
Confirm your SBC.
Teams calling reaches Bland through your certified SBC, so confirm which SBC will carry the Bland trunk.
Start a trunk.
In the Bland SIP setup wizard, choose Microsoft Teams and enter your SBC endpoint.
Trust Bland on the SBC.
Allow-list Bland's signaling and media IPs for your region, and enable TLS and SRTP toward Bland.
Route numbers and test.
Attach the numbers or DIDs your SBC sends to Bland, press Test connection, and test a transfer back to a Teams user.
Our FDE team scopes the integration, maps Bland to your stack, and stays on through go-live. Enterprise deployments go live in 30 days.
Drop Bland into your editor.
MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly.
curl -X POST https://api.bland.ai/v1/calls \
-H "Authorization: $BLAND_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"phone_number": "+14155552120",
"task": "Qualify refi lead",
"voice": "june"
}'
Frequently asked questions.
Can Microsoft Teams connect to an AI voice agent?
Yes. Teams calling connects through your certified session border controller, which sits between Teams and a Bland SIP trunk, routing chosen numbers to Bland agents and taking transfers back to Teams users.
What role does the SBC play?
Teams calling reaches outside SIP infrastructure through a certified session border controller. The SBC handles the Teams side, and Bland connects to it like any other SIP endpoint, with the same wizard, warm transfers, and SIP traces.
Can the AI agent transfer callers to a Teams user?
Yes. A Transfer Call node can target a DID or SIP URI that your SBC routes to a Teams user. Warm transfer calls that user first, briefs them on the caller, then merges the calls and steps back.
What does the SBC need to support?
SIP over TLS on port 5061 and SRTP media toward Bland, plus trust for Bland's static signaling and media IPs in your region. Transfers and consult calls from Bland connect from the media IPs.
Who actually wires this up?
Our FDE team scopes the integration, works with your voice team on the SBC and trunk, and stays on through go-live. Enterprise deployments go live in 30 days.
Related integrations.
See every integration on the integrations hub.
With our team
Our FDE team scopes the integration with you.
They map Bland to your stack, design the rollout, and stay on through go-live. Enterprise deployments go live in 30 days.
On your own
Or drop Bland into your editor.
The Bland MCP server runs in Claude Code, Cursor, and any MCP-aware editor. Or hit the REST API directly. Free sandbox, no credit card.