Issue Encountered - enable TLS for the Azure SQL connector in Oracle FDI

PRATHEEK

@Ashish-Oracle @Dayne-Oracle @EloiLopes-Oracle @Benjamin Arnulf-Oracle

1.  Azure SQL TLS is set to 1.2
2. I'm pretty sure I can get the certificate for Azure but I know nothing about where Oracles trust store is, I've asked our admin and he too doesn't know, but he is investigating it.
3. This seems to be talking about using a different connection methodology - i.e. JDBC rather than Azure SQL. There are 5 different JDBC connectors listed in the FDI preview features, should I be trying to use one of these? (Oracle JDBC1-5, they seem to be clones of one another). The instructions also seem to talk about assembling connection strings but from what I've seen so far there is no ability to do this in FDI, we're just limited to what we can type in the connector setup form.

Azure SQL TLS is set to 1.2
2. There is no facility to add extra properties to the connection string, I am limited to only entering discrete items into the connection form.
3. I have no idea how I am meant to verify that FDI/Data provider supports TLS 1.2

Not a FDI - Oracle networking to be honest, but We really need someone to guide us through implementing this

Sumanth V -Oracle

@PRATHEEK - Azure SQL requires TLS 1.2 or higher, and most FDI connectors enforce this implicitly.
Please ensure that the Azure SQL server-level firewall rules allow access from the IP address used by FDI or the Remote Agent.

From the Azure SQL side, kindly verify whether the connection request from FDI is reaching the server. If not, check if it's being blocked by firewall settings or other network restrictions.

Since the connection from FDI is public (not private), no additional parameters are required to explicitly enforce TLS—it is handled automatically by the connector.