Evaluate the Teams adapter

The adapter can send a question to a teammate in Teams and capture their reply. Guided setup is not released yet, so use this page only for advanced self-hosted evaluation, not a new production rollout.

What you get

Questions delivered as a Teams message

Replies captured in the chat

Delivery to the exact person, by their Microsoft account

Before you start

You need permission to register an app in Azure (Entra ID) and to approve a Teams app for your tenant.

Orako’s Teams endpoint must be reachable from Microsoft. It already is on app.orako.io.

Setup steps

5 steps

Register the bot in Azure

In the Azure portal → Microsoft Entra ID → App registrations → New registration, create an app named “Orako.” Copy its Application (client) ID and your Directory (tenant) ID.

Create a client secret

Under Certificates & secrets → New client secret, create one and copy the value immediately.

Azure hides the secret value after you leave the page. Copy it now, you can’t see it again.

Create the Bot and point it at Orako

Create an Azure Bot resource tied to the app registration. Set its messaging endpoint to the URL Orako shows on the Integrations page:

https://app.orako.io/teams/activities/<your-project>

This is where Teams delivers activities and replies; Orako verifies every message is genuinely from Microsoft before acting on it.

Approve the app for your tenant

Add the Teams channel to the bot, then upload/sideload the Orako Teams app so members can receive messages. A tenant admin approves it. This admin consent is what lets Orako start a chat with a person proactively.

Paste the four values into Orako

On the Integrations page, enter:

Tenant IDClient IDClient SecretBot App ID

Save. Orako shows Connected.

Advanced / self-hosted only: a Service URL field lets you override Microsoft’s default endpoint. Leave it blank unless you know you need it.

Match each teammate to their Microsoft account

A teammate opens Settings → Notifications, picks Teams, and enters their Microsoft account ID (Azure AD object id). An org admin can fill this on the teammate’s Members card instead.

Orako also learns a teammate’s Teams identity the first time they interact with the bot, so a manual entry can be corrected automatically later.

Microsoft account ID

a1b2c3d4-…

Your Microsoft account ID (a GUID like a1b2c3d4-…). Your Azure admin can find it under Users, or link it for you from the Members page.

Good to know

Every message is verified

Orako checks a Microsoft-signed token on each incoming reply, so nothing but genuine Teams traffic is ever accepted.

We message people, not channels

Orako starts a private chat with the teammate; it doesn’t post into your team channels.

Presence doesn't matter

Every reply stays attributed in the same Orako conversation.

Next provider

Connect Discord