I see the problem, and this probably is a question for Microsoft support. When I did a quick search, I could not really find how you can limit an Intune Wired profile to specific interfaces, or exclude interfaces.
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check
for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jun 18, 2025 12:14 PM
From: hornp
Subject: Windows 11 Wired TEAP Profile Issue
It did. The server name that I put here shows up in all three places - the "root" of the TEAP settings, and on the "Configure" for both the primary and secondary authentication screens. My problem is it's on ALL of my wired network adapters, virtual or physical.

Original Message:
Sent: Jun 18, 2025 11:45 AM
From: zshore
Subject: Windows 11 Wired TEAP Profile Issue
It put the server in and it checked the correct certs in that area?
Original Message:
Sent: Jun 18, 2025 10:30 AM
From: hornp
Subject: Windows 11 Wired TEAP Profile Issue
I was able to push a wired TEAP profile from Intune, and it did put the server in the root location as needed; I also found that It's pushing that profile to all of my wired adapters - including the PANGP Virtual adapter.
We're not ready to use TEAP for those VPN profiles, yet, and even if we could, that server also shows up in that setting. I can get around by checking the fallback option (but I'm not sure what that setting is when looking at the intune list).
Is there a way to prevent the virtual adapters from getting the policy?

Original Message:
Sent: Mar 27, 2025 01:58 AM
From: zshore
Subject: Windows 11 Wired TEAP Profile Issue
Intune does have a wired TEAP profile now. Let me know if you try it and experience the same.
I went the XML route and it works fine...just would be nice to use a profile. Submitted a ticket to MSFT on it.
Original Message:
Sent: Mar 26, 2025 01:44 PM
From: Herman Robers
Subject: Windows 11 Wired TEAP Profile Issue
I've not seen a TEAP or WiFi Profile in Intune, but may not have found it. Where did you find it?
For advanced configuration, like certificate selection or TEAP, use XML WiFi Export/Import
• Manually configure the SSID/Network on a Windows client
• Export XML of the settings:
netsh wlan show profiles
netsh wlan export profile name="ContosoWiFi" folder=c:\Wifi
• Create Intune Configuration Profile Windows 8.1 – Wi-Fi import
See attached for the steps and screenshots.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Mar 24, 2025 01:32 PM
From: zshore
Subject: Windows 11 Wired TEAP Profile Issue
Anyone having issues with the Intune Wired profile for TEAP?
I kept getting the "Client did not complete EAP transaction" error. After some digging I found that even though I specified all my trusted root CAs under "Root certificates for server validation" in the Intune profile they don't apply on this first screen here when you go to view settings in the network adapter, I have to manually check them:

But when I click the primary and secondary Configure options, all the cert auths are pre checked and working fine just as specified in my profile.
It seems like it needs the first page to be checked as well but somehow doesn't get the settings. This isn't great for scaling the solution. I would rather just set the Intune profile and be done, but it looks like I may still have to go with exporting an XML and deploying...
Has anyone run into this?