A factory can start work when users mention @Warp in configured standard or shared channels, and Warp replies in the same thread. Thread replies can continue an existing factory work item when that behavior is enabled.
Setup requires a Warp workspace administrator, a Microsoft Teams administrator or team owner, and a factory editor. The Teams administrator uploads and approves a warp-microsoft-teams-app.zip package, then Warp is added to each relevant team. Delegated approval links expire after seven days. Teams must be enabled for the Warp workspace; the documentation says customers should contact sales if the option is unavailable.
Factory editors select connected teams and at least one standard channel. Warp then creates a teams-app-mentions automation. Private channels and direct messages are not supported. The page also says unsupported attachments do not block request text, and code changes may open a pull request. It does not establish a launch date, pricing, general availability, or details of a separate Azure DevOps Services integration.