The First 72 Hours: Activation and Portal Setup
The moment your EA is countersigned by Microsoft, your organisation's entitlements move from "Pending" to "Active" status in Microsoft's systems. That transition is not automatic from a deployment perspective — you have work to do immediately to ensure licences are accessible and the administrative framework is in place.
In one engagement, a European logistics company signed a 3-year Microsoft EA with strong E5 security terms — then failed to activate Azure AD P2 and Defender for Endpoint within the 90-day window. When the True-Up arrived, Microsoft's SAM review flagged 340 users as non-compliant because the deployment records did not match licence entitlements. Redress was brought in post-audit; the dispute was resolved with zero back-charge, but the 90-day governance gap had cost six months of productive security tooling. The same risk applies to every new EA.
Microsoft's licensing portals have consolidated significantly. The legacy Volume Licensing Service Centre (VLSC) was retired in April 2024, and all EA administration now flows through the Microsoft 365 Admin Center and the Microsoft Admin Centre for Azure. Your first task is to ensure that the relevant internal stakeholders — IT, procurement, and finance — have appropriate admin roles assigned within these portals. Microsoft uses role-based access control, and the licensing admin role is separate from global admin, so provisioning the right people with the right permissions requires deliberate setup rather than default access.
Your Customer Success Account Manager (CSAM) from Microsoft will typically reach out within the first week to schedule an onboarding call. Accept this call, but prepare for it rather than treating it as a vendor formality. Your CSAM's primary role is to help you realise value from the products Microsoft has sold you — which aligns with their interest in the renewal. Use this initial call to confirm portal access, clarify your deployment timeline, and establish the cadence for ongoing engagement.
Licence Assignment: The Deployment Reality
Having signed for a number of licences and having those licences deployed to active users are two very different things. Enterprises consistently over-purchase at the point of signature, citing future headcount growth or anticipated project needs. The result is that 25 to 35 percent of EA licences are typically unassigned or underutilised in the first 12 months.
Establish a licence assignment workflow within the first 30 days. This means creating a clearly defined process for how new joiners get assigned licences, who approves licence type decisions (particularly the E3 versus E5 versus E7 question for new hires), and how leavers' licences are recovered and reassigned. Organisations that do not establish this process in the first month routinely pay for 18 months of unneeded licences before the first True-Up brings the issue into focus.
For M365 specifically, the 2026 SKU stack (F1 → F3 → E3 → E5 → E7) creates a richer set of assignment decisions than previous years. E7 is the new top tier at $99/user/month — do not default to E3 for everyone if you have a heterogeneous workforce. Frontline workers should be assigned F-tier licences (F1 at ~$2.25/month or F3 at ~$8/month) rather than E3, which saves $31/user/month for each correctly reclassified seat.
Understanding Your True-Up: The Annual Accountability Moment
The True-Up is the EA mechanism by which Microsoft reconciles your contracted licence count against your actual deployment. It happens annually on the anniversary of your EA start date. At True-Up, you report your actual usage across all products covered by the EA; if your deployment exceeds your contracted quantity, you owe Microsoft for the difference at the price point in your EA.
The True-Up is not just a compliance exercise. It is a negotiating window. If your usage is below contracted quantities, the True-Up is your opportunity to document under-utilisation formally and use that data in mid-term adjustments or at the next renewal. If your usage is above contracted quantities, the True-Up determines what you pay — and how you characterise the incremental consumption can affect the price applied to the overage.
Starting the True-Up Preparation Cycle Early
The 120-day mark before your EA anniversary date is when you should begin your True-Up preparation. The specific actions at each milestone:
- 120 days before: Pull a full licence utilisation report from Microsoft 365 Admin Center. Identify products where deployment has significantly diverged from contracted quantities in either direction.
- 90 days before: Brief business unit leaders on any significant overage or under-usage findings. Begin conversations about whether to adjust deployment plans or accept the True-Up charge.
- 60 days before: Prepare your True-Up submission document. This is also when you engage your CSAM to understand whether any mid-term pricing adjustments are available for overages rather than True-Up back-charges.
- 30 days before: Submit your True-Up report. Any disputes about the scope of products covered, the pricing applied to overages, or the classification of users should be raised at this stage — not after submission.
Critical timing note: The True-Up anniversary date is set at EA signing and cannot be changed without Microsoft's agreement. Organisations that lose track of this date and submit late lose their ability to challenge overage pricing and face penalties. Calendar this date immediately upon signing.
Building EA Governance: The Structures That Actually Work
EA governance is the set of internal processes, roles, and cadences that ensure your organisation stays in control of its Microsoft estate throughout the contract term. The absence of governance is the single most common factor in organisations arriving at renewal with little leverage, significant shelfware, and an inflated cost base.
Governance Committee Structure
Effective EA governance requires two operating levels. At the strategic level, a quarterly steering committee involving IT leadership, procurement, and finance should review total Microsoft spend, deployment status against contracts, and emerging product needs that might require agreement amendments. At the operational level, a monthly tactical team — typically the licensing admin and IT operations leads — should track daily assignment changes, monitor usage telemetry, and manage day-to-day licence requests.
Six Core Governance Policies to Establish in Year One
The policies that prevent the most costly EA problems are: a licence assignment approval policy (who can authorise what tier for which role); an exit process that recovers licences from leavers within five business days; a quarterly usage review cycle against entitlements; an escalation process for mid-term agreement changes; a data retention policy for True-Up submission documentation; and a rule that no new Microsoft product trials or pilots are initiated without licensing team awareness (to prevent shadow deployments that create undeclared True-Up obligations).
The Most Costly First-Year Mistakes
Based on advisory engagements across hundreds of EA implementations, these are the mistakes that generate the most preventable costs in year one of a Microsoft EA.
1. Failing to Reclassify Frontline Workers
Organisations with a significant field or frontline workforce — manufacturing, retail, logistics, field services — routinely assign E3 licences to users who would be fully served by F3 at $8/month. At scale, this represents $31/user/month in unnecessary spend. In a 3,000-user frontline population, that is $1.1 million in annual waste that will be locked in for the full EA term unless actively corrected.
2. Treating the True-Up as Purely Administrative
Organisations that use the True-Up only as a compliance report miss the strategic dimension. The True-Up is annual evidence of your consumption patterns. Over three years, this data is the most powerful tool you have in the next renewal negotiation. If it shows consistent under-utilisation, you have grounds to reduce your committed seat count. If it shows targeted usage in specific products, you have a basis to negotiate better unit pricing on those products at renewal.
3. Ignoring the CSAM Relationship
The CSAM assigned to your account has a dual role: helping you realise value from Microsoft products (which is genuine) and expanding your Microsoft footprint (which serves Microsoft's revenue objectives). Organisations that disengage from their CSAM entirely miss legitimate adoption support; organisations that treat every CSAM interaction as a commercial engagement miss the human value of the relationship. The optimal approach is to engage the CSAM for deployment support and product guidance, while keeping commercial conversations separate and mediated through procurement.
4. Not Understanding the E7 Upsell Timeline
Microsoft will begin positioning E7 to your account team well before your EA anniversary. E7 at $99/user/month (GA May 1, 2026) bundles Copilot, Agent 365, and Entra Suite — but the Agent 365 component is a governance control plane only, not an execution engine. Organisations that are pushed towards E7 for everyone in year two or three of their EA without first establishing Copilot utilisation baselines typically overspend significantly. Establish those baselines in year one.
5. Failing to Document the Negotiation Context
The promises and commitments made by Microsoft's account team during negotiation — "we can adjust the seat count mid-term," "pricing will be protected at this level" — have no contractual weight unless they appear in the signed agreement. Document every verbal commitment, request written confirmation, and file the complete negotiation record. This documentation becomes the foundation of your leverage in the next negotiation in three years' time.
Just signed a Microsoft EA? Make sure your first year sets you up for renewal leverage.
Redress Compliance's Microsoft licensing advisory specialists provide independent EA governance support from day one of your agreement.Quick-Reference: Post-Signing Checklist
- Confirm EA status changed from Pending to Active in Microsoft 365 Admin Center
- Assign Licensing Admin and Billing Admin roles to appropriate internal stakeholders
- Calendar the True-Up anniversary date and set 120-day, 90-day, 60-day, and 30-day preparation reminders
- Complete a full licence inventory in the first 30 days — identify assigned, unassigned, and over-provisioned seats
- Validate frontline workers are on F-tier licences (F1 or F3) rather than E3
- Establish the licence assignment approval policy and leaver recovery process
- Schedule the first quarterly steering committee review for 60–90 days post-signing
- Document all verbal commitments received during negotiation with a request for written confirmation
- Accept CSAM onboarding call — but separate deployment support from commercial conversations
- Brief finance on the True-Up mechanism and its annual budget implications