Artifact Signing organization validation repeatedly returns to Action Required after Verification successful

We are setting up Public Trust organization identity validation for a US company in Azure Artifact Signing (East US).

First request:

• The representative completed the ID/photo process, added a Verified ID to Microsoft Authenticator, tapped Share, and saw Verification successful in the desktop browser.
• After refreshing Azure, the request remained Action Required and asked us to complete verification.
• Reopening its verification link showed No Access: Sorry, this link has been used already. Please return to Artifact Signing to review the status of your request.
• The request later changed to Failed with no failure reason, error code, document request, or corrective action in its details.

Second request:

• We submitted a fresh organization validation request using the same company details and tax identifier. The existing Verified ID was already available in Microsoft Authenticator.
• During verification, the phone displayed a technical error. We could not capture the exact text or a screenshot.
• Despite that error, the desktop browser showed Verification successful again.
• The new request has now returned to Action Required in Azure, apparently repeating the first request's problem.

The signed-in Azure account matches the primary email on the request. We have preserved the failed request, current request, and Verified ID.

Our Basic Azure support plan blocks technical support case creation. The automated portal diagnostic suggested a stale or consumed verification-link state, but gave no backend error or confirmed failure reason.

Could the Artifact Signing team help determine whether the Verified ID presentations were recorded and associated with these requests, explain the first request's failure, and advise how to recover the current request without repeating the same process? Is the phone technical error consistent with a browser success confirmation followed by Action Required?

We can provide validation/account identifiers privately through an appropriate Microsoft secure channel.