Has anyone gotten Error 0x80FA

No solutions but, I too am receiving this when trying to add a MacBook Air via Apple Configurator from iPhone. I've run through regular setup assistant and confirmed that the device is not part of another ABM/ASM by using

profiles show -type enrollment

The result is:

Error fetching Device Enrollment configuration: Client is not DEP enabled.

However, when resetting the device and attempting to sideload via Apple Configurator, I too am getting the:

Desc : Provisional Enrollment failed.
Sugg : This device is already enrolled in the Device Enrollment Program.
Domain : DEPCloudConfigErrorDomain
Code : 0x80EF (33007)
...Underlying error:
NSError : Ox6aa833d40
Desc : This device is already enrolled in the Device Enrollment Program.
...

I've tried with shared wifi and with an Ethernet connection. The iPhone with Apple Configurator is running 16.1.1 and laptop is running macOS 12.6.1. Considering upgrading it to Ventura to see if the error persists. If I can get it into ABM then I will roll the unit back to Monterey to complete the validation.

So, interestingly enough, we are the original reseller and sold the device to the initial owner. At the time of purchase, it was assigned to their ABM and served nearly 5 years admirably. The device was recently decommissioned (2018 MBA and everyone is getting M2s!), and we have been charged with refurbishing/reselling/donating/destroying the old devices. We performed a remove through the reseller channel, withdrawling the device from the original purchaser's ABM. I have access to that ABM and can confirm that the device is no longer "owned" by them (as it has been released) and is no longer visible as a linked asset.

Now, since we are part of the chain of custody, I could simply resubmit the device to a different ABM. I still may do that. However, I was going the manual add route mostly for practice and staff training. But I was also doing this in the event that the device is distributed to someone who does not grant us access to their ABM (or who may not yet have one setup). In this case, the new owner may opt to manually sideload and end up with the same error.

I did not yet upgrade to Ventura as I needed to validate a Monterey workflow with the device. Thus, I user-initiated enrolled the device and completed my validation. I am waiting on an external vendor's validation and then I will upgrade to Ventura, wipe, and try again. If that doesn't work, I will work with my sales team and have them reassign to another ABM, bypassing the error.

But, as the profiles command shows, and as viewing the original ABM, this device has been released and should be acting like a retail, unassociated device.

R-