May's Partner Center announcements center on one launch: Microsoft 365 E7 and Agent 365 become generally available on May 1. But the month also brings a subscription lifecycle change that starts applying automatically on May 4, an API security requirement that's already blocking non-compliant calls, and two legal updates that CSP partners need to track before year end.
TL;DR:
Here are the announcements that matter most for CSP partners this month.
Ready to start?
Microsoft Updates - [05/2026]
| Update | Date | Who's Affected | Action Required |
|---|---|---|---|
| Microsoft 365 E7 and Agent 365 GA | Announced May 1, 2026 | All CSP partners | No |
| Extended Service Terms (EST) enforcement | In effect May 4, 2026 | All CSP partners | Yes |
| Mandatory MFA for Partner Center APIs | Enforced since April 1, 2026; reiterated May 4, 2026 | Partners using app+user APIs | Yes |
| Microsoft Marketplace Terms of Use updated | Effective May 27, 2026 | All partners using Marketplace | No |
| Updated Microsoft Partner Agreement (MPA) & CSP Program Guide | Announced May 28, 2026; effective Dec 1, 2026 | Direct bill, distributors, indirect resellers | Yes — France direct bill/distributor only |
| ReferenceId format change in recon files | June 15, 2026 | Direct Bill, Distributors | Update billing processing logic |
What's happening:
Microsoft 365 E7, the "Frontier Suite", is now generally available. It bundles Microsoft 365 E5, Microsoft 365 Copilot, and the new Agent 365 control plane into one SKU, along with the full Microsoft Entra Suite and advanced Defender, Intune, and Purview capabilities.
Date of Announcement: May 1, 2026
Effective Date: available on the CSP price list now
Who is affected: All CSP partners
Action Required: this doesn't affect existing customer subscriptions. Review the enablement materials before you pitch E7 to customers.
💡 Quick Note: E7 is the first SKU where Agent 365 governance isn't a bolt-on decision, it ships built in. If customers keep asking who's watching what their agents do, this SKU is your answer, and it's a stronger upsell than E5 alone. Check the Microsoft 365 E3 vs. E5 vs. E7 feature comparison before you build the pitch.
What's happening
Subscriptions that were purchased or renewed on or after April 1, 2025, expire on or after May 4, 2026, and have auto-renew turned off now transition automatically into a paid Extended Service Term instead of simply lapsing.
Date of Announcement: May 4, 2026
Effective Date: May 4, 2026. Already in effect
Who is affected: All CSP partners (direct bill, distributors, indirect resellers)
Action Required: Review subscriptions that meet the three EST criteria and decide to renew, cancel, or accept the EST transition before the expiration date.
💡 Quick Note If you're not actively managing auto-renew settings, EST becomes your default outcome, not a choice you made. Pull the list of subscriptions expiring after May 4 with auto-renew off now, before you bill a customer for a term nobody discussed with them. Instructions for exporting that list are in the Extended Service Terms documentation.
What's happening:
Partner Center now enforces MFA on every app+user API call. It blocks any call that lacks a valid MFA claim and returns a 401 response with error code 900421.
Date of Announcement: May 4, 2026 (reiterating enforcement that began April 1, 2026, and continued rolling out through the following months)
Effective Date: April 1, 2026. Full enforcement, with a progressive rollout still underway
Who is affected: All partners using Partner Center app+user APIs for automation — provisioning, billing, customer management, support
Action Required: Yes, inventory every app+user API integration, confirm MFA claims are present end-to-end, and test in a sandbox before production traffic hits the block.
💡 Quick Note This deadline already passed, but May's reminder is a signal that Microsoft keeps expanding enforcement rather than treating April 1 as a one-time cutover. If your billing reconciliation pipeline runs through app+user auth, a 900421 error deserves the same urgency as a production outage, not a "circle back next sprint" ticket. Full requirements are in Mandating multifactor authentication for your partner tenant.
What's happening:
Microsoft refreshed the Marketplace Terms of Use as part of a periodic review to align with current business practices and regulatory requirements.
Date of Announcement: May 5, 2026
Effective Date: May 27, 2026
Who is affected: All partners and customers transacting through Microsoft Marketplace
Action Required: No — the terms took effect automatically; partners and customers didn't need to sign or acknowledge anything.
💡 Quick Note: I'm not sure what specifically changed in this revision — Microsoft's announcement doesn't itemize the edits. Please verify at the Microsoft Marketplace Terms of Use directly if you resell through Marketplace and reference these terms in customer-facing agreements.
What's happening: Microsoft published updated versions of the Microsoft Partner Agreement and the CSP Program Guide, revising terms to reflect current business practices around privacy, security, compliance, and transparency.
Date of Announcement: May 28, 2026
Effective Date: December 1, 2026 for most partners, applied automatically. Direct bill and distributor partners in France must explicitly accept the updated MPA in Partner Center between December 1, 2026, and February 28, 2027.
Who is affected CSP direct bill partners, distributor partners, and indirect resellers. Direct bill and distributor partners in France carry an extra requirement.
Action Required No for most partners — the update applies automatically. Yes for direct bill and distributor partners in France — they must explicitly accept within the window above, or their agreement can expire.
💡 Quick Note December 1 feels distant, but if you're a direct bill or distributor partner in France, put February 28, 2027 on the calendar now as a hard deadline — miss it and your agreement can expire, which means you stop transacting. Everyone else can review at a normal pace, but it's worth reading how accepting the Microsoft Partner Agreement works so a future term change doesn't catch you off guard.
May's theme is compliance catching up with growth. Microsoft tightened enforcement on two fronts partners can't defer (API security and subscription lifecycle) while refreshing the legal foundation (the MPA, the CSP Program Guide, Marketplace Terms) that every CSP transaction runs on. At the same time, Microsoft 365 E7 points to where the next revenue conversation sits: governed, agentic AI at scale. Partners who treat May's updates as operational work, not background reading, will be in better shape for the deadlines already stacking up later in the year.
All announcements sourced from the official Microsoft Partner Center announcements: Microsoft Partner Center Announcements May 2026