mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3882] [Bug]: Autopilot settings incorrect in CIPP standard #1730
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#1730
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 @mruiterHU on GitHub (Mar 27, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3882
Originally assigned to: @rvdwegen on GitHub.
Required confirmations before submitting
Issue Description
When creating an Autopilot profile via a freshly created CIPP standard, the resulting profile in Intune differs from one created manually using the Autopilot profile form in Intune > Autopilot. The inconsistency matches the behavior described in issue #3745. Although this was marked as fixed, the issue still persists in version 7.4.1.
Also on the manual form, when having "Assign to all devices" enabled, the profile created inside intune is not assigned to anything.
Reproduction Steps
Expected Behavior
The Autopilot profile created via a CIPP standard should be functionally and structurally identical to a profile created manually via the form in Intune > autopilot.
Actual Behavior
The profiles created via CIPP standard differ from those created manually.
Settings inside CIPP:
Created profiles in Intune:
sponsering via: https://github.com/hypecipp
Environment Type
Sponsored (paying) user
Front End Version
7.4.1
Back End Version
7.4.1
Relevant Logs / Stack Trace
@github-actions[bot] commented on GitHub (Mar 27, 2025):
Thank you for reporting a potential bug. If you would like to work on this bug, please comment:
Thank you for helping us maintain the project!
@github-actions[bot] commented on GitHub (Apr 6, 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.
@HappyEarthDay commented on GitHub (Apr 6, 2025):
Thank you for submitting this. I also experienced this bug this evening and can confirm it is a real bug. It creates the policy, but does not assign to All Devices like it used to.
In addition to the Autopilot profile not being assigned to all devices, I found the following two fields should have input validation:
These two fields don't accept any special characters in the Intune portal, so when I had any special characters in either feild, deployment would fail, and the message in the logbook was as follows:
Failed to create Autopilot profile: Failed to add profile for REDACTEDDOMAIN.org: { "_version": 3, "Message": "An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: fdfc4b2-REDACTED-9eac813f - Url: https://fef.msua08.manage.microsoft.com/DeviceEnrollmentFE/StatelessDeviceEnrollmentFEService/deviceManagement/windowsAutopilotDeploymentProfiles?api-version=5024-09-28", "CustomApiErrorPhrase": "", "RetryAfter": null, "ErrorSourceService": "", "HttpHeaders": "{}" }@rvdwegen commented on GitHub (Apr 10, 2025):
Fixed in dev. There were a few casing issues and Microsoft has started using a new container property for a few of the settings so I updated that too.
I will also have a look at the issue @HappyEarthDay mentioned but that will likely not be in the next release.
@MarkFinGarde commented on GitHub (Apr 14, 2025):
As a test, I deployed an Autopilot profile directly from CIPP (not using a standard). Then, I applied the exact same settings to the same tenant using a standard.
The only difference I’m seeing so far is under the Out-of-box Experience (OOBE):
Using Standard: Deployment mode = User-Driven
From CIPP (not using a standard): Deployment mode = Self-Deploying
I’m still working through a few additional tests.
Front/Backend are on 7.5.0
@mruiterHU commented on GitHub (Apr 23, 2025):
@rvdwegen Just tested the standard Autopilot profile, it's almost working as expected. All settings are applied correctly, except for the Deployment mode. It remains set to User-Driven regardless of how the toggle is configured, just as @MarkFinGarde described.
Is this still on the roadmap to be fixed, or should I create a new bug report?
@mruiterHU commented on GitHub (Apr 23, 2025):
Did some digging, could this have something to do with it?
When i look at the standard in the API should $settings.DeploymentMode not be $settings.SelfDeployingMode? See the response from "listStandardTemplates", because if i read it correctly DeploymentMode will always be false at the moment so User-Driven.
https://github.com/KelvinTegelaar/CIPP-API/blob/master/Modules/CIPPCore/Public/Standards/Invoke-CIPPStandardAutopilotProfile.ps1