My first Elastic Job Agent jobstep to a privatelink sqldatabase target fails with "target principal name is incorrect." I can connect to servername.privatelink.database.windows.net and the specific database in SSMS with the same SQL login if I check "Trust Server Certificate" on the connection options, so the elastic job login, credentials, user are set up correctly. I don't see a way to specify Trust Server Certificate when setting up the jobstep. The Azure sql server has transparent data encryption enabled via a service managed certificate, as do all the databases on the sql server (via inheritance, i assume). Is there any way to force the job step to trust server cert? Thanks!
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
Azureand believe me: I don't receive more than 1-2 questions per week. Azure has not been adopted from a wide audience. Most of the companies do "Lift & Shift" and they basically migrate their servers to Azure VMs. Finding experts in Azure SQL DB or Managed Instance is not easy, that's why no one replied to your question. With SQL Server people copy/paste the code on their machine and they give you a reply but...