This started happening to a client of ours, but like most of you, it has only occurred on a few devices.
After a bit of investigation, I have a theory this may have something to do with the "Stale Device" state that AAD registered (not AAD joined) machines get put into after a period of time. If your machines have been used by other users in the past that no longer use that machine, then that particular device registration profile ends up going stale in AAD, unless it is properly removed from the machine when it is reassigned. This would be particularly problematic if you have a lot of movement across your machines.
The confusing elements of this issue are the following:
- This issue appears to have only started in the last 6 months or so from what I can see. So, is it a bug, or has this been intentionally added as functionality by Microsoft?
- The alert is showing in the currently active profile, even though the action has in most cases been carried out on a left-over profile in the background. If this is the case, then Microsoft have to update how the alert is displayed so it doesn't affect or confuse other users.
I read Microsoft documentation that removing stale devices does NOT remove the profile registration on the device. However, it will stop AAD from being concerned by that stale status. So, I have just removed all stale devices from our client's tenancy in the hope that it will stop the issue.
Maybe anyone having this issue could try the same and report in say a month or so as to whether it has stopped the issue.