mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #2939] Missing newer Microsoft Subscriptions #1459
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#1459
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @5q-cipp on GitHub (Oct 11, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2939
Description
CIPP does not have handling for newer SKUs within the "Users" report, showing which licenses are assigned to each user. For example, we have a user who has two newer SKUs: Microsoft Teams Enterprise, and Microsoft 365 E5 (no Teams), along with an older Microsoft Power Automate Free license. Viewing the API call results for the user reveals that it sees all three SKUs:
However, in the "Users" list, only the older Power Automate license shows up, the other two are not reflected at all.
Environment data
@github-actions[bot] commented on GitHub (Oct 11, 2024):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@KelvinTegelaar commented on GitHub (Oct 11, 2024):
Not a bug, support issue. If you're a sponsor feel free to contact support.
@5q-cipp commented on GitHub (Oct 14, 2024):
@KelvinTegelaar,
Can you please clarify this statement a bit? It is not displaying the subscription data properly when queried so what designates this as a sponsor issue versus a bug? The subscriptions for any client, sponsor or not would be the same and if the application is not displaying the data correctly, does that not constitute a bug?
Is this something which would be fixed in an upcoming release or no? Otherwise, the validity of the data is not trustworthy?
@KelvinTegelaar commented on GitHub (Oct 14, 2024):
As I said, this isnt a bug but a support issue and has to do with permissions. If you're a sponsor you can contzct the helpdesk and they'll get you setup right.