Teams App Manifests

Microsoft Teams requires an "app package" (a zip containing manifest.json + icons) to register a bot in a Teams tenant. This is not an application resource — the Orcha server never reads these files. They are used in two contexts:

  1. App Store submission — manifest.prod.json is submitted to Microsoft Partner Center for public listing in the Teams App Store. Once approved, customers find and install Orcha directly from Teams.
  2. Development sideloading — manifest.dev.json is zipped and manually uploaded to a test Teams tenant for local testing.

Files

File Purpose
manifest.prod.json Production manifest (app ID: eda62fe4-..., domain: app.getorcha.com)
manifest.dev.json Dev manifest (app ID: e8e6aca2-..., domain: orcha.barreto.tech)
color.png App icon 192x192 (shared)
outline.png App icon 32x32 transparent (shared)

Building a sideload zip (dev)

cd infra/teams-app
zip orcha-dev-teams-app.zip manifest.dev.json color.png outline.png
# Then rename manifest.dev.json to manifest.json inside the zip:
printf '@ manifest.dev.json\n@=manifest.json\n' | zipnote -w orcha-dev-teams-app.zip

Azure resources

Environment App Registration Azure Bot
Production eda62fe4-7d17-4f58-af23-838e1b554458 (Orcha) Orcha
Development e8e6aca2-5bca-4ef7-a267-985a03038ef6 (Orcha Dev) orcha-dev-bot

Both live in resource group orcha-bot-rg under the Orcha Azure tenant (818432d6-b012-47e8-a326-09e010bf22d0).