[GH-ISSUE #1357] CIPP Application Approval Failing for Tenants #746

Closed
opened 2026-03-02 12:44:51 +03:00 by kerem · 2 comments
Owner

Originally created by @REDDGit on GitHub (Feb 6, 2023).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1357

Description

Working through GDAP migration.
Approving the CIPP-SAM application in tenants has stopped working after v3 with new permissions.

When using the Application Approval wizard, It would result in a error "AADSTS900144: The request body must contain the following parameter: 'scope'."

To get around this I was able to remove the WindowsDefenderATP ID's from the manifest. Once I have done this I was able to use the generated link. Also having to remove the /v2.0 from the link.

Environment data

Azure
Originally created by @REDDGit on GitHub (Feb 6, 2023). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1357 ### Description Working through GDAP migration. Approving the CIPP-SAM application in tenants has stopped working after v3 with new permissions. When using the Application Approval wizard, It would result in a error "AADSTS900144: The request body must contain the following parameter: 'scope'." To get around this I was able to remove the WindowsDefenderATP ID's from the manifest. Once I have done this I was able to use the generated link. Also having to remove the /v2.0 from the link. ### Environment data ```PowerShell Azure ```
kerem 2026-03-02 12:44:51 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 6, 2023):

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://kelvintegelaar.github.io/CIPP
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!".

<!-- gh-comment-id:1418528576 --> @github-actions[bot] commented on GitHub (Feb 6, 2023): 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://kelvintegelaar.github.io/CIPP 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!".
Author
Owner

@re-geeks commented on GitHub (Feb 17, 2023):

Description

Working through GDAP migration. Approving the CIPP-SAM application in tenants has stopped working after v3 with new permissions.

When using the Application Approval wizard, It would result in a error "AADSTS900144: The request body must contain the following parameter: 'scope'."

To get around this I was able to remove the WindowsDefenderATP ID's from the manifest. Once I have done this I was able to use the generated link. Also having to remove the /v2.0 from the link.

Environment data

Azure

Same issue

<!-- gh-comment-id:1435019859 --> @re-geeks commented on GitHub (Feb 17, 2023): > ### Description > Working through GDAP migration. Approving the CIPP-SAM application in tenants has stopped working after v3 with new permissions. > > When using the Application Approval wizard, It would result in a error "AADSTS900144: The request body must contain the following parameter: 'scope'." > > To get around this I was able to remove the WindowsDefenderATP ID's from the manifest. Once I have done this I was able to use the generated link. Also having to remove the /v2.0 from the link. > > ### Environment data > ```powershell > Azure > ``` Same issue
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#746
No description provided.