Event details
We have recently begun deploying machines using Autopilot, and these machines are 100% cloud-based; the devices are only registered in Entra.
As they are purely cloud-based, they are not registered on our internal DNS, and this is causing us certain problems as their names cannot be resolved.
We haven’t found a document explaining the best way to get Entra devices to register with DNS so that their names can be resolved.
Could you please help us sort this out ?
- Jason_Sandys
Microsoft
Hi Sergio, DaveD-MS-CETS covered the answer here pretty well but I'm curious which tasks specifically that require client name resolution are causing you challenges?
Hi Jason_Sandys , DaveD-MS-CETS ,
Examples of the problems that have been reported to us are by our on-site teams:
- We can't ping those machines.
- It is not possible to connect to those machines via Remote Desktop.
- As the firewalls cannot resolve the names of those machines, they block access to OT environment.
- Jason_Sandys
Can you please expand on the scenarios where each of this is required or used and how not being able to do this impacts your business or users?
Also, have you explored using DHCP to register the devices in DNS as DaveD-MS-CETS called out?
- DaveD-MS-CETS
Hi Sergio, being cloud based, these devices won't be associated with internal DNS servers. If it's management tasks, such as sync, reset, remote control - Intune can provide those for Entra devices without needing internal DNS registration Device Actions - Wipe, Lock, Locate, and More - Microsoft Intune | Microsoft Learn Networks under your control, such as on-premises, could use DHCP server settings to set a specific DNS server. For public networks, DNS is typically via the network provider.
