I’m trying to create a small project using the instant setup.
the project name is Trombi.net
I’m running on Azure SQL Database (so technically MsSQL)
I get this error when filling my connection string:
I already added the forest admin IPs to my white list.
Do you have any idea ?
Hello @Simon_BRAMI1,
Did you try authorizing your own IP and open the DB from your computer?
I think that the IP address 127.0.0.1 in the error message is not correct, but it’s due to the internal implementation for opening requests with the same static IP address.
Which IP address did you authorize on your DB?
Hello @Simon_BRAMI1,
So you have followed the following link https://docs.forestadmin.com/documentation/extra-help/setup/forest-admin-ip-white-listing-forest-cloud
We got two kind issues from your tries:
Unable to connect to the given uri: mssql://XXXXXX.
Connection error: Server requires encryption, set ‘encrypt’ config option to true.
Unable to connect to the given uri: mssql://XXXXXX.
Access denied error: Cannot open server “127.0.0.1” requested by the login. The login failed.
Unfortunately, I don’t have an Azure SQL Database to try it myself.
Looking at some threads on the web, It could be an issue with SSH tunneling.
They propose a workaround, add the username to the URI:
mssql://username@yourdb.database.windows.net
Also please check that in the Azure SQL server the port 1433 should be opened or add a new inbound rule with this port.
Let me know if it helps.
Kind regards,
Morgan
What is the difference between columns 2 and 3?
It’s just in case I need to setup IP ranges 
My username and password are already filled in the URI, the port 1433 is also already setup by default
My URI looks like this:
mssql://<user>:<password>@fr-trombinoscope-sql.database.windows.net:1433/fr-trombinoscope-sql-prod
By the way this issue is only if I don’t require TLS so you can consider it “fixed”
the way this issue is only if I don’t require TLS so you can consider it “fixed”
Indeed, Azure SQL Database needs TLS/SSL.
I just doubled check the Azure SQL Database documentation for Node.js and mssql driver.
I don’t understand what could cause the issue. There maybe a specificity that we have missing with AZURE_SQL_AUTHENTICATIONTYPE=azure-active-directory-default
We will try to set up this on our side and try to understand the root of this issue. I will keep you updated when we have some more news. 
Some Azure resources on this topic for reference:
Kind regards,
Morgan
By default Azure SQL Database is usable with User and Password created during setup, I have never used the “Active Directory” auth.
Also, when configuring other Forest projects by setting my own backend, I use the same mssql:// URI format to connect to Azure Databases which works fine 
Don’t know if it will help, let me know how your investigation goes!
Superbe that’s very interesting since we have some specific handling in the Cloud to keep your URI secured.
Be sure that we will keep you updated but it might take a few days to put all of it together.
Kind regards,
Morgan
Thanks man
Let me know if you need me to test things
Hello @Simon_BRAMI1,
We have conducted some tests and we have run into the same issue as you Cannot open server “127.0.0.1” requested by the login.. Even though, it is likely a side effect of another issue (we need more time and extended tests to verify this).
We think that we encountered an issue close to the following: MSSQL - tables in a non "dbo" schema preventing onboarding
Mainly, we don’t support schema correctly during DB introspection. We have already started to work on this issue.
I will inform you once we have more information/news.
Kind regards,
Morgan
Hello Morgan,
If that can help, the schema hosting my business tables is dbo
Good luck with that issue.
Hello @Simon_BRAMI1,
Well, it took a while to fully investigate this one. First, I want to thank you for your feedback.
We detected an issue in our fixed IP (used for whitelisting) functionality thanks to you.
For now, we decided to remove the MSSQL Cloud onboarding since the issue cannot be tackled right away.
We will investigate more time in the future to reenable it for the cloud onboarding.
We will update you when the situation comes back to normal. Let me know if you have additional information.
Kind regards,
Morgan
