Technology
Microsoft 365 Copilot Spending Policies Now Auto-Add Newly Supported Copilot Services by Default
Microsoft updated its Copilot Cost Management documentation to confirm that "Auto-apply new services" ships turned on for every spending policy. For organizations using Copilot Credits for Cowork or the Work IQ API, newly supported Copilot services and agents are added to the policy as Microsoft makes them available, unless an admin turns the setting off.
Microsoft's own administrator documentation for Copilot Cost Management, updated September 10, 2026, confirms a default setting that changes how organizations pay for AI in Microsoft 365: when a spending policy has "Auto-apply new services" turned on, which it is by default, "newly supported Microsoft Copilot services and agents are automatically added to the policy as they become available," according to Microsoft's own guidance. Microsoft's documentation states plainly that this setting "is turned on by default" both when an organization first activates its default spending policy and when an admin creates any additional policy afterward.
Who This Actually Affects
This applies specifically to organizations that have enabled usage-based billing through Copilot Credits, the consumption-based payment model layered on top of flat-rate Copilot licensing for AI experiences such as Cowork (Copilot's multi-step agent feature) and the Work IQ API. If your organization uses only standard, per-user Microsoft 365 Copilot licensing and has never opened the Cost Management node in the Microsoft 365 admin center, this default does not apply to you. If you have set up a spending policy to fund Cowork, however, that policy is enrolled in the auto-apply default unless someone has already gone in and turned it off.
What the Default Actually Does
A spending policy is how an organization sets a monthly credit budget and decides which AI agents and services are allowed to draw against it. The auto-apply setting decides what happens when Microsoft ships something new: with it on, any future Copilot service or agent Microsoft adds to the usage-based billing program is automatically folded into your existing policy and immediately able to spend against your budget and your connected Azure billing method. With it off, a new service or agent is held out of every policy until an administrator reviews it and adds it manually. Microsoft's guidance is direct about the tradeoff, telling admins to "turn off the setting if you want to review and add future services manually," and separately to "turn off Auto-apply new services for any policy that shouldn't automatically govern future supported services or agents."
Why a Default-On Setting Is a Budget Question, Not Just an IT One
Microsoft has been expanding what counts as a usage-based billing service through 2026, and it says directly that it is "working to bring more agents and services" into the program going forward. Under the default setting, every one of those future additions inherits whatever budget and billing method the policy already has configured, with no review step and no notification beyond whatever consumption alert threshold was set when the policy was built. For a small or mid-size business running a lean finance or IT function, that means the monthly Copilot Credit spend an owner or controller approved for Cowork can grow to include agents nobody evaluated, without anyone having made an affirmative decision to fund them. The September update does add real visibility tools alongside this, including admin email alerts when policy usage crosses a set threshold and a policy-level consumption dashboard, but both are opt-in configurations an admin has to set up; neither is the default.
What to Check Now
If your organization has activated any Copilot spending policy, open the Microsoft 365 admin center, go to Copilot, then Cost Management, then the Configuration tab, and review the Auto-apply new services toggle on every existing policy, not just the default one. Decide, for each policy, whether unreviewed future services should draw against that budget automatically or wait for a manual add. While you are there, configure the policy-level spending alert threshold and recipient list if it has not already been set, since that alert is the only warning an admin gets before a policy runs into pay-as-you-go overage. If nobody at your organization has activated usage-based billing at all, this default does not currently affect you, but it is worth confirming that with whoever manages your Microsoft 365 tenant rather than assuming.
Cyber One Solutions helps commercial clients configure and monitor Microsoft 365 Copilot governance, including spending policies, as part of our managed cloud service, which handles ongoing Microsoft 365 and Entra ID administration. If you are rolling out Copilot more broadly, our recent guide on running a permissions audit before any Copilot rollout covers the related data-access review worth doing at the same time as a cost policy review.