GitHub Copilot in Slack vs Teams: Shared Agent Sessions

Quick answer

Choose Slack if the pilot organization already uses Copilot Business or Enterprise and wants task-specific Slack Code channels for visible plans, diffs, previews, steering, and session history. Choose Microsoft Teams if users have paid Copilot plans, the Teams Public Developer Preview prerequisite is acceptable, and the organization is ready to govern AI credits and separately billed cloud sandboxes.

The core security model is similar: a mention starts a shared cloud-agent session, the whole conversation becomes context, only users with repository write access can trigger changes, shared artifacts use the app identity, work runs asynchronously in a cloud sandbox, and a pull request still needs normal review.

Comparison

Decision	Slack	Microsoft Teams
Launch status	Public preview	Public preview
Announced plan scope	Copilot Business and Enterprise organizations	Paid Copilot plans
Collaboration space	Thread plus one Slack Code channel per task	Channel, thread, or direct message
Client prerequisite	Approved GitHub app for Slack	GitHub app plus Teams Public Developer Preview where required
Default repository	Channel default; shared setting	Channel default; direct messages do not use one
Who can trigger changes	Participant with repository write access	Participant with repository write access
Shared artifact identity	GitHub app identity	GitHub app identity
Cost wording in launch	Existing entitlements and cloud-agent budgets	AI credits plus separately billed cloud sandboxes

Do not infer that an omitted detail is absent from the other surface. Verify the current integration and billing documentation for the tenant you will operate.

Shared thread context is the first design choice

Both integrations can capture the entire thread and use it to understand and implement the request. That context can be stored in generated artifacts. A direct message narrows participation but does not remove GitHub, billing, repository, retention, or audit obligations.

Create a new thread for each task. Exclude customer data, credentials, incident secrets, private roadmap material, unrelated messages, and instructions from people without authority. Record which conversation and message initiated the session so reviewers can reconstruct intent.

Permissions, attribution, and merge rules

Conversation access and repository write access are different. A participant can add context without being allowed to trigger code changes. Guests and outside collaborators have additional restrictions in current GitHub docs. Test these denial paths rather than assuming the chat platform’s membership model maps cleanly to GitHub authority.

In shared contexts, Copilot-created artifacts use the app identity. GitHub supports an additional approval for unattributed Copilot pull requests when a ruleset already requires approval. Keep human authorship review, CODEOWNERS, required checks, workflow approval, environment protection, and branch rules intact.

Billing and FinOps

Map all usage to a billed owner before enabling a wide channel. Review plan entitlements, pooled or individual AI credits, metered overages, cloud-agent budgets, cloud-sandbox product or SKU budgets, Actions minutes, alerts, and hard-stop behavior. Slack’s launch wording is not evidence that sandbox use is free; Teams’ explicit split is a useful prompt to verify both controls on either surface.

Start with a per-session budget and a repository cohort smaller than the account budget permits. Monitor retries and abandoned sessions, not only merged pull requests.

Selection rule

Use the collaboration surface where administrators can reliably control apps, retention, guests, exports, identity linking, and incident response. Workflow fit comes second. If neither surface can keep the thread narrow, map the billed owner, enforce repository authority, and preserve human review, start sessions from GitHub or an IDE instead.

Follow the Slack setup guide, the Teams setup guide, and the ChatOps readiness checklist.

Official sources

• GitHub Copilot in Slack announcement
• GitHub Copilot in Teams announcement
• Slack integration guide
• Teams integration guide
• Budgets and alerts

Source check: August 23, 2026. Recheck preview scope, plans, app requirements, thread behavior, permissions, and billing for the exact surface.