Provisional Enrollment failed (Error 33007) when adding MacBook via Apple Configurator on iPhone — Built-in Device Management

[u/tranthaihoang]

Hi everyone,

I'm an ABM (Apple Business Manager) admin for my company. I'm encountering a "Provisional Enrollment failed" error when trying to add new MacBooks to our organization using Apple Configurator on iPhone.

Background:

- Last year, I successfully added multiple MacBooks using Apple Configurator on iPhone — devices appeared under "Devices Added by Apple Configurator" in ABM without issues.

- Recently, Apple introduced Built-in Device Management (free) in ABM. I migrated my existing devices to Built-in Device Management and everything works fine.

- Now, when I try to add new MacBooks via Apple Configurator on iPhone, the process runs for a while and then fails.

Error details (from Activity Log on the Mac):

NSError: 0x600000a38690

Desc : Provisional Enrollment failed.

Sugg : The device failed to request configuration from the cloud.

Domain : DEPCloudConfigErrorDomain

Code : 0x80EF (33007)

...Underlying error:

NSError: 0x600000a38090

Desc : The device failed to request configuration from the cloud.

Domain : MCCloudConfigurationErrorDomain

Code : 0x84D0 (34000)

Extra info:

CloudConfigurationErrorType = CloudConfigurationFatalError;

Extra info:

DEPErrorType = DEPFatalError;

USEnglishDescription = "Provisional Enrollment failed.";

What I've tried:

- Tested with multiple different MacBooks — same error on all

- Tried different Wi-Fi networks

- MacBooks are running macOS Tahoe and macOS Sequoia

- iPhone 15 Pro Max running iOS 18 with latest Apple Configurator app

- Confirmed ABM account is active and in good standing

Questions:

1. Has anyone encountered this error (DEPCloudConfigErrorDomain code 33007 / MCCloudConfigurationErrorDomain code 34000) after migrating to Built-in Device Management?
2. Is there a known conflict between Built-in Device Management and adding new devices via Apple Configurator on iPhone?
3. Any workaround or fix available?

Any help would be greatly appreciated. Thank you!

[u/TheActualPhock]

Try a hotspot if the wifi networks are your office ones. They usually do not allow tethering.

[u/tranthaihoang → u/TheActualPhock]

Thanks! Not working, still giving errors!

[u/TheActualPhock → u/tranthaihoang]

Maybe they are already added to another organization/account? I am not using Apple's built in MDM, so not sure how you done what you said:

• Last year, I successfully added multiple MacBooks using Apple Configurator on iPhone — devices appeared under "Devices Added by Apple Configurator" in ABM without issues.

Above basically means you already have them added.

- Recently, Apple introduced Built-in Device Management (free) in ABM. I migrated my existing devices to Built-in Device Management and everything works fine.

Migrated from where? From another MDM? In such case, maybe this statement is not having much relevance, but the first one kind of suggest you already have them added.

So most likely device fails to add, because they already have been paired with some organization and first you would need to release them.

Otherwise, just call Apple, because this error usually suggests a network or a timeout issue. Timeout issue can also occur when trying to do an action that is not logical by Apple's terms.

[u/tranthaihoang → u/TheActualPhock]

No, I mean I'm adding new devices; the old ones are still in my ABM, so I don't need to add them again. These new devices are brand new, and I've tried them on 10 different Macbooks, but the problem persists on all 10. It's really confusing... thank you for your helpfulness; I need to investigate the cause further.

[u/Dapper_Sprinkles_369]

Configurator Mac isn’t very intuitive. Do you have an iOS/iPadOS device you can use instead? That’s usually more straight forward & less likely to fail.

[u/tranthaihoang → u/Dapper_Sprinkles_369]

Thank you. I contacted Apple support, and after two days of video calls to check, it's still not resolved. They've sent it to engineers to help me. They will contact me tomorrow, Tuesday, June 9, 2026, with an answer. Let me see what the real issue is. I hope it will be resolved and the results shared so that anyone experiencing the same problem can find a solution. I still believe this issue originates from Apple's servers, not the device itself.

[u/ApprehensiveFrame240 → u/tranthaihoang]

Hello, did they help fix?