Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The stated change applies only to new standalone or bundled Microsoft 365 Copilot Business purchases through CSP. It does not establish that existing licenses will convert automatically.
- The default configuration is pay-as-you-go and includes the Azure subscription setup needed for usage billing. The announcement names Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness.
- Administrators can set monthly organization and user Copilot Credits limits, threshold emails, user or group scope, and available services, and can disable automatic inclusion of future services.
- After reaching a finite allowance, users lose access to agents and services governed by that policy for the remainder of the month, until credits reset on the first of the next month. This is more than a spending notification.
- The public announcement mentions a preset monthly limit without giving an amount or establishing one master switch that guarantees all newly configured usage billing is disabled. PRODUCT_FIT=NONE: a network exit cannot change license or billing eligibility.
Define Scope First: November 2 Changes Future Defaults, Not Proven Existing-License Conversion
Microsoft Partner Center announced on September 16, 2026, that new standalone Microsoft 365 Copilot Business licenses and bundles bought through Cloud Solution Provider (CSP) will default to pay-as-you-go from November 2. The audience includes CSP distributors, indirect resellers, direct-bill partners, SSPs, systems integrators, and software companies selling the product. The announcement gives a date but no exact activation time or timezone.
The key phrase is 'new purchases through CSP.' The official text does not say previously purchased licenses will automatically convert on November 2, nor does it specify regional phases, billing delays, or existing-license upgrade rules. Purchase orders, quotations, and customer explanations should distinguish license pricing from Copilot Credits consumption as two cost lines. Do not imply the base subscription covers all usage.
What the Default Setup Includes: Check Azure Billing and Service Access Separately
The announcement says new licenses include the Azure subscription setup required for usage billing and names eligible experiences such as Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness. Separate Microsoft 365 administration documentation currently lists Cowork, apps built with Cowork, and Work IQ API under Cost Management. Because the two public service lists differ, do not treat the Cowork management procedure as a complete Harness activation workflow.
The general administration guide still tells an authorized administrator to open Copilot > Cost Management in Microsoft 365 admin center, select Get Started, choose a billing method, and activate a default spending policy. Default purchase configuration, the actual tenant policy, and access to a specific service are three separate checkpoints. This article has not signed into a tenant, purchased a license, or verified any administrative execution result.
Assign Administrative Roles and a Billing Owner Before Purchasing
Global administrator and Billing administrator roles can add, select, and change billing methods and assign them to policies. AI administrator and License administrator roles can create spending policies and manage limits and alerts, but cannot configure or change a billing method. People who only need usage reports should use AI Reader, Global Reader, or another supported read-only role instead of a Global administrator account for routine reporting.
At quotation stage, record at least the customer tenant, license SKU, expected purchase date, Azure billing account and subscription owner, who can manage billing methods, who can manage policies, and who receives alerts. If the customer cannot identify the Azure billing owner or administrative responsibilities, do not complete the purchase first and add governance later.
Four Cost Controls: Organization Limits, User Limits, Alerts, and Service Scope
The default spending policy can cover the whole organization, or users, groups, and services can be customized before activation. The organization's monthly allowance can be unlimited or a finite number of credits. Individual monthly user limits can also prevent one person from exhausting the budget. Once a finite limit is reached, users lose access to agents and services governed by the policy for the rest of the month, until the first-day reset. Limits therefore affect business continuity as well as costs.
Administrators can set threshold emails separately for total policy usage and individual user allowances. They should also explicitly select which agents and services may consume credits. Auto-apply new services is enabled by default for spending policies; disable it if new services should require review first. Alerts are not hard limits, and hard limits do not replace service selection. Validate all four controls together.
Prepaid Versus PAYG: Billing May Continue After Prepaid Credits Run Out
Microsoft supports billing sources including Azure subscriptions and Copilot Credit Pre-Purchase Plan (P3). The official documentation says policies consume available prepaid credits first, then automatically move to pay-as-you-go. Buying prepaid credits does not inherently cap spending. Monitor prepaid balance, PAYG overage, organization limits, and user limits separately.
New policies use the preconfigured default billing method. Accessible Azure subscriptions appear in the list. If none are accessible, the system may create one using the billing account associated with Microsoft 365 admin center; creating that subscription requires a Global administrator. A policy's billing method cannot be changed directly after creation. The documented route is to delete and recreate the policy, so check whether users and groups would fall under another policy before switching.
Deleting a Policy Is Not a Master Off Switch: No Published One-Click Opt-Out
The public administration guide permits deleting spending policies but explicitly says deletion does not remove, reassign, or reset Copilot Credits, and historical usage remains. Users still covered by another group policy continue consuming under that policy. Deleting a policy removes its allowance constraints; it is not a master switch guaranteed to stop all usage billing.
The public pages describe restricting or deselecting individual services, disabling automatic inclusion of future services, and turning off Cowork where applicable. However, this review found no single verifiable complete opt-out for the new CSP default configuration, and no published preset monthly limit amount. Mark both as UNKNOWN in customer explanations instead of promising a one-click shutdown after purchase.
Pre-Rollout Validation, Failure Handling, and Review Triggers
Start with non-critical users or a test group. Verify the target policy's user and group scope, organization and user limits, threshold emails, service selections, Auto-apply new services, billing method, Copilot Credits consumption records, and access behavior after reaching a limit. Compare Microsoft 365 admin center usage with Azure cost records over the same time window. One successful request or alert email does not validate a monthly bill.
Stop expanding scope if subscription ownership is unclear, roles are insufficient, service scope differs from the quote, limits do not block as expected, billing and credits do not reconcile, or changing the billing method requires deleting an active policy. Preserve redacted evidence. Around November 2, recheck the preset amount, existing licenses, regions, Harness management path, and complete opt-out guidance. Merge official changes into this same page. A proxy or IP change cannot alter CSP procurement, administrator permissions, or Copilot Credits billing.
Sources
Frequently Asked Questions
Which Copilot Business purchases default to usage billing from November 2?
The announcement specifically covers new standalone and bundled Microsoft 365 Copilot Business purchases through CSP. It does not establish automatic conversion of existing licenses, and does not publish an exact activation time or regional rollout.
Does the base license price already include all Copilot Credits?
Do not assume that. Microsoft distinguishes fixed licensing from billing for actual usage. The new configuration can bill Copilot Credits for eligible experiences through an Azure subscription.
Has Microsoft published the preset monthly limit amount?
As of September 21, 2026, the public announcement says there is a preset monthly allowance but gives no credit or monetary amount. Do not substitute P3 pricing examples or values shown in another tenant for this default.
How can administrators control costs?
They can configure monthly organization and individual-user limits, policy and user alerts, user or group scope, permitted agents and services, and disable automatic inclusion of future services. An authorized role must manage the billing method.
Does reaching a limit only stop charges?
No. The documentation says users reaching a finite policy allowance lose access to its managed agents and services for the remainder of the month, until credits reset on the first of the following month.
Can usage billing for a newly purchased license be completely disabled with one click?
The official public pages reviewed here do not establish a master switch guaranteed to fully disable the new default configuration. Deleting a spending policy removes its own constraints; it must not be described as clearing credits, historical usage, or all other policies.