Leading US Telecom Operator Saves $8.4M on Microsoft EA Renewal

Updated August 2024 · 6 min read · Morten Andersen
April 2026
by Morten Andersen

The Challenge

The operator's fourth EA renewal was the largest and most structurally complex Microsoft engagement Redress had supported for this client. Three converging risks defined the renewal landscape. First, the November 2025 tier discount removal reset the pricing baseline and added $1.26M annually — a significant hit at this contract volume. Second, the frontline estate had evolved substantially since the prior renewal: a major network modernisation programme had migrated approximately 2,200 of the 11,000 F3 field technician workflows onto a specialist OSS (Operations Support System) platform, leaving those technicians assigned to F3 licences primarily used for company announcements and shift scheduling. Microsoft's account team was not proposing a downgrade — it was proposing a Teams Premium add-on at $10/user/month for the full 11,000 F3 field population, framing it as an operational transformation tool. That addition alone would have cost $13.2M over three years with no supporting business case from field operations management. Third, Copilot for Microsoft 365 was being pitched for full-fleet expansion across all 8,000 E3 corporate users at $30/user/month — a $28.8M addition over the term. The Azure OSS/BSS modernisation programme had completed Phase 1, leaving $2.4M in annual committed surplus.

"The Teams Premium pitch for our field technicians was well-constructed. But when we looked at what those 11,000 people actually do with Teams, the add-on had zero operational justification." — SVP of IT, Client Organisation

The Approach

Frontline Licence Audit and F3→F1 Conversion

A detailed licence utilisation audit was conducted across the full 11,000 F3 field population. Methodology: Teams activity data (calls, meetings, channel posts, file access), M365 app activation logs, and OSS platform activity logs cross-referenced by employee role, region, and job function. Finding: 2,200 field technicians whose primary workflow had migrated to the OSS platform were averaging fewer than 4 M365 interactions per week — primarily passive: receiving company broadcast messages and viewing shift schedules. These users qualified for Microsoft 365 F1 under Microsoft's own licensing use rights (F1 permits Teams Essentials, Exchange Online Kiosk, SharePoint, and basic Viva Connections). Converting 2,200 F3 seats ($8/user/month) to F1 ($2/user/month) generated $144,000/year in direct savings. The Teams Premium add-on for the field population was declined based on the audit findings: the proposed features (advanced calling queues, call recording, Teams Phone PSTN integration) mapped to zero workflow requirements for the field technician population.

Call Centre Licence Restructuring

The 3,000 call centre agent population was assessed separately. 1,800 agents were actively using Teams Phone and Microsoft 365 for omnichannel operations and were correctly positioned on F3. The remaining 1,200 agents were in a structured transition from a legacy PSTN platform to Teams Phone — a migration expected to complete over 18 months. For the transitioning population, Redress recommended a phased approach: F1 licences during the transition period (saving $72,000/year), with an agreed upgrade pathway to F3 upon platform cutover, documented in the EA schedule. Microsoft's standard position was to maintain all 3,000 on full F3 billing throughout; the phased approach required commercial escalation but was ultimately agreed.

Copilot Governance Assessment

The 500-seat Copilot pilot had been running for nine months across the corporate and engineering population. Usage telemetry showed 312 active regular users — concentrated in network engineering, finance, procurement, and legal — and 188 underutilising users primarily in back-office functions where Copilot workflow integration had not been completed. Redress recommended retaining the 500-seat commitment and negotiating a 12-month expansion option for up to 2,000 additional seats at pilot pricing, tied to a structured Copilot adoption programme for the underutilising population. The full-fleet expansion of 8,000 seats — representing $28.8M over three years — was declined.

Microsoft proposing Teams Premium add-ons or full-fleet Copilot at your EA renewal? Get an independent assessment before you commit. Book a Microsoft Review

Azure OSS/BSS Right-Sizing

Phase 1 of the OSS/BSS modernisation programme had completed on schedule. The Azure workloads supporting network telemetry ingestion, AI-driven fault detection, and OSS data integration had stabilised at 64% of the contracted commitment level. A 36% reduction in annual Azure commitment was negotiated, with the credit differential applied through a cross-pillar adjustment mechanism — converting the surplus into additional M365 discount depth rather than stranded future Azure credits. This partially offset the $1.26M tier removal impact on the M365 baseline.

The Outcome

17%
Total Cost Reduction
$8.4M
3-Year Savings
$13.2M
Teams Premium Avoided
36%
Azure Commitment Cut

The renegotiated EA delivered structured licence rationalisation across the frontline estate: 2,200 F3 field seats converted to F1 ($144K/year), 1,200 transitioning call centre agents moved to phased F1 pricing ($72K/year), and the Teams Premium add-on for the 11,000-person field population rejected outright ($13.2M avoided). Copilot was capped at 500 governed seats against a proposed full-fleet expansion of 8,000. Azure commitment was reduced 36%, partially mitigating the tier removal pricing reset.

Total savings over three years against Microsoft's renewal proposal: $8.4M — a 17% reduction. The operator retained full operational Microsoft capability across all populations and established a governed Copilot expansion pathway integrated with its IT workforce capability programme.

Key Takeaways

  • Teams Premium economics require actual workflow validation. The add-on's features — advanced calling, call queues, call recording — are irrelevant to field workforces that don't use Teams as a primary communication channel; licence additions should always be validated against documented workflow requirements.
  • F3→F1 conversion for OSS/platform-primary workers is consistently under-recognised. When the primary workflow system is not Microsoft 365, the F3 licence is often over-specified; Microsoft rarely proactively identifies this; a structured utilisation audit typically finds 15-25% of large F3 populations eligible for F1 reclassification.
  • Phased licence migration for transitioning populations is negotiable. Microsoft's default position prices transitioning staff at the destination licence tier throughout; phased pricing requires commercial escalation but is achievable with documented migration timelines.
  • Large EA Copilot expansions require adoption evidence, not just pilot existence. A 500-seat pilot with 312 active users does not justify an 8,000-seat full-fleet expansion; Microsoft's commercial playbook conflates pilot existence with fleet readiness; buyers should present usage-segmented adoption data as the basis for any expansion commitment.
  • Azure OSS/BSS right-sizing windows close at renewal. Post-Phase 1 stabilisation creates a measurable surplus that can be renegotiated through cross-pillar credit mechanics; this opportunity exists only at the EA renewal point and requires proactive modelling 6-9 months in advance.