Artifact Signing individual validation remains Action Required after sharing an existing Verified ID

Question

Artifact Signing individual validation remains Action Required after sharing an existing Verified ID

Desktop Signing Help 0

An individual developer in the United States is setting up Public Trust Artifact Signing on a paid Azure subscription with the Basic signing tier. The signing account is Succeeded, and the owner has the required Identity Verifier role.

An earlier request used an email that differed from the Microsoft verification login. The billing email was corrected, the unapproved request was replaced after confirming it had no linked certificate profiles, and the current request's saved primary email and Microsoft Credentials Profile were explicitly verified to match the Azure login.

The current request advanced from In Progress to Action Required. The owner reports sharing the existing valid Verified ID through Authenticator for this corrected request. After processing time and Azure refreshes, the request still shows Action Required and the existing browser page displays Present your Verified ID. No additional identity-proofing requests have been created after this correction.

Azure's automated diagnostic cites certificate-profile failures associated with the retired request ID; it does not explain the current request's validation status. No certificate profile or signed artifact exists yet.

Could a human moderator route this to the Artifact Signing / Verified ID team and provide a private channel to correlate the current presentation with the current validation request? Guidance is needed on the outstanding action or backend handoff without repeating completed identity proofing or creating more duplicate requests. Account and request identifiers can be supplied privately if requested.

Official reference: https://learn.microsoft.com/en-us/azure/artifact-signing/faq#what-if-i-need-assistance-with-identity-validation

Desktop Signing Help 0 Reputation points

2026-10-27T20:41:51.6066667+00:00

The AI-generated answer did not resolve this issue. A fresh Azure check still shows the current Individual Public Trust validation request as Action Required after the owner reported sharing an existing valid Verified ID. The saved primary email and Microsoft verification login have already been confirmed to match, and no further duplicate request has been created.

Could a human Microsoft moderator or Artifact Signing / Verified ID specialist review this stuck validation and identify the outstanding action or investigate the presentation-to-validation handoff? Azure's automated diagnostic references the retired request rather than explaining the current one.

The suggested Azure technical support route requires a paid support-plan upgrade, which is not authorized. Please advise an available route for human identity-validation assistance without a paid support upgrade or repeating completed identity proofing. Any necessary account/request identifiers must remain out of this public thread and would require an appropriate private Microsoft channel.
Meha-MSFT 2,465 Reputation points Microsoft Employee Moderator

2026-10-27T20:51:21.8466667+00:00

when you say the user verified ID, shared it with? please ensure they did step 19 and onwards - https://learn.microsoft.com/en-us/azure/artifact-signing/quickstart?tabs=registerrp-portal%2Caccount-portal%2Cindiedevvalidation%2Ccertificateprofile-portal%2Cdeleteresources-portal#tabpanel_3_indiedevvalidation. This will make sure the vID is scanned again to move froward
Desktop Signing Help 0 Reputation points

2026-10-27T20:55:06.9566667+00:00

Thank you. To confirm the requested steps for the latest corrected validation request: the existing Verified ID was shared with Artifact Signing in Microsoft Authenticator, and the nonmobile computer browser displayed Verification Successful. This was the credential presentation/share step in the instructions you linked, not only the initial ID-verifier success.

Despite that success, refreshed Azure checks continue to show Action Required rather than Completed. The saved primary email and verification login have already been confirmed to match, and no further duplicate request has been created.

Could you please investigate or route this to the Artifact Signing / Verified ID team to correlate the successful presentation with the current validation request and identify why the status is stuck? The automated Azure diagnostic references the retired request, so it has not explained the current status. Please advise a secure private Microsoft channel if request-specific details are needed; no private identifiers will be posted here. A paid support-plan upgrade is not authorized.

1 answer

Your answer

Desktop Signing Help 0 Reputation points

2026-10-27T20:41:51.6066667+00:00

The AI-generated answer did not resolve this issue. A fresh Azure check still shows the current Individual Public Trust validation request as Action Required after the owner reported sharing an existing valid Verified ID. The saved primary email and Microsoft verification login have already been confirmed to match, and no further duplicate request has been created.

Could a human Microsoft moderator or Artifact Signing / Verified ID specialist review this stuck validation and identify the outstanding action or investigate the presentation-to-validation handoff? Azure's automated diagnostic references the retired request rather than explaining the current one.

The suggested Azure technical support route requires a paid support-plan upgrade, which is not authorized. Please advise an available route for human identity-validation assistance without a paid support upgrade or repeating completed identity proofing. Any necessary account/request identifiers must remain out of this public thread and would require an appropriate private Microsoft channel.
Meha-MSFT 2,465 Reputation points Microsoft Employee Moderator

