starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #3930] [Feature Request]: Licensed User Count ALL TENANTS #1765

New issue

Closed

opened 2026-03-02 13:46:55 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:46:55 +03:00

Owner

Originally created by @FresnoGeek on GitHub (Apr 4, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3930

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

There is a License report for All Tenants and a User Report, which includes licenses, for each individual tenant. We are trying to find the metric of licensed users across all tenants. Just simply the count of licensed users. Not the count of licenses or of inactive users with licenses. Some users have multiple licenses. These should be combined as one user in the list.

Benefits for MSPs

Our RMM counts devices. Our PSA counts contacts. But nothing counts licensed users.

Value or Importance

Ultimately, we serve people. Not computers. We are trying to find this metric to report on as a Company Goal for the next year. Our hope is to support XXXX "licensed" people by Oct 31 and over XXXXX licensed people by 2032!

PowerShell Commands (Optional)

Requires the Microsoft.Graph.Users module

Install-Module Microsoft.Graph.Users

Connect to Microsoft Graph

Connect-MgGraph -Scopes "User.Read.All"

Get all licensed users

$LicensedUsers = Get-MgUser -Filter "assignedLicenses/`$count ne 0" -All

Count the licensed users

$LicensedUsersCount = $LicensedUsers.Count

Output the count

Write-Host "Total Licensed Users: $LicensedUsersCount"

Optionally, if you want to also see the details of each licensed user:

$LicensedUsers | Select-Object DisplayName, UserPrincipalName, AssignedLicenses

Or, to export to a CSV:

$LicensedUsers | Select-Object DisplayName, UserPrincipalName, AssignedLicenses | Export-Csv -Path "C:\LicensedUsers.csv" -NoTypeInformation

Disconnect from Microsoft Graph

Disconnect-MgGraph

Originally created by @FresnoGeek on GitHub (Apr 4, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3930 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement There is a License report for All Tenants and a User Report, which includes licenses, for each individual tenant. We are trying to find the metric of licensed users across all tenants. Just simply the count of licensed users. Not the count of licenses or of inactive users with licenses. Some users have multiple licenses. These should be combined as one user in the list. ### Benefits for MSPs Our RMM counts devices. Our PSA counts contacts. But nothing counts licensed users. ### Value or Importance Ultimately, we serve people. Not computers. We are trying to find this metric to report on as a Company Goal for the next year. Our hope is to support XXXX "licensed" people by Oct 31 and over XXXXX licensed people by 2032! ### PowerShell Commands (Optional) # Requires the Microsoft.Graph.Users module # Install-Module Microsoft.Graph.Users # Connect to Microsoft Graph Connect-MgGraph -Scopes "User.Read.All" # Get all licensed users $LicensedUsers = Get-MgUser -Filter "assignedLicenses/`$count ne 0" -All # Count the licensed users $LicensedUsersCount = $LicensedUsers.Count # Output the count Write-Host "Total Licensed Users: $LicensedUsersCount" # Optionally, if you want to also see the details of each licensed user: # $LicensedUsers | Select-Object DisplayName, UserPrincipalName, AssignedLicenses # Or, to export to a CSV: # $LicensedUsers | Select-Object DisplayName, UserPrincipalName, AssignedLicenses | Export-Csv -Path "C:\LicensedUsers.csv" -NoTypeInformation # Disconnect from Microsoft Graph Disconnect-MgGraph

kerem

2026-03-02 13:46:55 +03:00

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 13:46:56 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 4, 2025):

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

@github-actions[bot] commented on GitHub (Apr 4, 2025): Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, **feature requests are limited to paying users**. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "**I’d like to work on this!**" to assign the issue to yourself. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. _Thank you for understanding,_ **The CIPP Team**

kerem commented

2026-03-02 13:46:56 +03:00

Author

Owner

@FresnoGeek commented on GitHub (Apr 4, 2025):

I'm pretty sure we are a paying customer.

[cid:522921fe-506b-401c-83e8-9d9c89a9cf64]
Jacob Rylander, Network Support Specialist/Team Lead
Kotman Technology
[Kotman Technology]
700 Van Ness Ave Suite 110
Fresno, CA 93721
559-347-8200tel:559-347-8200

Email: @.@.>

From: github-actions[bot] @.>
Sent: Friday, April 4, 2025 10:09 AM
To: KelvinTegelaar/CIPP @.>
Cc: Jacob Rylander @.>; Author @.>
Subject: Re: [KelvinTegelaar/CIPP] [Feature Request]: Licensed User Count ALL TENANTS (Issue #3930)

Hello,

Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

—
Reply to this email directly, view it on GitHubhttps://github.com/KelvinTegelaar/CIPP/issues/3930#issuecomment-2779314623, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFR5RKWQGGKWBCIX2B7MWZD2X24E3AVCNFSM6AAAAAB2PFNEFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZGMYTINRSGM.
You are receiving this because you authored the thread.Message ID: @.***>

[github-actions[bot]]github-actions[bot] left a comment (KelvinTegelaar/CIPP#3930)https://github.com/KelvinTegelaar/CIPP/issues/3930#issuecomment-2779314623

Hello,

While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue.

Thank you for understanding,
The CIPP Team

@FresnoGeek commented on GitHub (Apr 4, 2025): I'm pretty sure we are a paying customer. [cid:522921fe-506b-401c-83e8-9d9c89a9cf64] Jacob Rylander, Network Support Specialist/Team Lead Kotman Technology [Kotman Technology] 700 Van Ness Ave Suite 110 Fresno, CA 93721 559-347-8200<tel:559-347-8200> Email: ***@***.******@***.***> ________________________________ From: github-actions[bot] ***@***.***> Sent: Friday, April 4, 2025 10:09 AM To: KelvinTegelaar/CIPP ***@***.***> Cc: Jacob Rylander ***@***.***>; Author ***@***.***> Subject: Re: [KelvinTegelaar/CIPP] [Feature Request]: Licensed User Count ALL TENANTS (Issue #3930) Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself. Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. Thank you for understanding, The CIPP Team — Reply to this email directly, view it on GitHub<https://github.com/KelvinTegelaar/CIPP/issues/3930#issuecomment-2779314623>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFR5RKWQGGKWBCIX2B7MWZD2X24E3AVCNFSM6AAAAAB2PFNEFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZGMYTINRSGM>. You are receiving this because you authored the thread.Message ID: ***@***.***> [github-actions[bot]]github-actions[bot] left a comment (KelvinTegelaar/CIPP#3930)<https://github.com/KelvinTegelaar/CIPP/issues/3930#issuecomment-2779314623> Hello, Thank you for your interest in improving CIPP! To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritize improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support. When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP. While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself. Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we’ll reopen the issue. Thank you for understanding, The CIPP Team — Reply to this email directly, view it on GitHub<https://github.com/KelvinTegelaar/CIPP/issues/3930#issuecomment-2779314623>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFR5RKWQGGKWBCIX2B7MWZD2X24E3AVCNFSM6AAAAAB2PFNEFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZZGMYTINRSGM>. You are receiving this because you authored the thread.Message ID: ***@***.***>

kerem commented

2026-03-02 13:46:56 +03:00

Author

Owner

@kris6673 commented on GitHub (Apr 4, 2025):

I think this might already be possible through the Graph Explorer

@kris6673 commented on GitHub (Apr 4, 2025): I think this might already be possible through the Graph Explorer

kerem referenced this issue

2026-03-02 13:58:11 +03:00

[PR #1765] [MERGED] Dev to release #3403

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#1765

No description provided.

Rows
Columns