Recent Android change regarding Wifi configuration
Hi everyone, I just want to share the current situation we are leaving in my company and that could be interesting for other Android customers as well. With the Android security update released in May 2023, Google has changed some requirements to connect on a corporate Wifi. The "domain" value has now to be filled in the Wifi profile that is pushed on the device, otherwise the profile will not install on the device and the wifi connection will fail: https://developer.android.com/guide/topics/connectivity/wifi-suggest "The framework enforces security requirements on TLS-based Enterprise suggestions (EAP-TLS, EAP-TTLS, and EAP-PEAP); suggestions to such networks must set a Root CA certificate and a server domain name." This change was not communicated to our EMM vendor or to us and we started to have a lot of device that were impacted. Moreover our EMM vendor was not supporting this additional parameter in the console UI and we are in the way to upgrade our platform to finally have this support in the very last version released this week. I don't know if we could be warned in advance regarding such kind of change in the community because it has very huge impact for us and I guess for other customers. LucNot able to print from Google Docs
Hi all, we provided Google docs, sheets and slides to our devices. We set managed app config (allow of using printing api and usage without Google account). We noticed now that printing is possible on sheets and slides but not on docs. Is there any known issue rgarding this? I mean I'm a bit confused because it works from the other two. Maybe Lizzie and ReeceK you kno more about that or can ask internally?
Android 14 - Android Enterprise WiFi Profile Issues - Microsoft Intune
With the latest Android 14 - new Microsoft Intune Android Enterprise device enrollments are not receiving the WiFi configuration profile. Android 13 and later will receive the WiFi profile and connect to the hidden SSID with no issue.
Renaming Managed Google Play Organization
Hello, we built our Managed Google Play connector in Intune like three years ago with our company name as organization name. Meanwhile our company name as slightly changed and since the company name is shown on all corporate-owned android devices lock screen, we have a high interest in changing that to the correct name. Unfortunately I can not find any way to change that company name. I can only delete that organization. I do not find a way to contact Google directly for that issue, so that is why I ended up here. So here are the questions: What exactly happens to our devices, if we disconnect and delete the organization and reconnect to a new organization with correct name? All devices will reset? All apps will be gone? Are there other ways to configure what is shown on the lockscreen? Maybe it is possible to disable the display of the company name on the lockscreen completely? Or is there a way to contact Google to change that name for us? Any help appreciated. 😎 Regards
Understanding Automatic Operating system update behaviour
I'm hoping to get a better understanding of the SystemUpdateType policy available for COWP devices, we're currently moving from POWP to COWP for our devices (40K) and are looking to benefit from streamlining as much as possible for our end-users. Looking at the documentation for the SystemUpdateType policy it isn't described as to whether the Automatic update option would force an Operating System update even if the device is in active use (User on a call, App open and in use etc). Does anyone have detailed information as to how the Automatic update option works? I'm hoping to get a reply from a google employee on this if possible. Below is the link to the documentation for anyone interested. https://developers.google.com/android/management/reference/rest/v1/enterprises.policies#systemupdate:~:text=accept%20system%20updates.-,AUTOMATIC,Install%20automatically%20as%20soon%20as%20an%20update%20is%20available.,-WINDOWED Thanks for your help.
Intune - Google Managed Play issue cannot complete the bind
Hi Everyone, sitting with an issue on three O365 tenants at the at the moment that I have escalated to Microsoft. Was hoping that someone else experienced this issue as well or can point me in the right direction. After opening the connector to bind the EMM (Intune) to the google play store the I grant Microsoft permissions to send both user and device information to Google is greyed out. I can close and the window and then reopen it and I can then tick the box. After that the Launch Google to connect now Button becomes available and the windows that pops up asks me to sign in with my google account. I have created numerous accounts, personal, work and school and tested with them. After the login into the google account it does not continue with the EMM setup. the box displays "The Page has expired. To restart your registration, please reload the page from your EMM console. Only way past that is to log out of the Gmail Account and then log in again with the same issue "The page has expired......" I have tried the connection from different devices, browsers, incognito... on different networks and have even tried it from a device with a vanilla install, Windows 10/11 and nothing helps. I have created different accounts on Google, personal, work and school etc, and the same issue. After logging in I can click on the google play icon in the left upper side and it shows the apps in the play store. I have attached screen shots.Android 15 - Cannot set default password app
We use Microsoft Intune to manage devices. For the devices which have upgraded to Android 15, the end users can no longer select Microsoft Authenticator as their default application for auto filling passwords. I cannot find any settings in Intune to allow it. All devices are fully managed corporate owned devices. The devices are all Google Pixel 8 or 8a devices. Is this a bug in 15 or am I missing something?  
