Un servicio de un extremo a otro totalmente administrado para firmar digitalmente código, documentos y aplicaciones. (anteriormente Firma de confianza)
Hello, David. I understand how frustrating it is to be stuck in a "loop" with identity validation, especially when you are doing exactly what the emails ask you to do. Dealing with Trusted Signing (formerly Azure Code Signing) can be tricky because the validation is handled by a third-party Certificate Authority (CA) integrated with Azure, and their systems can sometimes be very rigid.
The error "Email verification failed" usually points to a mismatch between your Microsoft Entra ID (Azure AD) identity and the Organization details provided for the certificate.
Here is a guide to troubleshoot and get that validation to "Completed" status:
1. The "Contact Email" vs. "Domain Email" Trap
The most common reason for this failure is that the email being verified does not match the Public Domain associated with the organization you are validating.
- The Rule: If you are validating "Your Company Ltd.", the email you use for verification must be on that company's domain (e.g.,
******@yourcompany.com).
The Issue: If you are using a generic email (Gmail, Outlook) or an email from a different tenant/domain to click the verification links, the CA system will often flag it as "failed" even if you clicked the button.
2. Check your "Public Record" Consistency
For Organization Validation (OV), Microsoft’s partner (DigiCert or similar) checks the Legal Entity data.
Go to your Azure Portal > Trusted Signing Account > Identity Management.
Ensure the Organization Name and Address match exactly with what is on your official registration documents (like Dun & Bradstreet or your local Chamber of Commerce).
If the email verification fails, it’s often because the email address you’re using isn't listed in the official public records for that company.
3. Clear Cache and use "Incognito" for the Link
The verification links sent via email often carry heavy metadata. If you are logged into multiple Microsoft accounts in your browser, the validation can fail silently or attach to the wrong identity.
Action: When you receive the "Please complete your email verification" email, right-click the button/link, copy it, and paste it into a Private/Incognito window where no other accounts are logged in.
4. Troubleshooting the "In Progress" Status
Since your ID 3cb74489-f16d-4c23-9b66-19d65626c816 is currently "In Progress":
Check the Junk folder: Sometimes a second email is sent by the CA (not Azure) to verify your authority to sign on behalf of the company.
Domain Verification: Ensure you have added the required DNS TXT record to your domain if requested. Without this, the email verification is considered incomplete.
How to get a human to check those specific IDs
Since you have the specific Identity Validation IDs, you have a significant advantage. Because this involves sensitive identity data, only the Microsoft Support team for "Identity and Access" can see why that specific GUID failed.
Go to Help + Support in the Azure Portal.
Create a ticket under Technical > Security > Trusted Signing.
Paste both IDs (49583ae0... and 3cb74489...) and state: "The email verification status says 'Failed' despite following the link. I need a manual sync between the CA and my Azure Tenant."
Pro Tip: If your organization has a D-U-N-S Number, make sure it's included in your identity profile. It speeds up the "Organization Validation" significantly and often bypasses some of the automated email hurdles.
Don't give up—once this bridge is crossed, signing your executables becomes a seamless process!