Skip to content

Commit eab12b3

Browse files
authored
Merge pull request #8073 from mabutc/patch-15
Adding scenario for COPE
2 parents 2bb3fb6 + d133b28 commit eab12b3

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

memdocs/intune/apps/apps-deploy.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -133,6 +133,9 @@ The information in the following table can help you understand the resulting int
133133
> iOS Store apps (not iOS/iPadOS VPP apps) that are targeted with required intent will be enforced on the device at the time of the device check-in and will also show in the Company Portal app.<br><br>
134134
> When conflicts occur in **Uninstall on device removal** setting, the app is not removed from the device when the device is no longer managed.
135135
136+
> [!NOTE]
137+
> Apps deployed as Required to corporate-owned work profile devices cannot be uninstalled manually by the user.
138+
136139
## Managed Google Play app deployment to unmanaged devices
137140

138141
For unenrolled Android devices, you can use Managed Google Play to deploy store apps and line-of-business (LOB) apps to users. Once deployed, you can use [Mobile Application Management (MAM)](../apps/android-deployment-scenarios-app-protection-work-profiles.md#mam) to manage the applications. Managed Google Play apps targeted as **Available with or without enrollment** will appear in the Play Store app on the end user's device, and not in the Company Portal app. End user will browse and install apps deployed in this manner from the Play app. Because the apps are being installed from managed Google Play, the end user will not need to alter their device settings to allow app installation from unknown sources, which means the devices will be more secure. If the app developer publishes a new version of an app to Play that was installed on a user's device, the app will be automatically updated by Play.

0 commit comments

Comments
 (0)