[GH-ISSUE #725] FEATURE REQUEST: Display SKU friendly License name in BPA report #369

Closed
opened 2026-03-02 12:41:41 +03:00 by kerem · 7 comments
Owner

Originally created by @mirceamitu on GitHub (Feb 5, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/725

Originally assigned to: @homotechsual on GitHub.

Is your feature request related to a problem? Please describe.
BPA Report displays the unused SKUs names as provided by M365 API (i.e O365_BUSINESS_ESSENTIALS, ATP_ENTERPRISE) instead of the friendly name as displayed in Users page (MICROSOFT 365 BUSINESS STANDARD, Microsoft Defender for Office 365 (Plan 1) )

Describe the solution you'd like
Display the license names in a consistent manner on all pages, using the official public name (as displayed on Identity / Users page),

image

instead of internal SKU name (as shown in BPA page)

image

Originally created by @mirceamitu on GitHub (Feb 5, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/725 Originally assigned to: @homotechsual on GitHub. **Is your feature request related to a problem? Please describe.** BPA Report displays the unused SKUs names as provided by M365 API (i.e O365_BUSINESS_ESSENTIALS, ATP_ENTERPRISE) instead of the friendly name as displayed in Users page (MICROSOFT 365 BUSINESS STANDARD, Microsoft Defender for Office 365 (Plan 1) ) **Describe the solution you'd like** Display the license names in a consistent manner on all pages, using the official public name (as displayed on Identity / Users page), ![image](https://user-images.githubusercontent.com/7716697/152652781-01dd0c62-2ab8-4859-ada4-96d56b18a3bc.png) instead of internal SKU name (as shown in BPA page) ![image](https://user-images.githubusercontent.com/7716697/152652766-d0c426fe-075a-4982-ab41-ce4863a352dc.png)
kerem 2026-03-02 12:41:41 +03:00
Author
Owner

@ROI-Admin-User commented on GitHub (Feb 7, 2022):

I think we raised this same request previously, and someone replied that it was already planned for the migration to react.

<!-- gh-comment-id:1032037167 --> @ROI-Admin-User commented on GitHub (Feb 7, 2022): I think we raised this same request previously, and someone replied that it was already planned for the migration to react.
Author
Owner

@homotechsual commented on GitHub (Feb 8, 2022):

It might have gotten lost.

<!-- gh-comment-id:1033130359 --> @homotechsual commented on GitHub (Feb 8, 2022): It might have gotten lost.
Author
Owner

@homotechsual commented on GitHub (Feb 8, 2022):

I would like to work on this please!

<!-- gh-comment-id:1033130455 --> @homotechsual commented on GitHub (Feb 8, 2022): I would like to work on this please!
Author
Owner

@github-actions[bot] commented on GitHub (Feb 8, 2022):

Great! I assigned you (@homotechsual) to the issue. Have fun working on it!

<!-- gh-comment-id:1033130579 --> @github-actions[bot] commented on GitHub (Feb 8, 2022): Great! I assigned you (@homotechsual) to the issue. Have fun working on it!
Author
Owner

@github-actions[bot] commented on GitHub (Feb 18, 2022):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.

<!-- gh-comment-id:1043723818 --> @github-actions[bot] commented on GitHub (Feb 18, 2022): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://cipp.app/GettingStarted/Contributions/ . Please notify the team if you are working on this yourself.
Author
Owner

@ROI-Admin-User commented on GitHub (Feb 18, 2022):

I don't know if my comment counts as activity, but I'm going to throw it out into the ether anyway to hopefully keep this feature request alive...

<!-- gh-comment-id:1045163629 --> @ROI-Admin-User commented on GitHub (Feb 18, 2022): I don't know if my comment counts as activity, but I'm going to throw it out into the ether anyway to hopefully keep this feature request alive...
Author
Owner

@gavsto commented on GitHub (Feb 25, 2022):

@ROI-Admin-User You'll be pleased to hear this is now in Dev and should be in the next release! Thank you for the request.

<!-- gh-comment-id:1051180593 --> @gavsto commented on GitHub (Feb 25, 2022): @ROI-Admin-User You'll be pleased to hear this is now in Dev and should be in the next release! Thank you for the request.
Sign in to join this conversation.
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#369
No description provided.