mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #5406] [Bug]: Standard "Set the state of the built-in Report button in Outlook" Consistently Failing #2607
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#2607
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 @mpressley-np on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5406
Originally assigned to: @TecharyJames on GitHub.
Required confirmations before submitting
Issue Description
greetings!
i'm seeing a handful of tenants struggling with the "Set the state of the built-in Report button in Outlook" standard.
there's no particular errors in the logbook (only seeing "User Submission policy is already configured" across the board), but it looks like this standard is failing on every tenant we have it deployed to.
here is an example:
only real commonality i've found thus far is that this looks to be failing primarily on tenants with the "strict" preset security policies enabled - is this related, and/or does microsoft's "strict" security preset cause this standard invocation to fail?
many thanks :~)
Environment Type
Sponsored (paying) user
Front End Version
10.0.9
Back End Version
10.0.9
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Feb 19, 2026):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@TecharyJames commented on GitHub (Feb 23, 2026):
I would like to work on this please!
@github-actions[bot] commented on GitHub (Feb 23, 2026):
Great! I assigned you (@TecharyJames) to the issue. Have fun working on it!
@KelvinTegelaar commented on GitHub (Feb 24, 2026):
Fixed in dev.