Home

Auto Enrollment Intune devices already azure AD joined?

%3CLINGO-SUB%20id%3D%22lingo-sub-283885%22%20slang%3D%22en-US%22%3EAuto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-283885%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnder%20All%20Devices%20I%20found%20all%20my%20computers%20that%20have%20join%20type%20%22Azure%20AD%20Joined%22%26nbsp%3B%20but%20under%20%22Intune%20Devices%22%20there%20is%20none.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIs%20there%20a%20way%20to%20auto%20enroll%20Computer%20that%20already%20has%20Azure%20AD%20joined%20to%20intune%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%2F%2FW%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-283885%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-401014%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401014%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20news%20to%20all%2C%20the%20%22%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fin-development%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EIntune%20In%20Development%3C%2FA%3E%22%20site%20does%20list%20a%20feature%20which%20will%20be%20released%20soon%20that%20solves%20the%20agent%20install%20on%20devices%20not%20auto-enrolled%2C%20see%20here%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22configure-your-win32-apps-to-be-installed-on-intune-enrolled-azure-ad-joined-devices-%22%20class%3D%22heading-with-anchor%22%20id%3D%22toc-hId-1455553127%22%20id%3D%22toc-hId-1505362682%22%20id%3D%22toc-hId-1505362682%22%3EConfigure%20your%20Win32%20apps%20to%20be%20installed%20on%20Intune%20enrolled%20Azure%20AD%20joined%20devices%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FH3%3E%0A%3CP%3EYou'll%20be%20able%20to%20assign%20your%20Win32%20apps%20to%20be%20installed%20on%20Intune%20enrolled%20Azure%20AD%20joined%20devices.%20For%20more%20information%20about%20Win32%20apps%20in%20Intune%2C%20see%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fapps-win32-app-management%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%20data-linktype%3D%22relative-path%22%3EWin32%20app%20management%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fin-development%23configure-your-win32-apps-to-be-installed-on-intune-enrolled-azure-ad-joined-devices-%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fin-development%23configure-your-win32-apps-to-be-installed-on-...%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebest%2C%3C%2FP%3E%0A%3CP%3EOliver%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-294041%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-294041%22%20slang%3D%22en-US%22%3EI%E2%80%99m%20having%20the%20same%20issue%20%2C%20which%20devices%20did%20you%20move%20under%20what%20section%20in%20azure%20%3F%20I%20have%20devices%20already%20enrolled%20into%20azure%20ad%20and%20trying%20to%20get%20them%20to%20enrol%20into%20Intune%20.%20Under%20accounts%20in%20settings%20I%20select%20enrol%20only%20in%20device%20management%20and%20it%20doesn%E2%80%99t%20install%20the%20Intune%20Management%20Extension.%20So%20question%20is%20what%20is%20the%20best%20way%20to%20enrol%20a%20device%20into%20Intune%20that%20is%20already%20azure%20ad%20joined%20%3F%20Btw%20license%20is%20Microsoft%20365%20business%20.%20And%20oobe%20works%20for%20brand%20new%20devices%20and%20Intune%20Management%20Extension%20is%20working%20for%20those%20devices%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285312%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285312%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Oliver%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20is%20only%20MDM%20user%20scope%20that%20is%20enabled%20and%20not%20MAM.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20just%20noticed%20that%20they%20have%20Intune%20clinet%20installed%20%3A%5C%3C%2Fimg%3E%20I%20have%20to%20remove%20the%20devices%20from%20the%20console%20first.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285310%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285310%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F174439%22%20target%3D%22_blank%22%3E%40Oliver%20Kieselbach%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EHi%20William%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethe%20problem%20is%20if%20you%20enable%20both%20enrollment%20user%20scopes%20and%20when%20they%20overlap%20the%20MAM%20scope%20will%20take%20precedence.%20I%20guess%20this%20is%20your%20problem%2C%20I've%20seen%20this%20very%20often.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Esee%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-enroll%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-enroll%3C%2FA%3E%3C%2FP%3E%3CP%20class%3D%22alert-title%22%3E%3CEM%3E%3CSTRONG%3EImportant%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%3CP%3EIf%20both%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EMAM%20user%20scope%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%20automatic%20MDM%20enrollment%20(%3CSTRONG%3EMDM%20user%20scope%3C%2FSTRONG%3E)%20are%20enabled%20for%20a%20group%2C%20only%20MAM%20is%20enabled.%20Only%20MAM%20is%20added%20for%20users%20in%20that%20group%20when%20they%20workplace%20join%20personal%20device.%20Devices%20are%20not%20automatically%20MDM%20enrolled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eto%20avoid%20this%20and%20get%20your%20MDM%20auto-enrollment%20working%20you%20can%20either%20disable%20the%20MAM%20user%20scope%20or%20you%20enable%20All%20for%20MDM%20user%20scope%20and%20assign%20a%20specific%20group%20for%20MAM%20user%20scope.%20Additionally%20keep%20in%20mind%20the%20MAM%20user%20scope%20is%20not%20for%20general%20MAM%20on%20iOS%20or%20Android%2C%20it%20is%20for%20the%20MAM%20Windows%20feature.%20It's%20the%20Windows%20Information%20Protection%20feature%20basically.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebest%2C%3C%2FP%3E%3CP%3EOliver%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3ESuperb%20and%20very%20informative%20answer%20Oliver%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-285290%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-285290%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20William%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethe%20problem%20is%20if%20you%20enable%20both%20enrollment%20user%20scopes%20and%20when%20they%20overlap%20the%20MAM%20scope%20will%20take%20precedence.%20I%20guess%20this%20is%20your%20problem%2C%20I've%20seen%20this%20very%20often.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Esee%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-enroll%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fwindows-enroll%3C%2FA%3E%3C%2FP%3E%0A%3CP%20class%3D%22alert-title%22%3E%3CEM%3E%3CSTRONG%3EImportant%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3EIf%20both%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3EMAM%20user%20scope%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eand%20automatic%20MDM%20enrollment%20(%3CSTRONG%3EMDM%20user%20scope%3C%2FSTRONG%3E)%20are%20enabled%20for%20a%20group%2C%20only%20MAM%20is%20enabled.%20Only%20MAM%20is%20added%20for%20users%20in%20that%20group%20when%20they%20workplace%20join%20personal%20device.%20Devices%20are%20not%20automatically%20MDM%20enrolled.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Eto%20avoid%20this%20and%20get%20your%20MDM%20auto-enrollment%20working%20you%20can%20either%20disable%20the%20MAM%20user%20scope%20or%20you%20enable%20All%20for%20MDM%20user%20scope%20and%20assign%20a%20specific%20group%20for%20MAM%20user%20scope.%20Additionally%20keep%20in%20mind%20the%20MAM%20user%20scope%20is%20not%20for%20general%20MAM%20on%20iOS%20or%20Android%2C%20it%20is%20for%20the%20MAM%20Windows%20feature.%20It's%20the%20Windows%20Information%20Protection%20feature%20basically.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ebest%2C%3C%2FP%3E%0A%3CP%3EOliver%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284115%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284115%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20maybe%20raise%20a%20wee%20Support%20Ticket%20within%20the%20Azure%20Portal.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStuart%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284059%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284059%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEnterprise%20mobility%20security%20E3%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284057%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284057%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112561%22%20target%3D%22_blank%22%3E%40William%20Hanna%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EI've%20choosen%20%22all%22%20shouldnt%20that%20enroll%20all%20computers%3F%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EOne%20would%20imagine%20so.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20licenses%20do%20you%20have%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStuart%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284054%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284054%22%20slang%3D%22en-US%22%3EI've%20choosen%20%22all%22%20shouldnt%20that%20enroll%20all%20computers%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284051%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284051%22%20slang%3D%22en-US%22%3E%3CP%3EAh%2C%20understood%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20the%20group%20scope%20not%20still%20enrol%20them%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStuart%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284042%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284042%22%20slang%3D%22en-US%22%3EHi%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI've%20already%20done%20that%20and%20that%20is%20if%20you%20enroll%20them%20to%20azure%20ad%20they%20will%20automatically%20enroll%20in%20intune.%20In%20this%20case%2C%20they%20are%20already%20AzureAd%20joined%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284034%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284034%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20you%20can%20set%20up%20auto%20enrolment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteps%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fquickstart-setup-auto-enrollment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fquickstart-setup-auto-enrollment%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStuart%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-412712%22%20slang%3D%22en-US%22%3ERe%3A%20Auto%20Enrollment%20Intune%20devices%20already%20azure%20AD%20joined%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-412712%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F174439%22%20target%3D%22_blank%22%3E%40Oliver%20Kieselbach%3C%2FA%3E%20%2C%20shouldn't%20ask%20this%20question%20here%20but%20have%20you%20came%20across%20any%20issues%20with%20Windows%20App%20(win32)%20updating%20to%20a%20new%20version.%20The%20issue%20with%20the%20app%20im%20trying%20to%20update%20requires%20the%20current%20version%20to%20exit%20so%20it%20can%20install%20the%20new%20version.%20The%20install%20fails%20cause%20the%20old%20version%20is%20still%20running%20inWindows%2010%3C%2FP%3E%3C%2FLINGO-BODY%3E
Deleted
Not applicable

