Share via

Error upgrading Mysql connector(s) for Azure Data Factory/Synapse

Renald Noordam 0 Reputation points
2025-08-08T07:09:09.92+00:00

We are unable to successfully upgrade our MySql connector in Synapse (Linked service) to a newer version before the termination date of 30 September 2025. We have created a ticket in the past and the outcome of the ticket was:

"Resolution:  

There is an ongoing issue with the new version of MySQL connector. The product group has confirmed that they are actively working on updates to the MySQL V2 linked service to include properties currently available in V1 but missing in V2. These updates are expected to be released within the next two months. "

Time has passed and we are still in the same situation.
In the old situation the linked service works and a connection can be made. We currently are using this one for our daily ETL.
After the upgrade we encounter a few errors for two of our linked service related to SSL settings.

Settings Result
Settings Result
Default (old connector) Failed to connect to the mysql source, errorMsg: SSL Authentication Error. SSL Authentication Error. A call to SSPI failed, see inner exception. The message received was unexpected or badly formatted
TLS=1.2/TLS=1.3 Failed to connect to the mysql source, errorMsg: SSL Authentication Error. SSL Authentication Error. A call to SSPI failed, see inner exception. The message received was unexpected or badly formatted
SSLMode = disabled Failed to connect to the mysql source, errorMsg: Access denied for user  '[user]'@'[ip]'  (using password: YES). Access denied for user  '[user]'@'[ip]'  (using password: YES)
Default (old connector) Failed to connect to the mysql source, errorMsg: Access denied for user  '[user]'@'[ip]'  (using password: YES). Access denied for user  '[user]'@'[ip]'  (using password: YES)
TLS=1.2/TLS=1.3 Failed to connect to the mysql source, errorMsg: Access denied for user  '[user]'@'[ip]'  (using password: YES). Access denied for user  '[user]'@'[ip]'  (using password: YES)
SSLMode = disabled Failed to connect to the mysql source, errorMsg: Authentication method 'caching_sha2_password' failed. Either use a secure connection, specify the server's RSA public key with ServerRSAPublicKeyFile, or set AllowPublicKeyRetrieval=True..Authentication method 'caching_sha2_password' failed. Either use a secure connection, specify the server's RSA public key with ServerRSAPublicKeyFile, or set AllowPublicKeyRetrieval=True.

Is there any known solution available for our scenario?

Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Venkat Reddy Navari 5,330 Reputation points Microsoft External Staff Moderator
    2025-08-08T10:26:24.8633333+00:00

    Hi Renald Noordam Currently, there isn’t a fully supported fix for the MySQL V2 connector issue in Synapse that covers all the SSL and authentication scenarios like the older version did. The product team has acknowledged the gaps and is working on updates, but those updates are not yet released.

    As a workaround for your scenario, you can try the following:

    • Ensure your MySQL server supports SSL with valid certificates, and explicitly set the SSL mode to Required or VerifyCA in the connection.
    • Add AllowPublicKeyRetrieval=True in your connection string along with SSL enabled to handle the caching_sha2_password authentication error.
    • If possible, temporarily switch your MySQL user to use mysql_native_password instead of caching_sha2_password: 
        
  ALTER USER 'your_user'@'%' IDENTIFIED WITH mysql_native_password BY 'your_password';

    These steps have helped others facing similar issues while waiting for the updated connector.

    Hope this helps. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.