A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Your instinct not to recreate is right, so let's keep that request alive. Creating additional identity validation requests for the same entity doesn't help and can't be expedited, and you'd have to redo the face check.
Two things to clear up, then the fix.
First, the credentials.microsoft.com link saying "already used" is expected and not a problem. That one-time link only covers the Microsoft Verified ID / face check step, which you passed with the green check. The document upload never happens through that link. It's a separate step that happens inside the Azure portal, within the identity validation request itself, and it only becomes available while the request status is Action Required, which yours is.
Second, when the status is Action Required but you still see no upload control, the most common cause is a missing role. The upload option only renders if your signed-in user holds the Identity Verifier role on the Artifact Signing account. So:
- Open the norrisstandsigning2026 account, go to Access control (IAM), and check whether your user has the Artifact Signing Identity Verifier role. If not, have someone with Owner or User Access Administrator rights on the account assign it, then sign out and back in.
- Then go to the account, Identity validations, and click into the NORRISSTAND LLC request itself. The upload control lives inside that request view, not on the account overview and not in any email link. If it still doesn't render after the role fix, try a fresh incognito window, since stale portal cache has caused this exact symptom before.
- When the upload does appear, be deliberate: there are only three upload attempts per request. Submit the Kentucky formation documents together with everything else Microsoft's email listed in one go, and make sure the legal name and address on the documents match the request exactly.
- If the role is confirmed and the control still won't show while the status reads Action Required, that mismatch has to be checked on Microsoft's side. Reply on your thread stating you've verified the Identity Verifier role, and a moderator can take your Identity Validation ID via private message to look at the request internally. Azure Support is the parallel channel. And you're already doing the right thing keeping the IDs and documents off the public post.
Reference: https://learn.microsoft.com/en-us/azure/artifact-signing/quickstart