A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing identity verification stuck in Action Required — HTTP 409 errors
Hello,
I’m trying to complete identity validation for an Azure Artifact Signing account so I can digitally sign Windows desktop applications.
I completed the AU10TIX identity verification and facial recognition process, but my identity validation remains stuck in “Action Required”.
I encountered the following errors:
1. Identity verification error
- HTTP 409
- Message: “The targeted resource in CosmosDB already exists.”
2. Azure Activity Log error
- Code: RoleAssignmentExists
- A role-assignment creation operation failed because the same assignment already exists.
- Azure’s diagnostic tool identified this duplicate role assignment on my Artifact Signing account.
My Artifact Signing account is in the West US 2 region. Azure’s diagnostic tool found no relevant service-health incident.
I understand that the duplicate RBAC assignment may be separate from the CosmosDB identity-verification error.
My questions are:
- Could an existing or partially completed identity-validation record be preventing verification from proceeding?
- Does the existing RBAC assignment require any action, or can it safely remain in place?
- Can the Artifact Signing identity-validation team investigate or reset the conflicting verification state without requiring me to create a new signing account?
I have already completed the identity verification process and would prefer not to restart it unnecessarily.
Any guidance or assistance from the Microsoft Artifact Signing team would be greatly appreciated.
Thank you. UPDATE — Identity validation now shows “Failed”
Since posting this question, the situation has changed.
I completed the identity verification process, including facial verification, but my Azure Artifact Signing identity validation has now changed from “Action Required” to “Failed.”
The HTTP 409 RoleAssignmentExists error was also identified during troubleshooting, although I don’t know whether it is related to the validation failure.
My account is registered to WARETHORN, a Canadian sole proprietorship.
Could someone from the Artifact Signing team advise why the validation failed and whether it can be reviewed, reset, or safely resubmitted?
I would prefer not to delete and recreate anything until I understand the cause.