starred/CIPP

Fork 0

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

[GH-ISSUE #3679] [Feature Request]: Allow auto emailing a list of cleaned up Excel spreadsheet with list of licensed users to selected individuals in the tenancy #1629

New issue

Closed

opened 2026-03-02 13:45:46 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @unifieditgit on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3679

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

We have 10s of clients who require the list of 365 licensed users each month and other who ask for it every quarter. While CIPP has made it easier to get that list, it's still manual and require manual clean-up
All we need is a cleaned up XLSX file with:
Enabled, Display Name, username, Last login and licenses assigned (Excluding free licenses)

Benefits for MSPs

Yes, described in Problem statement already

Value or Importance

Nice to have for functionality but critical for time saving

PowerShell Commands (Optional)

No response

Originally created by @unifieditgit on GitHub (Feb 20, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3679 ### 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 We have 10s of clients who require the list of 365 licensed users each month and other who ask for it every quarter. While CIPP has made it easier to get that list, it's still manual and require manual clean-up All we need is a cleaned up XLSX file with: Enabled, Display Name, username, Last login and licenses assigned (Excluding free licenses) ### Benefits for MSPs Yes, described in Problem statement already ### Value or Importance Nice to have for functionality but critical for time saving ### PowerShell Commands (Optional) _No response_

kerem

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

closed this issue
added the
enhancement

no-priority
labels

kerem commented

2026-03-02 13:45:47 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Feb 24, 2025):

You can use the Graph Explorer for this, or the task scheduler, we however will never email clients directly.

@KelvinTegelaar commented on GitHub (Feb 24, 2025): You can use the Graph Explorer for this, or the task scheduler, we however will never email clients directly.

kerem commented

2026-03-02 13:45:47 +03:00

Author

Owner

@unifieditgit commented on GitHub (Feb 24, 2025):

Hi Kelvin,

Thank you for your response. I understand that feature requests are being rejected quickly without exploring possible options, which can be discouraging for those of us trying to contribute critical ideas.

I reviewed the task scheduler but couldn't determine which command would achieve the desired result. It's understandable if the MSP needs to initiate the schedule rather than CIPP, but not providing any option at all, with the explanation that "CIPP never emails clients directly," seems limiting. There are always multiple ways to achieve a goal. For instance, we could receive the email and create a Power Automate rule to forward it to the client.

Additionally, I noticed there's no option to reopen a feature request when adding comments. This leaves me with the choice of either creating a new feature request or abandoning this important feature that could benefit the community. Unfortunately, it seems that all feature requests I've submitted have been closed abruptly, similar to this one.

There might be alternative methods, such as using Graph Explorer or Task Scheduler, as you suggested. However, without documentation on how to achieve this, we're left in the same position as before the feature request was made.

@unifieditgit commented on GitHub (Feb 24, 2025): Hi Kelvin, Thank you for your response. I understand that feature requests are being rejected quickly without exploring possible options, which can be discouraging for those of us trying to contribute critical ideas. I reviewed the task scheduler but couldn't determine which command would achieve the desired result. It's understandable if the MSP needs to initiate the schedule rather than CIPP, but not providing any option at all, with the explanation that "CIPP never emails clients directly," seems limiting. There are always multiple ways to achieve a goal. For instance, we could receive the email and create a Power Automate rule to forward it to the client. Additionally, I noticed there's no option to reopen a feature request when adding comments. This leaves me with the choice of either creating a new feature request or abandoning this important feature that could benefit the community. Unfortunately, it seems that all feature requests I've submitted have been closed abruptly, similar to this one. There might be alternative methods, such as using Graph Explorer or Task Scheduler, as you suggested. However, without documentation on how to achieve this, we're left in the same position as before the feature request was made.

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#1629

No description provided.

Rows
Columns