Artifact Signing Public individual identity validation fails twice with no detailed reason

Question

Artifact Signing Public individual identity validation fails twice with no detailed reason

Matthew Hinson 0

I am trying to complete Azure Artifact Signing Public identity validation as an individual in the United States. Two individual validation requests have changed to Failed, but the portal's request details show no specific failure reason. I only saw Failed in the verification flow.

Before creating the individual requests, I corrected the Azure billing account's sold-to address. The latest failed request displays the corrected address and my legal first and last names. These match my government-issued ID, apart from Azure's postal normalization of the street suffix and ZIP+4.

The request's primary email matches the Microsoft account I used to open the verification link and complete the Microsoft Authenticator flow.

Azure's automated troubleshooting reports that the signing account was created successfully, the role assignment succeeded, and it found no relevant control-plane error or service incident. This is an automated assessment, not a confirmed explanation of the identity-validation failure.

My Basic support plan does not allow a private technical-support ticket. I would appreciate guidance from the Artifact Signing team on:

How can I obtain the failed validation stage or a specific rejection reason through an appropriate private channel?
Where can I confirm that the billing account has the required Individual account type? The billing properties page shows Microsoft Customer Agreement, which I understand is the agreement type rather than confirmation of Individual versus Organization.
Could Azure's address normalization matter when my ID uses a five-digit ZIP code or a different spelling of the street suffix?
Should I remove an existing Verified ID from Microsoft Authenticator and create a fresh one before retrying, even when the portal does not report a name/address mismatch or FaceCheck error?
Is there a recommended escalation path for repeated unexplained individual-validation failures without purchasing a support plan?

I can provide the validation identifiers and any required evidence through a verified private support channel. I have intentionally omitted personal information and account/resource identifiers from this public question.

I have not established a root cause and would prefer targeted guidance before creating more duplicate requests.

Matthew Hinson 0 Reputation points

2026-10-16T00:41:43.74+00:00
Update: After reviewing all four requests, I believe the failures relate to an address conflict rather than a technical error.

My government-issued ID shows my residential address. My business (a sole proprietorship, registered with my state's Department of Revenue) uses a different address.

My most recent organization request used the business address. An earlier organization request used my residential address with a slightly different street spelling than my ID. Both individual requests used the billing account's sold-to address, which is the residential address.

The billing sold-to block also shows an extra line containing only my first name, which may be in a company-name field.

Billing account Properties shows "Microsoft Customer Agreement" but does not show whether the account type is Individual or Organization.

All four requests show Failed with no reason and no pending step.

Questions:

When the address on my ID can't match my business address, which address should the billing sold-to and each request use?

For organization validation, can the billing sold-to address be set to the business address while individual validation uses the ID address, or do both have to match one billing record?

Should the extra first-name line in the sold-to block be removed, and how do I confirm the account type is Individual?

Is there a different validation path for a sole proprietor whose business and residential addresses differ?

I can share validation IDs and documents through a private channel.

1 answer

Your answer

Matthew Hinson 0 Reputation points

2026-10-16T00:41:43.74+00:00

Update: After reviewing all four requests, I believe the failures relate to an address conflict rather than a technical error.

My government-issued ID shows my residential address. My business (a sole proprietorship, registered with my state's Department of Revenue) uses a different address.

My most recent organization request used the business address. An earlier organization request used my residential address with a slightly different street spelling than my ID. Both individual requests used the billing account's sold-to address, which is the residential address.

The billing sold-to block also shows an extra line containing only my first name, which may be in a company-name field.

Billing account Properties shows "Microsoft Customer Agreement" but does not show whether the account type is Individual or Organization.

All four requests show Failed with no reason and no pending step.

Questions:

When the address on my ID can't match my business address, which address should the billing sold-to and each request use?

For organization validation, can the billing sold-to address be set to the business address while individual validation uses the ID address, or do both have to match one billing record?

Should the extra first-name line in the sold-to block be removed, and how do I confirm the account type is Individual?

Is there a different validation path for a sole proprietor whose business and residential addresses differ?

I can share validation IDs and documents through a private channel.

Answer 1

For a failed or unexplained Artifact Signing identity validation, the supported escalation paths are Azure Support or Microsoft Q&A with the artifact-signing tag. If another identity validation is needed for the same organization with a different primary email address, support is specifically required to continue onboarding. For repeated unexplained failures, Microsoft Q&A is the documented path when a private support ticket is not available under the current plan.
For Public Trust individual identity validation, the billing account associated with the subscription must have an Account Type of Individual. The agreement type such as Microsoft Customer Agreement does not confirm that requirement by itself. The documented guidance is to review and update the billing account legal name and sold-to address as needed through billing account management.
Address and identity details must match the government-issued ID used for validation. For individual validation, the legal name and sold-to address on the billing account must match the ID. If billing address formatting cannot be changed in the portal, Azure CLI can be used to update the sold-to address, including casing changes and removing hyphens that the portal cannot update. This indicates formatting can matter enough to require correction in billing data.

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

Note: this changes the billing information for the account, so the address should be entered exactly as it should appear.

Removing the existing Verified ID and creating a fresh one is recommended only for the documented error cases address does not match, first name last name not matched, or FaceCheck fail. In that case, delete the existing identity validation request, remove the associated Verified ID from Microsoft Authenticator, then submit a new request and create a new Verified ID. If those specific errors were not shown, that exact remediation is not documented as the general next step.
Before retrying, use the documented technical checks for Microsoft Authenticator and Verified ID:
1. Close all open instances of Microsoft Authenticator and relaunch it.
2. Make sure the latest version of Microsoft Authenticator is installed.
3. Clear browser cache or try a different browser.
4. Avoid weak Wi-Fi, VPN, or proxy connections.
5. Try a different device.
Avoid creating duplicate in-progress requests. The documented guidance states that creating more identity validation requests for the same entity while one is already in progress does not help, and requests cannot be expedited.
If the validation email link was missed or expired, a new identity validation request is required. The verification link expires in seven days and cannot be resent on the same request.
If the failure remains unexplained after the above checks, the documented assistance path is to post on Microsoft Q&A with the artifact-signing tag or use Azure Support if available. The context does not provide any other private self-service channel for retrieving a failed stage or backend rejection reason.

References: