mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 08:16:01 +03:00
[GH-ISSUE #3891] [Feature Request]: Allow Group assignemnt in Autopilot profiles #1735
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#1735
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 @ndit-dev on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/3891
Please confirm:
Problem Statement
When setting up Autopilot profiles through a standard or Intune > Autopilot > Profiles. The only assignment option available is to assign or not assign it to all devices.
It would be very beneficial to allow for both group assignment and group exclusions in the same manner as Intune Templates.
Benefits for MSPs
When multiple Autopilot Profiles is needed for a tenant, it has to be handled through group assignment.
Use cases:
Value or Importance
There is no way to do this automatically in CIPP today, you have to do it per tenant through admin panel or script
PowerShell Commands (Optional)
No response
@OfficialEsco commented on GitHub (Mar 31, 2025):
To add to this feature request, it would be awesome if we could deploy multiple autopilot profiles just like Intune templates
@HappyEarthDay commented on GitHub (Apr 6, 2025):
I would also love this feature!
@m365mgmtprd commented on GitHub (Apr 11, 2025):
Yes, this feature would be great!
@github-actions[bot] commented on GitHub (Apr 24, 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 (Oct 9, 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 (Oct 14, 2025):
This issue was closed because it has been stalled for 14 days with no activity.
@github-actions[bot] commented on GitHub (Oct 19, 2025):
This issue was closed because it has been stalled for 14 days with no activity.