Share
Report
313I have an instance of SQL Server installed on an Azure VM which is accessed by multiple Power Apps, Automate and BI applications using the On-Premises Data Gateway, which is installed on the same VM.
The SQL Server instance is exposed to the internet on Port 1433, which I know is a security risk. (It was originally set up this way using an 'AllowAnyMS_SQLInbound' Network Security Group rule by a long-departed consultant.) But if I deny this exposure by deleting the rule, I lose access for my Power applications.
Is there a way to configure the gateway so that it communicates securely with SQL Server without having to open the port to the wider internet?
I've looked at the Network settings in the gateway itself but find these very confusing - they seem to be about how the gateway connects with the rest of the world, rather than with the server it is protecting.
I'm a real novice on networking. All my attempts to resolve this by normal searches just end in a minefield of acronyms I just don't understand. But I know my security is compromised and I need help to sort it.
All responses (
Answers (
