Release Notes 210 / 211

💡 Please note that this release will be deployed on Saturday, the 17th.

Microsoft Extended Service Terms for Expiring NCE Subscriptions

January 19th, 2026, the Platform is introducing protective measures against Microsoft's Extended Service Term (EST) model to prevent unexpected billing for expiring NCE subscriptions. Effective April 1, 2026, Microsoft is discontinuing the free grace period, and subscriptions without explicit renewal settings will automatically convert to EST—separate SKUs priced at the standard monthly rate plus a 3% uplift. When you uncheck the auto-renewal checkbox in the Platform, it will now automatically send "Cancel at end of term" to Microsoft, ensuring subscriptions are cancelled rather than converted to EST with higher pricing. This update enables Distributors, Sellers, and direct CSPs to avoid unexpected EST charges and service disruption while maintaining control over subscription renewals.

Learn more: Microsoft Extended Service Terms for NCE Subscriptions
 

Improved Microsoft Customer Agreement (MCA) Flow for Greater Automation and Compliance

An MCA sequence flow now integrates updated Microsoft APIs to deliver a more automated, reliable, and future-ready agreement journey. This improvement ensures backward compatibility while enabling CSPs to seamlessly check, track, and complete Microsoft Customer Agreements using a centralized, persistent agreement store. By automatically determining agreement status, generating signing links when required, and completing MCA acceptance once attestation is confirmed, the updated flow reduces manual intervention, minimizes onboarding friction, prevents order blocking, and helps partners maintain continuous compliance as Microsoft evolves its agreement requirements.

Learn more: New Microsoft Customer Agreement (MCA) verification flow
APIs: Check MCA, MCA acceptance

Webhook Alert for Tenant Creation Failures

The Platform introduces the NewTenantNotCreated webhook to notify Distributors and Sellers in real time when tenant creation fails. This webhook-only event triggers on validation errors, missing data, API issues, or vendor rejections, providing key details including the attempted tenant name, error message, vendor ID, and timestamps in multiple formats. Partners can use this immediate notification to automate error handling, log failures systematically, and take corrective action quickly, reducing customer onboarding delays without relying on email notifications.

Learn more: NewTenantNotCreated Webhook

Enhanced Webhook Payloads for Improved Integration

The platform extends five existing webhooks with additional data fields to improve partner integration capabilities and reduce the need for follow-up API calls. The OfferProvisioned, NewTenantCreated, OnPurchaseNotification, OrderStatusChanged, and OfferProvisionError webhooks now include enriched information such as vendor subscription IDs, offer identifiers, customer references, order item IDs, and standardized timestamps in multiple formats (UTC, platform-formatted, and ISO 8601). These enhancements enable partners to process webhook events more efficiently with complete context, streamline automated workflows, and better track provisioning and order lifecycle events without additional data lookups.

Learn more: Platform Webhooks Guide for Partners, Webhooks documentation