mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-26 00:36:27 +03:00
[GH-ISSUE #2364] [Feature Request]: Ability to export, view and add Compliance Policies in Intune #1208
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#1208
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 @SGeeves on GitHub (Apr 25, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2364
Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.
For Microsoft Intune, the built in feature for marking devices as compliant, then utilising Conditional Access based on this compliance status is a big one for us for device security and data access for our customers.
We have over 30 customers utilising a pretty standard format, which is a pain to have to dial into each tenant manually and either run a custom PowerShell script/function or add manually each time we want to adjust.
This would be the same ability as the current Intune section in CIPP with the configuration profiles.
We are a sponsor under: FutureITNZ
PowerShell commands you would normally use to achieve above request
No response
@KelvinTegelaar commented on GitHub (Apr 25, 2024):
Hold on there bot, a little bit too fast.
@KelvinTegelaar commented on GitHub (Apr 25, 2024):
This already exists. :)