Azure Elastic Jobs not able to run when using a private end point

Aaron Dunlop 1 Reputation point
2021-11-03T20:10:52.44+00:00

I cannot get elastic jobs to run when using a private endpoint. The jobdb resides on the same subscription but on a different SQL Server on Azure. We added a private end point between the job server and the Azure database server (Azure SQL Database) where the jobs run, both sql server's private endpoints are on a same subnet and same vnet. When running a test job "select 1" I recieve the following error message:

Failed to connect to the target database: A connection was successfully established with the server, but then an error occurred during the login process.
(provider: SSL Provider, error: 0 - The target principal name is incorrect.) (Msg -2146893022, Level 20, State 0, Line 0)

I am using the FQDN to connect "Server.database.windows.net" to connect to the database but this error keeps happening. Is this a known issue or is there something we need to configure differently on the private link to allow the elastic jobs to run?

Azure SQL Database
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Oury Ba-MSFT 16,081 Reputation points Microsoft Employee
    2021-11-10T18:16:21.373+00:00

    Hi anonymous user-5377 Thank you for posting your Question on Microsoft Q&A.

    Private endpoint is not supported when using elastic job on Azure SQL.

    You can migrate to SQL MI(managed instance) or use SQL Agent which provides similar functionality and that is currently supported.

    Hope that helps.

    Regards,
    Oury