Zoho Analytics - Action Required: Migrate SQL Server Connections

Zoho Analytics has revised its migration guidance for Microsoft SQL Server connections, replacing the previously shared cipher suite configuration with two supported migration paths that must be completed before the end of May 2026.

• This change applies only to users connecting to Microsoft SQL Server as a data source via direct cloud connectivity. Local imports already configured through Zoho Databridge are not affected.
• The previously shared cipher suite configuration is no longer the recommended path and is being retired in line with industry-wide deprecation of legacy cipher suites and outdated TLS protocols.
• You are likely to be affected if your SQL Server runs on an end-of-life version or on a host that supports only legacy TLS protocols and weak ciphers, such as Windows Server 2012, 2012 R2, or 2014.
• Recommended path: upgrade your SQL Server to a modern, supported version on an operating system that complies with current cryptographic standards. No further changes on the Zoho Analytics side are needed once the upgrade is complete.
• Alternative path: install Zoho Databridge inside your private network and move from direct cloud connectivity to local connectivity. Databridge handles JDBC connectivity and TLS handshakes locally, so legacy protocols are not exposed to the cloud.
• To migrate via Databridge, install the agent on a host with direct access to your SQL Server, complete setup using an Organization Admin or Account Admin account, and email support with your Workspace ID, existing connection name, and new Databridge agent name so the team can switch the connection.
• After the end of May 2026, scheduled imports on affected connections will fail at the next sync window, no new connections can be created or modified, and dashboards will continue rendering against the last successful sync without refreshing.
• If you are unsure whether your setup is affected, email support with your Windows Server version, SQL Server version, SQL port number, and Workspace ID for confirmation.