How to Ensure Microsoft Entra Licensing Compliance

  • Post author:
  • Post category:Microsoft Entra
  • Post last modified:
  • Reading time:8 mins read
  • Post published:

The license utilisation blade in Microsoft Entra provides you a glimpse of insight into how many users in your organisation are utilising Microsoft Entra. However, it is a far shot away from being a reliable source of information to help you monitor and maintain license compliance. Announced in February 2024, the license utilisation blade was released in preview, while almost a year and a half later, it is out of preview, and its lack of features is still prevalent.

So, whilst we wait for new developments in the Microsoft world to support this task, we admins must take this into our own hands to ensure we maintain Microsoft Entra’s illustrious licensing requirements. In this blog, I will walk through the complexities and nuances of Entra licensing to support your licensing journey.

Microsoft Entra license compliance in a minefield

License compliance for Microsoft Entra is not simple to manage, nor maintain, unless you operate an extremely rigid environment that doesn’t necessarily cater to the dynamic needs of most users. This is because the Entra licensing model is flexible, almost too flexible, enabling users to benefit from premium features even without a license assigned.

Adding to this mix is Microsoft’s philosophy of “One person, one license”, which essentially means only one Entra ID license is required per employee. For example, if an employee has multiple accounts in the same tenant or across multiple tenants owned by the same organisation, this principle applies. This is highlighted in a Microsoft blog post here, but unfortunately alludes only to Entra ID Governance features.

A good example of where this philosophy applies most often is administrative accounts. A person with a standard account and a separate administrator account only needs one Entra ID premium license between these accounts to leverage the premium features, like PIM for example.

The problem rears itself when you need to limit those capabilities to only users with the required licensing, as different personas within an organisation may have different licensing requirements. Limiting those capabilities could be done with dynamic group-based licensing combined with further nested groups, but that may not cater for the administrative users, or users across tenants. As well as this, a lack of understanding of what ‘benefiting from the service’ really means and also the fact that not all services actually support limiting benefits to specific users plays a huge part, as I have highlighted from the Microsoft 365 licensing terms document below.

Unable to limit to specific users
Unable to limit to specific users

Unfortunately this problem leaves organisations unprepared to tackle a problem Microsoft are so passionate about, which is maintaining license compliance.

Microsoft's lack of tools and documentation

Over a year ago, Microsoft began to support its customers tackle this problem by releasing the License Utilization feature within the Monitoring & Insights section of the Microsoft Entra admin centre, although, as you can see, it’s fairly rudimentary and has remained that way for a while.s

License Utilisation as of June 2025
License Utilisation as of June 2025

Currently it only contains insights into the use of Conditional Access from a P1 perspective and from a P2 perspective with risk-based insights. But what about all of the other features?

So far, in regards to tooling, that’s about all Microsoft have been able to provide us to support maintaining license compliance. Entra Copilot does have a built-in skill that supports querying this data and maybe AI could help deduce usage of other Entra services, but would the output from Copilot be reliable? I for one would still need an alternative source of truth to be convinced.

But it’s not only the tooling that bears the problem; documentation is also fairly slim when it comes to license entitlements with Microsoft Entra. So far, the only other sources of information I trust come from the social media posts of Microsoft employees who work within Microsoft’s Identity divisions… see Alex Simons’ post all the way back in 2020!

https://x.com/Alex_A_Simons/status/1232741945190912000
https://x.com/Alex_A_Simons/status/1232741945190912000

As well as Merill’s post from June 2024:

https://www.linkedin.com/posts/merill_i-todays-blog-post-on-entra-id-licensing-activity-7209407252506558464-xR3z

On a positive note, Microsoft have slowly been updating some references to Entra licensing across tenants, regarding entitlements for Entra P1 and P2 here Configure cross-tenant synchronization – Microsoft Entra ID | Microsoft Learn.

Approaches to maintaining compliance

So the lack of complexity and lack of tools begs the question: How do I practically manage both the compliance and the cost of my Microsoft Entra licensing? Here are some of my thoughts…

Entra P1 for all primary accounts. Maybe it isn’t what you want to hear; however, there are plenty of features of Entra Premium, specifically Entra P1, that all users should benefit from in the name of security, namely, Conditional Access. Once that is established, the remaining features really only become a question of adoption, rather than compliance, but what is a primary account? Well, consider a primary account to be the day-to-day working account of a unique person in your business, likely the first account that was created for them when they started, the one they sign in to each day, the one they email from… You get the point.

So you have your starting point, all users are to be assigned an Entra P1 license or at least have it within their license bundle (Microsoft 365 E3, for example). The next challenge is ensuring that for users with second accounts, their primary is correctly licensed. In this case, it is a matter of distinguishing between a primary user’s second account and a contractor or external party with an administrator account in your environment. This goes back to HR and the user provisioning process… not only should you keep the naming convention of these accounts consistent, you should use extension attributes within the provisioning flow to help you distinguish the account type and purpose. Once you have done this, you can use these extension attributes to create dynamic groups, or even filter with Microsoft Graph, which I go into detail on in this article.

