identity validation

paul douglas 0 Reputation points
2026-10-23T13:15:19.3033333+00:00

Hello,

I have an issue and I want to know if the procedure is what I am failing with, the verification sends the email and then also the system has the action required. The answer I am needing is at this point is how to proceed with email, so I don't get the timeout notice when i share the government id verification with my state driver's license and the selfie picture??

This I ran after submitting the Validation Requests and before opening the email link.

*** code signing account is in a healthy state. Its provisioning state is Succeeded, and the certificate profiles collection contains 1 profile with provisioning state checks passing. No remediation is indicated by the available diagnostics.

ARM Diagnostic Workflow completed without failures

The diagnostic completed successfully for <!--$type-->Microsoft.CodeSigning/codeSigningAccounts<!--/$type-->. Account provisioning state is <!--$provisioningState-->Succeeded<!--/$provisioningState-->, the certificate profiles collection returned <!--$certificateProfilesCount-->1<!--/$certificateProfilesCount--> item, and certificate profile provisioning state checks passed.

  1. No remediation is required based on this diagnostic result.
  2. If you want to confirm the current state in the Azure portal, open the code signing account resource and verify that Overview shows Succeeded.
  3. Check Certificate profiles and confirm that the collection contains 1 profile and that each profile shows a provisioning state of Succeeded.
Microsoft Security | Microsoft Authenticator
0 comments No comments

1 answer

Sort by: Oldest
  1. AI answer

    2026-10-23T13:16:01.5366667+00:00

    The resource diagnostic does not complete identity validation; while the request shows Action Required, open its verification link, sign in with the same email address entered in the request, and complete the email PIN, driver’s-license, and selfie flow in one uninterrupted session.

    Correct verification sequence

    1. In the Azure portal, open Artifact Signing account → Objects → Identity validations.
    2. Select the validation request showing Action Required.
    3. In the right-hand pane, select Please complete your verification here. You can use this portal link or the equivalent link sent to the primary email address.
    4. Sign in using the same email address specified as the primary email when the request was created. A different signed-in address can produce a permissions error.
    5. Select Get verified here through our trusted ID-verifiers.
    6. On the identity verifier’s page:
      • Enter that same primary email address.
      • Open the verifier’s email and enter its PIN code.
      • Enter your phone number when prompted.
      • Select Start, then capture the driver’s license and selfie as directed.

    The email/PIN step verifies your email address; the government ID and selfie are submitted through the trusted identity-verification session, not by replying to or sharing them through email. After successful individual verification, the Azure request should return to In Progress while validation continues, and ultimately change to Completed or Failed.^1^

    Avoiding expiration and session failures

    • Complete the verifier flow immediately after entering the emailed PIN rather than leaving the browser or Authenticator session open.
    • Use the latest Microsoft Authenticator version, close other open Authenticator instances, and relaunch it before beginning.
    • Use a stable connection without a VPN or proxy.
    • If the browser handoff fails, clear its cache or use another browser. Another phone can also eliminate device-specific interference.
    • Take the ID and selfie in adequate, even lighting, avoiding glare on the driver’s license.

    Microsoft documents a seven-day expiration for the Artifact Signing email verification link, but does not specify a duration for the separate ID/selfie session timeout. If the seven-day link expires, it cannot be resent for that request; create a new identity-validation request.^2^

    If it times out again

    • If the request remains Action Required, reopen it from Identity validations and use Please complete your verification here.
    • If it reports an address/name mismatch or FaceCheck failed, delete the existing request, remove its associated Verified ID from Microsoft Authenticator, and create a new identity-validation request with accurate details and improved lighting.^2^
    • If the request is already In Progress, do not create duplicate requests; they do not expedite validation.
    • If the request cannot be restarted, deleted, or progresses no further after successful submission, open an Azure Support request for Artifact Signing identity validation, or post on Microsoft Q&A using the artifact-signing tag.^2^

    The successful ARM diagnostic only confirms that the Artifact Signing account and certificate profile are provisioned. It does not confirm that the separate identity request, email verification, or ID/selfie presentation has completed.


    References

    1. Quickstart: Set up Artifact Signing
    2. Artifact Signing FAQ
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.