Skip to main content

Microsoft 365 Copilot Gets a Setting That Decides Who Can Ask for Cowork, Code and Autopilot

Microsoft's new admin setting controls who can request pay-as-you-go Copilot features, and from the end of January 2027 those features show up for every licensed user by default. What the setting does, the dates, and what to decide.

KBY News Desk7 min read
Call center agent wearing headphones working on a laptop in a modern office setting.

Microsoft has added a setting to the Microsoft 365 admin center that decides who in your organisation can ask for access to Copilot’s pay-as-you-go features, such as Cowork, and it is changing what your staff see by default. According to Microsoft’s documentation, the setting is called “Access to usage-based billing experiences” and sits under Copilot, then Settings. Its default, “All users”, lets anyone without a spending policy request one. Microsoft’s Message Center notice adds that at the end of January 2027 the entry points to Cowork, Code and Autopilot become visible by default to everyone with a Microsoft 365 Copilot licence, whether or not you have switched them on, and that an older setting is retired on the same date. The change does not start any billing by itself, but it does mean your helpdesk will be asked about features you may not have decided to offer.

#What Microsoft has published

Everything in this story comes from two Microsoft pages, and we attribute the details to Microsoft throughout. The first is Microsoft Learn’s page titled “Access requests to usage-based billing experiences”, which carries a date of 12 November 2026. The second is Message Center post MC1546354, “Discover usage-based billing (UBB) experiences like Cowork, Code, and Autopilot”, dated 9 November 2026. We read the Learn page directly. We read the Message Center post through a public archive that reproduces it, because the original is in the Microsoft 365 admin center, so treat our summary of the post as the archive’s copy of Microsoft’s text. Both pages were read on 20 November.

“Usage-based billing” here means features that Microsoft bills by use, in units it calls Copilot Credits. The Message Center post names Cowork, Code and Autopilot as the experiences concerned. Microsoft says a person still needs an applicable spending policy and available credits before they can use one.

#The setting, step by step

Microsoft’s documentation gives the path: sign in to the Microsoft 365 admin center, go to Copilot, then Settings, then All Settings, and select “Access to usage-based billing experiences”. A flyout titled “Choose who can request a spending policy” offers three options:

  • All users: any user without a spending policy can request one. Microsoft marks this as the default.
  • Specific users and groups: only the people and groups you select can request one.
  • No users: nobody can request one. Those users instead see a link to learn more about “Advanced AI experiences that require usage-based billing”.

You then select Save, and Microsoft says the change might take up to 24 hours to apply. The page says that to configure the setting you need the Global Administrator role, and it adds that you should use the role with the fewest permissions and keep Global Administrator for emergencies. The documentation is explicit that this choice “does not complete the usage-based billing setup by itself”: the billing and spending side is configured separately under Copilot, then Cost Management.

#What changes, and when

Microsoft’s Message Center post sets out a schedule in three steps. In mid-November 2026 the new setting becomes available, which matches the Learn page already describing it. In mid-December, Microsoft says it will add an option to point users to a custom web address for “Your organization’s guidance”, and that option will only be available if you have chosen “Specific users and groups” or “No users”. At the end of January 2027, Microsoft says, the new behaviour and the setting are enforced and the older setting, “Allow users to discover and use AI experiences enabled by usage-based billing”, is retired. The post says the date is the end of February 2027 for organisations on deferred release.

The behaviour that is enforced is the one that matters. Microsoft says the Cowork, Code and Autopilot entry points will be visible by default to users with a Microsoft 365 Copilot licence even if their organisation has not enabled access. A user who has no applicable spending policy will see either a “Request access” option or a “Learn more” option, depending on how you have set the new control. Microsoft states that the change “does not automatically enable usage-based experiences or initiate billing”, and that users still need a spending policy and available credits.

One small inconsistency in the post: its summary says the visibility change starts in January 2027, while the body says the end of January. We have used the more specific wording.

#Our reading: you are choosing a tone, not a switch

Here is how we read it, and it is our interpretation, not Microsoft’s statement. From the end of January you will not be able to hide these features from licensed users. What you can control is what happens when someone clicks. That makes the setting less like an on-off switch and more like a decision about how much demand you are willing to generate. Leave it on “All users” and every licensed person who has not been given a spending policy gets a button inviting them to ask for one. That is a fair default if you want to hear who is interested, and a poor one if you have no process for answering.

The cost risk sits behind the request, not the button. Microsoft says this change does not itself start billing, and that who can actually use the features depends on spending policies. We think the likeliest problem in the first weeks is therefore not a surprise invoice but a stream of questions and requests that nobody owns, though you should check which spending policies already exist in your tenant before you assume there are none. Decide who answers them, and what they say, before the end of January, not after.

For most organisations we would lean towards “Specific users and groups” while you work out whether anyone needs these features. It lets a pilot group ask, keeps everyone else on a “Learn more” path, and works with the custom guidance address that arrives in mid-December. Where nobody is meant to use them yet, “No users” is the plain statement of that policy. We would only leave “All users” in place deliberately.

#What to do

  1. Find out who can change it. Microsoft says the Global Administrator role is needed. If you do not hold it, ask whoever does. In a small business that may be an outside IT provider.
  2. Look at the current value now and write it down, together with the value of the older “Allow users to discover and use AI experiences enabled by usage-based billing” setting. Microsoft’s pages we read do not say how an existing value carries across, so a note of what you had gives you something to compare against.
  3. Choose one of the three options on purpose and save it. Allow for up to 24 hours before it takes effect.
  4. Write the guidance your staff will be pointed to. In mid-December Microsoft adds a place to link it, for those who pick “Specific users and groups” or “No users”. A short internal page saying who can have these features, why, and how to ask is enough.
  5. Review your spending policies under Cost Management, since those, not the request setting, decide who can actually use the features. Microsoft recommends doing this before the end of January.
  6. Diary two dates: mid-December for the guidance address, and the end of January 2027 (end of February on deferred release) for enforcement and the retirement of the old setting.

If your Copilot is managed for you, send your provider this question, word for word: “Which option is our tenant set to for access to usage-based billing experiences, who receives the requests, and what does our spending policy allow?”

#What Microsoft’s pages do not say

  • Where a request goes and who approves it. The pages we read describe the choices users see but not the approval workflow.
  • How the value of the retired setting carries over to the new one.
  • Whether the setting is visible in every tenant yet. Microsoft describes a rollout from mid-November, and we have not seen it in a live tenant.
  • The cost of the features. These pages do not give prices, and we have not relied on any third-party figure.

For the wider picture of what Microsoft is changing for administrators in its agent and Copilot controls, see our Ignite coverage, and for a plain definition of the product name, our Microsoft Copilot lexicon entry. We will update this story if Microsoft changes the dates or explains how the retired setting carries over.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Microsoft Learn, Access requests to usage-based billing experiences, dated 12 November 2026learn.microsoft.com
  2. 02Microsoft 365 Message Center post MC1546354, Discover usage-based billing (UBB) experiences like Cowork, Code, and Autopilot, 9 November 2026 (public archive copy)mc.merill.net

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Microsoft 365 Copilot Gets a Setting That Decides Who Can Ask for Cowork, Code and Autopilot. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.

Microsoft 365 Copilot Usage-Based Billing Access Requests Setting