Original Message:
Sent: Dec 19, 2024 10:36 AM
From: Shadow101
Subject: Comparing different Endpoint Attributes for 802.1x Authentication - ClearPass 6.12.3 and Intune Extension 6.3.5
Yeah, DeviceId will be the best option to match on - we found the following links really good as we started the process of certificates and Intune;
https://www.arubanetworks.com/techdocs/NAC/clearpass/integrations/unified-endpoint-management/intune/#appendix-e--scep-certificate-configuration-profile
https://community.arubanetworks.com/viewdocument/atmosphere23-belgium-brussels-202?CommunityKey=07affbbb-b455-4b3e-be10-01880637640c&tab=librarydocuments
(about the six one down on AzureAD and Intune by Herman Robers)
Hope that helps,
Original Message:
Sent: Dec 19, 2024 07:28 AM
From: emzed
Subject: Comparing different Endpoint Attributes for 802.1x Authentication - ClearPass 6.12.3 and Intune Extension 6.3.5
Thank you both for the quick answers!
Unfortunately, I suspect that I have not expressed myself correctly. Part of our problem is that the devices log into the network with different Mac addresses. Sometimes there are also old Mac addresses in the device database which are synchronized by Intune.
How can we ensure that the device is still recognized correctly?
Our common factor here would be the Intune Device ID, which matches the Certificate CN.
Is there a way to set the attributes the same or to trigger a synchronization?
Best regards Marc
Original Message:
Sent: Dec 19, 2024 03:20 AM
From: GorazdKikelj
Subject: Comparing different Endpoint Attributes for 802.1x Authentication - ClearPass 6.12.3 and Intune Extension 6.3.5
Hi Marc.
You can always test your role mapping or enforcement policies with Simulation. You can compare two attributes.

Best, Gorazd
------------------------------
Gorazd Kikelj
MVP Guru 2024