Basic WiFi-profiles (configuration profiles) do not deploy into Device

[jarmo_akkanen]

Dear all,

Since three weeks ago we noticed issue to deploy basic Configuration profiles (WiFi) into devices (MDM is Intune). Problem ONLY occurs with newly enrolled COPE devices running on Android 15.

So we think it's Android 15 (Google) issue on COPE enrolled devices because all the other scenarios working fine:

• BYOD enrolled devices get WiFi profiles successfully deployed to device (Android 14/15)
• COPE enrolled devices get WiFi profiles successfully deployed to device (Android 14)
• COPE enrolled devices do NOT get WiFi profiles successfully deployed to device (Android 15)

Anyone else noticed the same/similar issue with Configuration profiles with Android 15 clients?

Best Regards
Jarmo

[smithappdevjohn]

Here’s a thoughtful response you can post on the discussion forum:

Hi Jarmo,

Thank you for bringing up this issue. It does seem like a potential Android 15 compatibility problem with COPE devices in Intune, especially since other enrollment scenarios and versions (like Android 14) are working fine.

A few troubleshooting steps you might consider:

1.  Check Intune updates: Ensure that your Intune configuration is up-to-date. Sometimes Microsoft releases patches to address new OS compatibility issues.
2. Review Android 15 release notes: Look for any known issues related to WiFi configuration profiles or COPE enrollment. Google may have acknowledged this in their documentation.
3. Test with different WiFi profiles: If possible, try deploying a simplified WiFi profile to see if there’s a specific setting causing the problem.
4. Logs and diagnostics: Collect logs from a test COPE device on Android 15 to identify where the deployment is failing. The Intune Troubleshooting + Support feature might also provide some insights.

If the issue persists, it might be worth raising a support ticket with both Microsoft and Google. Cross-verifying with others in the community (as you’re doing here) is also a great step—I’ll keep an eye out and share if I encounter anything similar.

Best regards,
smithjohn

[mattdermody]

Did you really just copy and paste something from GenAI? 

"Here’s a thoughtful response you can post on the discussion forum:"

[jasonbayton]

😂

[Moombas]

@jarmo_akkanen Such issues are most likely issues on the MDM (like Intune, Soti,...) or OEM (Samsung, Zebra,...). Google is not the provider of the OEM as the manufacturers always are the ones working on it.

I would recommend to raise this on OEM Manufacturer side as your A14 works and stopps working with A15 or even to both as maybe something in A15 changed on COPE devices regarding Wifi management on API side.

And if the OEM (and/or MDM) support gets to the result that there's a general issue on A15 regarding this, they can reach out directly to Google to solve it.

[jarmo_akkanen]

Thank you @Moombas and @smithappdevjohn for your replies, much appreciated. We (SAP) have Premium Service agreement with both Microsoft and Google. I have opened cases for both.
Google already mentioned they have another customer experiencing same issue. I'll keep you posted once we get more info. 

UPDATE Info:
We only have Samsung and Google Pixel devices in use and this issue only occurs with Google Pixel devices. But I think it's because we don't have any Samsung devices running on A15 at the moment.

Thanks 
Jarmo
  

[Moombas]

Ok in case of the Pixel devices, ofc Google is responsible from OEM side 😉 But very interested in the result, looking forward.

[jarmo_akkanen]

@Moombas @smithappdevjohn 
Latest info from Google engineers:

We tested it on Intune and Knox Manage EMMs and WiFi configuration is NOT working on A15 and COPE mode.

However, using our vanilla test DPC it's working properly on the same device and configuration.

After all.. might be something EMM (Intune) related.... I'll keep you posted 

-jarmo

[jasonbayton]

COPE in particular for 15 seems exceptionally buggy. I've documented a few of the issues I've found so far here and it wouldn't surprise me to see this is another issue. 

[jarmo_akkanen]

Hi colleagues, 

*UPDATE*

We have done lot of testing related to this basic Wi-Fi profile deployment issue. We believe it's Android 15 + COPE issue because all the other scenarios working fine:

• BYOD enrolled devices get WiFi profiles successfully deployed to device (Android 14/15)
• COBO enrolled devices get WiFi profiles successfully deployed to device (Android 14/15)
• COPE enrolled devices get WiFi profiles successfully deployed to device (Android 14)
• COPE enrolled devices do NOT get WiFi profiles successfully deployed to device (Android 15)

At the moment Google passed the case to the wifi team for any changes in the Android V that might be rejected in the ONC (open network configuration) specifications. I'll keep you posted.....

@jasonbayton @mattdermody @Moombas @smithappdevjohn 

Thanks
Jarmo

[jasonbayton]

Awesome effort mate, thank you!

[Rakib]

We just did the testing our self and can also confirm COPE enrolled devices do not get deployed. Intune reports the profile have been sent successfully, but no wifi profile on the device. This was tested on a Pixel device.

• COPE enrolled devices do NOT get WiFi profiles successfully deployed to device (Android 15)

[jarmo_akkanen]

Hi @Rakib @jasonbayton @Moombas @mattdermody @smithappdevjohn 

Root cause found!

We just got the new important information from our Google Technical Account Manager. 

“According to Google engineering this issue should be fixed in CloudDPC v124, due for production at the end of January.”

Referring to info from Google, issue seems to be on Google side after all. I have asked more details from Google. 

Could you please open issue resolution bit more? So, Google will make some configuration changes to CloudDPC and this goes to production end of January 2025? I mean... is the configuration (configuration update missing) the root cause which keeps Wi-Fi profiles failing to deploy Android 15 devices enrolling as COPE? Does this require some action from our end and/or from Microsoft to get those changes implemented to EMM (MS Intune) once in production from Google?"

I'll keep you all posted once getting answer.

thanks

Jarmo

[jeremy]

If this is fixed using a CloudDPC update, there will be nothing else to do on the EMM side, you will just need to wait until the new CloudDPC version is avaiable, if your EMM support this you can retrieve a device report and see the current "com.google.android.apps.work.clouddpc" version. I'm not sure how the update mechanism works for the CloudDPC if this is linked or not to Play Services but I'm confident @jasonbayton might know this 🙂

[jasonbayton]

It rolls out ad-hoc. They just pushed a fix for delegated scopes this last week too 🙌