Artifact Signing Organization Identity Validation stuck in Action Required – AU10TIX Verified ID presentation hangs on Processing

I am setting up Azure Artifact Signing Public Trust for ReadThisAloud LLC.

The organization identity validation is stuck in Action Required.

AU10TIX government identity verification completed successfully. A valid Government Issued ID - GLOBAL credential is visible in Microsoft Authenticator under Verified IDs.

The problem occurs during the final Microsoft Verified ID presentation.

When I select Please complete your verification here, credentials.microsoft.com displays Present your Verified ID. After attempting to present the existing AU10TIX credential, the browser remains indefinitely on Processing… and the Artifact Signing validation remains Action Required.

We have reproduced this multiple times over several days.

We have already tried:

• Fresh verification sessions
• Microsoft Authenticator restarted
• Existing valid AU10TIX Government Issued ID - GLOBAL
• Different browser/private session
• VPN/proxy eliminated as a variable
• Repeated presentation attempts

Azure’s built-in diagnostic reports that there is no resource-side fault with the Artifact Signing account and identifies the blocker as the separate identity-validation onboarding workflow.

The Azure Support request wizard also loops indefinitely between Problem Description and Recommended Solution, so it never allows us to reach Additional Details or submit the support case.

Please escalate this to the Artifact Signing / Microsoft Verified ID engineering team and investigate or reset the Verified ID presentation/callback associated with the existing organization identity-validation request.

I do not want to create another identity-validation request unless Microsoft determines that the existing request cannot be recovered.

Organization: ReadThisAloud LLC Artifact Signing account: ReadThisAloudSigning Region: East US Validation status: Action Required

I can provide the Subscription ID, Tenant ID, Identity Validation ID, timestamps, and screenshots privately to a Microsoft engineer. I will not post identity documents or other sensitive information publicly.