%3CLINGO-SUB%20id%3D%22lingo-sub-1447289%22%20slang%3D%22en-US%22%3EUpcoming%20UI%20Change%3A%20Updated%20Android%20APP%20Conditional%20Launch%20end-user%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1447289%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EBy%3A%20Ileana%20Wu%20%7C%20PM%20%7C%26nbsp%3BMicrosoft%20Endpoint%20Manager%20-%20Intune%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOver%20the%20past%20couple%20of%20months%2C%20we%20have%20been%20rolling%20out%20a%20new%20user%20experience%20for%20the%20conditional%20launch%20behavior%20within%20Intune%20App%20Protection%20Policies%20(APP)%2C%20targeting%20the%20Android%20platform%20first.%20We%20are%20excited%20to%20bring%20this%20refreshed%2C%20guided%20process%20to%20users%20which%20streamlines%20their%20first-launch%20experience%20and%20improves%20their%20experience%20when%20their%20app%20or%20device%20goes%20out%20of%20compliance.%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CEM%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3C%2FEM%3E%3A%20The%20changes%20discussed%20below%20only%20apply%20to%20Android%20devices%20but%20will%20be%20coming%20to%20iOS%2FiPadOS%20in%20a%20future%20Intune%20SDK%20release.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20the%20older%20Android%20Company%20Portal%2C%20when%20users%20first%20signed%20into%20a%20protected%20app%2C%20they%20saw%20this%20dialog%20message%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Ileanapost1.png%22%20style%3D%22width%3A%20401px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197131iDA1C781A37D3D4E2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Ileanapost1.png%22%20alt%3D%22Ileanapost1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20our%20June%20release%20(Company%20Portal%20version%205.0.4805.0)%2C%20in%20beta%20now%20and%20expected%20to%20slowly%20roll%20out%20starting%20the%20week%20of%20June%208th%2C%20users%20see%20this%20checklist%20%E2%80%9CGet%20Access%E2%80%9D%20screen%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Ileanapost2.png%22%20style%3D%22width%3A%20333px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197132iEB88C5126D459133%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22Ileanapost2.png%22%20alt%3D%22Ileanapost2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEach%20of%20the%20four%20items%20in%20the%20list%20represents%20a%20category%20of%20compliance%20requirements%20that%20will%20be%20evaluated%20before%20the%20user%20can%20gain%20access%20to%20the%20app.%20If%20all%20compliance%20requirements%20per%20category%20are%20met%2C%20the%20corresponding%20grey%20number%20icon%20for%20the%20category%20will%20turn%20to%20a%20green%20checkmark.%20Each%20compliance%20category%20is%20sequentially%20and%20automatically%20evaluated.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20also%20updated%20the%20experience%20if%20Conditional%20Launch%20is%20configured%20such%20that%20users%20should%20receive%20a%20warning%2C%20be%20blocked%20from%20accessing%20the%20app%2C%20have%20the%20app%E2%80%99s%20work%20or%20school%20account%20data%20wiped%2C%20or%20if%20the%20app%20does%20not%20meet%20the%20compliance%20requirements.%20With%20this%20new%20release%2C%20users%20may%20tap%20%E2%80%9CContinue%E2%80%9D%20in%20the%20new%20%E2%80%9CGet%20Access%E2%80%9D%20screen%20to%20view%20the%20reason%20they%20are%20not%20in%20compliance%20and%20the%20recommended%20remediation%20steps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBefore%2C%20users%20were%20shown%20a%20dialogue%20like%20the%20one%20below%20if%20one%20or%20more%20requirement%20categories%20were%20not%20met%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ileanapost3.png%22%20style%3D%22width%3A%20309px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197133iEEF4290FE9201C20%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22ileanapost3.png%22%20alt%3D%22ileanapost3.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20of%20Android%20Company%20Portal%20version%205.0.4769.0%20(2005%20release)%2C%20we%20rolled%20out%20updated%20screens%20for%20these%20remediation%20messages.%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ileanapost4.png%22%20style%3D%22width%3A%20379px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F197134i7CF521D44CB2EA7A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22ileanapost4.png%22%20alt%3D%22ileanapost4.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20users%20who%20are%20using%20an%20app%20that%20has%20previously%20received%20policy%2C%20they%20will%20not%20be%20shown%20the%20new%20%E2%80%9CGet%20Access%20screen%E2%80%9D.%20Each%20compliance%20requirement%20continues%20to%20be%20evaluated%20silently%2C%20which%20is%20the%20same%20behavior%20that%20occurred%20prior%20to%20these%20changes.%20However%2C%20what%20has%20changed%20is%20that%20if%20the%20app%20is%20evaluated%20to%20be%20non-compliant%2C%20the%20user%20will%20be%20shown%20the%20redesigned%20remediation%20screen.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EInterested%20in%20understanding%20more%20about%20the%20Conditional%20Launch%20capabilities%20within%20APP%3F%20See%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fapps%2Fapp-protection-policy-settings-android%23conditional-launch%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EConditional%20Launch%20settings%20available%20in%20Android%3C%2FA%3E%20and%20the%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fapps%2Fapp-protection-framework%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EData%20protection%20framework%20using%20app%20protection%20policies%3C%2FA%3E%20for%20recommended%20data%20protection%20settings%20to%20deploy%20in%20your%20organization.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1447289%22%20slang%3D%22en-US%22%3E%3CP%3ERead%20this%20article%20for%20screen%20shots%20of%20the%20new%20App%20Protection%20Policies%20(APP)%20UI.%20No%20additional%20screens%20have%20been%20added%2C%20just%20a%20few%20have%20been%20simplified%20for%20the%20end%20user%20experience.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1447289%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E

By: Ileana Wu | PM | Microsoft Endpoint Manager - Intune

 

Over the past couple of months, we have been rolling out a new user experience for the conditional launch behavior within Intune App Protection Policies (APP), targeting the Android platform first. We are excited to bring this refreshed, guided process to users which streamlines their first-launch experience and improves their experience when their app or device goes out of compliance.


Note: The changes discussed below only apply to Android devices but will be coming to iOS/iPadOS in a future Intune SDK release. 

 

With the older Android Company Portal, when users first signed into a protected app, they saw this dialog message:

Ileanapost1.png

 

With our June release (Company Portal version 5.0.4805.0), in beta now and expected to slowly roll out starting the week of June 8th, users see this checklist “Get Access” screen:

Ileanapost2.png

 

Each of the four items in the list represents a category of compliance requirements that will be evaluated before the user can gain access to the app. If all compliance requirements per category are met, the corresponding grey number icon for the category will turn to a green checkmark. Each compliance category is sequentially and automatically evaluated.

 

We have also updated the experience if Conditional Launch is configured such that users should receive a warning, be blocked from accessing the app, have the app’s work or school account data wiped, or if the app does not meet the compliance requirements. With this new release, users may tap “Continue” in the new “Get Access” screen to view the reason they are not in compliance and the recommended remediation steps.

 

Before, users were shown a dialogue like the one below if one or more requirement categories were not met:

ileanapost3.png

 

As of Android Company Portal version 5.0.4769.0 (2005 release), we rolled out updated screens for these remediation messages.

ileanapost4.png

 

For users who are using an app that has previously received policy, they will not be shown the new “Get Access screen”. Each compliance requirement continues to be evaluated silently, which is the same behavior that occurred prior to these changes. However, what has changed is that if the app is evaluated to be non-compliant, the user will be shown the redesigned remediation screen.

 

Interested in understanding more about the Conditional Launch capabilities within APP? See Conditional Launch settings available in Android and the Data protection framework using app protection policies for recommended data protection settings to deploy in your organization.