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.
Update, October 11, 2026
Two changes since this article was published widen who it affects. First, Microsoft's October 2026 Partner Center announcements state that "starting December 1, 2026, usage-based billing will be enabled by default for new Microsoft 365 Copilot Business licenses purchased in Cloud Solution Provider (CSP)," with a default spending limit of 4,000 Copilot Credits per user per month that admins can adjust. Microsoft says the change will initially not be available in some markets. A business that buys new Copilot Business licenses through a CSP partner from that date can have usage-based billing turned on without anyone opening the Cost Management node. Second, Microsoft's Copilot Credits documentation now lists more services managed by usage-based billing: Cowork, Advanced work in SharePoint, Advanced work in OneDrive, the Work IQ API, Copilot Managed Runtime, and Teams Phone Agent. With Auto-apply new services turned on, a spending policy can draw on newly supported services like these without a separate review.
Update, November 4, 2026
Microsoft pushed back the December 1, 2026 date described in the update above. A November 2026 Partner Center announcement, dated November 3, 2026, states that usage-based billing will now be "enabled by default for new Microsoft 365 Copilot Business subscriptions purchased in Cloud Solution Provider (CSP) during Microsoft's FY27 Q3 (January-March 2027), instead of December 1, 2026, as previously announced." Microsoft's stated reason: "We heard your feedback and are adjusting the effective dates to give you extra time to prepare for these upcoming changes and support your customers." The default spending limit for this change, when it does take effect, is unchanged at 4,000 Copilot Credits per user per month, which an administrator can adjust. A related date also moved: the Partner Center sandbox environment Microsoft had planned to open on November 2, 2026, for partners to test the new billing experience, did not open on that date, and Microsoft says it will announce a replacement date separately. This delay is specific to new Microsoft 365 Copilot Business license purchases made through the CSP channel, which is how most small and mid-size businesses buy Copilot through a reseller or managed service provider; it does not change the September default covered above, which already applies today to any organization that has turned on a Copilot spending policy for Cowork, the Work IQ API, or other usage-based AI features, regardless of when those licenses were purchased. If your business has not yet bought new Copilot Business licenses through a partner, this delay buys more time to prepare, not an exemption from the change itself.
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 usage-based billing has never been enabled for your tenant, this default does not currently apply to you; new Microsoft 365 Copilot Business licenses bought through CSP during Microsoft's FY27 Q3 (January-March 2027) change that (see the November 2026 update above). 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.