teamsApp

teamsApp

Azure Functions sample app demonstrating the Microsoft Teams connector triggers from @azure/functions-extensions-connectors.

Triggers included

Function	Connector operation	Description
onNewChannelMessage	OnNewChannelMessage	Fires when a new root message is posted to a channel
onNewChannelMessageMentioningMe	OnNewChannelMessageMentioningMe	Fires when a channel message @mentions the signed-in user
onGroupMembershipAdd	OnGroupMembershipAdd	Fires when a member is added to the team
onGroupMembershipRemoval	OnGroupMembershipRemoval	Fires when a member is removed from the team

Run locally

npm install
npm start

Update local.settings.json with your connector runtime URL and access token before starting.

Deploy to Azure

azd up will provision:

• A Flex Consumption Function App (Node 20)
• A Storage account, Application Insights, Log Analytics
• A Connector Namespace (Microsoft.Web/connectorGateways) containing:
  • A Microsoft Teams connection
  • Four trigger configs, one per Functions trigger above, each routed to the corresponding function's connector webhook URL

azd auth login
azd up

During the postdeploy step, if TEAMS_GROUP_ID / TEAMS_CHANNEL_ID aren't already set on the azd environment, the script calls Microsoft Graph (/me/joinedTeams and /teams/{id}/channels) using your az login credentials and prompts you to pick a team and channel interactively. The selections are then persisted via azd env set so subsequent runs are non-interactive.

To skip the prompt (e.g. for CI), set them ahead of time:

azd env set TEAMS_GROUP_ID   <team / Microsoft 365 group object id>
azd env set TEAMS_CHANNEL_ID <channel id, e.g. 19:abcd...@thread.tacv2>

After provisioning, an azd postdeploy hook (infra/scripts/postdeploy.ps1 / .sh) uses the connector-namespace Azure CLI extension to:

1. Ensure the Teams connection exists and grant your user access to it.
2. Walk you through OAuth consent by opening the consent link in your browser and polling until the connection flips to Connected.
3. Create one trigger config per Functions trigger, each bound to the Teams connection and parameterized with TEAMS_GROUP_ID / TEAMS_CHANNEL_ID.

The Bash script requires jq. The PowerShell script requires PowerShell 7+ (pwsh).

Connector Namespace currently requires the brazilsouth region (the only region with the required preview features as of writing). Override via azd env set CONNECTOR_NAMESPACE_LOCATION <region> if needed.

To re-run only the post-deployment configuration without redeploying code:

azd hooks run postdeploy

The connector trigger requires the Preview Functions Extension Bundle (Microsoft.Azure.Functions.ExtensionBundle.Preview). This is already configured in host.json.

Verify the Connector Namespace, connection, and triggers

After azd up finishes, open the Connector Namespaces portal to verify the resource was provisioned and that all four triggers are wired to a Connected Microsoft Teams connection:

Connectors — Connector Namespaces

You should see:

• One Connection (Microsoft Teams) with status Connected
• Four Triggers (one per function), each in Enabled state and bound to the connection above

If a trigger is not listed or the connection shows as Unauthenticated, re-run azd hooks run postdeploy and complete the consent flow when prompted.

Project layout

teamsApp/
├── src/
│   ├── index.ts              # app.setup({ enableHttpStream: true })
│   └── functions/            # one file per trigger
├── infra/
│   ├── main.bicep            # azd entrypoint (subscription scope)
│   ├── resources.bicep       # Storage + App Insights + Function App
│   ├── connectorNamespace.bicep  # Connector Namespace + Teams connection
│   ├── main.parameters.json
│   └── scripts/
│       ├── postdeploy.ps1    # Creates trigger configs + OAuth consent (Windows)
│       └── postdeploy.sh     # Creates trigger configs + OAuth consent (Linux/macOS)
├── azure.yaml
├── host.json
├── local.settings.json
├── package.json
└── tsconfig.json