EA Renewal, Seasonal Staff, and a Nine-Day Sev A at Harborline Retail

The 2,100-seat quote is the wrong shape regardless of channel - nobody should buy 300 annual seats that are used for 14 weeks.

• Annual-term seats for 1,800. Cheapest per seat-month, and matches the permanent headcount. Either the EA or annual-term CSP works; EA brings price protection for three years and a single organisation-wide commitment, while CSP brings no minimum seat count and lets you change quantities per subscription.
• Monthly-term seats for the 300 seasonal users. In CSP, terms are set per subscription, so 1,800 can sit on annual and 300 on monthly in the same tenant. Monthly-term pricing carries a per-seat premium, but four months of premium beats twelve months of idle seats by a wide margin.

Judgement points to raise with the CFO:

• Confirm whether an EA minimum commitment is even met by 1,800 - if the organisation no longer qualifies, the EA conversation is moot.
• If the EA is retained, the 300 seasonal seats must not be swallowed into the annual quantity at true-up, or the org re-learns this lesson every anniversary.
• Use group-based licensing tied to the HR seasonal group, with a scheduled sign-in block at season end, so seats are reclaimed rather than merely paid for.

Nothing in the licence tier fixes it. M365 E3 includes break/fix support with web and phone channels, but no designated engineer, no proactive posture, and no contractual Sev A response target for your integration. That is a support contract decision, not a SKU decision.

Options:

• Microsoft Unified (the successor to Premier): paid contract, named account team, Sev A 24x7 with contractual response times, escalation management, and proactive service reviews. This is what the CIO described, and it is the right fit for a revenue-impacting ERP-to-Exchange path.
• Smaller-scoped advanced support for just the critical systems, if the full Unified enterprise tier is disproportionate.
• CSP partner support: many partners resell or bundle tiered support. Often the cheapest route, but verify the response-time commitments in writing - a partner promising 24x7 informally is not the same as a contractual Sev A.

Cheaper habits to fix regardless: check Service Health first to see whether the fault is Microsoft-side before opening the ticket, and get the integration owner into the escalation path on day one. Nine days is partly a ticket-hygiene failure.

Use the deployment benefit that comes with the subscription you are already buying.

FastTrack is a Microsoft-funded benefit included with eligible subscriptions at sufficient seat counts - Harborline's 1,800 E3 seats qualify. It provides remote, guided assistance from Microsoft engineers or an approved partner: onboarding planning, adoption guidance, and remediation for workloads including Teams and Teams Phone. It is advise-and-guide rather than hands-on-keyboard delivery, and it does not cover custom PSTN carrier contracting or store-by-store cutover execution.

Practical play for 60 stores:

1. Engage FastTrack early - during the CSP/EA negotiation - and get the Teams Phone rollout plan and the PSTN/SBC design reviewed before ordering numbers.
2. Use FastTrack for the plan, remote configuration reviews, and adoption assets; use internal staff for the repeatable store cutover pattern.
3. Push the carrier and SBC work to a partner, or choose a Microsoft Calling Plan where available, so the PSTN complexity sits outside your understaffed team.

Be honest with the CIO: FastTrack closes the planning gap, not the delivery gap. If the stores cut over on a hard date, one partner engagement for cutover weekends is usually cheaper than a failed weekend.