Cost · 11
Do not promise the new Home to every seat
Microsoft's 25 September 2026 announcement is a staged rollout, not a statement that every Copilot customer has Home and Code today. Home and Code start through Frontier. Code was aimed at late September for that programme, with broader availability expected in the following weeks. Autopilot's private preview was planned to expand at the end of September. Promising the new screen in a launch mail creates a cost: support, expectation, and seats bought for a shelf people cannot open.
Availability is a budget line
A feature you cannot switch on has no return, and it still consumes the time of the people waiting for it. Sequence the spend. Cowork has been generally available since 16 June 2026, subject to tenant access and a spending policy. That is something a new team can assess now.
The default is still off
Enterprise usage-based services stay off until a policy exists. Even a team inside the Frontier programme does not get a blank meter. Access without a cap is a different, larger promise. Do not make it by accident in a newsletter.
Say what is actually on
FrontierOrg, fiction, will not let an in-world claim outrun the evidence. Your Monday version is a sentence in the staff note: what is on, for whom, and what is not here yet. That sentence is cheaper than a month of questions to the help desk.
Monday
Rewrite the next Copilot note so it names who has Home or Code, who does not, and the date you will check again. If you do not know, the note says you do not know.
What will you stop promising until you can see it in your own tenant?
Sources: Microsoft blog, 25 September 2026, Introducing the new Copilot with Home, Code and Autopilot (opens in a new tab). Microsoft, 16 June 2026, Copilot Cowork is now generally available (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.