Enablement · 05
Four ways to build, four owners
A company new to AI will hear 'Copilot can build it' and assume one course will cover the estate. It will not. Code, Copilot Studio, GitHub Copilot and Foundry serve different builders. The habit that matters is knowing which door you are allowed to open, and who maintains what comes out.
Match the person to the door
Code is the natural-language route inside the new Copilot, on a Frontier rollout from late September 2026. Studio is where a maker packages an agent or, since the public preview after 10 September, an app. GitHub Copilot stays with people who already work in a repository. Its 25 September release notes were about the software lifecycle, including a local sandbox in public preview.
Maintenance is the lesson
Whoever builds the tracker also creates a thing that will be wrong next month. Enablement includes who updates it, who is asked when it breaks, and which admin center shows it. Microsoft Learn still treats the choice between Agent Builder in Microsoft 365 Copilot and Copilot Studio as a real choice. Teach that choice. Do not collapse it into a single 'build an agent' hour.
No fictional headcount
FrontierOrg's department sizes are a planning fixture in a fictional simulation, not a staffing model. Do not hire from them. Do decide, in your own words, which of the four doors is shut this quarter.
Monday
Put the four names on a slide with one owner each, or the word 'shut'. Use that slide instead of a general 'app building' session.
Which door are you teaching because it is interesting, rather than because someone owns the result?
Sources: Microsoft Learn, Choose between Agent Builder and Copilot Studio (opens in a new tab). Microsoft Learn, What is Microsoft Foundry Agent Service? (opens in a new tab). GitHub Changelog, 25 September 2026 (opens in a new tab).
Where this note mentions FrontierOrg, that is a fictional method for rehearsing a decision. It is not a company, not a client, and not a case study.