Recent discussions
Managed configuration to Gboard has disappeared from MDM
The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability. Environment: MDM = Omnissa Workspace One UEM (we are also hearing reports of this impacting SOTI customers as well) Rugged Zebra Mobile devices, majority running either A11 or A13 Leads: Managed App configs are still present on Chrome & ServiceNow Now Agent, hence why we believe this is not an MDM Console issue. We have escalated to Omnissa support anyway, who have in turn escalated to Google. Is anyone else seeing this issue?
Wifi profile on Android Enterprise via Intune
Hello All We have a problem with our Android devices enrolled as kiosk devices with Microsoft Intune. We set up SCEP and NDES to get certificates. All is set up correctly (We opened up a Intune support ticket for this issue, after 6 months the conclusion was that it is not an Intune issue, MS recommended to open up a Android support ticket..) We us a wifi profile, with al the recommended settings. Wifi profile comes trough on the device. But the settings are not filled in. We give the options like outer identity and use scep profile as user cert, but we still need to manually adjust the wifi profile. (despite the fact the wifi profile is applied correctly). we used this to setup our WiFi enterprise profile : https://learn.microsoft.com/en-us/mem/intune/configuration/wi-fi-settings-android#enterprise We use Zebra devices, so they use the oemconfig. we only use our oemconfig for specific settings. General settings, like wifi, we set up those trough Intune configuration profiles. Is there someone who encountered this issue as well?
Lost access to Google Account for Intune
Dear Community, I have a problem signing in to the Google Account that we are using for Intune. When trying to sign in we only get an error. It seems that the MFA method changed from Phone Call to SMS, and the registered number is from a VoIP system that can't receive SMS. Other account recovery methods don't work as we don't have enough information for recovery. Is there any chance that a support employee can help or swap the MFA method back to a phone call? Best regards, Thomas
Help Needed: Issue with Deploying Managed Google Play private App
I'm trying to deploy a Managed Google Play app on Samsung Galaxy tablets using Intune. The devices are enrolled as Corporate-owned with a work profile. The app is uploaded to the Play Console, approved by Google, and synced with Intune, but it's not deploying. Intune reports the devices as not applicable, and the app isn't visible in the work-badged Play Store. I've tried different assignment settings, switching between "required" and "available," and tested both user-based and device-based groups separately. I also experimented with BYOD enrollment types, but none of these approaches worked.
how to be partner of Google’s Device Lock Controller (DLC)
We are certified Android Enterprise Mobility Management (EMM) provider and an authorized Zero-touch Reseller based in Bangladesh. We specialize in enterprise mobility, with our proprietary MDM platform, MobiManager, actively used by leading organizations for secure device management at scale. In line with the growing demand for secure and inclusive smartphone access, we’ve developed PayProtect—a custom Device Policy Controller (DPC) tailored to support EMI-based smartphone financing. This solution enables real-time compliance, device-level control, and robust protection against default, thereby minimizing risks for telcos, lenders, and retailers. Now we want to integrate Google’s Device Lock Controller (DLC) for built-in solution for better performance. So how can we make partnership Google’s Device Lock Controller (DLC). Thanks in advance.
Oneplus Nord CE4 not in Android Enterprise Recommended (AER) devices list
Hello Everyone, I've noticed that the OnePlus Nord CE4 is not included in the Android Enterprise Recommended (AER) devices list, which can be found here: https://androidenterprisepartners.withgoogle.com/devices/#!?search=Oneplus. While the OnePlus Nord CE3 and CE4 Lite are currently listed, I'm curious to know when the OnePlus Nord CE4 might be added. Could someone provide insight into whether the OnePlus Nord CE4 will be added to the AER list in the near future? Your guidance would be greatly appreciated.
Common identifier between AMAPI & Require for setup app for validation
We are enrolling devices using AMAPI by generating a QR code with an assigned policy either for work profile or fully managed enrollment. During enrollment, the device prompts for a require for setup app, which, after configuration, returns RESULT_OK, marking the setup as complete and finalizing the device enrollment. Before returning RESULT_OK, To identify the enrolling device, the backend gets the device ID and enterprise ID from the Pub/Sub provisioning notification. The device ID (which matches the GSF ID) is then sent by the require for setup app to the backend for validation. This identifier is also used to enforce enrollment limits based on the enterprise license count. The Issue: Up to Android 14, retrieving the GSF ID was possible. However, in Android 15, it now returns null. Question: Is there an alternative identifier that can be used to identify the enrolling device—one that the backend can retrieve and that the setup app can also access during enrollment? Below is the information we receive from Pub/Sub when a device is enrolled: { "name": [*Hidden for privacy reasons] "managementMode": "PROFILE_OWNER", "state": "PROVISIONING", "enrollmentTime": "2025-04-04T06:17:02.751Z", "lastPolicySyncTime": "2025-04-04T06:17:02.817Z", "softwareInfo": { "androidVersion": "15", "androidDevicePolicyVersionCode": 10323580, "androidDevicePolicyVersionName": "128.32.3 (10323580)", "androidBuildNumber": "AP3A.240905.015.A2", "deviceKernelVersion": "5.15.149-android13-8-00010-gc2e0ba41ba85-ab12040008", "bootloaderVersion": "unknown", "androidBuildTime": "2025-03-11T13:26:50Z", "securityPatchLevel": "2025-03-01", "primaryLanguageCode": "en-IN", "deviceBuildSignature": "c9009d01ebf9f5d0302bc71b2fe9aa9a47a432bba17308a3111b75d7b2143456", "systemUpdateInfo": { "updateStatus": "UP_TO_DATE" } }, "hardwareInfo": { "brand": "Redmi", "hardware": "mt6835", "deviceBasebandVersion": "MOLY.NR17.R1.TC8.PR2.SP.V1.P51,MOLY.NR17.R1.TC8.PR2.SP.V1.P51", "manufacturer": "Xiaomi", "serialNumber": [*Hidden for privacy reasons] "model": "23124RN87I", "enterpriseSpecificId": [*Hidden for privacy reasons] }, "policyName": [*Hidden for privacy reasons] "memoryInfo": { "totalRam": "5865836544", "totalInternalStorage": "806965248" }, "userName": [*Hidden for privacy reasons] "enrollmentTokenName": [*Hidden for privacy reasons] "securityPosture": { }, "ownership": "PERSONALLY_OWNED" } *Updated by Community admin - removed due to privacy reasons 4 April
unable to enroll the Samsung S25 ultra into Intune as BYOD.
Hi Team, We are unable to enroll the Samsung S25 Ultra devices in Intune as BYOD. We are getting the "Can't add work profile " error during the enrollment process. So far we received couple of requests for same issue and the affected users count is increasing day by day. We have reached to Microsoft team as well, they suggested to check with Samsung team.
