
You can contact my best friend and food provider with this form. Suggestions, corrections, and questions are always welcome! Please also message me French fries...

placeholder
All content and design elements on this website are the exclusive property of Josh Fridey and are protected by United States copyright and intellectual property laws. Unauthorized use, reproduction, or distribution of any material without prior written permission is strictly prohibited and may result in civil or criminal penalties.
This website includes third-party code, assets, or open-source libraries used under their respective licenses.
© 2025 JoshFridey.com. All rights reserved.
Website designed by AB Computer.
Remote Desktop Protocol (RDP) is an essential tool for IT professionals and end users alike, allowing seamless remote management and access to multiple devices. However, with the transition to Microsoft Entra ID (formerly Azure Active Directory), the traditional process of accessing remote devices has changed slightly, introducing a few additional steps.
In this guide, I’ll share my preferred method for accessing Microsoft Entra ID-joined devices via RDP. Keep in mind that there are multiple ways to accomplish this, some potentially easier. However, this method works effectively for both onsite and offsite configurations.
To ensure a successful remote connection, you’ll need the following:
Set a Static Local IP Address
Enable Remote Desktop Protocol (RDP)
Network Level Authentication (NLA), recommended enabled. Keep this checked for security. If you are having trouble connecting and suspect NLA is the blocker, you can temporarily disable it to test.
(For Offsite Access) Connect to VPN
Modify the Host File
Launch the Remote Desktop Application
Enter Login Credentials
By following these steps, you can successfully remote into a Microsoft Entra ID joined device using RDP. This method ensures compatibility with both onsite and offsite (with VPN) setups, allowing seamless access across different environments.