Identity Validation stuck "In Progress"

Hello @Erlun Lian, I am answering based on my capabilities and experience in handling Azure Trusted Signing workflows and cloud identity management. This is a very interesting and crucial question because it actually touches a critical point in the Artifact Signing infrastructure, as Azure enforces security standards equivalent to Extended Validation (EV). A delay of more than two weeks typically indicates a disconnect of information between Microsoft Azure and the external validator (usually DigiCert) or there is a data mismatch in the Microsoft Entra ID profile (formerly Azure AD). Technically, this process involves verification of the organization's legal documents, domain validation through DNS records (TXT/CNAME), and verification of administrative contacts. If the status remains "In Progress", the system might be waiting for a response from the business registration authority in your region, or there is an automated failure when the system tries to match the company's legal name with the data registered in the Partner Center portal.

To speed up resolution from the technical side, you need to log into the Azure Portal and navigate to the Trusted Signing Account section, then check thoroughly under the Identity Assets tab. Ensure that the Identity Validation you selected matches the legal entity, whether it is a Private Organization or Individual. If you are using an organization profile, make sure the business registration number (such as NIB or DUNS number) has been validated in the Microsoft Partner Center because Azure Trusted Signing pulls identity metadata directly from there. A highly recommended technical step is to check the Email Verification, which is often filtered into the spam folder; the validator will send an approval link to the email address listed in your domain's Whois or the organization's official administrative email. Without clicking the approval in that email, the status will be permanently locked in the "In Progress" phase because the Certificate Authority Browser Forum (CA/B Forum) security protocol requires human confirmation.

If all technical data has been confirmed to be synchronized but there is still no progress, you must perform a manual intervention by opening a Support Ticket under the "Configuration and Setup" category for the Trusted Signing service. In that ticket, include the Correlation ID from your Azure activity logs and attach proof that your business entity has been verified in the Microsoft Partner Center. Technically, the Microsoft backend team can trigger a manual re-sync between the identity validation provider and your Trusted Signing resource to update the Identity Validation status. Once this validation succeeds (changes to "Completed"), you can then proceed to the Certificate Profile creation stage and sign artifacts using the Azure Sign Tool or GitHub Actions integration. Do not let this status linger too long, because typically certain validation sessions have an expiration timeout; if missed, it will force you to repeat the document submission process from the beginning.

Thank you and Hopefully Helpful 🙏