devices
63 TopicsOneplus 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.26Views0likes2CommentsCommon 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 April79Views0likes1Commentunable 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.49Views0likes2CommentsWork profile on S25 Ultra
Just bought a Galaxy S25 Ultra a few weeks ago and unfortunately I'm not able to create a work profile with MS Intune. I've tried all workarounds that I found on Reddit and Samsung community (https://us.community.samsung.com/t5/Galaxy-S25/New-S25-Ultra-Unable-to-setup-work-profile-using-company-portal/td-p/3126410/page/29). I think that this can be related to some Android Enterprise support because I could not find any reference of the models when searching for it. Does anyone else are having issues when trying to create a work profile on S25 series?1.4KViews1like10CommentsHi, I try to enroll an andorid 12 aosp (raw and also with a shell, two versions). currently during provision, it is always stuck with the intune client screen(fetching intune authentic information) after scan QR code(generated for userless enrollment). MS is also help troubleshooting but it seems the broadcasting command was consumed somewhere and no trace on my device side(which they said it is weird). Anyone has experience with aosp Intune side can help? With compensation.
36Views0likes0CommentsHelp Needed: Support for Device Enrollment on Android (Corporate/Work Profile)
Hi everyone, I'm trying to set up device enrollment for Android devices, possibly for corporate or enterprise use (such as Android Enterprise/Zero-touch/Work Profile enrollment). However, I'm running into issues with device compatibility or support for enrollment features. Can anyone help clarify: What are the general requirements for a device to support corporate/work profile or Android Enterprise enrollment? Are there specific Android OS versions or manufacturers that limit this functionality? Appreciate any insights or guidance! Thanks in advance.28Views0likes2CommentsHELP! Enrollment Stuck on Choose Device Category
I need help. When enrolling a device on Intune, we are getting stuck on the Choose Device category page where it does not allow us to press the OK button. We have two vendors supplying us phones and the issue is happening with both vendors (devices are Pixel 8s and 9s). Please help!371Views2likes10CommentsAndroid Management API Returning HTTP 502
Hi, We have noticed that the Android Management API is currently not working. After a long delay, it returns an HTTP code 502 error. We have tested this across multiple accounts, and the behavior remains the same. Could someone provide clarification on this issue? Thank you.38Views0likes1Comment