Fix Invalid License Options for Office 365 E3 in PowerShell
Question details
Identify invalid service-plan options when assigning an Office 365 E3 license with PowerShell.

- Product
- Microsoft Office 365 E3
- Device & OS
- not provided
- Scenario
- An administrator uses a PowerShell script to assign Office 365 E3 licenses with selected service plans.
- Observed behavior
- The script reports invalid license options without identifying the offending plan, and PowerShell lists more service plans than the administration portal.
Identify the affected user's account, the Office 365 E3 SKU, and the service plans specified in the script. Check that you have the administrative permissions needed to read subscriptions and assign licenses.
Compare the Script's Service Plans with the Office 365 E3 SKU
Use the plans returned for the specific subscribed SKU to find invalid, duplicated, or unavailable entries.
PowerShell may expose service plans that are not shown in the administration portal. A longer list alone does not establish which entry caused the error; compare the script against the plans for the exact SKU.
Office 365 E3 commonly uses the SKU part number ENTERPRISEPACK. Confirm the SKU in your tenant rather than confusing it with Microsoft 365 E3.
In PowerShell, install the Microsoft Graph PowerShell SDK if needed, then run Connect-MgGraph -Scopes 'Organization.Read.All' and sign in with an authorized account.
Run Get-MgSubscribedSku -All | Select-Object SkuPartNumber, SkuId to list subscriptions. Confirm the Office 365 E3 SKU part number and select the matching subscription.
Run $sku = Get-MgSubscribedSku -All | Where-Object SkuPartNumber -eq 'ENTERPRISEPACK', then run $sku.ServicePlans | Select-Object ServicePlanName, ServicePlanId, ProvisioningStatus. If the tenant returns more than one matching subscription, inspect the results and select the intended SKU.
Open the assignment script and compare each specified plan with the selected SKU's ServicePlanName and ServicePlanId values. Remove duplicates and replace or remove names or IDs that are deprecated, unavailable, or absent from that SKU.
Review the disabled plans in the script for service-plan dependencies, then rerun the assignment for the affected user. If it still fails, provide Microsoft support with the exact error, SKU, and plan list.

Assign the License with Microsoft Graph PowerShell
Use the current Microsoft Graph approach if the script relies on legacy license-options commands.
Work with Office Documents Using WPS Office
WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation work. Its familiar interface and Microsoft Office format support make it easier to move existing files, although it does not fix Microsoft 365 license assignments.

Frequently Asked Questions
Why does PowerShell show more service plans than the Microsoft 365 admin center?
PowerShell can expose additional service-plan entries that are not displayed in the portal. Run Get-MgSubscribedSku and inspect the selected SKU's ServicePlans rather than assuming every extra entry is invalid.
How do I find the service-plan IDs for Office 365 E3?
In Microsoft Graph PowerShell, select the Office 365 E3 subscription with Get-MgSubscribedSku -All, then display its ServicePlans property with Select-Object ServicePlanName, ServicePlanId, ProvisioningStatus.
Does DisabledPlans list the services I want to enable?
No. In a Microsoft Graph license assignment, DisabledPlans contains the IDs of plans to turn off. When updating an assignment, include all plans that should remain disabled for that SKU.
What should I check if all plan IDs belong to the SKU?
Check for duplicate entries, plan dependencies, the user's usage location, and available licenses. If the error persists, give Microsoft support the exact PowerShell error, SKU, and plan list.




