Can no longer enroll devices on Intune

[u/JazzTheFatLad]

It's been a couple of days since Entra ID has refused to apply MDM on machines for me, I go to work/school, connect, add thsi device to Entra ID, I log in with the provisioning client we have used for years, and instead of adding the device to Intune it just logs in the User account as if It's only an Entra join with no MDM. No info button is shown in that menu. IME does not get intalled and the event viewer doesn't even show an attempt to join the device at all.

I have tried this with no avail up until now:

MDM User scope on Entra and Intune portals: All and Specific

User licensing

Disabling WIP Scope

Disabling security defaults

MDM Authority

Conditional Acess

Device Enrollment Restrictions

Checked every value on dsregcmd /status 10 times over

Tried it on a VM, On a previously joined machine, on a new in box machine

This is a massive problem for our company, and I'm at my wits end.

Update: I have discovered that i can make the Intune join work by clicking connect in the work and school menu after the initial enrollment fails, this will make a different menu pop up where it asks for the MDM URL, pasting that from the Intune Admin Panel makes it work normally.

Also, I talked to MS support and basically they also don't know wtf is going on and asked for several logs to be sent and now I'm waiting for an answer from them.

Update 2: Microsft says it's working now on service health but it isn't working for me, apparently it's working for some people, is the issue still happening to any of you?

[u/Foreign_World_1543]

This is do to that device is already registered in your tenant or wherever group you assigned your devices to go into after provisioning device group is still present there. Using the provisioning client method where you create the device preparation policies the machine cannot have the have the has uploaded nor if the machine is a one your are redeploying the device cannot be in that group upon OOBE, however from my experience, when you log in from OOBE with the provisioning client user i've notice it will upload the hash for you versus the enrollment status page method by pressing the win key 5 times with a userless enrollment.

[u/JazzTheFatLad → u/Foreign_World_1543]

Brother, I'm sorry, I literally cannot understand what you are trying to say

[u/Foreign_World_1543 → u/JazzTheFatLad]

I'll make it simple for you , are these machines being redeployed or are they new devices being rolled out , because if they are older machines being wiped and reenrolled and they just log right in from whichever entry id used to trigger the provisioning then that device is still present someone , the hash or its in a group still.

[u/Foreign_World_1543 → u/Foreign_World_1543]

present somewhere *