Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hellofriday.ai/llms.txt

Use this file to discover all available pages before exploring further.

Connect a Microsoft Teams bot to any Friday workspace so users can chat with it over DM or @mentions. Messages flow into the same conversation pipeline the web chat uses, and replies go back to Teams. You create the Azure Bot at portal.azure.com, build a Teams app package, and connect via Studio.

​
Prerequisites

  • An Azure account with an active subscription. The F0 pricing tier for Azure Bot is free and sufficient for development.
  • Admin rights in a Microsoft 365 tenant that lets you sideload custom Teams apps. A personal Microsoft account (“Teams free”) does not work — you need a work/school tenant or a Microsoft 365 Developer Program tenant.
  • Friday running with the bundled tunnel active (Azure Bot requires a public HTTPS URL — http:// is rejected).

​
Setup

1

Create the Azure Bot

  1. Open portal.azure.com and click Create a resource → search for Azure Bot.
  2. Fill in:
    • Bot handle — a unique identifier, e.g. friday-studio-bot
    • Pricing tier — F0 (free)
    • Type of App — Single Tenant if you only plan to install into one M365 tenant; Multi Tenant for cross-tenant distribution. This choice is immutable — see SingleTenant vs MultiTenant.
    • Creation type — Create new Microsoft App ID
  3. Click Review + create → Create. Provisioning takes 30–60s.
The Type of App dropdown is permanently greyed out after the bot exists. If you pick the wrong one, you have to delete and recreate the Azure Bot resource.
2

Collect three credentials

From the Bot resource you just created:
ValueWhere
Microsoft App IDBot resource → Configuration → Microsoft App ID
Client secret valueManage Password → Certificates & secrets → New client secret → copy Value
Directory (tenant) IDApp Registration → Overview → Directory (tenant) ID
The tenant ID is only required for SingleTenant bots, but it’s harmless to set either way.
Azure only shows the client secret value once. Copy it immediately — if you miss it, delete the secret and create a new one.
3

Connect Teams in Studio

  1. In Studio, select your workspace from the sidebar and click Info.
  2. Find the Communicators card and click Connect next to Microsoft Teams.
  3. Paste the App ID, Client Secret, Tenant ID, and select the App Type (SingleTenant or MultiTenant) into the form, then submit.
Studio stores the credentials securely. The status flips to Connected when it’s done.
4

Point Azure at your messaging endpoint

  1. Open Studio → Settings → Webhook tunnel and copy the URL — something like https://<random>.trycloudflare.com.
  2. In the Azure portal, open your Bot resource → Configuration → Messaging endpoint and set it to <tunnel>/platform/teams, e.g. https://<random>.trycloudflare.com/platform/teams.
  3. Click Apply.
  4. Under Channels, click Microsoft Teams, accept the ToS, and enable the channel.
5

Build and sideload a Teams app package

Azure Bot is the API endpoint; the Teams app package is what puts your bot in front of real users. It’s a zip containing manifest.json plus two icons.
  1. Create a directory with this manifest.json (replace <APP_ID> with your Microsoft App ID):
    manifest.json
    {
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",
  "manifestVersion": "1.16",
  "version": "1.0.0",
  "id": "<APP_ID>",
  "packageName": "com.yourco.friday",
  "developer": {
    "name": "Your Team",
    "websiteUrl": "https://example.com",
    "privacyUrl": "https://example.com/privacy",
    "termsOfUseUrl": "https://example.com/terms"
  },
  "icons": { "color": "color.png", "outline": "outline.png" },
  "name": { "short": "Friday", "full": "Friday Teams" },
  "description": {
    "short": "Friday agent orchestration",
    "full": "Chat with your Friday workspace from Teams."
  },
  "accentColor": "#4F46E5",
  "bots": [
    { "botId": "<APP_ID>", "scopes": ["personal"], "isNotificationOnly": false, "supportsFiles": false }
  ],
  "permissions": ["identity", "messageTeamMembers"],
  "validDomains": []
}
  2. Drop a 192×192 PNG named color.png and a 32×32 PNG named outline.png beside the manifest.
  3. Zip those three files (manifest must be at the root of the archive, not inside a subfolder).
  4. In Teams, go to Apps → Manage your apps → Upload an app → Upload a custom app and pick the zip.
  5. Click Add when Teams prompts. The bot appears in your apps list.
6

Talk to your bot

  1. Open the bot’s app page in Teams and click Chat to start a DM.
  2. Send a message. The first message creates a chat in the workspace — it should appear in Studio with a TEAMS badge, and replies flow back to Teams automatically.
  3. To @mention the bot in a channel, add the app to the team first, then @<bot-name> hello.

​
SingleTenant vs MultiTenant

TypeTenant ID requiredWhen to pick
SingleTenantYesYou only install the bot into your own M365 tenant (most dev setups).
MultiTenantNoThe same bot will be installed across multiple tenants (SaaS).
The App Type you select in Studio’s connect form must match what the Azure Bot was created as. Mismatched values produce an Authorization has been denied for this request on outbound replies — inbound routing still looks fine, which makes it easy to miss.

​
Troubleshooting

app_type doesn’t match the Bot Service’s registered Type of App. Check Azure Bot → Configuration → Type of App and reconnect via Studio with the matching value.
Most likely the Teams channel isn’t enabled in Azure. Go to Bot resource → Channels → click Microsoft Teams → accept ToS and enable. Second most likely: the messaging endpoint in Azure points at a stale tunnel URL.
The incoming JWT is being rejected. Usual causes: the App ID you pasted doesn’t match the Bot’s Microsoft App ID, or a missing tenant ID on a SingleTenant bot.
The bundled Cloudflare quick-tunnel gets a new random URL every restart. Each restart requires updating the Messaging endpoint in the Azure portal. For stable development, use a named Cloudflare tunnel, ngrok paid, or a real reverse proxy on your own domain.

​
Production notes

  • Rotate the client secret under App Registration → Certificates & secrets. Azure doesn’t let you edit an existing secret — create a new one, reconnect via Studio with the new value, then delete the old one.
  • Client secrets expire (default 24 months). When they do, every outbound reply returns 401 until you rotate.

​
Configure via YAML

For CI or fully scripted setups, paste credentials directly into workspace.yml or the .env file in the Friday home directory (default ~/.friday/local/.env). app_id is always required.
workspace.yml
communicators:
  teams:
    kind: teams
    app_id: 05ad3c58-7bfc-41d6-a249-011a6fe5337b
    app_password: <client secret value>
    app_tenant_id: <directory tenant id>
    app_type: SingleTenant  # or MultiTenant — must match Azure Bot's registered Type of App
Restart Friday so the new config is picked up.