License & Subscription Issues

Find Microsoft 365 and Office 365 AccountSkuId Values for PowerShell

Emma BrownEmma Brown Oct 22, 2026 868 views

Question details

The administrator needs the correct AccountSkuId string values for Microsoft 365 Business Standard and Office 365 E3 to use in PowerShell licensing scripts.

Find Microsoft 365 and Office 365 AccountSkuId Values for PowerShell
Product
Microsoft 365
Device & OS
not provided
Scenario
Automating the assignment or management of Microsoft 365 licenses in bulk using PowerShell scripts.
Observed behavior
The correct execution of license assignment commands requires the exact string identifiers for the specific subscription tiers.
Before you start

Ensure you have the Microsoft Graph PowerShell SDK installed and possess the necessary global or license administrator privileges in your tenant to query and assign licenses.

Solution 1Recommended

Use the Standard AccountSkuId Values for E3 and Business Standard

Apply the precise string IDs assigned by Microsoft for these specific license plans to ensure your PowerShell scripts execute correctly.

Microsoft uses specific internal string names, known as SkuPartNumbers, to identify licenses in PowerShell. Due to legacy naming conventions, some of these strings differ from the current commercial product names.

1
Identify Office 365 E3

For Office 365 E3 licenses, the correct AccountSkuId is ENTERPRISEPACK. Use this string when scripting license assignments for your standard enterprise users.

2
Identify Microsoft 365 Business Standard

For Microsoft 365 Business Standard licenses, the correct AccountSkuId is O365_BUSINESS_PREMIUM. Microsoft retained this older identifier internally to avoid breaking existing scripts.

3
Format the AccountSkuId

When using older MSOnline cmdlets, combine your tenant prefix with the SKU ID using a colon (e.g., yourtenant:ENTERPRISEPACK). For Microsoft Graph cmdlets, you may query by SkuPartNumber.

Use the Standard AccountSkuId Values for E3 and Business Standard
Scripting Tip: Always test your license assignment scripts on a single test user account before deploying them in bulk across your organization.
Free Microsoft Office alternative

Switch to WPS Office for a Streamlined Experience

Managing Microsoft 365 licenses and automation via PowerShell can be complex and time-consuming for growing teams. WPS Office offers a free, lightweight, and incredibly easy-to-use alternative with full compatibility for your essential document, spreadsheet, and presentation needs—no advanced scripting or complex administration required.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install WPS Office: Run the downloaded installer file and follow the simple on-screen instructions to set up the software.
  3. 3. Start Creating: Open WPS Office and immediately begin working with your existing Microsoft Office files without any compatibility issues.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation with zero complex PowerShell licensing administration needed.Familiar user interface that ensures a seamless migration and zero learning curve for your team.Built-in robust PDF editing, formatting, and cloud collaboration tools.
microsoft office alternative - wps office

Frequently Asked Questions

Why is Microsoft 365 Business Standard called O365_BUSINESS_PREMIUM in PowerShell?

Microsoft updated their commercial subscription names in 2020. However, the internal AccountSkuId strings (SkuPartNumbers) used in PowerShell were not changed in order to prevent breaking existing automation scripts created by administrators.

How do I find the AccountSkuId for other Microsoft licenses?

You can use the Get-MgSubscribedSku cmdlet in Microsoft Graph PowerShell. This command returns a list of all subscriptions associated with your tenant, including their SkuPartNumber, which acts as the AccountSkuId.

Do I need to include my tenant name with the AccountSkuId?

Yes, if you are using the older MSOnline PowerShell module, the format requires you to prefix the SkuPartNumber with your tenant name (e.g., contoso:ENTERPRISEPACK). In the newer Microsoft Graph PowerShell modules, you generally reference the SkuId directly or query by SkuPartNumber.