Artifact Signing organization identity validation failed after Authenticator showed "technical problem" when presenting Verified ID (Japan)

Question

Artifact Signing organization identity validation failed after Authenticator showed "technical problem" when presenting Verified ID (Japan)

英寿鈴山 0

Hello,

Our organization identity validation (Public Trust) for Azure Artifact Signing ended in "Validation Fail". The portal shows no failure reason, and we only have the Basic support plan, so we cannot open a technical support case.

Environment

Organization: a Japanese company (stock company, registered in Osaka, Japan)
Artifact Signing account region: Japan East
Identity type: Public, Organization
Requester name entered in the form in Japanese kanji (first and last name)
ID verifier: AU10TIX, using a Japanese driver's license (name in kanji only)

What happened (JST, UTC+9)

2026-10-16: Submitted the organization identity validation in the Azure portal.
2026-10-16 22:12: Received the email "Action required: complete the identity validation for Artifact Signing".
2026-10-17 ~15:26: Completed AU10TIX verification with the driver's license and received a Verified ID ("Government Issued ID - GLOBAL", issuer Au10tix) in Microsoft Authenticator.
2026-10-17 ~15:55: Scanned the QR code on the credentials.microsoft.com verify page. Authenticator showed the Verified ID and the Face Check result, both with green check marks. After tapping "Share", Authenticator showed: "We can't continue because of a technical problem with the request. Please try again later."
Reopening the verification link showed: "Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request."
2026-10-17 15:59: Received the email that the identity validation status was updated to "Validation Fail".

Questions

Can someone check the actual failure reason? Was it caused by the error during the Verified ID presentation, or by a mismatch (e.g. the requester name)?
The Japanese driver's license shows the name in kanji only. When we resubmit, should the requester first/last name be entered in kanji or in romanized letters?
What is the correct way to retry? Should we delete the failed identity validation and remove the Verified ID from Authenticator before submitting a new request? Is there a limit on the number of identity validation attempts?

We can share the subscription ID, tenant ID and identity validation ID privately.

Thank you.

小澤裕 0 Reputation points

2026-10-30T14:30:27.51+00:00
Sharing our experience: organization validation completed with a Japanese driver’s license (kanji only)

We are also a Japanese company (kabushiki kaisha), and our organization identity validation (Public Trust) for Artifact Signing has just completed successfully. We hope this helps others in the same situation.

Environment

Artifact Signing account region: Japan East

Identity type: Organization → Public

Business Identifier: D-U-N-S number

Organization name and address: entered in English (romanized)

Representative’s first/last name: entered in Japanese kanji, exactly as printed on the driver’s license (same character forms)

ID document: Japanese driver’s license (name in kanji only)

What happened

We submitted the request. The status changed to “Action Required” the same day.

We completed the AU10TIX check with the driver’s license and received a Verified ID in Microsoft Authenticator.

We scanned the QR code and shared the Verified ID. The desktop browser showed “Verification successful!”.

However, Authenticator on iPhone then showed an error: Error code 409, “The targeted resource in CosmosDB already exists.” We did not retry, and we kept the Verified ID in Authenticator.

A few minutes later, we received the email “Action needed: Verify your email account with Microsoft” from Microsoft Vetting Services. After we clicked “Verify email address”, the status changed to “In Progress”.

Some time later, the status changed to “Completed”.

Takeaways

A Japanese driver’s license with a kanji-only name worked, with the first/last name entered in kanji exactly as printed.

In our case, the 409 error in Authenticator appeared after the browser had already shown “Verification successful!”, and it did not affect the result. It seems to have been a duplicate submission. If you see this error, check the browser result and the portal status before retrying.

Before scanning the QR code, we updated Authenticator, fully closed and relaunched it, and used a stable connection without a VPN.

We can’t say whether this applies to every case, but we hope it is useful.Sharing our experience: organization validation completed with a Japanese driver’s license (kanji only)

We are also a Japanese company (kabushiki kaisha), and our organization identity validation (Public Trust) for Artifact Signing has just completed successfully. We hope this helps others in the same situation.

Environment

Artifact Signing account region: Japan East

Identity type: Organization → Public

Business Identifier: D-U-N-S number

Organization name and address: entered in English (romanized)

Representative’s first/last name: entered in Japanese kanji, exactly as printed on the driver’s license (same character forms)

ID document: Japanese driver’s license (name in kanji only)

What happened

We submitted the request. The status changed to “Action Required” the same day.

We completed the AU10TIX check with the driver’s license and received a Verified ID in Microsoft Authenticator.

