Licensing is the pillar nobody wants to lead with in a pitch and the pillar that shows up in almost every engagement anyway. GitHub Copilot seat reselling through CSP is a good example: the commercial model looks simple until a partner has actually run it through a full billing cycle.
The mistake that shows up most often
Copilot ships in multiple tiers (Business and Enterprise, with different feature sets and different price points), and CSPs frequently quote and provision at the tier the customer asked for by name rather than the tier the customer’s actual usage pattern justifies. A customer who asks for Enterprise because of the brand name, but only needs Business-tier functionality, is a customer who will notice the delta on renewal and question the partner’s advice, not just the price.
The fix is not complicated: map the requested tier against actual feature requirements (custom knowledge bases, fine-tuned models, org-wide policy controls) before quoting, not after provisioning.
Where margin actually leaks
Three patterns account for most of the margin erosion I see on Copilot resale specifically:
- Seat assignment drift. Seats get assigned at rollout and never revisited. Six months later, a meaningful share are assigned to contractors who have left or teams that stopped using the tool, and the customer is paying (through the partner) for seats nobody is using, which becomes the first line item cut at renewal.
- CSP program tier mismatch. Not every CSP indirect reseller has the same margin structure on every Microsoft 365 and GitHub SKU combination, and Copilot seat pricing does not always sit inside the same program tier as the rest of a customer’s Microsoft estate. Quoting it as if it does is a common source of quiet margin loss.
- No seat utilization reporting built into the account. Without a recurring seat utilization check, the first time a partner learns about drift is when the customer raises it at renewal, at which point the conversation is defensive instead of advisory.
The checklist I use with partners
Before quoting Copilot seats through CSP, I ask partners to confirm four things: the tier maps to actual feature requirements, the seat count maps to active users rather than headcount, the program tier and margin structure for that specific SKU combination has been checked rather than assumed, and there is a quarterly seat utilization review built into the account plan from day one.
None of this is exotic. It is the difference between licensing being a line item a customer tolerates and licensing being a reason they trust the partner with the next conversation, whether that is Azure, AI or the rest of the GitHub Enterprise estate.