Artifact Signing
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing organization validation Failed after representative verification, no reason or upload option, Basic support
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 55.00000000000001%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETA%3C/text%3E%3C/svg%3E)
TiTum Audio
0
Reputation points
Our US company, TiTum Audio, Inc., submitted an Organization/Public identity validation for Artifact Signing in East US. The representative reports successfully completing the requested identity-verification step. The request changed from Action Required on October 11 to Failed by October 12, 2026. Both the request list and details show Failed. The Microsoft Azure notification for this exact request says Validation Fail and directs us to the Portal, but gives no reason. The details offer neither a verification link nor a document-upload control. We have not found an additional-document request in the monitored primary mailbox or Junk. The primary and distinct secondary addresses use our organization's own domain. The Azure technical-support workflow blocks submission under our Basic support plan. No duplicate validation request has been created. Could the Microsoft Artifact Signing validation team advise: 1. How can we privately obtain the exact rejection reason and confirm whether representative verification was recorded? 2. Must the failed request be replaced, or can any required verification/document step be reopened? 3. Which organization/domain documents are needed, and what secure channel should we use to provide them? We can provide the validation/account identifiers privately to authorized Microsoft staff. We will not post identifiers, verification links, personal IDs, or company documents publicly.
Artifact Signing
-
TiTum Audio 0 Reputation points
2026-10-13T11:59:58.3+00:00 Update: representative verification fails with Authenticator timeout and tokenError/CosmosDB conflict
On October 13, 2026, TiTum Audio, Inc. submitted a replacement Organization/Public Artifact Signing validation. The previous Failed request was preserved. The replacement request has now also changed to Failed.
Clarification of our original report: the representative reports that the ID scan and face scan passed, but the final Microsoft Verified ID presentation did not complete successfully.
The desktop browser displays "Error: Face Check failed" and "Verification unsuccessful". Microsoft Authenticator provides these additional diagnostics:
- LocalNetworkException: Failed to send request because of timeout
- SocketTimeoutException: timeout
- SocketException: Socket closed
- Error Code: tokenError
- Server conflict: "The targeted resource in CosmosDB already exists."
The timeout occurred at 11:13:44 UTC and the server-conflict error at 11:14:21 UTC on October 13, 2026. These screenshots do not establish that a genuine facial mismatch is the cause.
Could the Artifact Signing / Microsoft Entra Verified ID team investigate the credential issuance/presentation transaction, including any duplicate or stale state after the timeout? Please advise whether the failed validation can be recovered, or whether the associated Verified ID and validation must be reset before a fresh ID/face scan. We would like to avoid repeating the same backend conflict.
The Artifact Signing FAQ describes deleting the validation and its associated Verified ID for FaceCheck failures under Individual identity validation. Our request is Organization/Public and the failure occurs while verifying its representative. Can that reset procedure be safely applied here, and would it clear the reported server conflict?
We can provide the validation ID, diagnostic Request ID, Correlation ID, device/app versions and original screenshots privately through a secure Microsoft support channel. Please tell us which channel to use under our Basic support plan. We will not post those identifiers, verification links, ID documents or facial images publicly.
Sign in to comment
Sign in to answer