{"id":741,"date":"2021-05-04T11:12:43","date_gmt":"2021-05-04T15:12:43","guid":{"rendered":"https:\/\/blog.markdepalma.com\/?p=741"},"modified":"2021-05-05T11:35:50","modified_gmt":"2021-05-05T15:35:50","slug":"intune-android-enterprise-work-profile-devices-no-longer-launching-dialer-for-telephone-tel-links-after-installing-zoom","status":"publish","type":"post","link":"https:\/\/blog.markdepalma.com\/?p=741","title":{"rendered":"Intune Android Enterprise Work Profile devices no longer launching dialer for telephone tel: links after installing Zoom"},"content":{"rendered":"\n

We recently came across an issue where after a recent Zoom app update anytime a user clicked a tel: link from within the work profile the Zoom app was launched instead of the native dialer. We first looked into what changed within the app in the release notes<\/a>. It was obvious that a change in 5.6.3 caused this:<\/p>\n\n\n\n

Support for tel: protocol links <\/strong>- Android\nUsers can tap a telephone number in an email or web page to call that number with Zoom Phone.<\/pre>\n\n\n\n
What is happening here is Zoom is now registered to handle tel: links and because it exists inside <\/strong>of the work profile it is taking precedence (the dialer is not really part of the work profile). This would have happened if we introduced ANY application that was registered to handle tel: links, but Zoom was the only one for us. What we need to do is bring the dialer into the work profile to give it precedence and to do that we use the ‘Android Enterprise system app<\/strong>‘ option to create instances of the native dialers in the environment. In our case we created one for the native (Google) Android dialer and one for the Samsung dialer. You may have other vendors in your environment so there may be others you need to add.<\/em><\/p>\n\n\n\n
First, we need a target group of devices. We could simply deploy the applications to all devices and it will take effect where applicable, but it is better to be more targeted and specific when possible. We already have two Azure AD dynamic device groups that target our Android Enterprise devices. You can also get more specific using properties like deviceManufacturer to target specific vendor devices.<\/em><\/p>\n\n\n\n
The first group is for our personally-owned work profile devices:<\/p>\n\n\n\n
\"\"<\/a>
Name: dyn All BYOD-Enrolled Android Devices
Dynamic Membership rule: (device.deviceOSType -eq “AndroidForWork”)<\/figcaption><\/figure>\n\n\n\n
The second group is for our corporate-owned devices (this technically will also target non-work profile Android Enterprise devices, but there is no harm in that<\/em>):<\/p>\n\n\n\n
\"\"<\/a>
Name: dyn All CORP-Enrolled Android Devices<\/em>
Dynamic Membership rule: (device.deviceOSType -contains “AndroidEnterprise”)<\/em><\/figcaption><\/figure>\n\n\n\n
Next, we need to create our dialer apps in Intune and assign them to our dynamic device groups. We are going to create one for the native Android dialer (com.google.android.dialer<\/strong>) and one for the Samsung dialer (com.samsung.android.dialer<\/strong>). The first time I attempted this I had an issue with the Samsung app installing because I had a capital ‘S’ in Samsung. Make sure the app id is all lowercase.<\/strong><\/p>\n\n\n\n