Microsoft will be removing remote desktop access to Sandbox Tier2 through Tier5 environments. Here’s some help on how to access Microsoft Azure SQL from a self-service non-production environment.
Question –
I no longer have Remote Desktop access to my sandbox environment. How do I connect to Microsoft Azure SQL db on in my Sandbox environment?
Answer –
Microsoft provided the answers on self-service deployment here: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/deploymentfaq#i-dont-have-remote-desktop-access-to-my-sandbox-environment-and-the-critical-action-that-i-must-perform-isnt-listed-in-this-topic-how-do-i-get-help
Here are the detailed steps with screenshots to make it easier to follow:
In Lifecycle Services project, I selected the Sandbox environment, clicked on Full details – note the environment type is “self-service”.
You will notice account information and links to the machines are no longer available.
You will need to add the IP of the machine you will be using to connect to Microsoft Azure SQL. To add your IP to the safe list, go to Maintain > Enable access, then add the IP of the machine you will be using to connect via SSMS. You will need to install SSMS on your local machine. You may download SSMS from Microsoft’s web site OR alternatively, you can use the SSMS on your developer box in the project
To request access – pick one of the options in the Reason for access field –
If you need to update the Dynamics AX database with the move environment script, for example you will need to pick Performance tuning for AX (write to AX).
0 Comments