Support for Intune Device Preparation Policies

My workaround for this right now to avoid the sudden deletions in the Intune device preparation policy of scoped PMPC apps is to create a 2nd dedicated deployment of the app, scoped to the autopilot device group but with "Updated Paused" on the PMPC Cloud Portal side. This lets the app not update itself out of existence, so you can still rely on it to exist in Intune for deployment in Autopilot V2, albeit you must manually go in periodically to update that app that is initially deployed on both the PMPC Cloud & Intune Autopilot Device Prep side.

Not sure at this moment if other deployments that target updates of the same app have any conflict, but minimally, your Autopilot V2 deployments can be more reliable this way. It was untenable for us to periodically peak in to see if an app was deleted from V2 deployment due to the way PMPC handles updates.

Hi All,

It would be great if you could update us on this matter.

We are considering using Device Preparation Policies, and the only workaround we have found is setting the retention policy of the required app to 1, so at least the old package will not be removed after the new package is released. This gives us time to adjust the setting each month for new packages. However, this is manual work, so please consider adding this feature.

We haven't been using DPP, but we are moving our VDI to Windows 365 so support for DPP is going to become critical for us to have. I'm actually shocked this doesn't have more votes yet as it is the eventual way forward for physical PCs too.

I've stopped using PMPC for these apps as it breaks the profile when it removes the apps as the link stays behind on the profile causing it to timeout and fail enrolment, but it's a double edged sword as these are also our critical and/or security related apps.

Hi there — thanks for submitting this idea!

I've shared your feedback with our Product Team so they can review the idea and evaluate whether this is something we can take on in a future release. We’ll assess it alongside other requests, technical considerations, and overall product direction.

We appreciate you taking the time to submit the idea and explain the use case — feedback like this is extremely helpful in shaping future improvements.

Thanks again!

This one is important to anyone using the Autopilot V2 workflows, as we are no longer utilizing Autopilot V1.

As it stands currently, we have to manually override Win32 Application options for the apps we want to deploy to retain all previously created applications when an updated application is published, and have to manually update the assigned application in the V2 deployments periodically.

We are transitioning to Device Prepartion Policies and it is SUCH a better experience than APv1. We will keep AP for zero touch device driven enrollments for shared PCs, but Device Prep will be the way forward for individual workstations for sure. Would love to see support added to PMPC

Went to a Microsoft Ignite session this year where Microsoft mentioned this is the way forward and will eventually replace Autopilot as we currently know it.