Hello,

 

Under All Devices I found all my computers that have join type "Azure AD Joined"  but under "Intune Devices" there is none. 

Is there a way to auto enroll Computer that already has Azure AD joined to intune?

//W

13 Replies
Hi,

I've already done that and that is if you enroll them to azure ad they will automatically enroll in intune. In this case, they are already AzureAd joined

Ah, understood

 

Does the group scope not still enrol them?

 

Stuart

I've choosen "all" shouldnt that enroll all computers?

@Deleted wrote:
I've choosen "all" shouldnt that enroll all computers?

One would imagine so.

 

What licenses do you have?

 

Stuart

Hi,

 

Enterprise mobility security E3

OK, maybe raise a wee Support Ticket within the Azure Portal.

 

Stuart

Hi William,

 

the problem is if you enable both enrollment user scopes and when they overlap the MAM scope will take precedence. I guess this is your problem, I've seen this very often.

 

see here: https://docs.microsoft.com/en-us/intune/windows-enroll

Important

If both MAM user scope and automatic MDM enrollment (MDM user scope) are enabled for a group, only MAM is enabled. Only MAM is added for users in that group when they workplace join personal device. Devices are not automatically MDM enrolled.

 

to avoid this and get your MDM auto-enrollment working you can either disable the MAM user scope or you enable All for MDM user scope and assign a specific group for MAM user scope. Additionally keep in mind the MAM user scope is not for general MAM on iOS or Android, it is for the MAM Windows feature. It's the Windows Information Protection feature basically.

 

