Using offline mode and app access without signing in on Android Enterprise dedicated devices

This week is all about the recently introduced functionalities of offline mode and app access without signing in. Those functionalities are specifically created for Android Enterprise dedicated devices that are enrolled into Microsoft Entra shared device mode and that are using the Managed Home Screen as launcher for other approved apps. Both of these functionalities are focused on scenarios in which the user is required to sign in to the device before the apps on the device can be used. With these functionalities, however, the IT administrator can enable specific apps to be available even when the device is offline, and even before signing in to the device. That makes sure that the user can still be productive when the device is offline, and can …

Read more

Blocking Bluetooth on Android devices

This week is all about a new configuration option for corporate-owned Android Enterprise devices. That new configuration option is the ability to block the usage of Bluetooth. There can be many different reasons why organizations might want to block the usage of Bluetooth on (some) Android devices within the environment. That could be simply from a functional perspective to preserve battery and to extend the usage time, but that could also be more from a security perspective to prevent the device from being exploited. For the latter think about unauthorized access, data interception, malware distribution, or even something like bluejacking (sending messages to nearby devices). All pretty good reasons to think about the default availability of Bluetooth on Android devices within the environment. Especially on …

Read more

Understanding custom device naming templates for Android devices

This week is about another nice new feature for the enrollment of Android Enterprise corporate-owned devices, and that feature is the ability to use custom device naming templates. Custom device naming templates enable IT administrators to adjust the name of Android Enterprise corporate-owned devices during the enrollment. That provides IT administrators with the ability to adhere naming conventions to their devices and with that organize the devices neatly within the console. That can also make it a whole lot easier to locate devices. This post will focus on the required configurations for using custom device naming templates for Android Enterprise corporate-owned devices. Note: Keep in mind that custom device naming templates will adjust the management name of the device. Introducing custom device naming templates for Android devices …

Read more

Understanding enrollment time grouping for Android devices

This week is all about enrollment time grouping for Android devices. More specifically, enrollment time grouping for Android Enterprise corporate-owned devices. The focus of enrollment time grouping for Android devices is exactly the same as for Windows devices; the focus is to speed up app and policy provisioning during the device enrollment. With enrollment time grouping, the IT administrator can add a device to an Entra security group directly during the enrollment of the device. That enables the IT administrator to use that security group for assigning required apps and device configurations. Together that provides a faster delivery of the required apps and device configurations, as the device will be a member of the security group directly after the enrollment. This takes away any delays …

Read more

Using a QR code to easily sign in to apps on shared Android devices

This week is all about the new ability to use a QR code to sign in to specific apps on (shared) Android devices. QR code authentication is a new authentication method in Entra that enables frontline workers to sign in to apps on shared devices. That authentication method provides users with the ability use a unique QR code in combination with a PIN to sign in. That eliminates the need for users to enter usernames and passwords, making it a more user-friendly experience on shared devices. On Android devices, QR code sign in is now available for the Managed Home Screen app, the Teams app, and even during the web sign-in. This post will briefly go through the QR code authentication method, directly followed with …

Read more

Temporarily removing apps and configurations from mobile devices

This week is all about a new feature that is specifically for mobile devices, and that feature is the ability to remove, reinstall, and re-apply specific configuration policies, configuration profiles, and apps. The best part is that it can be achieved without changing the assignments of those apps and configurations. That can be really useful to help with resolving specific challenges and to quickly restore the productivity of the user. The apps and configurations that were removed will automatically be restored within 8-24 hours. Alternatively, the IT administrator can also manually initiate an action to restore the removed apps and configurations earlier. So, in the end, the focus remains on ensuring that the devices remain consistent with the assigned apps and configurations. This post will …

Read more

Remotely locating corporate-owned Android Enterprise devices

This week is all about remotely locating corporate-owned Android Enterprise devices. More specifically, about the configurations that are related to remotely locating those devices. With one of the latest service updates of Microsoft Intune (2401) a new configuration was introduced to specifically block the location on corporate-owned Android Enterprise devices. That configuration, however, has a direct impact on the ability to locate those devices. Besides that, the availability of remotely locating the device depends on the Android Enterprise deployment method. So, multiple reasons why the ability of remotely locating devices could be unavailable. This post will focus on the available settings related to the location of Android Enterprise devices, followed with the steps to configure those settings. This post will end with the user experience. …

Read more

Getting started with Remote Help for Android

This week is back to the Android platform. More specifically, Remote Help for Android. Remote Help on itself is nothing new, as it was already introduced a while ago for Windows devices, but it is new for Android devices. Starting with the latest service release of Microsoft Intune (service release 2308), Microsoft introduced support for Remote Help on Android devices. More specifically, support for Remote Help on Android Enterprise dedicated devices. And even more specifically, only Samsung and Zebra devices. That enables IT administrators to provide remote support to users on Android Enterprise dedicated devices, by simply starting a screen sharing session or asking for full control. This post will start with a short introduction, followed with the steps to get Remote Help working for …

Read more

Welcome to the still growing Android device management jungle: A summary

The second short post of this week is another extension of one of my sessions at the Workplace Ninja Summit 2022. At the summit I did my second session about Welcome to the still growing Android device management jungle. During that session I shared information around the still growing device management options for Android devices, pointers that can help with making the right decisions and information around the different configuration options. This post will provide a quick summary of that session by going through the different management options, providing important differences and summarizing the main configuration capabilities. The slides (PDF) of that session are available for download here. Android (device) management options When looking at the Android (device) management options, there are many options. And the number …

Read more

Android Enterprise corporate-owned dedicated devices and Azure AD shared device mode

This week is all around the Android Enterprise corporate-owned dedicated devices deployment scenario. That deployment scenario is designed to address the typical kiosk-type devices, which are often referred to as the corporate-owned, single-use (COSU) use case. This week is specifically focused on enrolling those devices in to Azure AD shared device mode. That mode will provide users with a single sign-on and single sign-out experience across all of the participating apps on the device. In other words, users will be able to sign in to the device and will automatically be signed in to any participating apps. That enables an organization to provide a little personalized experience across dedicated devices that are shared between multiple users. In this post I’ll have a look at the …

Read more