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

jarmo_akkanen
Level 2.0: Eclair

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

1 REPLY 1

smithappdevjohn
New member

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