Enablement · 04
One internal app, with someone from IT in the room
September's app-building release adds a /app skill in Cowork, available through Frontier, and app creation in Copilot Studio in public preview from the 10 September 2026 rollout. Code then puts natural-language apps, dashboards and workflows into the new Copilot experience, itself a staged Frontier rollout. The enablement move is one small internal app, not a programme of makers.
Who the first builder is
Microsoft's pitch for Code is a person without a conventional development workflow. That person still needs a named owner for the result, a data set they are allowed to use, and someone from IT who has seen the connections. A lunchtime app with no owner is a habit you will have to unwind.
What the first app should not do
Microsoft's own illustrations, an onboarding app that updates records, a field app that writes back, are product examples, not outcomes. For a first habit, pick a read: a tracker of work the team already keeps in a spreadsheet. Leave write-back until the owner agrees. The skill being taught is describing users, data and actions, then looking at what came back.
A fiction does not ship on day one
FrontierOrg, a fictional method, holds agent deployment until discovery has produced evidence. Your version is lighter. One app. One reviewer. A decision to keep, change, or delete. Deleting a bad prototype is a successful class.
Monday
Choose the app you will not build: anything that emails a customer or edits a live record. Choose the app you might: a tracker three people already share. Book the IT reviewer before the build.
Who owns the app on the day the person who built it is on leave?
Sources: Microsoft, 10 September 2026, Build business apps with Copilot Cowork and Copilot Studio (opens in a new tab). Microsoft blog, 25 September 2026, Introducing the new Copilot (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.