A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Reopen the existing Action Required validation from the Artifact Signing portal and present the representative’s existing, unexpired Verified ID; do not create a duplicate request or repeat document verification unless the existing credential is expired or the current flow explicitly requires a new credential.
Resume the existing presentation
- In the Azure portal, open Artifact Signing account → Objects → Identity validations.
- Select the existing organization validation.
- In its detail pane, select Please complete your verification here.
- Sign in using the same primary email address specified when the organization validation was created.
- At the Verified ID presentation page:
- Open Microsoft Authenticator.
- Select Verified IDs.
- Scan the displayed QR code.
- Select the existing valid credential.
- Verify that the displayed requesting party is the expected Microsoft/Artifact Signing verifier.
- Select Share.
- Return to the browser and complete any final Continue or confirmation action shown there.
Issuance and presentation are separate operations: having the credential in Authenticator does not mean it was shared with Artifact Signing. In a standard presentation, the user scans the verifier’s QR code, selects Share, and then continues in the browser.^1^
Artifact Signing specifically instructs users who already possess a valid, unexpired Verified ID to present that existing credential. It also warns that additional validation requests for the same entity while one is in progress do not help.^2^
If reopening the link displays a new QR code, use it to present the existing credential. If it reports that the link was already used, returns an HTTP error, or never offers the existing credential, there is no documented self-service method to reset that presentation transaction. Preserve the current request and escalate it rather than deleting or duplicating it.
Interpret the portal status
Use both the top-level status and the message inside the validation details:
- Action Required, still showing Please complete your verification here: Artifact Signing has not recorded successful completion of the representative-verification stage. Reopen the link and complete the presentation/Share sequence.
- In Progress: the representative’s individual identity validation completed and the organization-validation process resumed. Further organization checks or an email-verification action may still follow.
- In Progress with Please complete your email verification: check the primary organization mailbox. Organization verification links are sent there and expire after seven days.
- Completed: organization identity validation is finished. Only then can it satisfy the prerequisite for creating the matching Public Trust certificate profile.
- Failed: inspect the detail message before taking action. A missed or expired organization email link requires a new validation request; a new link cannot be resent on the same request.^2^
The documented successful transition after the representative completes individual verification is Action Required → In Progress. Remaining at Action Required with the same completion prompt is therefore not the documented normal-processing state.^3^
Do not create the certificate profile yet. A completed identity validation matching the profile type is a prerequisite for certificate-profile creation.^4^
If presentation still cannot complete
For general Authenticator or browser failures—not a consumed-link or backend transaction error—the supported checks are:
- Fully close and reopen Microsoft Authenticator.
- Update Authenticator to the latest Android/iOS version.
- Clear browser cache or use another browser.
- Avoid VPNs, proxies, and weak connections.
- If possible, try another phone.^2^
Do not remove the existing Verified ID unless the portal reports a documented identity mismatch, address mismatch, or FaceCheck failure. Those specific failures require deleting the request and credential and starting again; uncertainty about whether Share completed does not establish that condition.^2^
Escalation without a paid Azure support plan
Microsoft documents two Artifact Signing support routes:
- Azure Support
- Microsoft Q&A using the
Artifact Signingtag^2^
Azure subscription-management support is free, but this is a technical workflow issue, and Azure technical support requires a support plan.^5^
Therefore, Microsoft Q&A is the documented no-cost route, but it is a public forum—not a guaranteed private support case. In the Q&A post, request moderator escalation and a private channel for identifiers. Include publicly only:
- Azure region and validation type: Organization / Public
- Current status and exact detail message
- UTC times of Verified ID issuance and attempted presentation
- Whether Authenticator still contains a valid credential
- Any exact browser error or HTTP status
- Confirmation that no duplicate request was created
Provide the subscription ID, tenant ID, validation ID, correlation IDs, screenshots containing personal data, and identity documents only through a private moderator/support exchange. Ask Microsoft to confirm whether the existing presentation was received and, if not, to recover or reissue the presentation session without replacing the issued credential.
References