Device management notification

You are correct in your assumption. Additionally, if one has skipped Windows Hello this error can occur.

Read my reply below to find out more about how to repair and possible resolutions.

Solved,

2 items are notable to resolution.

1. Microsoft in their infinite wisdom has decided to deprecate Windows Information Protection
2. The local account named mddprov is no longer associated with my device as a result of changing the account password.

Actions Taken to resolution:

1. In Windows 10, click on Start->Settings-> Apps
2. Select Microsoft Office-> Advanced options -> Repair
3. Reboot with Start->Run-> shutdown /r /f /t 0

A friend of mine recently registered the domain (elrant.team) on behalf of her team, in which I also take place.

Checking the admin console, there have been 3 people registered their machines in the organization so far, with all of them having app installation failures.

But when it comes to me, as soon as I add the work account, I'm disconnected with the following notification, with no traces of my laptop to be seen in the admin console.

I wonder if this is happening because I have my school account (erdogan.edu.tr) added on this machine already. I want to format this laptop and try to go through OOBE only with the work account, but I have ongoing assignments and important data, not to mention my NVMe disk health being at 61%, which also keeps me from doing so.

As a troubleshooting attempt, I suggest to try to do what I mentioned - backing up data, formatting the machine and going through OOBE using work account. If it's reported to work, then I'll also do the same.

Thanks from now!

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:

1. 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?
2. 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.

I can help with this issues I been diagnosing this issues , there are actors connecting the azure servers of companys to an alternate Azure account and remotely accessing the devices and removing all company data I been trying to let yoou guys knows its a script exploiting the servers and the Microsoft infrastructure. Email me here we can continue chatting ******@ggservicesdo.onmicrosoft.com. Always a pleasure to help Mr. Gates and our Microsoft Team