A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Force-close and update Microsoft Authenticator, clear the browser cache, retry on a stable connection without VPN or proxy, and use another mobile device if available; if AU10TIX still errors or Authenticator still reports “Card missing,” request Microsoft to investigate and reset the active validation.
Complete the remaining client-side checks
Using Safari and Chrome rules out one browser-specific issue, but the Artifact Signing guidance also specifies these checks for Authenticator and Verified ID technical errors:
- Force-close every instance of Microsoft Authenticator, then reopen it.
- Update Authenticator to the latest Android or iOS version.
- Clear the browser cache before opening the portal verification link again.
- Disable any VPN or proxy and use a stable Wi-Fi or mobile-data connection.
- If available, try the verification flow on another phone or device.
These are diagnostics for the AU10TIX/Verified ID flow; they are not a documented fix for the separate deletion conflict. ^1^
If the request remains stuck
Do not create additional validations while this one remains active unless Microsoft instructs you to do so. The FAQ states that creating more requests for the same entity while one is in progress does not help and that validation requests cannot be expedited. It lists Azure Support and Microsoft Q&A with the Artifact Signing tag as the assistance channels. ^1^
Update this Q&A post with a concise escalation request containing:
- Artifact Signing account name and Azure region
- Subscription type: pay-as-you-go
- Validation type: Individual / Public
- Identity-validation request ID
- Delete-operation correlation ID
- Approximate UTC timestamps of the latest verification and deletion attempts
- Exact messages:
- AU10TIX: “An error has occurred”
- Authenticator: “VerifiableCredential - Card missing”
- Portal deletion: “Request data is updated by some other source”
- Confirmation that the documented Authenticator, cache, connectivity, and alternate-device checks were completed
Ask a Microsoft moderator to route the case to the Artifact Signing team for backend state review and either a reset/new verification session or removal of the stuck request. Moderator escalation is a request, not a guaranteed support case, but a similar Artifact Signing validation case was resolved after the identity-validation and account details were sent to the internal team for backend investigation. ^2^
Do not post the subscription ID, tenant ID, billing details, identity documents, or other personal data publicly. Provide those only through a private channel if Microsoft staff requests them.
About deletion
Artifact Signing permits deletion when a validation is not in the In Progress state. It requires the Artifact Signing Identity Verifier role, plus read permission at subscription level or on all Artifact Signing accounts so the portal can identify linked certificate profiles. Deletion is irreversible and can affect signing or certificate renewal when profiles are linked. ^3^
Because deletion already reaches the service and fails with a concurrent-update message, repeatedly pressing Delete is unlikely to provide useful new information. If Microsoft clears the stale state and asks you to retry, first review the linked-profile list shown by the deletion blade, then delete only if no required signing profile will be affected.
A standard Azure technical support request normally requires a support plan; subscription-management support is available without one. ^4^ If the portal will not permit a technical ticket, continuing through this tagged Q&A post is the documented alternative for Artifact Signing identity-validation assistance.
References