Microsoft Teams

Mention @Factory in a Microsoft Teams channel to have Droid investigate, implement, and test work on a remote computer. Droid posts progress and results in the same thread.

You delegate directly from Teams; you do not need to create a Software Factory automation. The Remote delegations settings control the shared execution configuration.

A personal Microsoft Teams connector gives Droid tools to use inside a session. It does not install the Factory app in Teams or enable channel delegation.

Prerequisites#

To connect and configure Teams delegation, you need:

• The Manager or Owner role in the Factory organization you want to connect.
• Access to Settings → Remote Delegations, including Teams app setup.
• Permission to authorize the app for your Microsoft organization and install it in Teams. Your Microsoft administrator may need to approve it.
• Service-account access and an active service account for shared execution.
• An execution template for Dynamic compute, or service-account-owned Droid Computers for Persistent compute.

Team members who delegate work need a Factory account in the connected organization. Use the same work email in Microsoft Teams and Factory so Factory can match the person making the request.

Connect and install the app#

Linking your Microsoft tenant and installing the app in Teams are separate steps. Complete both before delegating work.

1. 1
   Open Teams delegation settings

   In Factory, open Settings → Remote Delegations. Under Delegation Apps, find Teams and select Set Up for Org.

   If Teams is already connected, select Configure to open its setup page.

2. 2
   Authorize your Microsoft organization

   Select Connect on the Teams setup page. Sign in to Microsoft with an account in the tenant you want to connect and complete the consent flow.

   If Microsoft requires administrator approval, ask your Microsoft administrator to approve the app. Check that you are connecting the intended Microsoft tenant to the intended Factory organization.

3. 3
   Finish installation in Teams

   After authorization, Factory shows Connected and opens Microsoft Teams to finish installation. Select Install App on the confirmation if Teams does not open automatically.

   Install the app in the team whose channels will receive delegation requests. If the app is blocked or unavailable, ask your Teams administrator to check app availability and policy in the Teams admin center. Your Factory account team can confirm the installation path for your preview.

4. 4
   Verify the connection

   Return to Settings → Remote Delegations and confirm that Teams is connected. In Teams, check that the app is installed in the intended team and available in the channel's mention picker.

   A connected tenant alone does not confirm that the Teams app is installed. Complete the execution configuration below before sending your first request.

Configure shared execution#

In Settings → Remote Delegations, find Remote Delegation Configs and select Edit on Apps.

Follow Configure delegated sessions to review:

Eligible organizations receive a default configuration, service account, and execution template. Review those defaults to confirm that the environment can access the repositories and tools your task needs.

Teams channel delegations using the Apps configuration run with its service-account identity, Git credentials, and connectors, not the sender's personal connections. This configuration is shared with other delegation apps, so changes can affect more than Teams.

Team members can set a preferred model and reasoning level under Settings → Session Defaults → Delegations. When organization policy allows it, the requester's model preference overrides the configuration's model. Choose Org default to use the configuration's model and reasoning settings. A personal model preference does not change the execution identity or connector access.

Delegate a task from a channel#

1. 1
   Open a channel in a team where the app is installed.
2. 2
   Start a new post and select @Factory from the mention picker.
3. 3
   Describe the task, including the repository, desired outcome, and verification steps.
4. 4
   Send the message.

For example:

@Factory In the storefront repository, investigate the failing checkout test. Fix the cause, run the relevant tests, and open a pull request with a summary and test results.

Factory starts a session using the shared configuration and posts status updates in the thread. For code changes, Droid is instructed to open a pull request and return its URL. Review the proposed changes and test results before merging.

Follow progress and send follow-ups#

To continue the task, reply in the same thread and mention @Factory again with your instruction. For example:

@Factory Add a regression test for the empty-cart case, then rerun the checkout tests.

If Droid asks a question, mention it again in that thread with your answer. Teams does not support interactive question forms; if Droid reports that a question stopped the run, send the answer as a new mention to continue.

For shared service-account sessions, only the person who started the delegation can send follow-ups or stop the task. Other channel members can read the replies, but cannot take over that session.

Start a new channel post with a new mention for a separate task. Mentions in an existing delegation thread continue its session.

Stop a running task#

Select Stop on the running task's status card in Teams. Use the Teams account that started the delegation.

Stopping does not undo work already performed. Review any changes or pull requests produced before the stop.

Troubleshooting#