best,

Oliver


@Oliver Kieselbach wrote:

Hi William,

 

the problem is if you enable both enrollment user scopes and when they overlap the MAM scope will take precedence. I guess this is your problem, I've seen this very often.

 

see here: https://docs.microsoft.com/en-us/intune/windows-enroll

Important

If both MAM user scope and automatic MDM enrollment (MDM user scope) are enabled for a group, only MAM is enabled. Only MAM is added for users in that group when they workplace join personal device. Devices are not automatically MDM enrolled.

 

to avoid this and get your MDM auto-enrollment working you can either disable the MAM user scope or you enable All for MDM user scope and assign a specific group for MAM user scope. Additionally keep in mind the MAM user scope is not for general MAM on iOS or Android, it is for the MAM Windows feature. It's the Windows Information Protection feature basically.

 

best,

Oliver


Superb and very informative answer Oliver

Hello Oliver,

 

It is only MDM user scope that is enabled and not MAM.

I just noticed that they have Intune clinet installed :\ I have to remove the devices from the console first.

Thanks!

I’m having the same issue , which devices did you move under what section in azure ? I have devices already enrolled into azure ad and trying to get them to enrol into Intune . Under accounts in settings I select enrol only in device management and it doesn’t install the Intune Management Extension. So question is what is the best way to enrol a device into Intune that is already azure ad joined ? Btw license is Microsoft 365 business . And oobe works for brand new devices and Intune Management Extension is working for those devices

Good news to all, the "Intune In Development" site does list a feature which will be released soon that solves the agent install on devices not auto-enrolled, see here:

 

Configure your Win32 apps to be installed on Intune enrolled Azure AD joined devices 

You'll be able to assign your Win32 apps to be installed on Intune enrolled Azure AD joined devices. For more information about Win32 apps in Intune, see Win32 app management.

 

https://docs.microsoft.com/en-us/intune/in-development#configure-your-win32-apps-to-be-installed-on-...

 

best,

Oliver

Hi @Oliver Kieselbach , shouldn't ask this question here but have you came across any issues with Windows App (win32) updating to a new version. The issue with the app im trying to update requires the current version to exit so it can install the new version. The install fails cause the old version is still running inWindows 10

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies