Microsoft Teams Integration
Microsoft Teams integration is not available in any released build today. Every backend handler behind it — connecting a workspace to Teams, editing the Teams command script, listing available teams/channels, running a Teams message test, and requesting a Teams approval — is a stub that unconditionally returns an error, in every edition alike. The working implementation these stubs were meant to delegate to has not been rebuilt since Orvanta forked from its upstream project. There is no licensing workaround; this isn’t gated by tier, it simply isn’t implemented yet. Contact Orvanta support for current status.
The description below documents the intended design so you know what to expect once it ships, not current behavior.
Overview
Section titled “Overview”Once implemented, Orvanta’s Microsoft Teams integration is meant to work in both directions: triggering an Orvanta script from a Teams command, and posting back to a Teams channel from an Orvanta script or flow.
Action on Orvanta from Microsoft Teams
Section titled “Action on Orvanta from Microsoft Teams”Setup requirements
Section titled “Setup requirements”The intended setup is for a workspace admin to open Workspace Settings, the “Slack / Teams” tab, and connect the workspace to Microsoft Teams — with OAuth configuration required first on self-hosted instances.
Command handler implementation
Section titled “Command handler implementation”Once connected, a script would handle the /orvanta command in Teams, receiving parameters including the Teams conversation activity ID, the command text, the initiating user’s name, the Teams Team ID, and the original Teams payload.
Permission management
Section titled “Permission management”The design calls for connections and variables used by the Teams command handler to be shared with an automatically created teams group — either directly, or by hosting them in folders associated with that group.
Advanced command handling
Section titled “Advanced command handling”Multiple commands would be manageable through flows with branches, text parsers, and approval steps, for human-in-the-loop command logic.
Approval steps integration
Section titled “Approval steps integration”Two approval types are planned:
- Interactive approval — Teams members approve or reject a request from within Teams, without opening the Orvanta UI.
- Basic approval — a link that opens Orvanta’s approval page in a browser.
Action on Teams from Orvanta
Section titled “Action on Teams from Orvanta”The design calls for a Teams-specific connection carrying a webhook URL (per Microsoft’s incoming-webhooks documentation), which scripts would use to post messages to a Teams channel.
Error handlers and alerts
Section titled “Error handlers and alerts”Once implemented, critical alerts (worker or queue health issues the instance itself detects) would be configurable to post to a Teams channel, alongside the Slack and email channels instance settings already support — gated to Enterprise and requiring SMTP configuration.
Related
Section titled “Related”See Slack Integration for the equivalent integration, which shares the same underlying gap on the “trigger scripts from chat” side.