[GH-ISSUE #3677] [Feature Request]: Autopilot Device Preparation policies

kerem commented

2026-03-02 13:45:44 +03:00

Owner

Originally created by @IP-Jordan on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3677

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

While CIPP already allows us to deploy Autopilot profiles, there’s currently no way to configure and deploy Windows Autopilot Device Preparation Policies (formerly White-Glove) within the platform. For MSPs managing multiple customers, this is a missing piece that could significantly improve efficiency in large-scale device rollouts.

Autopilot Device Preparation enables pre-provisioning, reducing setup time for end users by applying policies before the device is delivered. Right now, we have to manually configure these policies in Intune and assign devices individually, adding unnecessary overhead.
https://learn.microsoft.com/en-us/autopilot/device-preparation/overview

Benefits for MSPs

By integrating Autopilot Device Preparation Policies into CIPP, we could:

Automate pre-deployment profile creation, modification, and assignment to enrolled devices.
Streamline the import process for devices purchased from manufacturers (Dell, Lenovo, etc.) by automatically adding them to the correct Azure security groups.
This would reduce friction in device setup, improve consistency, and cut down the time MSPs spend on manual configurations.

This would enhance scalability and managing clients and device deployments at scale. Reduce MSPs per device setup time and make it easier to handle larger deployments.

Value or Importance

Streamlines Autopilot pre-provisioning, reducing manual effort and ensuring consistent, secure device deployments at scale

PowerShell Commands (Optional)

No response

Originally created by @IP-Jordan on GitHub (Feb 20, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3677 ### 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 While CIPP already allows us to deploy Autopilot profiles, there’s currently no way to configure and deploy Windows Autopilot Device Preparation Policies (formerly White-Glove) within the platform. For MSPs managing multiple customers, this is a missing piece that could significantly improve efficiency in large-scale device rollouts. Autopilot Device Preparation enables pre-provisioning, reducing setup time for end users by applying policies before the device is delivered. Right now, we have to manually configure these policies in Intune and assign devices individually, adding unnecessary overhead. https://learn.microsoft.com/en-us/autopilot/device-preparation/overview ### Benefits for MSPs By integrating Autopilot Device Preparation Policies into CIPP, we could: - Automate pre-deployment profile creation, modification, and assignment to enrolled devices. - Streamline the import process for devices purchased from manufacturers (Dell, Lenovo, etc.) by automatically adding them to the correct Azure security groups. - This would reduce friction in device setup, improve consistency, and cut down the time MSPs spend on manual configurations. This would enhance scalability and managing clients and device deployments at scale. Reduce MSPs per device setup time and make it easier to handle larger deployments. ### Value or Importance Streamlines Autopilot pre-provisioning, reducing manual effort and ensuring consistent, secure device deployments at scale ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:45:44 +03:00

closed this issue
added the
enhancement

no-priority

no-activity

roadmap
labels

kerem commented

2026-03-02 13:45:45 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 2, 2025):

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 (Mar 2, 2025): 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:45:45 +03:00

Author

Owner

@JRivett-ITSG commented on GitHub (Mar 10, 2025):

We are interested in this as well. We would consider this a high priority request.

@JRivett-ITSG commented on GitHub (Mar 10, 2025): We are interested in this as well. We would consider this a high priority request.

kerem commented

2026-03-02 13:45:45 +03:00

Author

Owner

@JRivett-ITSG commented on GitHub (Mar 14, 2025):

I would like to upgrade the priority on this request.
Sponsorship via org:
https://github.com/itsupportguys

@JRivett-ITSG commented on GitHub (Mar 14, 2025): I would like to upgrade the priority on this request. Sponsorship via org: https://github.com/itsupportguys

kerem commented

2026-03-02 13:45:46 +03:00

Author

Owner

@m365mgmtprd commented on GitHub (Mar 19, 2025):

We are also interested in this.

@m365mgmtprd commented on GitHub (Mar 19, 2025): We are also interested in this.

kerem commented

2026-03-02 13:45:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 29, 2025):

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 (Mar 29, 2025): 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:45:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 20, 2025):

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

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

kerem commented

2026-03-02 13:45:46 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 27, 2025):

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

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

kerem referenced this issue

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

[PR #1627] [MERGED] Pull - Automatic updates #3327

kerem referenced this issue

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

[PR #1640] [MERGED] Dev to release #3336