2026-10-27T20:51:21.8466667+00:00

when you say the user verified ID, shared it with? please ensure they did step 19 and onwards - https://learn.microsoft.com/en-us/azure/artifact-signing/quickstart?tabs=registerrp-portal%2Caccount-portal%2Cindiedevvalidation%2Ccertificateprofile-portal%2Cdeleteresources-portal#tabpanel_3_indiedevvalidation. This will make sure the vID is scanned again to move froward
Desktop Signing Help 0 Reputation points

2026-10-27T20:55:06.9566667+00:00

Thank you. To confirm the requested steps for the latest corrected validation request: the existing Verified ID was shared with Artifact Signing in Microsoft Authenticator, and the nonmobile computer browser displayed Verification Successful. This was the credential presentation/share step in the instructions you linked, not only the initial ID-verifier success.

Despite that success, refreshed Azure checks continue to show Action Required rather than Completed. The saved primary email and verification login have already been confirmed to match, and no further duplicate request has been created.

Could you please investigate or route this to the Artifact Signing / Verified ID team to correlate the successful presentation with the current validation request and identify why the status is stuck? The automated Azure diagnostic references the retired request, so it has not explained the current status. Please advise a secure private Microsoft channel if request-specific details are needed; no private identifiers will be posted here. A paid support-plan upgrade is not authorized.

Answer 1

Open an Azure technical support request for the current Artifact Signing identity-validation request and ask Support to correlate the existing Verified ID presentation with that request; do not repeat identity proofing or create another validation request.

Microsoft Q&A moderators cannot provide a guaranteed private account-investigation channel. The documented path for Artifact Signing identity-validation assistance is Azure Support or Q&A, and Microsoft explicitly states that creating additional requests for the same entity while one is in progress does not help and that validation cannot be expedited.^1^

Create the private support case

In the Azure portal, open the affected Artifact Signing account.
In its resource menu, select Support + Troubleshooting.
Complete the prompts and, if the suggested diagnostics do not resolve the issue, select Create a support request.^2^
Select:
- Issue type: Technical
- Service: Artifact Signing, if available
- The closest identity-validation problem type/subtype
- Subscription: the paid subscription containing the Artifact Signing account
Use a title such as: Artifact Signing Individual validation remains Action Required after existing Verified ID presentation

The Owner role is sufficient to create a support request at subscription scope. Technical support may require an Azure support plan.^2^

Request this specific backend action

Include the following wording in the case:

Please route this case to the Azure Artifact Signing identity-validation/Verified ID team. Correlate the completed presentation of my existing valid Verified ID with the current Individual Public Trust identity-validation request. The portal remains at Action Required and the presentation page still displays “Present your Verified ID.” Please identify the outstanding action or repair/reprocess the backend handoff. Do not associate the investigation with the retired request ID, and do not ask me to create another identity-validation request unless the current request is first determined to be unrecoverable.

Provide these details only in the private support request, not in Q&A:

Azure subscription ID
Tenant ID
Artifact Signing account name, resource group, and Azure region
Current identity-validation request ID
Retired request ID, clearly labelled as retired
Validation type: Individual / Public Trust
Current status: Action Required
UTC date and approximate time when the Verified ID was presented
Azure sign-in address and saved primary email—state that they match; avoid sending credentials
Screenshot of:
- The current request and status
- The browser page showing Present your Verified ID
- Authenticator showing the valid Verified ID, with unnecessary personal fields redacted
The diagnostic result that incorrectly references certificate-profile failures associated with the retired request
Confirmation that no certificate profile or signed artifact exists
Confirmation that no later duplicate validation request was created

The current validation must reach Completed before a certificate profile can be created, so the absence of a certificate profile is expected at this stage.^3^

After creating the ticket, additional evidence can be added through Help + support → All support requests → select the case → New message or Upload file. The portal supports up to five files after case creation; files containing unnecessary personal information should not be uploaded.^4^

If Support needs sensitive diagnostic material, ask the assigned engineer to provide a case-specific Secure File Exchange workspace. Access is restricted to Microsoft Support personnel working on the case.^5^

Do not repeat the completed paths

No further deletion, Verified ID removal, browser troubleshooting, or duplicate request creation is indicated by the documented guidance for the facts reported. The FAQ’s delete-and-recreate procedure applies specifically to explicit address mismatch, name mismatch, or FaceCheck failures—not merely an unexplained Action Required state.^1^

References