Copilot Sept 28 Flip: 4 Checks for PR Flow and Invoices

If your team still treats Copilot as a chat add-on, the Sept 28 default changes are the last moment to decide what it costs and how it behaves. The upcoming changes matter because several settings move from user choice to platform choice.

The review default should feel like a warning label, not a feature name. It is the kind of change that looks harmless in a changelog and then shows up in your PR queue as extra review noise.

For admins, the real risk is coordination. Your review effort, access surface, and billing timing can all shift at once, and nobody on your team may have written the new defaults into the plan.

Four checks that keep the surprise out

Run these in the order that protects the most fragile thing first: access, then review behavior, then cash flow, then procurement. Each item is a setting you can open, a number you can count, or a status you can screenshot.

• Confirm the opt-in/out status: The github.com chat, GitHub Mobile chat, and cloud agent are being folded into one unified experience no sooner than September 28, 2026. Choosing the opt-out path will strip the assistant from github.com and GitHub Mobile for you or your team after the launch, which is scheduled no sooner than September 28, 2026. Open the admin setting and note whether your org is opting in or out.
• Set the review effort: To keep Lite as the default, choose Lite explicitly in the org or repo before September 28, 2026. If the review setting stays on Default, the effort then shifts, from Lite to Balanced, on September 28, 2026. Then check the saved value, not the dropdown.
• Forecast the seat billing change: Beginning October 1, 2026, assigned Business and Enterprise seats will be billed before the following billing cycle begins. Count assigned seats and model that timing before the next invoice lands.
• Verify payment and sign-up status: New Business and Enterprise customers can pay with credit cards or PayPal when sign-ups resume on September 1, 2026. Confirm the account is ready before you promise a seat to a new hire.

The access tradeoff is the loudest one

The opt-out decision gets personal where chat surfaces are involved. It changes whether your team can reach the tool at all, not just where the tool lives. That is a real access decision, and it deserves a named owner.

Before choosing, map who actually uses the assistant outside the editor. When people rely on it for quick questions while reviewing a PR, the access loss will be felt immediately. If it is mostly an editor feature, the opt-out may be easier to live with. Write down who uses it where before making the choice.

The review default deserves a screenshot

The review setting is the easiest one to miss because it hides in repository or organization settings. It is also the one most likely to change the daily feel of your PR flow. A lower-effort mode can keep the tool out of the way. A higher-effort mode can add more automated comments, more triage, and more friction on every merge.

When people have been living with the lighter setting, do not assume the new default is a harmless upgrade. Ask what the extra review effort will do to your merge queue, your on-call attention, and your tolerance for automated noise. If the answer is that you will find out, you have already lost the decision.

Take a screenshot of the current setting before changing it. That gives you a baseline after the switch: more comments, fewer comments, same comments, or a different kind of comment. The baseline is what lets you say whether the change helped or just added work.

The invoice will move timing, not just total

The billing change is less visible than the review change, but it is the one finance will remember. Cash timing is still a decision, even when the sticker price does not move. If your team assigns seats late in the cycle, the invoice can look larger than the usage you expected.

Before approving the next seat, write down the counts: assigned seats, unassigned seats, and the date the next charge lands. You do not need a spreadsheet. You need enough information to answer why the invoice moved when it moved.

If you are adding new seats, the payment method matters. Payment-method sign-ups have their own timing, and procurement can stall if nobody knows whether the account is ready to accept new customers. Check the status before promising a seat to a new hire.