We scanned the QR code and shared the Verified ID. The desktop browser showed “Verification successful!”.

However, Authenticator on iPhone then showed an error: Error code 409, “The targeted resource in CosmosDB already exists.” We did not retry, and we kept the Verified ID in Authenticator.

A few minutes later, we received the email “Action needed: Verify your email account with Microsoft” from Microsoft Vetting Services. After we clicked “Verify email address”, the status changed to “In Progress”.

Some time later, the status changed to “Completed”.

Takeaways

A Japanese driver’s license with a kanji-only name worked, with the first/last name entered in kanji exactly as printed.

In our case, the 409 error in Authenticator appeared after the browser had already shown “Verification successful!”, and it did not affect the result. It seems to have been a duplicate submission. If you see this error, check the browser result and the portal status before retrying.

Before scanning the QR code, we updated Authenticator, fully closed and relaunched it, and used a stable connection without a VPN.

We can’t say whether this applies to every case, but we hope it is useful.

1 answer

Your answer

Answer 1

Delete the failed validation, remove its related Verified ID from Authenticator, and submit a fresh Organization → Public request using the representative’s name exactly as printed on the Japanese driver’s license—kanji rather than an added romanization. ^1^ ^2^

Before resetting

Preserve the diagnostic evidence first:

Screenshots of the Authenticator technical-error message and green checks.
The exact timestamps, including the time zone.
The failed identity-validation ID.
Authenticator, OS, browser, and device versions.
In Authenticator, use the top-level menu → Send feedback to submit diagnostic logs. ^3^

Do not post subscription, tenant, validation, request, or correlation identifiers publicly.

The portal timeline does not establish whether the final rejection came from the failed Verified ID presentation, a name comparison, or another organization-validation check. The “link has been used” message only shows that the one-time presentation link was consumed. Only Microsoft’s validation team can inspect the backend transaction and provide the actual reason. Comparable cases with no portal reason required backend investigation. ^4^

Reset and resubmit

Deletion is irreversible, but a failed request cannot be reused through its consumed verification link.

In Azure portal, open the Artifact Signing account.
Select Objects → Identity Validation.
Select the failed validation and choose Delete.
Review the linked-account/profile information, then confirm deletion.

A validation can be deleted when it is not In Progress. You need the Artifact Signing Identity Verifier role. Deleted validations cannot be recovered; deletion can also affect linked certificate-profile renewal, although a failed validation normally should not have a usable profile attached. ^5^

In Microsoft Authenticator, open the Government Issued ID - GLOBAL credential associated with this attempt and remove it.
Before retrying:
- Fully close every Authenticator instance.
- Update Authenticator.
- Use a stable connection without VPN or proxy.
- Clear the browser cache or use another browser.
- If practical, use another phone.

These are Microsoft’s documented mitigations for technical errors during Authenticator/Verified ID processing. ^6^

Return to Artifact Signing account → Objects → Identity validations → Organization → New Identity → Public.
Enter:
- First Name / Last Name: the exact name displayed on the government-issued ID. Because the Japanese license contains kanji only, enter the corresponding kanji in these fields; do not independently substitute a romanized spelling.
- Organization name, business identifier, and registered address: the legal-entity information reflected in the applicable public records.
- Primary email: a monitored address on the company-owned domain.
- Secondary email: a different address whose domain matches the primary address.
Submit and complete the new email and Verified ID flow in the Azure portal. Identity validation cannot be completed through Azure CLI. ^2^

Failure reason and escalation under Basic support

Because the Basic plan is blocking an Azure technical-support case, continue through Microsoft Q&A with the Artifact Signing tag, which the Artifact Signing FAQ identifies as a support option. Ask a Microsoft moderator to arrange a private-data collection method and escalation to the Artifact Signing validation team. Ordinary community respondents cannot inspect backend logs. ^6^

Provide privately:

Identity-validation ID
Subscription and tenant IDs
Artifact Signing account and region
Exact timestamps and time zone
Authenticator feedback/log reference, if supplied
Screenshots with personal ID data and QR codes redacted

Do not change the primary email on another request unless Microsoft directs you to do so. The FAQ says another validation for the same organization using a different primary email requires support assistance. ^6^

Attempt limit

Microsoft documents three attempts only in the specific situation where additional documents were requested and all three document-submission attempts were exhausted. It does not state a general three-attempt limit for every organization-validation or Authenticator technical failure. ^6^

If the fresh request fails again, stop creating further requests and request backend escalation through Q&A; duplicate requests for the same entity do not help and cannot be expedited.

References