Can't add a new private app to a Collection in Managed Google Play Store (Intune)
Hello, i've recently published a new private app to our Managed play Store through the iFrame in Intune. I can assign the app now, install it and search for it on the Work Profile Play Store on my phone but i can't find the app when i want to add it to a collection. We have a few similar private apps already published and these work fine. It is only the most recent one i can't find in the collections. Is there another Sync i am missing or is it a problem with our Managed Play Store? Thanks for the help. BR Seb
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.
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
ATOK installation Failed in Corporate-owned devices with work profile
Hi, I have enrolled 2 samsung devices to intune using the Corporate-owned devices with work profile and assigned many applications to the devices. However, 1 specific application has failed to install stating the "country or region doesn't support this application." This is strange because in the same tenant I have other samsung devices enrolled as BYOD which is assigned this same application can install. I tried to reach out to intune support and they cannot do anything about this and asked me to raise ticket to google and I don't really know where I can raise the ticket to google regarding. Please help as I have to figure this out and deploy the application. PS: This application is available in the play store for the region and country. So the error message doesn't make sense. Thank you
Work 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?Device Admin App not present in work Profile
Hey Guys, I am enrolling a device in my MDM app as profile owner. A work profile was created but the MDM app with the device admin privilege is missing from the work profile . Has anyone come across such an issue before? If yes any help would be really appreciated . This is a Samsung M05 .Android 14 device.
Managed Google Play private app not available on Corporate-owned devices with work profile
Hi community, I'm encountering a strange issue and could use some guidance. A Google developer account released an app to Managed Google Play (so it's automatically private and not available on the public store) and entered our organization ID in the appropriate field. We can find the app on the iframe in our MDM (Microsoft Intune in this case), select it, and assign it to groups. Everything looks good: BYOD deployments (Personally-owned devices with work profiles) can install the app from the Managed Google Play store. However, COPE devices (Corporate-owned devices with work profiles) cannot search for it, and it's also not visible in the app collections we've created. Could there be a setting in the Google developer account's store listing that prevents availability for COPE devices? I've exhausted all options in Intune, including multiple store syncs, with no success. Intune is telling me, that the App is available to install on the specific COPE devices, but it does simply no appear. The only thing left to check is the Google developer account that released the app for us. Has anyone else experienced this issue? Any hints or suggestions would be greatly appreciated. Thanks! Walter
