Securly DNS + Intune

[Katy]

Hello,

 

Has anybody else experienced the same issue I am facing, or found a workaround? We have configured the DNS forwarding (so it requires the user to authenticate when they try to access anything filtered in the browser, but it doesn't require this for unfiltered sites e.g. Microsoft.com), however if we have a device which isn't logged on we find it won't check in to Intune, presumably being blocked by Securly (although nothing ever shows up in the Activity log). We can make the device check in if we log on to it and manually sync, but at this point it's installed the admin user's SmartPAC and authenticated. I don't want to have to do this with every device that comes back.

 

Similarly we get AUTOPILOTVETOESTS error when trying to build self-deploying PCs now (but only in 50% of cases), previously these were sporadic, although I've only tried 4 PCs since implementing the DNS setting so not sure if it is related, but we have 260 devices to go out in September.

 

Our devices have the browser extension and Smart PAC but we have added the DNS as a catch-all to make sure anything else on the network still gets filtered as we do not have any traditional on-site appliance any more.

 

There is very little on the Internet about this, very frustrating, so hoping somebody else has got Intune managed devices and the DNS filter method set up? Or do other people have a subnet without the DNS filtering for this kind of thing?

 

Cheers

 

Katy

[Katy]

Well, I think it might have been a red herring that I had so recently changed the filtering.... the PCs with AUTOPILOTVETOESTS worked after their third re-image from the Windows ISO/delete from Autopilot/re-add to Autopilot, and the laptops eventually synced after 5 restarts and an hour's wait.

[mjhardisty]

It's always useful to ensure that Intune, Entra, Microsoft, etc endpoints are excluded from any filtering/inspection to ensure service delivery.

https://learn.microsoft.com/en-us/intune/fundamentals/endpoints?tabs=north-america