How to Reassign Microsoft 365 Licenses When Moving from EA to CSP
Question details
The user needs to understand if they must repurchase and manually reassign Microsoft 365 licenses when transitioning a tenant from an Enterprise Agreement (EA) to a Cloud Solution Provider (CSP) agreement.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Transitioning Microsoft 365 subscriptions from an Enterprise Agreement to a Direct CSP within the same tenant.
- Observed behavior
- Licensing and subscription management must be properly transitioned to the new CSP model to avoid service disruption when the EA ends.
Before making any changes, ensure you have Global Administrator rights to the Microsoft 365 tenant and a complete roster of all current users and their assigned EA licenses.
Provision New CSP Subscriptions and Reassign User Licenses
Ensure continuous service by purchasing equivalent CSP licenses and assigning them to users before the EA expires.
When moving from an Enterprise Agreement to a CSP agreement, the billing and subscription management models change. Even if your tenant and partner remain the same, you must provision new subscriptions under the CSP model to replace the expiring EA licenses.
Contact your Direct CSP partner to purchase the equivalent Microsoft 365 or Office 365 subscriptions (e.g., Office 365 F3, Exchange Online Plan 2) required for your organization.
Once purchased, log into the Microsoft 365 Admin Center and navigate to 'Billing' > 'Your products' to ensure the new CSP licenses are active and visible in your tenant.
Navigate to 'Users' > 'Active users' in the Admin Center. Select the affected users, and assign the newly purchased CSP licenses while simultaneously removing the old EA licenses to avoid potential conflicts.
Double-check that all active users have the correct CSP licenses applied before the Enterprise Agreement officially ends to prevent any service interruptions, email access issues, or data loss.

Consult Microsoft Partner Center Support
If you encounter errors during the transition or need clarification on specific licensing migrations, escalate the issue through Partner Center.
Simplify Licensing and Reduce Costs with WPS Office
Managing Enterprise Agreements and complex CSP transitions can be expensive and administratively heavy. If you want to reduce overhead while maintaining enterprise-level productivity, consider WPS Office. It provides a lightweight, highly compatible, and cost-effective alternative to Microsoft Office, completely bypassing the hassle of complicated subscription migrations.
- 1. Download the installer: Visit the official WPS Office website and download the enterprise or free version.
- 2. Install the software: Run the lightweight installer on your devices—it takes only minutes to complete.
- 3. Start creating: Open your existing .docx, .xlsx, or .pptx files directly in WPS Office with full format retention.

Frequently Asked Questions
Do I lose my data when switching from an Enterprise Agreement to CSP?
No. As long as you transition within the same tenant and assign the new CSP licenses to users before the EA licenses expire, user data such as Exchange emails, SharePoint sites, and OneDrive files will remain completely intact.
Can I keep the same Microsoft partner when moving to CSP?
Yes, you can use the same direct partner for your CSP agreement as you did for your Enterprise Agreement. However, the underlying subscription management and billing model will change, requiring action on your part.
Do users need to reinstall Office apps after the license change?
Generally, no. If the new CSP license includes the same desktop app entitlements (for example, switching from Microsoft 365 E3 EA to Microsoft 365 E3 CSP), the installed applications will recognize the new license automatically upon their next background check.
Is it required to manually reassign every user license?
Yes, you or your partner must explicitly assign the newly provisioned CSP licenses to your users and remove the EA licenses to avoid overlap. This process can be manual in the Admin Center, or automated using PowerShell scripts and Microsoft Entra ID group-based licensing.




