Why This Matters

Adding Copilot to a platform without architecture leads to wasted credits, frustrated developers, and unclear ownership. Architecting it deliberately turns a feature into a force multiplier.

Concept Explained

Copilot as a platform layer: 8 surfaces, each serving different workflows. Architecture decides which surface for which workflow, who owns what, how costs are tracked, and how the platform evolves.

How It Works

Map team workflows to Copilot surfaces. Assign ownership (DevEx owns Extensions, QA owns test pipelines). Set budgets per team. Plan rollout in phases. Document.

Step-by-Step Tutorial

1. Map workflows

2. Match to surfaces

3. Assign ownership

4. Set budgets

5. Document

Real-World Example

A platform team architected Copilot: inline+Chat for daily coding, CLI for ops, Spaces for onboarding, coding agent for delegated chores, Extensions for internal services. Assigned owners. Set budgets. Documented. Adoption: 90% of developers using Copilot daily within 3 months.

Example Prompts / Commands / Code

Workflow              Surface             Owner        Budget
----------------------------------------------------------------
Daily coding          Inline + Chat      Dev          Per-seat
Code review           @workspace         QA          Shared
Debugging             @terminal + CLI    Ops          Shared
Onboarding            Spaces             DevEx        Shared
Infra scripts         CLI                DevOps       Shared
Delegated chores      Coding agent       Eng Manager  Per-task
Internal APIs        Extensions          Platform     Shared
PR descriptions       GitHub Action      DevEx        Per-PR

graph TB
    subgraph "Developer Platform"
        A[Inline + Chat] --- Dev[Devs]
        B[CLI] --- Ops[Ops]
        C[Spaces] --- DX[DevEx]
        D[Coding Agent] --- EM[Eng Mgrs]
        E[Extensions] --- Plat[Platform]
        F[GitHub Action] --- CI[CI/CD]
    end

    subgraph "Governance"
        G[Metrics API]
        H[Org Policy]
        I[Audit Log]
    end

    G -.-> A
    G -.-> B
    G -.-> D
    H -.-> E

Common Mistakes

• No ownership — everyone uses everything, no one owns anything.
• No budgets — credits burn uncontrollably.
• One surface for everything — misses other surfaces' value.
• No documentation — tribal knowledge only.

Best Practices

• Map workflows to surfaces deliberately.
• Assign ownership per surface.
• Set per-team credit budgets.
• Document architecture in a one-pager.
• Plan phased rollout (start with 1–2 surfaces).

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• Copilot for business

Official References

• Copilot for business

Related lessons: PR-02, PR-14