When using Network Policy Server (NPS) as your RADIUS server, authenticating Entra ID/Intune cloud-only devices does not work out of the box. NPS uses Active Directory for device authentication, and since Intune does not write back device objects to AD, this creates issues when devices exist only in the cloud without corresponding AD objects. This article guides you through how to fix this issue and enable authentication for cloud-only devices in RADIUS.
Note: If you’re not married to NPS, and are open to modernizing your RADIUS infrastructure, at the bottom of the article we use a cloud RADIUS service for Azure and Microsoft 365 to to simplify your RADIUS setup and allow you to turn off NPS forever.
One common workaround is creating “ghost” accounts in Active Directory that mirror your cloud-only devices. Here’s how this method works:
Since AD write-back for cloud-only devices has been an issue for years, the community has developed automated scripts for Intune device write-back. These scripts automatically create ghost accounts based on devices enrolled in Intune, ensuring NPS can locate corresponding AD objects during authentication.
If you are tired of managing NPS and don’t want to add additional hacks just to get Microsoft products to work together, you can use a cloud-based RADIUS solutions and forget about managing your own RADIUS service in NPS. These services integrate directly with Entra ID, eliminating the complexity of ghost account management.
One of the best things about EZRADIUS is that unlike many cyber security tools, you don’t have to do 300 calls just to get a demo, you can actually get started without ever talking to a human, you just need to register for a free trial on the Keytos website and follow the steps to set up your RADIUS clients and policies.
The video below walks through the steps to set up EZRADIUS and Intune for authenticating Entra ID cloud-only devices in less than 30 minutes: