MDMFull vs MDMFullWithAAD

%3CLINGO-SUB%20id%3D%22lingo-sub-686836%22%20slang%3D%22en-US%22%3EMDMFull%20vs%20MDMFullWithAAD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-686836%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20two%20Azure%20Registered%20devices%20(local%20domain%20joined).%3C%2FP%3E%3CP%3EThey%20are%20both%20joined%20to%20Intune%20MDM%20automatically%20using%20the%20add%20work%2Fschool%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20in%20MDMdiagnostics%20one%20is%20%22MDMFull%22%20and%20the%20other%20is%20%22MDMFullWithAAD%22.%3C%2FP%3E%3CP%3EThe%20first%20receives%20powershell%20scripts%20(though%20no%20win32)%20and%20the%20latter%20does%20not.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20can't%20find%20ANY%20info%20on%20%22MDMFull%22%20at%20all%2C%20and%20I%20have%20no%20idea%20why%20they%20differ%3F%20They%20are%20both%20domain%20and%20NOT%20Azure%20AD%20joined%20machines.%3C%2FP%3E%3CP%3EMy%20true%20Azure%20AD%20joined%20machines%20are%20%3CSPAN%3EMDMDeviceWithAAD.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-686836%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMDMFullWithAAD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM).%20MDMFULL%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-687043%22%20slang%3D%22en-US%22%3ERe%3A%20MDMFull%20vs%20MDMFullWithAAD%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-687043%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20apparently%2C%20using%20the%20%22%3CSTRONG%3EEnroll%20only%20in%20device%20management%3C%2FSTRONG%3E%22%20instead%20of%20the%20%22CONNECT%22%20button%2C%20gives%20the%20MDMFull%20and%20allows%20powershell%20to%20work%20on%20even%20workspace%20joined%20accounts%20(AD%20registered%20only%20devices).%3CBR%20%2F%3E%3CBR%20%2F%3E%26nbsp%3B%22%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fmdm-enrollment-of-windows-devices%23connecting-to-mdm-on-a-desktop-enrolling-in-device-management%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fclient-management%2Fmdm%2Fmdm-enrollment-of-windows-devices%23connecting-to-mdm-on-a-desktop-enrolling-in-device-management%3C%2FA%3E%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20even%20Microsoft%20employees%20don't%20know%20anymore.%3C%2FP%3E%3CP%3EIs%20there%20any%20way%20to%20get%20users%20who%20used%20the%20CONNECT%20button%20to%20become%20MDMFull%2C%20so%20we%20get%20Intune%20Management%20Extension%20support%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Hi,

 

I have two Azure Registered devices (local domain joined).

They are both joined to Intune MDM automatically using the add work/school account.

 

However, in MDMdiagnostics one is "MDMFull" and the other is "MDMFullWithAAD".

The first receives powershell scripts (though no win32) and the latter does not.


I can't find ANY info on "MDMFull" at all, and I have no idea why they differ? They are both domain and NOT Azure AD joined machines.

My true Azure AD joined machines are MDMDeviceWithAAD.

 

Thanks

1 Reply
Highlighted

So apparently, using the "Enroll only in device management" instead of the "CONNECT" button, gives the MDMFull and allows powershell to work on even workspace joined accounts (AD registered only devices).

 "https://docs.microsoft.com/en-us/windows/client-management/mdm/mdm-enrollment-of-windows-devices#con..."

 

I think even Microsoft employees don't know anymore.

Is there any way to get users who used the CONNECT button to become MDMFull, so we get Intune Management Extension support?