The consumed verification link cannot be reused, so first ask Azure Support to identify the backend failure reason; then either reuse the existing valid Verified ID or perform a clean retry if support confirms that the credential or identity data failed.
1. Obtain the actual failure reason
Because the portal and notification email expose no reason, further client-side attempts cannot determine which validation stage failed. Similar Artifact Signing cases with a successful identity check followed by an unexplained Failed status required Microsoft to inspect the Identity Validation ID and account details in backend logs.^1^
In Azure portal → Help + support → Create a support request, provide:
- Artifact Signing account name and Azure region
- Identity Validation request ID
- Approximate UTC time of the Authenticator sharing attempt
- Current status: Failed
- Exact Authenticator sharing error, including a screenshot if available
- Confirmation that AU10TIX completed and the Verified ID was added
- Confirmation that reopening the original link says it was already used
- Any correlation or request ID shown by the browser, portal, or Authenticator
Ask support to identify whether the failure was:
- A Verified ID presentation/processing error
- An address, name, or FaceCheck mismatch
- A transient backend failure
- Another validation-stage rejection
Do not create several concurrent requests while waiting. Microsoft states that additional requests for the same entity while one is in progress do not help, and validation cannot be expedited.^2^
2. Retry according to the diagnosed result
If support identifies a transient sharing or processing error
Keep the existing Verified ID if it remains valid. Artifact Signing supports presenting an existing, non-expired Verified ID, so removing it is not automatically required.^2^
Before opening the new verification link:
- Fully close every Microsoft Authenticator instance.
- Update Authenticator to the latest Android or iOS version.
- Clear the browser cache or use another browser.
- Disable VPN/proxy and use a stable connection.
- If the sharing error recurs, try another supported phone.
These are Microsoft’s documented steps for technical errors during Authenticator and Verified ID validation.^2^
If support identifies an address, name, or FaceCheck failure
Perform a clean retry:
- Delete the failed identity-validation request.
- Remove its associated Verified ID from Microsoft Authenticator.
- Submit a new identity-validation request.
- Create a new Verified ID, checking that all identity information is accurate.
- For FaceCheck, use an adequately lit environment.
Microsoft explicitly requires both request deletion and Verified ID removal for these three failure categories.^2^
3. Safely delete the failed request when a clean retry is required
A request that is no longer In Progress can be deleted:
- Open Azure portal → Artifact Signing account.
- Select Identity Validation.
- Select the failed request and choose Delete.
- Review the listed Artifact Signing accounts and linked certificate profiles.
- Delete only after confirming that nothing active depends on it.
You need the Artifact Signing Identity Verifier role. The deletion is irreversible and can stop certificate renewal for linked profiles, so check the dependency list even if this is an initial setup.^3^
If New identity validation is unavailable afterward, verify that the same role is still assigned; identity validation itself is completed only through the Azure portal, not Azure CLI.^4^
In short: delete the failed request only when starting a replacement request, but remove the Verified ID as well only if it is invalid/expired or support confirms an address, name, or FaceCheck failure. For an unexplained sharing error, preserve the credential until backend diagnosis determines whether it is reusable.
References
- Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
- Artifact Signing FAQ
- Renew or delete Artifact Signing Identity Validations
- Quickstart: Set up Artifact Signing