Client Profile
The client is a US regional telecom operator providing broadband, managed network, and enterprise connectivity services. The organisation employs approximately 11,000 staff across corporate functions, network operations, field engineering, and customer support. Its Microsoft footprint is substantial: a three-year Enterprise Agreement covering Microsoft 365 E3 and E5, Windows, and a suite of Teams add-ons including Teams Phone Standard, Teams Rooms, and Microsoft Audio Conferencing, accumulated over two successive EA cycles.
The telecom sector presents a distinctive Microsoft licensing dynamic: organisations in this sector often have complex telephony environments with pre-existing PBX infrastructure, carrier-grade switching platforms, and regulated communications requirements. The result is a persistent tension between Microsoft's push to consolidate voice into Teams and the operational reality that PBX migrations are technically complex and commercially sensitive in a regulated environment.
The Challenge
Microsoft's renewal proposal was submitted at $12.4M over three years — a 28% increase over the prior agreement. Two elements of the proposal attracted immediate scrutiny: a renewal of the organisation's 6,200-seat Teams Phone Standard deployment at an increased per-licence rate, and a new 3,000-seat Microsoft 365 Copilot commitment at $30 per user per month ($3.24M over three years).
The Teams Phone issue was identified in a pre-engagement review. The operator had licensed Teams Phone Standard for 6,200 users at the prior renewal, based on a project plan to migrate all corporate voice users off the legacy Cisco Unified Communications Manager (CUCM) system within 18 months. Two and a half years later, that migration had progressed to approximately 2,800 seats — leaving 3,400 licences assigned to users who remained on CUCM and had no active Teams Phone deployment. The licence cost for this unused population was approximately $8 per user per month, representing approximately $326,400 per year in pure waste.
— VP of Technology Procurement, US telecom operator client
The Copilot proposal was evaluated against the organisation's actual AI tooling roadmap. The operator had an emerging AI programme focused primarily on network operations, predictive maintenance, and customer churn analysis — none of which were addressed by Microsoft 365 Copilot. The 3,000-seat Copilot deployment proposed by Microsoft targeted the corporate workforce, where the business case was speculative at best.
The Approach
Redress Compliance was retained eight weeks before the renewal date. The engagement proceeded across three concurrent workstreams.
Teams Phone Audit and Right-Sizing
A full Teams Phone activation audit was conducted, cross-referencing the 6,200 licensed accounts against the Microsoft Teams admin centre activation records and the operator's CUCM routing tables. The audit confirmed 2,786 active Teams Phone users and 3,414 accounts with Teams Phone licences that had never been activated and remained on CUCM. The right-sized Teams Phone commitment was established at 2,900 seats — the active population plus a 4% buffer for anticipated migration activity over the new EA term.
Copilot Demand Assessment and Counter-Position
A structured Copilot demand assessment was conducted across the corporate population. Department heads across finance, HR, legal, and commercial functions were asked to articulate specific use cases, quantify expected productivity improvements, and estimate realistic adoption timelines. The assessment surfaced a credible business case for approximately 350 seats in document-intensive roles (contract management, regulatory filings, commercial proposals) — but could not support the 3,000-seat deployment proposed by Microsoft.
A counter-proposal was constructed: a 350-seat Copilot pilot in year one of the new EA, with a contractual option to expand to up to 2,000 seats in years two and three at pre-agreed pricing. The pilot would be evaluated against a defined set of KPIs including document turnaround time, user adoption rate, and departmental productivity scores.
Licence Mix and Pricing Negotiation
In addition to the Teams Phone and Copilot workstreams, the team identified 820 E5 users in network operations and field engineering roles whose job functions did not require the advanced E5 security and compliance features. These users were transitioned to E3, generating a further saving of approximately $21 per user per month.
| Optimisation Action | Scope | Annual Saving | 3-Year Total |
|---|---|---|---|
| Teams Phone — remove unused licences | 3,414 seats removed | $327,744 | $983,232 |
| Copilot — reduce from 3,000 to 350 seats (yr 1 pilot) | 2,650 seats not committed | $954,000 (yr 1 saving) | $1,271,520 |
| E5 → E3 rationalisation | 820 seats | $206,640 | $619,920 |
| Negotiated per-seat pricing improvement | E3 population | $74,000 approx. | $222,000 |
The Outcome
The operator signed a restructured three-year EA at $9.3M, against Microsoft's opening proposal of $12.4M — a reduction of $3.1M (25%). The final agreement included:
- Teams Phone Standard renewed at 2,900 seats, eliminating 3,314 unnecessary licences and saving $983,232 over three years.
- Copilot structured as a 350-seat year-one pilot, with pre-agreed expansion pricing and a defined exit provision at the end of year one — saving $1.27M in avoided Copilot commitment relative to Microsoft's proposal.
- E5-to-E3 migration for 820 network and field engineering staff, saving $619,920 over three years with no reported operational impact.
- Negotiated per-seat pricing improvement on the E3 population, contributing approximately $222,000 over three years.
At the end of the Copilot pilot year, the operator's deployment had reached 310 of the 350 committed seats, with departmental adoption rates in contract management and commercial proposal roles exceeding target KPIs. The expansion conversation for year two was therefore conducted from a position of demonstrated value — the opposite of the speculative 3,000-seat commitment that Microsoft had proposed.
Carrying Teams Phone licences you're not using? Facing a Copilot upsell?
Independent add-on audit and EA negotiation support — no conflicts, buyer side only.Key Takeaways
Teams add-on licences are among the most commonly wasted items in an EA
Microsoft's success in selling Teams Phone, Teams Rooms, Teams Premium, and Audio Conferencing into EA renewals has outpaced the pace of actual deployment in many organisations. The result is a widespread pattern of add-on licences sitting on accounts where the corresponding infrastructure migration has stalled, been deprioritised, or simply never started. A specific add-on activation audit — separate from the general M365 usage review — is essential for any organisation carrying Teams telephony or rooms infrastructure licences.
Copilot pilots should be negotiated into the EA, not purchased speculatively
The correct structure for a first-time Copilot deployment is a defined pilot with a limited seat commitment, explicit success criteria, pre-agreed expansion pricing, and an exit provision if adoption targets are not met. Organisations that accept a large Copilot seat commitment at renewal without this structure will find themselves locked into a multi-million dollar obligation for a product whose adoption, in most organisations, reaches 30–40% of committed seats in the first year — not 80–100% as Microsoft's productivity case assumes.
Add-on pricing is opaque and negotiable
Microsoft's EA renewal proposals typically present add-on products (Teams Phone, Audio Conferencing, Teams Premium, Copilot) at list pricing or at a modest bundled discount. These prices are individually negotiable, particularly when the customer has independent benchmark data and a credible argument about competitive alternatives. In this engagement, the Teams Phone per-licence rate was reduced by approximately 9% relative to the prior EA rate — a saving that compounded significantly across 2,900 licences over three years.
The organisations that win at EA renewal are the ones that track consumption
The 3,414 unused Teams Phone licences in this case had been invoiced and paid across the prior three-year EA term without challenge. The total cost of that oversight was approximately $982,000 — a sum that would have been avoided entirely if the operator had conducted an annual activation audit. The governance structures established after this engagement — quarterly add-on activation reviews, annual E-level segmentation audits, and a formal Copilot adoption dashboard — are designed to ensure that no future renewal begins from the same starting point of accumulated, unexamined waste.