Documentation for recently released licensing plans

Question

Hello,

There is a bunch of licensing plans missing from the following documentation list (https://learn.microsoft.com/en-us/entra/identity/users/licensing-service-plan-reference), and those licensing plans have been available for quite sometime already.
Here is "String ID" for some of them:

BUSINESS_BASIC_AND_COPILOT_FOR_BUSINESS

BUSINESS_PREMIUM_EEA_NO_TEAMS_AND_COPILOT_FOR_BUSINESS

BUSINESS_PREMIUM_NO_TEAMS_AND_COPILOT_FOR_BUSINESS

BUSINESS_STANDARD_AND_COPILOT_FOR_BUSINESS

BUSINESS_STANDARD_NO_TEAMS_AND_COPILOT_FOR_BUSINESS

M365_G5_AND_M365_COPILOT_GCC

MICROSOFT_365_E7_NO_TEAMS_EEA

MICROSOFT_365_E7_NOPSTNCONF

MICROSOFT_365_E7_WITHOUT_COPILOT

MICROSOFT_TEAMS_ESSENTIAL_WITH_PHONE

Office_365_E1_Plus_(no_Teams)

SPE_E3_HIDDEN_OFFER

Microsoft_365_A3_Suite_features_for_student

Those are just the most important ones, the actual list is much longer.

The questions are:
Are there any timelines for the update of the page with info on these licenses?
Are there any other source in which GUIDs or Service Plans included in licenses can be found? (outside of calling PowerShell commands, which is obviously not applicable in this case)

Thanks in advance

Answer 1

Hi,

I reviewed the current Microsoft Learn article (Product names and service plan identifiers for licensing) and can confirm that several newer SKUs, including Copilot bundles, EEA-specific offers, and some education or hidden offers, do not currently appear in the published reference list. This documentation is updated periodically rather than in real time, and the article is only accurate as of its last published update (March 17, 2025). At this time, Microsoft has not published any timeline or ETA for when additional SKUs will be added to the documentation.

Regarding your second question, there is currently no alternative Microsoft-maintained public catalog that is more comprehensive than the licensing reference page. Available options include:

• Microsoft Graph (subscribedSku): This is the authoritative source for SKU IDs, SKU part numbers, and included service plans available within a tenant. However, it requires access to a tenant and is therefore similar in concept to using PowerShell.
• The downloadable CSV provided from the Learn article, which contains the same licensing reference data in a more consumable format.
• The Microsoft Learn GitHub repository, where the source content for the article is maintained and where updates may become visible as documentation changes are published.

Based on the examples you provided, the absence of those SKUs from the documentation appears to be a documentation lag rather than an indication that the licenses are invalid or unsupported.

For more information, please refer to the following link:

• https://github.com/MicrosoftDocs/entra-docs/blob/main/docs/identity/users/licensing-service-plan-reference.md
• View Microsoft 365 licenses and services with PowerShell

As an Independent Advisor, I don't have the ability to modify Microsoft documentation or directly escalate product-related issues. However, I encourage you to submit your feedback through the Microsoft 365 Feedback Hub.Feedback submitted through this channel is reviewed by the relevant Microsoft product teams and is the most effective way to raise awareness of documentation gaps, request updates, and influence future improvements. Once you've submitted your feedback, feel free to share the link here in the comments. I’ll be happy to upvote it to help bring more visibility.   

Additionally, since many other users have expressed similar concerns but may not know where to submit feedback, if my response has helped you better understand the situation and guided you toward a possible next step, please mark it as "Yes". Your action will help pin this post to the top, making it easier for others in the community who are experiencing the same issue to find your feedback and support it.   

Thank you again for your time and for raising this important usability concern. If you have any further questions or need additional assistance, please don’t hesitate to reach out. 

I look forward to your thoughts on this. 

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.