These pages are maintained as opinionated implementation guides — worked examples you can copy and adapt, not documentation. Think of it in three tiers:

• The aircraft manual — GitHub Docs: what every switch does.
• Flight doctrine — the Well-Architected Framework: the design principles behind a good rollout — what to consider and why — but it stops short of naming specific tools.
• A proven flight plan — these guides: one concrete, runnable way to actually do it on a real stack.

Each guide is a working flight plan for the how: specific tooling, real config, and the trade-offs behind each choice. Treat it as one reference implementation. Take what works for your environment and adapt the rest.

Copilot Adoption Official Resources

• Rolling Out GitHub Copilot at Scale — GitHub’s official rollout guide
• Well-Architected: Adopting Copilot at Scale — GitHub’s Well-Architected Framework guidance
• Copilot Feature Matrix — Official feature comparison across plans and IDEs

Top 3 Recommendations for Skilling Up Developers at Scale

The highest-impact adoption strategies focus on raising the floor across your organization — ensuring every developer has the tools and support to be productive with Copilot, not just the early adopters and power users.

1. Implement a Champion Program — Identify and empower internal advocates who can mentor peers and drive adoption organically. See the Well-Architected Champion Program guide.

2. Get Users on the Copilot CLI — The CLI shifts developers from single-agent pair programming to orchestrating multiple agents in parallel. Instead of watching code change line by line, developers can multitask between terminals — delegating work across agents while staying focused on architecture and decisions. Training: Copilot CLI Zero to Hero.

3. Create an Internal Plugin Marketplace — and make your plugins required — Curate and share custom plugins/skills so teams can leverage each other’s work. See the Copilot Plugins Marketplace docs and the open-source awesome-copilot collection for inspiration. A marketplace only offers plugins, so pair it with enterprise managed settings (GA July 2026) to make your standards the default. Its enabledPlugins key — part of enterprise-managed plugin standards (public preview) — auto-installs your required plugins at sign-in for enterprise users on supported Copilot clients. That is how you distribute the skills, agents, and hooks that carry your standards, rather than relying on developers to install them.

The Guides

Each of these is a proven flight plan — one concrete, runnable implementation on a real stack, not the only way to do it. Lift the flight plan and adapt the waypoints to your own tooling.

• Managing Copilot Usage-Based Billing — budget sizing math, promo-window credit arbitrage, and a troubleshooting checklist for when developers get blocked.
• Pulling Copilot Metrics & Billing Into Your Data Lake — the credentials, endpoints, and daily pull to keep your own long-term usage and billing history.
• Measuring AI in Pull Requests — measure AI leverage across merged PRs with trailer scanning and the Copilot usage metrics API.
• Deploying Copilot Settings via MDM — enforce settings with enterprise-managed settings (including OpenTelemetry export), and push overridable defaults across VS Code and the CLI with Intune.
• Using CLI-Backed Skills Instead of MCP Servers — package a skill plus a CLI as a required plugin across the CLI, VS Code, and the Copilot app, with a pre-flight install check instead of running an MCP server.