Artifact Signing Individual Identity Validation – “Address matching failed” despite matching address

Kim Hamdoun 0 Reputation points
2026-09-13T17:27:40.5633333+00:00

I am trying to complete Public identity validation as an Individual Developer for Azure Artifact Signing in the United States.

The verification repeatedly fails immediately with:

“Error: Address matching failed. Please confirm that the address on your Verified ID matches the address provided in your initial request.”

My government-issued ID and Azure billing information contain the same street address, city, state, and ZIP+4.

Troubleshooting already completed:

  • Successfully completed the government ID and face verification process previously.
  • Confirmed the street address and city.
  • Corrected the state abbreviation from lowercase to uppercase using Azure CLI.
  • Tested the ZIP+4 both with the hyphen and as nine digits without the hyphen, following Microsoft guidance for billing-address formatting.
  • Deleted previous failed identity validations and Verified ID credentials and created fresh validation requests.
  • The same “Address matching failed” error continues.

The current validation remains in Action Required status. Azure's automated troubleshooter was unable to determine the root cause.

Could someone from the Artifact Signing team please advise whether this is an address-normalization/Verified ID issue or whether the validation needs to be reviewed or reset on Microsoft's side?

I can provide the Identity Validation ID privately if a Microsoft representative needs it. I am intentionally not posting personal address information or account IDs publicly.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-13T17:27:55.05+00:00

    For this specific failure pattern, the supported remediation is to fully reset the individual validation flow and recreate it with a new Verified ID:

    1. Delete the existing identity validation request.
    2. Remove the associated Verified ID from the Microsoft Authenticator app.
    3. Create a new individual identity validation request.
    4. Recreate the Verified ID and ensure all information is entered exactly and accurately.

    For Individual identity validation, Microsoft documents the address does not match error together with first-name/last-name mismatch and FaceCheck failures, and the prescribed action is the full reset above.

    Since the request is still in Action Required, also verify these points before retrying:

    • The email address entered in the identity validation request is the same one used to sign in when opening the validation link.
    • The billing account address is entered exactly as it should appear. If portal formatting prevents correction, Azure CLI can be used to update the billing account sold-to address. This changes billing information for the account, so plan accordingly.
    • Use the same address details as they appear on the government-issued ID or supporting proof-of-address document.
    • If the verification link was missed or expired after seven days, a new identity validation request is required.

    If the issue continues after deleting the request, removing the Verified ID, and submitting a fresh request, the documented escalation path is to contact Azure Support or post on Microsoft Q&A with the artifact-signing tag. Microsoft also states that creating more in-progress requests for the same entity does not help, and requests cannot be expedited.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. kagiyama yutaka 5,330 Reputation points
    2026-09-14T03:01:59.5666667+00:00

    I think Azure checks the address against both the gov ID and the billing profile, and those already match. So when the same error keeps showing up even after recreating the validation request and the Verified ID, reaching out to support is the only move left, since the user‑side checks are already exhausted.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.