Artifact Signing - Verified ID cannot be issued: itemNotFound

When creating a new organization identity validation in the Artifact Signing service, I try to obtain a Verified ID via the AU10TIX integration. The AU10TIX flow itself completes successfully - I can scan my ID document, complete the face scan, and reach the success page.

The failure occurs at the final step, when the credential should be issued into Microsoft Authenticator (iPhone). Authenticator shows a generic "Something went wrong"; View Details shows itemNotFound.

The Authenticator diagnostic log shows the actual error. Issuance completion (PostIssuanceCompletionResponseOperation) to verifiedid.did.msidentity.com returns HTTP 400:

error: badRequest / badOrMissingField

message: issuance_service_error

target: responseCode

Reproduced three times on 2026-07-15 (all times UTC):

17:57:16 - QR code scan - Request ID e3d5ea541b5a37e40277522b834c8b76 - MS-CV keo4naG.....

18:42:18 - deep link - Request ID 717d8d0998fb0b3d9eb022f1e28c70de - MS-CV /+Zl5G70Se.....

19:31:48 - QR code scan - Request ID 65ac70586bc95f0884d5dd25d06e5e9e - MS-CV Sm0Lu.....

Additional observations:

• The failure occurs 2-4 seconds after the issuance flow starts, so it is not a session timeout.
• It fails identically via QR scan and via deep link, so it is not a QR/handoff problem.
• The issuer's linked domain validates correctly (RootOfTrust verified, au10tix-vc.com).
• The same flow succeeds on a temporary spare iPhone with a fresh Microsoft Authenticator installation. It fails consistently on my primary iPhone, which has approximately 20 accounts registered in Authenticator. But I won't have this phone very long.

This suggests device-local wallet state on the primary device rather than a problem with the AU10TIX flow or my identity validation request. Reinstalling Authenticator on the primary device is not a viable workaround, as it would require re-registering MFA across roughly 20 customer tenants that I administer.

Requests:

1. Please trace the above Request IDs to determine why the issuance service returns issuance_service_error.
2. Please confirm whether any attempt limit / voucher state on my identity validation request has been consumed by these failures, and reset it if needed.

The Authenticator diagnostic log is attached. It contains only timestamps, correlation vectors, request IDs and error codes — no identity or credential data.

Subscription ID / Tenant ID / Identity Validation ID: available on request or via private channel.

Regards,

Andy