Sometimes you need to use Remote Desktop (RDP) to get into your cloud-hosted sandboxes for Dynamics 365 for Operations. Whether it’s to poke into a SQL database, clean off a full drive on a build machine, or… well, I can’t think of a lot of other reasons, but those are good ones.
As you should already know, to do this, you want to go to the Lifecycle Services (LCS) page for your VM and use the links (and usernames and passwords) there to RDP and log in. Those basics are out of scope for this blog post… but they should be pretty intuitive anyway.
But: For security reasons, you are now required to whitelist the IP addresses that are allowed to connect. If you don’t do that, you’ll get an error that looks like “Remote Desktop can’t connect to the remote computer…”:
Adding your IP address seems pretty easy at first. So, you happily pull up a Command Prompt, run IPCONFIG, and on the environments LCS page go to Maintain > Enable access:
“Easy!,” you think.
Then it still doesn’t work.
Here’s the deal: Most internet service providers (whether they be your home provider or your work/office) use different internal IP addresses than the ones they use out on the internet. To get the actual IP address that Microsoft’s filters think you are using, you need to ask the internet outside of where you are. Go to a site like http://whatismyip.host/ , https://www.whatismyip.com , or just search Google for “what is my ip address” to get it:
Plug in this IP address instead, and you’ll be good to go.
Just hope Microsoft doesn’t accidentally erase them. If you are managing this list for a bunch of other people, maybe keep a copy somewhere.