starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #2540] [Feature Request]: Intune Template Standard Revamp #1283

New issue

Closed

opened 2026-03-02 13:42:58 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:42:58 +03:00

Owner

Originally created by @MWG-Logan on GitHub (Jun 11, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2540

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.

Currently, with the Intune Template Standard, you can only assign a batch of policies in one way for the entire batch.
If the UI were adjusted to be a table of entries, where the entries can be dropdowns or select boxes, controlling how each policy is assigned would be much easier and more intuitive.

Along with usability, many policies have a best-practice assignment method (device or user, depending on what it is doing). The current setup does not allow for easily deploying all desired policies in the best-practice configuration for each via standards.
This would also make setting up exclusion groups and breaking out policies for them easier.

Example:

Policy Template	Assigned Group(s)
`CIPP: Enable OneDrive Silent Logon`	`All Users`, `All Devices`	X
`CIPP: Automatic Configuration of Outlook`	`All Users`	X
`MSP: Configure ASR`	`Dynamic Device Group {bla}`	X
Dropdown to add new	Dropdown to add new	+

Group DisplayName -> ID evaluation should probably be stolen from the Conditional Access function and turned into its own helper function, as it would likely be handy here.
Multiple groups should be able to be chosen or entered
Group options for All Devices, All Users, {Custom Group}, and None/Unassigned
Would likely need a decently hefty change to the API function for Intune Templates

PowerShell commands you would normally use to achieve above request

UI / Existing functionality change

Originally created by @MWG-Logan on GitHub (Jun 11, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2540 ### 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. Currently, with the Intune Template Standard, you can only assign a batch of policies in one way for the entire batch. If the UI were adjusted to be a table of entries, where the entries can be dropdowns or select boxes, controlling how each policy is assigned would be much easier and more intuitive. Along with usability, many policies have a best-practice assignment method (device or user, depending on what it is doing). The current setup does not allow for easily deploying *all* desired policies in the best-practice configuration for each via standards. This would also make setting up exclusion groups and breaking out policies for them easier. **Example:** | Policy Template | Assigned Group(s) | | |------------------|----------------------|----------| | `CIPP: Enable OneDrive Silent Logon` | `All Users`, `All Devices` | **X** | | `CIPP: Automatic Configuration of Outlook` | `All Users` | **X** | | `MSP: Configure ASR` | `Dynamic Device Group {bla}` | **X** | | *Dropdown to add new* | *Dropdown to add new* | **+** | * Group DisplayName -> ID evaluation should probably be stolen from the Conditional Access function and turned into its own helper function, as it would likely be handy here. * Multiple groups should be able to be chosen or entered * Group options for `All Devices`, `All Users`, `{Custom Group}`, and `None/Unassigned` * Would likely need a decently hefty change to the API function for Intune Templates ### PowerShell commands you would normally use to achieve above request UI / Existing functionality change

kerem

2026-03-02 13:42:58 +03:00

closed this issue
added the
enhancement

Planned

no-priority
labels

kerem commented

2026-03-02 13:42:59 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 21, 2024):

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@github-actions[bot] commented on GitHub (Jun 21, 2024): This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

kerem commented

2026-03-02 13:42:59 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 5, 2024):

This issue was closed because it has been stalled for 14 days with no activity.

@github-actions[bot] commented on GitHub (Jul 5, 2024): This issue was closed because it has been stalled for 14 days with no activity.

kerem commented

2026-03-02 13:42:59 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Aug 2, 2024):

Implemented in dev

@KelvinTegelaar commented on GitHub (Aug 2, 2024): Implemented in dev

kerem referenced this issue

2026-03-02 13:57:09 +03:00

[PR #1283] [CLOSED] Pull latest #3168

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#1283

No description provided.

Rows
Columns