- Configuring BlackBerry UEM
- Changing the certificates that BlackBerry UEM uses for authentication
- Installing the BlackBerry Connectivity Node to connect to resources behind your organization's firewall
- Configuring BlackBerry UEM to send data through a proxy server
- Configure connections through internal proxy servers
- Connect to an SMTP server to send email notifications
- Connecting to your company directories
- Connect BlackBerry UEM to Entra ID to create directory user accounts
- Configuring BlackBerry UEM to manage Microsoft Intune app protection profiles
- Configuring BlackBerry UEM as an Intune compliance partner in Entra
- Obtaining an APNs certificate to manage iOS and macOS devices
- Configure BlackBerry UEM for DEP
- Configuring BlackBerry UEM to support Android Enterprise devices
- Configuring BlackBerry UEM to support Android Management devices
- Extending the management of Chrome OS devices to BlackBerry UEM
- Simplifying Windows 10 activations
- Migrating users, devices, groups, and other data from a source server
- Prerequisites: Migrating users, devices, groups, and other data from a source BlackBerry server
- UEM migration best practices and considerations
- Connect to a source server
- Migrate IT policies, profiles, and groups from a source server
- Migrate users from a source server
- Migrate devices from a source server
- Configuring network communication and properties for BlackBerry Dynamics apps
- Manage BlackBerry Proxy clusters
- Configure Direct Connect using port forwarding
- Configure BlackBerry Dynamics properties
- Configure communication settings for BlackBerry Dynamics apps
- Sending BlackBerry Dynamics app data through an HTTP proxy
- Methods for routing traffic for BlackBerry Dynamics apps
- Configuring Kerberos authentication for BlackBerry Dynamics apps
- Encrypt the connection between BlackBerry UEM and Microsoft SQL Server
- Integrating BlackBerry UEM with Cisco ISE
- Set up VPN using Knox StrongSwan for UEM dark site environments
- BlackBerry Docs
- BlackBerry UEM 12.21
- UEM Configuration Guide
- Simplifying Windows 10 activations
- Integrate UEM with Entra ID join
Integrate UEM with Entra ID join
UEM
with Entra ID
joinYou can integrate
BlackBerry UEM
with Entra ID
join for a simplified enrollment process for Windows 10
devices. When it’s configured, users can enroll their devices with UEM
using their Entra ID
username and password. Entra ID
join is also required to support Windows Autopilot
, which allows Windows 10
devices to be automatically activated with UEM
during the Windows 10
out-of-the-box setup experience. A UEM
certificate can be installed on the device manually or administrators can deploy the certificate using SCCM.You will need the MDM terms of use URL and the MDM discovery URL to complete the steps below. To determine these URLs, in the
UEM
management console, create a test user account and send the user an activation email using the default activation email template. The default template contains the %ClientlessActivationURL% variable that resolves to the appropriate value in the received email. Use that value for the following URLs in the steps below:
- MDM terms of use URL:%ClientlessActivationURL%/azure/termsofuse
- MDM discovery URL:%ClientlessActivationURL%/azure/discovery
- Log in to the Microsoft Azure portal.
- In the Mobility (MDM and WIP) section, add an application and give it a friendly name (for example, BlackBerry UEM).
- Specify the user scope. If applicable, select groups.
- Specify the MDM terms of use URL and the MDM discovery URL.
Optionally, Configure Windows Autopilot for device activation.