This table presents a summary of the BlackBerry UEM extension—what it provides, what you need to know about enabling and configuring it, and what are the corresponding workflow steps and other relevant topics. The rest of this page provides configuration details. 

Services provided by this extension

The BlackBerry UEM extension provides access to the BlackBerry UEM service for endpoint management, which allows you to distribute modified and secured mobile apps to designated BlackBerry UEMs. Use the BlackBerry UEM to manage BlackBerry Dynamics features and distribute apps to your organization users, who can install the app on their mobile device from this UEM.

See  Integrating BlackBerry Dynamics features with Blue Cedar Platform  for an overview of the features that are available when you manage BlackBerry Dynamics apps.

Extension configuration

Create a configuration with the URL and login credentials for your BlackBerry UEM instance.

Related workflow steps

Add the BlackBerry UEM step to the Testing and/or Production stage of your workflows.

See Distribution - BlackBerry UEM for details.

Other related topics 

Use the BlackBerry UEM to manage apps integrated with BlackBerry Dynamics.

The BlackBerry no-code integration extension lets you include workflow steps in the App Enhancement stage to integrate BlackBerry Dynamics. See the extension (Extension - BlackBerry Dynamics) and workflow step (No-Code Integration - BlackBerry) for more information.


You need a BlackBerry UEM host with a URL and login credentials. If you have several BlackBerry UEM hosts, you can set up multiple configurations on the Blue Cedar Platform. Since BlackBerry is a third-party technology provider, you also need a BlackBerry account in order to set up BlackBerry endpoint management.

Enable the extension

Before users can add BlackBerry UEM distribution to workflows, you must enable the corresponding extension. From the Blue Cedar Platform main menu, select Extension > Distribution. On the BlackBerry UEM card, click Add Extension, and then proceed with configuring as described below.

Configure the extension

BlackBerry UEM requires a URL for a UEM host, plus login credentials. Create a configuration with these details when you enable the extension. Optionally, you can provide proxy server information to access on-premises BlackBerry UEM web services behind a firewall without a VPN.

On the BlackBerry UEM extension card, click the gear icon. Click Add Config and enter the values.

​Config Name​A name for this configuration, which becomes available as a choice when you add a Distribution - BlackBerry UEM step to a workflow.
Server URLThe URL for your BlackBerry UEM instance.

Username to log into the BlackBerry UEM instance.

Note: This user must have REST API access to BlackBerry UEM.

PasswordPassword for the designated user to log into the BlackBerry UEM instance.
Use Active Directory (AD) domainSelect to use an AD domain to authenticate the designated user to a firewall-protected BlackBerry UEM instance.
AD Domain

If "Use Active Directory" is selected, enter the subdomain (no URL scheme, such as http) for the AD database for the UEM user, for example:


Access via BlackBerry proxySelect to access a firewall-protected BlackBerry instance through the BlackBerry infrastructure. This is also known as a private BlackBerry UEM.
BlackBerry Proxy URL

If "Access via BlackBerry proxy" is selected, enter the URL for the BlackBerry proxy server. This URL can vary based on your region; confirm with your BlackBerry administrator. The form includes the hostname and port, but no URL scheme (such as http), something like this:


You can create multiple configurations and choose among them when adding the step to a workflow.

Note: You may have separate UEM environments for testing and for production. Coordinate with your UEM administrator to configure all relevant UEM environments for your workflows.

Next steps

The BlackBerry UEM extension is now available for workflows. When you add the BlackBerry UEM step to a workflow, choose the UEM instance as configured above.

Related topics