It really does come down to ensuring you have a source of truth for all things access-related (HR system) and then that you take a layered approach using dynamic groups. This way you can ensure that:

  • Account provisioning is accurate with the required attributes.
  • The lifecycle of your accounts is maintained.
  • You can take a dynamic approach to license assignments.
  • You can take a layered approach to assigning P2 licenses where needed.

Of course, in a perfect world, you would have all users also assigned a Microsoft Entra P2 license, but economically, that may not be the most desired solution.s

Microsoft Entra P1 vs P2 feature matrix

Below represents a table highlighting all the features of both the Entra Plan 1 and Plan 2 licenses, including whether you are able to limit the benefit via group and whether the benefit should apply to all users.

Entra ID Plan 1 Able to limit benefit via group?  Should apply to all?
Administrative Units  Yes No
Advanced Security Reports & Alerts No Yes
App Proxy Yes No
Cloud App Discovery No Yes
Conditional Access Yes Yes
Custom Security Attributes Yes No
Dynamic Groups Yes No
Enterprise State Roaming Yes No
Entra ID Connect Health Yes No
External ID Yes No
Microsoft Identity Manager Yes No
Password Protection No Yes
Self-Service Group Management Yes No
SSPR in AD Yes No
Service Level Agreement No Yes
SMS Sign-In Yes No
Terms of Use Yes Yes
Windows Autopilot Yes No
3rd Party MFA Integration Yes No
Standard Risk Signals No Yes
Entra ID Plan 2
Access Reviews Yes No
Entitlement Management (basic) Yes No
Entra ID Protection Yes Yes
MFA Registration Policy Yes Yes
Privileged Identity Management Yes No
Premium Risk Signals No Yes
Risk-Based Conditional Access Yes Yes

Reporting on usage of premium features

The current License Utilization blade uses data which is available only from the reporting API in Microsoft Graph here:

https://graph.microsoft.com/beta/reports/azureADPremiumLicenseInsight

This essentially means that the data is gathered and processed on the back end, which is convenient to start with, but doesn’t give us the full picture, although the page does state that additional features will be added over time.

Entra ID Premium usage
Entra ID Premium usage

As it would be impossible for us to analyse the service user with the tools provided by us, we instead need to complement this information by analysing the assigned user accounts to the supported Microsoft Entra services. While I won’t go through all the available services, here is an example of finding users benefiting from using dynamic groups.

Count of users benefiting from Dynamic groups

Here we have obtained a list of dynamic groups, then extracted a list of members from each group, highlighting the unique values from the total.

$Groups = Get-MgGroup -Filter "groupTypes/any(c:c eq 'DynamicMembership')" -Property "id,displayName"
$allUniqueMembers = @()

foreach ($group in $groups){
    $groupmembers = Get-MgGroupTransitiveMember -GroupId $group.Id -ConsistencyLevel Eventual 
    $allUniqueMembers += $groupmembers.Id
}

$uniqueMembers = $allUniqueMembers | Select-Object -Unique
$totalMembers = $uniqueMembers.Count

Write-Host "`nTotal unique members across all dynamic groups: $totalMembers" -ForegroundColor Green

Summary

Microsoft Entra license compliance remains a significant challenge for administrators due to the platform’s overly flexible licensing model, which allows users to benefit from premium features without proper license assignment, whilst Microsoft’s “One person, one license” philosophy permits employees with multiple accounts to share a single license. The current Microsoft tooling is somewhat inadequate, with the License Utilisation blade offering only basic Conditional Access insights and comprehensive documentation on license entitlements is practically non-existent. To maintain license compliance, I suggest getting your user provisioning in order, then tackling each secondary, service or other account which may be benefiting from the core Entra P1 and Entra P2 services as a starting point.

Daniel Bradley

Daniel Bradley is a UK-based technical architect and Microsoft MVP in Security. He specialises in Microsoft Entra, Intune, and Microsoft Graph PowerShell and is the author of Microsoft Graph PowerShell for Administrators. He writes and edits Our Cloud Network using experience gained from working with Microsoft cloud environments.

This Post Has One Comment

  1. Biswajit Biswas

    I used that beta API & got the below output, Do I have 28 P2 License?

    EntitledP1LicenseCount : 0
    EntitledP2LicenseCount : 28
    EntitledTotalLicenseCount : 28
    P1_ConditionalAccessUsers : 9
    P1_ConditionalAccessGuestUsers : 1
    P2_RiskBasedConditionalAccessUsers : 7
    P2_RiskBasedConditionalAccessGuests : 1

Leave a Reply