A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Keep the existing identity-validation request open and request validation-team review through this Microsoft Q&A post; completing Verified ID normally returns the request to In Progress while organization validation continues, so the used link does not indicate that the step failed.^1^
What to do now
- Do not create another request or delete this one.
Microsoft states that duplicate identity-validation requests for an entity already In Progress do not help, and validation cannot be expedited.^2^ - Keep this Q&A question tagged
artifact-signing.
Microsoft lists Azure Support and Microsoft Q&A with that tag as the supported assistance channels for identity validation. A paid support plan is therefore not required to raise the issue here.^2^ - Ask a Microsoft moderator to route the request for private validation-team review.
Include only these non-sensitive details publicly:- Validation type: Organization, Public
- Region: East US
- Submission date: October 27, 2026
- Current status: In Progress
- Verified ID completed
- No document request received at either address
- Continue monitoring both configured mailboxes and the portal status.
The documented sequence is:- Verified ID completes.
- Status returns to In Progress.
- If documents are needed, status changes to Action Required and an email is sent.
- The final status becomes Completed or Failed, with an email notification.^1^
Since junk mail and both addresses have already been checked, repeating those checks or reopening the consumed Verified ID link is unlikely to advance this request. The published documentation does not specify a guaranteed completion time for the remaining organization review.
Similar prolonged In Progress cases were resolved after the validation team reviewed the submitted details, which indicates that this stage can require service-side intervention rather than another customer action.^3^^4^
References