mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #5032] [Feature Request]: Make checks from openintunebaselines #2390
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#2390
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 @kontorvarehuset on GitHub (Dec 1, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5032
Please confirm:
Problem Statement
We have problems with opneintunebaselines. They work to deploy the tempaltes in both standard and drift templates, but the check will indiciate drift even when they are applied correctly. The error we see most often is these:
f.ex in the baseline: MacOS - OIB - Compliance - U - Device Health - v1.0
the checkerror: {"MatchFailed":true,"Difference":"This policy does not exist in Intune."}
Another example:
policy: Win - OIB - Compliance - U - Device Health - v3.1
error: {"Property":"wslDistributions","ExpectedValue":"","ReceivedValue":[]}
Benefits for MSPs
Our techincian will always check drift, and when they see this checks go into error they will use time to check it out.
Would be nice to get these two errros check out fine.
Value or Importance
It will save time for many technicians. by not checking known erorrs, we can get "fatigue" of th error and miss real errors.
PowerShell Commands (Optional)
No response
@frankemann commented on GitHub (Dec 3, 2025):
Got an email from the support team that this will be fixed in the next release!