Security

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

Hi Herman,

thanks for clarification.

But how can I migrate for the time being from the "old" cluster to the new one?

Is there a way to install a new and an older Intune extension?

Thanks,

Erik

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

Probably, yes... you can install multiple Intune extensions in parallel. Just be a bit careful to prevent that both extensions synchronize to the endpoint database at the same time. For HTTP Authorization, it shouldn't be an issue.

Hi Herman,

thanks for clarification.

But how can I migrate for the time being from the "old" cluster to the new one?

Is there a way to install a new and an older Intune extension?

Thanks,

Erik

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

Is there a guide available how to install it?

My search results gave me only the latest version in the extension.

Regards,

Erik

Probably, yes... you can install multiple Intune extensions in parallel. Just be a bit careful to prevent that both extensions synchronize to the endpoint database at the same time. For HTTP Authorization, it shouldn't be an issue.

Hi Herman,

thanks for clarification.

But how can I migrate for the time being from the "old" cluster to the new one?

Is there a way to install a new and an older Intune extension?

Thanks,

Erik

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

In that case you may need to go through TAC. If you have the extension ID from your current installation, you may be able to install based on the ID, but not sure if older versions are still posted.

Is there a guide available how to install it?

My search results gave me only the latest version in the extension.

Regards,

Erik

Probably, yes... you can install multiple Intune extensions in parallel. Just be a bit careful to prevent that both extensions synchronize to the endpoint database at the same time. For HTTP Authorization, it shouldn't be an issue.

Hi Herman,

thanks for clarification.

But how can I migrate for the time being from the "old" cluster to the new one?

Is there a way to install a new and an older Intune extension?

Thanks,

Erik

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

Hi Herman,

thanks for clarification.

But how can I migrate for the time being from the "old" cluster to the new one?

Is there a way to install a new and an older Intune extension?

Thanks,

Erik

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

Even if you installed the old extension, there will likely be issues because Microsoft changed the Graph API behaviour that the extension uses.

Hi Herman,

thanks for clarification.

But how can I migrate for the time being from the "old" cluster to the new one?

Is there a way to install a new and an older Intune extension?

Thanks,

Erik

Erik,

That is expected. The newer Intune Extensions use different APIs (GraphAPI), instead of older (deprecated) APIs. Part of that is that lookup is done through the Intune DeviceID, no longer to the MAC address, except that you can use the sync option to sync Intune data to the Endpoint Database and lookup by (wireless!) MAC there.

I did a presentation at a recent event in Belgium, where the slides are posted here. It also explains why using the MAC address to lookup/link security data is a bad idea in many cases.

Is there a setup guide on Intune extension for 6.3.5. 

We did a upgrade from 6.10 to 6.11 and the intune extension didn't import. So I installed the latest 6.3.5 and I get the error:

[2025-03-05T11:03:02.401] [INFO] Intune - [20-1e-88-fb-f5-9f] Request for information received from ::ffff:172.17.0.1.[2025-03-05T11:03:02.402] [INFO] Intune - [20-1e-88-fb-f5-9f] Device not found.

I see from Herman's slides - he has "filters $(Certificate:Subjuect-CN)"

Just wondering if theres a guide that goes over this more in depth. Thanks!!

This is the latest version of the TechDocs. 

Looks like you're using the old way of intergration. Based on MAC address lookup. Latest versions will do a lookup using attributes information fetched from the certificate. This is documented in the TechDoc. 

Is there a setup guide on Intune extension for 6.3.5. 

We did a upgrade from 6.10 to 6.11 and the intune extension didn't import. So I installed the latest 6.3.5 and I get the error:

[2025-03-05T11:03:02.401] [INFO] Intune - [20-1e-88-fb-f5-9f] Request for information received from ::ffff:172.17.0.1.[2025-03-05T11:03:02.402] [INFO] Intune - [20-1e-88-fb-f5-9f] Device not found.

I see from Herman's slides - he has "filters $(Certificate:Subjuect-CN)"

Just wondering if theres a guide that goes over this more in depth. Thanks!!

This is the latest version of the TechDocs. 

Looks like you're using the old way of intergration. Based on MAC address lookup. Latest versions will do a lookup using attributes information fetched from the certificate. This is documented in the TechDoc. 

Is there a setup guide on Intune extension for 6.3.5. 

We did a upgrade from 6.10 to 6.11 and the intune extension didn't import. So I installed the latest 6.3.5 and I get the error:

[2025-03-05T11:03:02.401] [INFO] Intune - [20-1e-88-fb-f5-9f] Request for information received from ::ffff:172.17.0.1.[2025-03-05T11:03:02.402] [INFO] Intune - [20-1e-88-fb-f5-9f] Device not found.

I see from Herman's slides - he has "filters $(Certificate:Subjuect-CN)"

Just wondering if theres a guide that goes over this more in depth. Thanks!!

Willem will there be an updated version of the doc for 6.3.5? 

This is the latest version of the TechDocs. 

Looks like you're using the old way of intergration. Based on MAC address lookup. Latest versions will do a lookup using attributes information fetched from the certificate. This is documented in the TechDoc. 

Is there a setup guide on Intune extension for 6.3.5. 

We did a upgrade from 6.10 to 6.11 and the intune extension didn't import. So I installed the latest 6.3.5 and I get the error:

[2025-03-05T11:03:02.401] [INFO] Intune - [20-1e-88-fb-f5-9f] Request for information received from ::ffff:172.17.0.1.[2025-03-05T11:03:02.402] [INFO] Intune - [20-1e-88-fb-f5-9f] Device not found.

I see from Herman's slides - he has "filters $(Certificate:Subjuect-CN)"

Just wondering if theres a guide that goes over this more in depth. Thanks!!