mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #125] Feature request: Intune import support multiple policy types #78
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#78
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 @freezscholte on GitHub (Oct 26, 2021).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/125
Describe the solution you'd like
Currently you can only upload administrative templates in JSON form, it would be useful if you could upload multiple policy/setting types. This way setting up a new tenant or adding new policy's to existing tenants would not be restricted to Administrative Templates only.
Describe alternatives you've considered
We currently use this -> https://github.com/nicolonsky/ModernWorkplaceConcierge/wiki
Also, the reason opening this issue is to point out this solution and mayby you can look at it for inspiration how they achieve it and implement this in the CIPP.
Additional context
When we export with the "ModernWorkplaceConcierge" all the data is stored in json files. Furthermore, with my limited coding skill if I look up the code it most certainly looks like they are using GraphAPI to export and import policies.
Anyway, maybe you already have something planned to support multiple policy types in Intune and this information is obsolete. Or some other good reason not to do it...
@KelvinTegelaar commented on GitHub (Oct 26, 2021):
Planned for v1.3
@KelvinTegelaar commented on GitHub (Oct 31, 2021):
Added in Dev