Artifact Signing individual Public Trust validation failed after successful Verified ID verification

Preserve the failed request and its Identity Validation ID, verify the Individual billing-account data, and request an Azure Support review before deleting it, because the portal does not document a self-service way to retrieve a silent failure category or verify backend correlation with the successful Verified ID transaction.

What “Verification successful” establishes

That message confirms completion of the Verified ID presentation step; it does not mean the overall Artifact Signing identity validation has completed. The Artifact Signing request continues processing afterward and reaches either Completed or Failed. Only a completed identity validation can be used for a certificate profile.^1^

There is no documented portal, CLI, or public API procedure that exposes the backend failure category or transaction-level association between that Verified ID result and the Artifact Signing request. Azure Support may be able to inspect the backend status and correlation, but disclosure of a specific category is not guaranteed. A comparable organization-validation case was resolved after support obtained the Identity Validation ID and account details for backend investigation; that is illustrative, not a guarantee of the same intervention or outcome for an individual request.^2^

Checks to complete before deleting or retrying

1. Record the current request details
   • Identity Validation ID and exact request name.
   • Artifact Signing account, subscription, tenant, region, and timestamps.
   • The primary email used to create and access the verification.
   • Any relevant notification emails and screenshots already available.
   • Note that Verified ID displayed Verification successful, followed by the request changing from Action Required to Failed.
   Keeping the failed request and ID may help support correlate the records.
2. Confirm eligibility
   • Individual Public Trust onboarding currently supports individual developers only in the United States or Canada.^1^
   • Artifact Signing does not support free, trial, or sponsored subscriptions. A paid subscription is required.^3^
   Because the Artifact Signing account was successfully created after conversion to pay-as-you-go, provide both the earlier failed deployment and the later paid-subscription request timestamps to support so the obsolete diagnostic is not mistaken for the current failure.
3. Check the selected billing account
   • Its Account Type must be Individual.
   • The legal first and last names must exactly match the government-issued ID.
   • The sold-to street, city, state/province, country, and postal code must match the government ID, utility bill, or bank statement used for validation.
   • The primary email must be the same email used to sign in and open the identity-validation link.
   Individual validation fields are sourced from the selected Azure billing account and are read-only in the Artifact Signing request. Corrections must therefore be made on the billing account before creating another request.^1^
4. If portal formatting cannot be corrected, the FAQ documents updating the sold-to address through Azure CLI. This changes the billing information for the account, so verify every value before running it.^3^

az billing account update \
  --name "<billing-account-name>" \
  --sold-to first-name="<first-name>" last-name="<last-name>" \
  address-line1="<address>" city="<city>" \
  region="<region>" country="<country-code>" \
  postal-code="<postal-code>"

When to delete and retry

The FAQ explicitly prescribes deleting the request, removing its associated Verified ID from Microsoft Authenticator, and creating both again when the reported error is address does not match, first name/last name not matched, or FaceCheck fail.^3^

For a silent generic Failed status, first preserve the request for support review. If support advises resubmission—or a billing mismatch is found—delete it through:

Artifact Signing account → Objects → Identity Validation → select request → Delete

A failed request is eligible for deletion because it is no longer In Progress. Deletion is irreversible. The confirmation pane shows associated accounts and certificate profiles; none should be linked in this case, but inspect it before confirming.^4^

Private support with Basic support

The official private intake is an Azure support request:

Azure portal → ? → describe the issue → Create a support request, or from the resource choose Support + Troubleshooting.^5^

Include the preserved Identity Validation ID and ask for:

• the backend failure category, if it can be disclosed;
• confirmation whether the successful Verified ID presentation correlated to that validation ID;
• review of the paid-subscription state versus the obsolete trial deployment diagnostic.

Owner access is sufficient to create a support request. However, Azure includes unlimited subscription-management/billing support, while technical investigation normally requires a paid support plan.^5^ The Artifact Signing FAQ also names Microsoft Q&A as a support option, but Q&A is public and is not a private channel for identifiers or identity evidence.^3^

References

1. Quickstart: Set up Artifact Signing | Microsoft Learn
2. Artifact Signing ID validation fails repeatedly 9afac007-6e27-4e93-84b1-34ac87fcdc90 - Microsoft Q&A
3. Artifact Signing FAQ
4. Renew or delete Artifact Signing Identity Validations
5. Create an Azure support request