I have a fully managed (by Microsoft Intune) Samsung Galaxy A34 phone, that comes with a system camera but no gallery. I have added a third-party gallery app to our managed Play Store along with a third-party camera app. The third party apps work along nicely, however, the system camera app tells me that there's no app associated for this action, when I tap on the miniature image that the camera app shows of the last photo that was taken. Is there a solution for this, or am I stuck with my third-party apps workaround?

We have a project and development within an Esri ArcGIS enterprise platform that will utilise the FieldMaps Android (standard Play Store) application. We need to work out how to side-load data (regional map data) onto the device within an MDM-managed environment. However, we are struggling to use Android Studio to create a fully managed device within a mobile device management platform. We have tried: - At AVD Creation, we don't get an option to allow the out-of-the-box experience (i.e. initially setup) to enroll a device into fully managed. - We have attempted to factory reset the emulated device but it never actually resets - We have been able to enroll a device as a work profile, but this isn't the same as a Managed Device. For a fully managed Android device, you press the screen 8 times at the setup stage and it asks how you want to enroll, but in the emulator, it bypasses this. Any way to get it back? Or is it a specific image we need or is it not possible?

I have made the observation, respectively some colleagues of mine, that some low-end phones struggle after being enrolled into our mobile device management (MDM). We use Microsoft Intune for that, but for this question, this shouldn't be relevant. Before rolling out the MDM, the low-end phones were used *as they were*, and some additional apps were installed for work purposes. Nothing too tasking. When we introduced MDM, all existing phones were automatically enrolled as *personally owned, work profile*. Hence, a work profile was created on them. Colleagues then remarked that certain low-end phones, specific models or makers aren't relevant here, have suffered severly performancewise. On the other hand, newly enrolled phones of the same model under the *fully managed* scheme, did not show any noticeable degradation in performance. Does creating separate profiles, one personal and one for work, in the enrollment into an MDM translate into an increase of the minimum requirements for RAM, the CPU etc.? Naively, or intuitively, this seems logical, since having two profiles and a set of duplicated apps running at the same time should result in more base-use of system resources. However, I couldn't find any information on this, as in "You must be this tall, to support a personal and a work profile". Is my hunch correct? Low-end phones being fine for single-profile use, but not for having two profiles.

We're trying to configure Intune so that people with Android devices can access their corporate email through Outlook for Android. In the Access Requirements blade (dashboard > client apps- app protection policies > intune app protection - properties), we've activated PIN (including simple PINs) and fingerprint for accessing the apps. Whenever a user tries to access the corporate email through Outlook, it's prompted to install the Intune app (company portal app) from the store. After doing that, the user is asked for a PIN after setting up the corporate email account in Outlook. After the specified timeout, the user will be asked for a PIN again. However, the app never allows the users to use fingerprints to unlock the app. It will only allow the user to enter the PIN. The Intune portal seems to imply that I should be able to use a fingerprint (instead of a PIN) to access the mail, but we've tried it on a couple of Android Devices (OnePlus 3T and 5T) and the fingerprint option is never shown. Any ideas on what's happening? Thanks.

I have a Huawei P20 lite, which reports (per System -> About this phone) an OS version EMUI 9.1.0, Android 9, Kernel 4.9.148, Security Patch Level of 1st January 2022. However, Microsoft Intune reports an OS version of Android 9.0 and a Security Patch Level of 2020-08-01. So, which is it? Is the 2022 patch level the patch level of the EMUI part of HUAWEI's Android variant, and the 2020 patch level the latest patch level of the underlying Android version?

Has anyone experience or knowledge of whether it is possible to deploy Android apps via Microsoft Intune when the source of apps is e.g. the F-Droid app store? I am considering setting up fully managed Android devices at work, and I am also quite fond of the idea of using open-source apps. However, installing F-Droid and giving the users the privileges to install apps somehow defeats the purpose and premise of the devices being fully managed.

I recently installed Microsoft Intune company portal on my Samsung Galaxy Note 10+ for work. Unfortunately, doing so resulted in the following change to my USB debugging settings: "Block - Prevent devices from using the USB debugging feature" . Once I discovered this, I fully uninstalled and unenrolled from the Intune company portal, however the USB debugging block remains. I did notice that I can toggle on and use USB debugging for 2-4 minutes after rebooting my phone, but after that, the switch instantly goes back to off when I try to enable it. I've tried resetting my phone settings, re-enabling developer options, and then trying to turn on USB debugging, but the setting still behaves the same. I've also tried the solutions here , but the setting remains disabled. Any help undoing what the company portal did to my phone would be massively appreciated. Note: I already disabled/uninstalled several apps potentially related to the issue via adb shell commands during the first few minutes after rebooting. If I knew which lingering app was responsible for enforcing the USB debugging block, I think uninstalling it would fix the issue. I've disabled several so far with no effect. Hoping to avoid a factory reset. Phone details/bug screen recording: https://drive.google.com/drive/folders/1uyIRKBnrpW4RH5hmlKJ2mAOMmJXt8j5d?usp=sharing

I used to have Outlook for Android installed on my personal mobile to access my work email which runs on Office 365. I reinstalled it recently only to find that now I have to install Microsoft Intune Company Portal and make it a device administrator to proceed with logging in (I couldn't get around it by restoring from a Titanium Backup of when I had it installed before). I think this is somewhat overkill when all the same information and more can be accessed via a web browser anyway, so I don't want to give Microsoft almost total control of my phone just to get my work email and contacts if I can avoid it. I tried the app Nine because I heard that it could set the security policies to be at the app level instead of the device lever, but when I logged in, I still got nothing except one email telling me I had to install Intune. The same thing happened with the Gmail app and Mailwise, but on those, I could see an empty version of my folder directory. Somehow logging in through Cloudmagic was actually seamless as far as grabbing my email, but it has no support yet for syncing contacts between Exchange and the device. I actually wanted the contacts *more* than the email in order to get some mobile numbers. So, what's the best way to work around Intune? Installing it but neutering it via Xprivacy or another permissions manager? Finding another app that will do for contacts what Cloudmagic did for email? I'm less concerned about adding my calendar.

After enrolling my Android device in the Intune company portal, I removed it from the company portal. Now, if I install any APK from other sources downloaded via Chrome, it keeps saying > Unkown apps can't be installed by this user. I tried to go to Settings -> Install unknown apps -> Files by Google -> Allowed, still the same error. Device admin apps are all off. Still getting the same error. --- This may answer it: https://support.google.com/pixelphone/thread/249737257/unknown-apps-can-t-be-installed-by-this-user