We’re currently in the middle of a quarterly equipment lease swap and have had a couple of people on our team getting the DeviceCapReached error when we go to enroll an Autopilot device. This is happening because we’re enrolling the devices with our accounts, rather than having the user sign in, then taking the laptop back from them to put it in the right on prem OU, run updates and install all of the software they need. I understand this isn’t how Microsoft designed Autopilot to work, but this is where we’re at.

I’ve done research into potential resolutions, but I have a lot of questions. First, some important details

User-driven deployment profile (future proofing, I guess)Microsoft Entra hybrid enrollmentIntune device enrollment limit – 7Azure tenant device limit – 20

The first option seems to be creating a script that clears out stale devices from our Azure tenant. When I’ve spoken with our Infrastructure team about device removal in the past, they said we’re using Entra Connect to sync with on prem AD, so they we’re against the idea. I’ve found a way to convince them otherwise, but it’s going to take time and scripting.

The next option is using a device enrollment manager account, but the Microsoft documentation mentions it enrolls the device in shared mode and that device limits won’t work on devices enrolled this way. It also says “Do not delete accounts assigned as a Device enrollment manager if any devices were enrolled using the account. Doing so will lead to issues with these devices.” but doesn’t elaborate further. So, this option seems like a dead end.

Third option is to increase the device enrollment quota in Azure, but since this is a tenant wide setting, we don’t necessarily want to give Rick in accounting the ability to enroll as many devices as he can carry.

I found a comment in this thread that suggested using Remove-AzureADDeviceRegisteredOwner (now Remove-MgDeviceRegisteredOwnerByRef with the graph modules). But this just change the primary user. Doing so didn’t stop me from getting the error message.

So here are my questions –

If you’ve gone through this, how did you resolve the issue?

What exactly are the consequences of using a DEM account to enroll devices?

If I look at the devices attached to my user account, and filter by Autopilot devices, I have 42. Other offices have a single desktop person, and they have > 80 devices. What device property, in which directory, causes this error?

Do you have a stale device script you’d recommend? I’ll write my own, for sure, but having something to go off of would be nice

​We’re currently in the middle of a quarterly equipment lease swap and have had a couple of people on our team getting the DeviceCapReached error when we go to enroll an Autopilot device. This is happening because we’re enrolling the devices with our accounts, rather than having the user sign in, then taking the laptop back from them to put it in the right on prem OU, run updates and install all of the software they need. I understand this isn’t how Microsoft designed Autopilot to work, but this is where we’re at. I’ve done research into potential resolutions, but I have a lot of questions. First, some important detailsUser-driven deployment profile (future proofing, I guess)Microsoft Entra hybrid enrollmentIntune device enrollment limit – 7Azure tenant device limit – 20The first option seems to be creating a script that clears out stale devices from our Azure tenant. When I’ve spoken with our Infrastructure team about device removal in the past, they said we’re using Entra Connect to sync with on prem AD, so they we’re against the idea. I’ve found a way to convince them otherwise, but it’s going to take time and scripting. The next option is using a device enrollment manager account, but the Microsoft documentation mentions it enrolls the device in shared mode and that device limits won’t work on devices enrolled this way. It also says “Do not delete accounts assigned as a Device enrollment manager if any devices were enrolled using the account. Doing so will lead to issues with these devices.” but doesn’t elaborate further. So, this option seems like a dead end. Third option is to increase the device enrollment quota in Azure, but since this is a tenant wide setting, we don’t necessarily want to give Rick in accounting the ability to enroll as many devices as he can carry. I found a comment in this thread that suggested using Remove-AzureADDeviceRegisteredOwner (now Remove-MgDeviceRegisteredOwnerByRef with the graph modules). But this just change the primary user. Doing so didn’t stop me from getting the error message.  So here are my questions -If you’ve gone through this, how did you resolve the issue?What exactly are the consequences of using a DEM account to enroll devices?If I look at the devices attached to my user account, and filter by Autopilot devices, I have 42. Other offices have a single desktop person, and they have > 80 devices. What device property, in which directory, causes this error?Do you have a stale device script you’d recommend? I’ll write my own, for sure, but having something to go off of would be nice  Read More

​