starred/CIPP

Fork 0

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

[GH-ISSUE #2527] Error 403 when trying to add a autopilot device #1272

New issue

Closed

opened 2026-03-02 13:42:54 +03:00 by kerem · 5 comments

kerem commented

2026-03-02 13:42:54 +03:00

Owner

Originally created by @v1corp on GitHub (Jun 6, 2024).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2527

Description

I am trying to add an Autopilot device to one of my tenants via Microsoft Product Key ID. I go through the steps of adding it and on Step 4 once I submit it. I receive an error message saying Failed to create autopilot devices. Response status code does not indicate success: 403(Forbidden).

I attempted to conduct some troubleshooting to see why I am experiencing this issue. I attempted to add an autopilot device to a different tenant just to see if this an issue affecting all tenants. I was able to get the device enrolled into a separate tenant using the same Product Key ID method. I then removed it from the test tenant I added it to. Then manually got the HW info and manually added the device through the windows autopilot devices page in the tenant. Which was a success. I have 3 more devices that I need to add to the tenant and all of them are receiving the error message. I have attempted to clear tenant cache, CPV refresh on the tenant in question, and run a tenant access check which was successful, none of which have helped. I am fairly new to CIPP but, I feel like I have exhausted my troubleshooting steps with this.

Environment data

Sponsored Instance
Front End Version: 5.7.1
Back End Version: 5.7.4
Tried Tenant Cache Clear: True
Tried Token Cache Clear: False

Originally created by @v1corp on GitHub (Jun 6, 2024). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/2527 ### Description I am trying to add an Autopilot device to one of my tenants via Microsoft Product Key ID. I go through the steps of adding it and on Step 4 once I submit it. I receive an error message saying Failed to create autopilot devices. Response status code does not indicate success: 403(Forbidden). I attempted to conduct some troubleshooting to see why I am experiencing this issue. I attempted to add an autopilot device to a different tenant just to see if this an issue affecting all tenants. I was able to get the device enrolled into a separate tenant using the same Product Key ID method. I then removed it from the test tenant I added it to. Then manually got the HW info and manually added the device through the windows autopilot devices page in the tenant. Which was a success. I have 3 more devices that I need to add to the tenant and all of them are receiving the error message. I have attempted to clear tenant cache, CPV refresh on the tenant in question, and run a tenant access check which was successful, none of which have helped. I am fairly new to CIPP but, I feel like I have exhausted my troubleshooting steps with this. ![CIPP Autopilot Failure](https://github.com/KelvinTegelaar/CIPP/assets/170590996/572d5756-877f-4973-898c-83ff14f87d5e) ### Environment data ```PowerShell Sponsored Instance Front End Version: 5.7.1 Back End Version: 5.7.4 Tried Tenant Cache Clear: True Tried Token Cache Clear: False ```

kerem

2026-03-02 13:42:54 +03:00

closed this issue
added the
bug

unconfirmed-by-user
labels

kerem commented

2026-03-02 13:42:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 6, 2024):

Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug."

Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

@github-actions[bot] commented on GitHub (Jun 6, 2024): Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://docs.cipp.app/ If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug." Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".

kerem commented

2026-03-02 13:42:55 +03:00

Author

Owner

@v1corp commented on GitHub (Jun 6, 2024):

I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

@v1corp commented on GitHub (Jun 6, 2024): I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.

kerem commented

2026-03-02 13:42:55 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jun 6, 2024):

403 forbidden most likely means that your CIPP service account is not in AdminAgents or the correct GDAP groups. This is a support issue, hit up our helpdesk as you're a sponsor :)

@KelvinTegelaar commented on GitHub (Jun 6, 2024): 403 forbidden most likely means that your CIPP service account is not in AdminAgents or the correct GDAP groups. This is a support issue, hit up our helpdesk as you're a sponsor :)

kerem commented

2026-03-02 13:42:55 +03:00

Author

Owner

@v1corp commented on GitHub (Jun 6, 2024):

When I first signed up, I knew I could reach out to support. What would be the best way of getting in contact with them to open a ticket or get assistance? Thank you!

@v1corp commented on GitHub (Jun 6, 2024): When I first signed up, I knew I could reach out to support. What would be the best way of getting in contact with them to open a ticket or get assistance? Thank you!

kerem commented

2026-03-02 13:42:55 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Jun 6, 2024):

helpdesk@cyberdrain.com is the best method, you'll receive an auto-reply with a ticket number if you ever need to reference that. Another option is Discord #quicksupport channel. https://discord.gg/cyberdrain. :)

@KelvinTegelaar commented on GitHub (Jun 6, 2024): helpdesk@cyberdrain.com is the best method, you'll receive an auto-reply with a ticket number if you ever need to reference that. Another option is Discord #quicksupport channel. https://discord.gg/cyberdrain. :)

kerem referenced this issue

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

[PR #1272] [MERGED] #1271 - Added item clear ImmutableId in users-cippactions #3162

kerem referenced this issue

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

[PR #1276] [MERGED] Dev #3167

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

No description provided.

Rows
Columns