Non-breaking error AADSTS50196 at end of SQLPackage.exe deployment

Darren Gulliver 21 Reputation points
2022-07-20T14:16:07.837+00:00

Hi,

As the title suggests I'm getting this error when deploying to an Azure DB Elastic Pool.
222755-image.png
You can see in the image I have enabled debugging but no further messsages as to why I'm getting this.

I did find this question Non-breaking error AADSTS50196 at end of SQLPackage.exe deployment to Azure SQL Database using Azure Active Directory Password authentication but I'm not sure if this is exactly the same scenario mainly because I'm not seeing Auth0 errors like the poster in the question. Same as the poster the deploy does run successfully but it does take around 10 minutes per environment.

I'm deploying the dacpac via pipelines using the sqlpackage command as follows
222700-image.png

The connection string is as follows (which is stored in Azure Key Vault).
Server=#####.database.windows.net, 1433;Authentication=Active Directory Password;Database=####InvoiceDB_Dev;User Id=svc-invoice@#####com;Password=###

I know there is a known issue Increased deployment time due to MSAL throttling but again I'm not 100% if this relates to me.

Any advice would be appreciated.

Regards,
Darren

Azure SQL Database
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,392 questions
0 comments No comments
{count} votes

Accepted answer
  1. Oury Ba-MSFT 16,076 Reputation points Microsoft Employee
    2022-07-20T17:59:17.54+00:00

    Hi @Darren Gulliver Thank you for posting your question on Microsoft Q&A and for using Azure services.

    I am sorry to hear that you are having issues when deploying an Azure SQL database elastic pool.

    *I did find this question non-breaking error AADSTS50196 at end of SQLPackage.exe deployment to Azure SQL Database using Azure Active Directory Password authentication but I'm not sure if this is exactly the same scenario mainly because I'm not seeing Auth0 errors like the poster in the question. Same as the poster the deploy does run successfully but it does take around 10 minutes per environment. *

    The "client loop" error is the same. This is the fix in this GitHub issue provided by our Product group? https://github.com/microsoft/DacFx/issues/92

    Please let us know if that works

    Regards,
    Oury


0 additional answers

Sort by: Most helpful