[GH-ISSUE #4809] [Bug]: Retrieve Intune scripts still causes errors #2244

Closed
opened 2026-03-02 13:50:46 +03:00 by kerem · 3 comments
Owner

Originally created by @jjvandenberg on GitHub (Oct 10, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4809

Required confirmations before submitting

  • I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
  • I have searched existing issues (both open and closed) to avoid duplicates.
  • I am not requesting general support; this is an actual bug report.

Issue Description

https://github.com/KelvinTegelaar/CIPP/issues/4671 is closed, however a new error occurs now

Application is not authorized to perform this operation. Application must have one of the following scopes: DeviceManagementScripts.Read.All, DeviceManagementScripts.ReadWrite.All - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: ba33a77f-39cb-474c-9f12-290ed945483e - Url: https://proxy.msub06.manage.microsoft.com/DeviceFE/StatelessDeviceFEService/deviceManagement/deviceManagementScripts?api-version=5025-05-19

Image

Environment Type

Sponsored (paying) user

Front End Version

8.5.1

Back End Version

8.5.1

Relevant Logs / Stack Trace


Originally created by @jjvandenberg on GitHub (Oct 10, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4809 ### Required confirmations before submitting - [x] **I can reproduce this issue on the latest released versions** of both CIPP and CIPP-API. - [x] **I have searched existing issues** (both open and closed) to avoid duplicates. - [x] I am **not** requesting general support; this is an actual bug report. ### Issue Description https://github.com/KelvinTegelaar/CIPP/issues/4671 is closed, however a new error occurs now Application is not authorized to perform this operation. Application must have one of the following scopes: DeviceManagementScripts.Read.All, DeviceManagementScripts.ReadWrite.All - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: ba33a77f-39cb-474c-9f12-290ed945483e - Url: https://proxy.msub06.manage.microsoft.com/DeviceFE/StatelessDeviceFEService/deviceManagement/deviceManagementScripts?api-version=5025-05-19 <img width="1612" height="395" alt="Image" src="https://github.com/user-attachments/assets/2c70606c-2690-4972-a48e-02adaf402a9a" /> ### Environment Type Sponsored (paying) user ### Front End Version 8.5.1 ### Back End Version 8.5.1 ### Relevant Logs / Stack Trace ```plaintext ```
Author
Owner

@github-actions[bot] commented on GitHub (Oct 10, 2025):

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

<!-- gh-comment-id:3390297701 --> @github-actions[bot] commented on GitHub (Oct 10, 2025): Thank you for reporting a potential bug. If you would like to work on this bug, please comment: > I would like to work on this please! Thank you for helping us maintain the project!
Author
Owner

@github-actions[bot] commented on GitHub (Oct 10, 2025):

Hello,

Thank you for reaching out! This report has been classified as a support request rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support.

Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there.

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

Thank you for your understanding,
The CIPP Team

<!-- gh-comment-id:3390383291 --> @github-actions[bot] commented on GitHub (Oct 10, 2025): Hello, Thank you for reaching out! This report has been classified as a **support request** rather than a bug or feature request. To keep our development process focused, support requests are limited to paying users. This policy allows us to prioritize resources for those actively supporting CIPP, helping us maintain high-quality development and support. Sponsors can contact our helpdesk directly via email for assistance with any issues or questions. For non-sponsor support, please refer to our documentation and community discussions—many questions have been answered there. **Did you get this notification in error?** Reply with a screenshot of your sponsorship payment, and we’ll gladly reopen the request. _Thank you for your understanding,_ **The CIPP Team**
Author
Owner

@jjvandenberg commented on GitHub (Oct 12, 2025):

So this isn't a bug? But if I'd been identified as a paying customer, it would be? Strange line of reasoning.
Besides, our company is a paying member, so the rejection is a bit disappointing and not very encouraging.

<!-- gh-comment-id:3395246316 --> @jjvandenberg commented on GitHub (Oct 12, 2025): So this isn't a bug? But if I'd been identified as a paying customer, it would be? Strange line of reasoning. Besides, our company is a paying member, so the rejection is a bit disappointing and not very encouraging.
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#2244
No description provided.