Deploying Internal Application on Android Devices

Internal apps are company-specific apps developed by your organization that you might not necessarily want to be searchable in the public app store, but you want your users to have access to this application from their devices.

There are two options for deploying internal applications:

• Add it to Google Play as a private application. These applications are added as public applications in the Omnissa Workspace ONE UEM console after publishing in Google Play.
• Host the application .apk file as a local file. This is for Android 6.0+ devices only.

If you are deploying internal apps on Android Work profile devices, add internal apps to the Managed Google Play Store so that they are available to Android-specific users. Upload your application by logging into the Google Play Developer Console with your enterprise credentials. There is an option to enable, Restrict Distribution, which only allows users of your domain to view this application on the Managed Google Play Store (the badged Play Store). Once you have added your internal application to the developer console, these apps are treated as public applications.

Note: There are a few changes to Corporate Owned Personally Enabled (COPE) in Android 11. For more information, see Changes to Corporate Owned Personally Enabled (COPE) in Android 11

• Internal applications that are hosted by Workspace ONE UEM can no longer be pushed on the personal side of the device. Both internal apps that are pushed as private apps and public apps must be deployed to the work profile only.
• Any other functionality such as Compliance Rules that rely on the internal application is no longer supported.

Application Configuration for Internal Applications

Workspace ONE UEM supports provisioning application configuration to internal applications, regardless of whether the applications are published to Google Play as private applications or uploaded to Workspace ONE UEM as local files. In both cases, the supported application configuration key-value pairs depend on the application developer.