Home > Blog > How to Access Microsoft Azure SQL from a Self-Service Non-Production Environment

How to Access Microsoft Azure SQL from a Self-Service Non-Production Environment

Issue –

Microsoft will be removing remote desktop access to Sandbox Tier2 through Tier5 environments.

Question –

I no longer have Remote Desktop access to my sandbox environment.  How do I connect to Microsoft Azure SQL db  in my Sandbox environment?

Answer –

Microsoft provided the answer 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 LCS 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.

Firstly, 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 SQL Server Management Studio (SSMS). This step adds a SQL firewall rule and the rule will expire after 8 hours.

You may install SSMS on your local machine OR alternatively, you may use the SSMS on your developer box in the project

To request access to SQL – pick one of the options in the Reason for access field –

If you need to update the AX database for example, you will need to pick Performance tuning for AX (write to AX) and enter a reason in Details field and click Request Access.

You will need to refresh the page a couple times. Within a couple minutes you will see your temporary login information that you can use to login to SQL Azure server for your environment.

It will look something like this –

NOTE –

The first column contains the SQL server name AND the database name in this format (separated by “\”) – dbServerName\dbName. 

spartan-srv-nam-d365opsprod-b90492b86d59.database.windows.net\db_d365opsprod_ssitest_ax_20210118_05211896_e540

Then the second column is the SQL login name.

The 3^rd column contains the password for the SQL login.

In this example I want to connect to that SQL Azure server from my laptop. I downloaded SSMS 18.8 to my laptop.

Download SQL Server Management Studio (SSMS) – SQL Server Management Studio (SSMS) | Microsoft Docs

Launch SSMS

In the Server Name, copy the database server name from your LCS environment’s page.  That would be everything in the first column right up to the last character before the “\”. So, in this example the Server name is –

spartan-srv-nam-d365opsprod-b90492b86d59.database.windows.net

Select SQL server Authentication for Authentication field. Then enter your login and password.

Next, click on Options.>> button on the bottom right.

Click on the Connections Properties tab and enter the database name. (the stuff after the “server name\”

In this example, the database name is – db_d365opsprod_ssitest_ax_20210118_05211896_e540

Then click on Connect.

If the connection failed, check to make sure you have added the IP of the machine you are running SSMS on to Maintain> Enable access in the environment’s page in LCS.

Or if you are a partner, make sure you are not connected to another customer’s environment via VPN.

Source:

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

Enable just-in-time database access – Finance & Operations | Dynamics 365 | Microsoft Docs