A Microsoft app for iOS and Android devices that enables authentication with two-factor verification, phone sign-in, and code generation
For Artifact Signing identity validation, the expected flow after scanning is:
- On the browser, keep the verification page open.
- On the mobile device, select Start and complete the identity-verification steps.
- After the third-party verification finishes on the phone, select Open Authenticator.
- Back on the browser, scan the next QR code from the mobile device.
- In Microsoft Authenticator, select Add to add the Verified ID.
- When the browser shows Present your Verified ID, scan that QR code.
- In Authenticator, select Verifiable Credential, then Share.
- The browser should update to Verification Successful.
If the app closes and the browser stays stuck on processing, check these points:
- Do not close the browser during the flow.
- Make sure the verification is being completed with the same email address that was entered in the identity validation request. If the email used to sign in to access the validation link is different, Artifact Signing can show a permission/access error.
- If a push or credential prompt is not appearing on the current phone, check whether Microsoft Authenticator is still active on an older device. Registration prompts can go to the device where Authenticator was last used.
- If a valid Verified ID already exists, present that existing valid credential for Artifact Signing instead of creating a new one.
If the identity validation link has expired, or email validation failed, a new identity validation request is required. A new link cannot be resent for the same request.
If the verification continues to fail and the flow cannot be completed, create a support ticket in the Azure portal for Artifact Signing support.
References: