This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 26%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAR%3C/text%3E%3C/svg%3E)
We try to enable conditional access and try to enroll devices to Intune. As we have a lot of remote workers we choose 'Azure AD registered' join type.
Auto-enroll is enabled and working as expect (when user add Microsoft account his device auto enroll to Intune). But some devices doesn`t have Jointype, Owner, Registered fields. All devices already in AD domain.
How to fix it?
Did you find a solution? none of the 'answers' are answers for me.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 86%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELD%3C/text%3E%3C/svg%3E)
@Artem Rozhko Thanks for posting in our Q&A.
Based on my experience, I doubt that these Azure AD records which have no Join type, Owner, Registered fields information are the old remained Azure AD records for enrolled devices. And my suggestion is to check if there are any duplicated records for these devices in AAD.
Meanwhile, please compare their Azure AD device ID in Azure portal with which in Intune portal to make sure if they are the correct Azure AD records for these enrolled Intune devices.
Please check the above information and if there’s anything unclear, feel free to let us know.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hello @Luchuan Deng-MSFT and thanks for your reply.
These devices are NOT old remained Azure AD records for enrolled devices.
I enrolled them on 24 of Jun ("Activity" field) by myself. In that day I enrolled a lot of devices, but only 3 of them in this strange state.
And I check all "Azure AD device ID" and "Device ID" and didn`t find any duplicates.
Hi @Artem Rozhko
Could you try to retire one of the enrolled devices which in "strange state" in Intune and also remove it in Azure AD? then enroll the device again and let's see if the problem persists.
Ok, I will try, and respond ASAP.
Hi @Luchuan Deng-MSFT , I tried your method (remove from AAD Devices and Intune and again enroll) but this didnt resolve the problem. But I notice some trend between all this 3 PC. At "Access work or school" tab in Settings there is no connected Microsoft account. Only 2 records. First one is Device is in domain and second one is Device is under MDM control. When I try to add Microsoft account I get the error "Device already managed by an organization". If I remove device from Intune and from AAD Devices and try to add Microsoft account, its again enroll to only Intune but not add Microsoft account.
All PC that have Microsoft account displayed correctly in AAD Device section (they have Join type, Owner, Registered fields).
II discover the possible reason of this "strange state", when I try to add Microsoft account I get error CAA50021. I am starting to investigate this error.
I found a lot of people that stuck with this error and some Microsoft assistants state that I need to go to Azure AD admin center->Devices->Devices settings, and check if “Users may register their devices with Azure AD” setting is enabled. But in my tenant this settings already enabled.
Hi, @Artem Rozhko For the error CAA50021, based on my research, it means “Number of retry attempts exceeds expectations.” I think it occurs when we try too many times.
I notice the device information still didn't display correctly in Azure AD even though we have already tried to register the device to Azure AD and reenroll the devices into Intune. And also, the “Uses may register their devices with Azure AD” is set as ALL. For our issue, it seems to be a little complex and may need more logs for further analysis. With Q&A limitation, for such case, we suggest to open a support ticket for Azure AD to get more help. To open a support ticket for Azure AD, here is the link for the reference: https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/active-directory-troubleshooting-support-howto
Thanks for your understanding and have a nice day!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 28.999999999999996%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBZ%3C/text%3E%3C/svg%3E)
Hey there, do you have found a solution? We are also stuck with this problem. Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 44%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDR%3C/text%3E%3C/svg%3E)
I have the same problem with a few of our Laptops. The biggest part of devices I enrolled work perfectly fine.
Still don't get why a few of these don't work like they used to.
Would really appreciate a solution for this problem.