starred/CIPP

Fork 0

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

[GH-ISSUE #5400] [Feature Request]: Intune Application Deployment Templates #2599

New issue

Open

opened 2026-03-02 13:53:39 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 13:53:39 +03:00

Owner

Originally created by @Lowell-Syncrety on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5400

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

CIPP currently allows Intune applications to be deployed manually to one or more tenants, which works well for one‑off or ad‑hoc deployments. However, there is no way to define a reusable Intune application deployment template that can be applied consistently to newly onboarded tenants or reused as part of an ongoing standard.

For MSPs, application deployment (e.g. Company Portal, Microsoft To Do, Edge, core LOB apps) is a repeatable baseline task, not a one‑time event. Today, each new tenant requires manually redeploying the same applications again, even though the configuration and assignments are identical.
This creates unnecessary manual effort and makes application deployment inconsistent compared to other CIPP objects that already support templating and standards (groups, Conditional Access, Intune policies).

Benefits for MSPs

Reduces repetitive manual work during tenant onboarding
Ensures consistent application deployment across all managed tenants
Aligns app deployment with CIPP’s existing standards‑based approach
Improves scalability as the number of managed tenants grows
Makes application deployment predictable, auditable, and repeatable

Instead of redeploying apps tenant by tenant, MSPs could define an app deployment once and reuse it across their entire customer base.

Value or Importance

Adding Intune Application Deployment Templates would complete the Intune templating story in CIPP by covering both policies and applications, which are equally foundational to tenant standards.
This capability would:

Fit naturally into CIPP’s existing template and onboarding architecture

Improve day‑1 tenant onboarding efficiency
Bring application deployment in line with how policies and standards are already handled

Future Enhancement (Optional)
As a natural extension, application deployment templates could later (or even in v1) be grouped similarly to CIPP Standards, allowing MSPs to apply multiple application templates with a single action (e.g. a “Core Apps” or “Baseline Apps” standard), rather than deploying each app template individually.

PowerShell Commands (Optional)

No response

Originally created by @Lowell-Syncrety on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/5400 ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement CIPP currently allows Intune applications to be deployed manually to one or more tenants, which works well for one‑off or ad‑hoc deployments. However, there is no way to define a reusable Intune application deployment template that can be applied consistently to newly onboarded tenants or reused as part of an ongoing standard. For MSPs, application deployment (e.g. Company Portal, Microsoft To Do, Edge, core LOB apps) is a repeatable baseline task, not a one‑time event. Today, each new tenant requires manually redeploying the same applications again, even though the configuration and assignments are identical. This creates unnecessary manual effort and makes application deployment inconsistent compared to other CIPP objects that already support templating and standards (groups, Conditional Access, Intune policies). ### Benefits for MSPs - Reduces repetitive manual work during tenant onboarding - Ensures consistent application deployment across all managed tenants - Aligns app deployment with CIPP’s existing standards‑based approach - Improves scalability as the number of managed tenants grows - Makes application deployment predictable, auditable, and repeatable Instead of redeploying apps tenant by tenant, MSPs could define an app deployment once and reuse it across their entire customer base. ### Value or Importance Adding Intune Application Deployment Templates would complete the Intune templating story in CIPP by covering both policies and applications, which are equally foundational to tenant standards. This capability would: Fit naturally into CIPP’s existing template and onboarding architecture - Improve day‑1 tenant onboarding efficiency - Bring application deployment in line with how policies and standards are already handled **Future Enhancement (Optional)** As a natural extension, application deployment templates could later (or even in v1) be grouped similarly to CIPP Standards, allowing MSPs to apply multiple application templates with a single action (e.g. a “Core Apps” or “Baseline Apps” standard), rather than deploying each app template individually. ### PowerShell Commands (Optional) _No response_

kerem added the

labels

2026-03-02 13:53:39 +03:00

kerem commented

2026-03-02 13:53:40 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 28, 2026):

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 (Feb 28, 2026): 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.

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

No description provided.

Rows
Columns