GitHub began the announced rollout that maps unconfigured eligible generally available Copilot features and supported client capabilities to an enterprise or organization global default. Enforcement runs from 22 through 26 October; explicit choices and preview opt-ins remain unchanged.
Why it matters: The policy moved from a future deadline into active enforcement. Administrators that left eligible features unconfigured can now see behavior change on different days across organizations even when no individual setting was edited.
GitHub made Copilot budget-increase requests generally available for Business and Enterprise plans using usage-based billing. When a member exhausts AI credits, the request routes to the paying organization or enterprise, where an owner or billing manager can approve, adjust or deny it and immediately restore access at the new amount.
Why it matters: Copilot consumption can now trigger a governed exception instead of an opaque block or an off-platform support path. That reduces friction, but it also makes request ownership, approval criteria and spend telemetry part of day-to-day AI access control.
GitHub began gradually reopening credit-card and PayPal signups for Copilot Business and Enterprise. New seat assignments require payment before access, and existing customers on those payment methods move to upfront charges for every assigned seat at the next billing cycle starting 1 October; included usage may be prorated and overages can require more payment.
Why it matters: The change turns idle assignments and usage overages into immediate continuity and cash-flow concerns for self-serve enterprise customers, without changing headline plan prices.
GitHub announced three upcoming Copilot changes: credit-card enterprise signups and prepaid seats return from 1 September; no earlier than 28 September, web, mobile, and cloud-agent experiences share one default-enabled policy while chat is retained for the life of the account rather than 28 days; and code review's Default effort moves from Lite to Balanced. Existing card-funded enterprise customers move to upfront seat billing from 1 October.
Why it matters: One announcement changes data lifetime, default enablement, agent policy, review behavior, and cash timing. Organizations that treat Copilot settings or chat retention as stable can silently accept a broader agent surface and a much longer evidence and…
GitHub began a staged rollout of its generally available global model policy for Copilot Business and Enterprise. Unconfigured and future generally available models inherit the organization or enterprise default, explicit per-model choices are preserved, and open-weight or data-retaining models remain disabled by default.
Why it matters: New model availability now follows a durable enterprise default instead of requiring every administrator to react model by model, reducing silent policy drift while making the default itself consequential.
Copilot Business and Enterprise administrators can establish an enterprise model baseline while assigning optional models to specific teams. Access is additive across every enterprise team a user belongs to.
Why it matters: Model governance can now follow job role, training, and experimentation cohort rather than relying only on repository or organization ownership.