Individual validation (Canada): Verified ID presentation fails with tokenError "resource in CosmosDB already exists"

Open an Azure technical support request and ask the Artifact Signing team to investigate the failed transaction and, if appropriate, clear or resume it; do not submit a fourth validation while the existing request remains in progress.

The Cosmos DB message is consistent with a backend conflict, but it does not by itself prove that a stale presentation record is the cause. Similar Artifact Signing incidents have occurred after the ID and face checks, and Microsoft advises that creating additional requests for the same entity while one is in progress does not help.^1^^2^

Escalate the current transaction

1. In the Azure portal, open Help + support → Create a support request.
2. Select:
   • Issue type: Technical
   • Subscription: The subscription containing the Artifact Signing account
   • Service: Artifact Signing, if offered; otherwise choose the closest available signing service/category
   • Resource: The affected Artifact Signing account
3. Request backend investigation of the Verified ID presentation conflict. Azure Support needs the affected subscription selected because engineers receive access only to resources in that subscription.^3^
4. Include privately in the ticket:
   • Identity Validation ID
   • Artifact Signing account name and region
   • Subscription and tenant IDs
   • Exact timestamp, time zone, request ID, and correlation ID
   • Full tokenError text
   • Confirmation that AU10TIX accepted the ID and selfie and issued the Verified ID
   • Screenshots of the malformed Verified ID address and the 30-character form restriction
   • The three attempt timestamps and resulting statuses
5. Ask support to determine:
   • Whether the current request actually completed despite the presentation error
   • Whether the transaction can be resumed or, if appropriate, cleared
   • Whether AU10TIX must issue a replacement Verified ID because of the OCR corruption

Before opening another request, check Artifact Signing account → Identity validations once for the final status. A reported case with this error later changed to Completed, so another attempt might be unnecessary.^4^

Entering the Canadian apartment address

For individual Public Trust validation, Artifact Signing takes the legal name and sold-to address from the Azure billing account. That address must match the government-issued ID, including the apartment or unit number.^5^

Use separate address lines:

• Address line 1: Street address
• Address line 2: Apartment/unit number
• City, province, postal code, country: Exactly as shown on the supporting document

The Azure CLI supports address-line2, but az billing account update is currently Preview and supports this operation only for a Microsoft Customer Agreement (MCA) billing account.^6^

First open Cost Management + Billing and identify the billing account type. If it is MCA, list the accounts available to the signed-in user, then update the applicable account:

az billing account list --expand soldTo -o table

az billing account update \
  --name "<billing-account-name>" \
  --sold-to first-name="<first>" last-name="<last>" \
  address-line1="<street>" address-line2="<apartment-or-unit>" \
  city="<city>" region="QC" country="CAN" \
  postal-code="<postal-code>"

This changes the billing account’s sold-to information account-wide, not merely the validation form. Review the billing impact before saving. The portal alternative is Cost Management + Billing → Properties → Update sold-to; some accounts require support approval for the change.^7^

Do not assume that correcting the sold-to address will repair the Verified ID already issued with malformed OCR data. If support directs you to start clean, the documented address-mismatch recovery is to delete the failed validation request, remove its associated Verified ID from Authenticator, correct the billing address, and then create a new request and Verified ID.^2^ Because deletion discards the current request, perform that only after support confirms it is not recoverable.

References

1. Artifact Signing individual validation: CosmosDB resource already ...
2. Artifact Signing FAQ
3. Create an Azure support request
4. Individual identity validation – Face Check keeps failing and “CosmosDB ...
5. Quickstart: Set up Artifact Signing
6. az billing account update
7. Update tax details for an Azure billing account