Getting error while trying to setup Deployment using Deployment Center

Question

I am getting following error while trying to use

Failed to set up deployment: Repository 'UpdateSiteSourceControl' operation failed with System.Net.Http.HttpRequestException: Response status: 409 (Conflict). Content: "Vso GetConnectionData: TF14045: The identity with type 'Microsoft.IdentityModel.Claims.ClaimsIdentity' and identifier '******@live.com' could not be found." at Microsoft.Web.Hosting.RegionalScaleClient.HttpLoggingHandler.<EnsureSuccessResponse>d__3.MoveNext() in //src/hosting/Microsoft.Web.Hosting/Utilities/RegionalScaleClient.cs:line 217 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.RegionalScaleClient.HttpLoggingHandler.<SendAsync>d__2.MoveNext() in //src/hosting/Microsoft.Web.Hosting/Utilities/RegionalScaleClient.cs:line 174 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.RegionalScaleClientExtensions.<AddVSOWebHook>d__29.MoveNext() in //src/hosting/AdministrationService/Microsoft.Web.Hosting.Administration.Api/Utilities/RegionalScaleClientExtensions.cs:line 403 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.VsoSiteRepositoryProvider.<UpdateSiteSourceControl>d__7.MoveNext() in //src/hosting/AdministrationService/Microsoft.Web.Hosting.Administration.WebCommon/Providers/VsoSiteRepositoryProvider.cs:line 72 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.Administration.WebCloudController.<>c__DisplayClass398_1.<<UpdateSiteSourceControl>b__1>d.MoveNext() in //src/hosting/AdministrationService/Microsoft.Web.Hosting.Administration.WebCommon/Controllers/WebCloudController.cs:line 11142 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Web.Hosting.AsyncHelper.RunSyncTResult in //src/hosting/Microsoft.Web.Hosting/Utilities/AsyncHelper.cs:line 27 at Microsoft.Web.Hosting.Administration.WebCloudController.UpdateSiteSourceControl(String subscriptionName, String webspaceName, String name, SiteSourceControl siteSourceControl) in /_/src/hosting/AdministrationService/Microsoft.Web.Hosting.Administration.WebCommon/Controllers/WebCloudController.cs:line 11137.

Answer 1

Hi @Amit

Thank you for posting your question on Microsoft Q&A.

This error occurs during Azure App Service deployment setup (Source Control / CI/CD) and is related to Azure DevOps identity mapping, not to your application code. Azure App Service internally attempts to create an Azure DevOps webhook, and when the associated user identity cannot be resolved, Azure DevOps returns a 409 (Conflict – identity not found) error. This behavior is expected and does not indicate a service outage.

This issue commonly occurs when:

• The Azure DevOps organization owner has changed
• The original Microsoft account (for example, @live.com) was removed
• The repository belongs to a different Entra ID (Azure AD) tenant
• The existing deployment connection has become stale or corrupted

As a next step, please try manual deployment using Local Git, ZIP Deploy, or deployment directly from Visual Studio to help determine whether the issue is specific to the Azure DevOps CI/CD integration.

Please feel free to post back if you need any further assistance or clarification.