Forum Discussion
Identity Validation - How long does it take?
I’ve been trying to complete identity validation for Azure Trusted Signing so I can use it for code signing. My situation:
- I submitted my business registration documents over 5 weeks ago. The status has been "In Progress" ever since.
- I tried creating a new identity 2 weeks ago, but that one is also stuck "In Progress."
- I have not received any updates, rejections, or communication from support during this time.
The first few times I did the process it at least failed because I didn't attach the right email addresses, but now I am waiting endlessly.
Could someone at Microsoft please advise on:
- Why my identity validation is stuck "In Progress" for so long.
- Whether I should restart the process or if it’s possible to get my current submission escalated.
- How to ensure the required documents (business registration, status of information, etc.) are properly reviewed.
Thanks to anyone who can help for their time! I feel stuck and this is directly impacting my business so I appreciate it.
Best!
5 Replies
Thanks for raising this. Here’s a focused plan that reliably gets stalled Trusted Signing identity validations moving.
What to verify first
- Role: Confirm the requester has the Trusted Signing Identity Verifier role on the Trusted Signing account (Owner/Contributor alone isn’t sufficient).
- Provider: Ensure the Microsoft.CodeSigning resource provider is registered on the subscription.
- Data/doc match: The legal entity name and address in the request must exactly match the business registration and “active/good standing” status pages; upload clear scans of all relevant pages.
- Contact: Use an organization-domain email for the primary contact or include a short note explaining any mismatch (parent company/DBA, etc.).
Actions to break the “In Progress” stall
- Open a formal Azure support request from the Azure portal (Help + Support).
- Service: Trusted Signing (Code Signing)
- Problem type: Identity Validation
- Severity: set to reflect that releases are blocked
Include: Subscription ID, Tenant ID, Trusted Signing account resource ID, all identity validation request IDs with submission dates, and attach the same documents. Ask explicitly for routing to the Trusted Signing validation team and an ETA.
- Post minimal identifiers here for an internal check
Share the identity validation request IDs and your Azure support ticket number so a moderator/engineer can review and, if needed, close duplicates to avoid queue confusion. - Keep one request as primary
Avoid creating new requests unless support confirms corruption or instructs a fresh submission. Duplicates can slow manual review.
If your legal details changed recently, add a short note and attach both old/new proof plus the official change record to the support ticket.
Template you can copy into your support ticket and this thread
- Subscription ID: <sub-id>
- Tenant ID: <tenant-id>
- Trusted Signing account: <resource group/name>
- Identity validation requests: <ID-1 submitted on …>, <ID-2 submitted on …>
- Business impact: Code signing blocked for production release
- Setup verified: CodeSigning provider registered; Identity Verifier role assigned; documents uploaded (current registration + active/good standing, exact name/address match)
Request: Please route to the Trusted Signing validation team, provide status/ETA, and advise on closing duplicates if appropriate.
Identity Validation Request ID: 2cc1df60-4d03-4d8c-bdb0-aec913a4260c
Organization Name: Michael ZajnerI can confirm that the role, provider, data/doc, and contact are all correct on my account.
To try to break the stall, I attempted to open a formal support ticket, but I do not want to pay for an additional support plan when this core service is already not functioning as expected.
Thanks for raising this and providing the checklist of next steps. I’ve verified the requirements on my side (Identity Verifier role assigned, Microsoft.CodeSigning provider registered, legal documents uploaded with exact name/address match, and domain-based contact email).
Could you please help escalate this stalled validation internally or confirm if there’s a specific path forward that doesn’t require an extra paid support plan?
Hello SoaebRathod thanks for the detailed response!
The request:
Identity Validation Request ID: 2cc1df60-4d03-4d8c-bdb0-aec913a4260c
Organization Name: Michael Zajner
In order of what I can verify:
1. Role: I can confirm that the requester has the Trusted Signing Identity Verifier role on the Trusted Signing account.
2. Provider: the Microsoft.CodeSigning resource provider is registered on my subscription.
3. Data & Contact: Can confirm the legal entity name, address match and I am using an organization-domain email.
To break the "In Progress" stall:
1. Formal Azure support ticket: I tried to do this but it looks like I have to pay an extra fee, which I am not willing to do for a service that has yet proven to even work for me. It is a shame Microsoft can't just add support for this (I have had no comparable issue when working with Apple in this regard).
My legal identities haven't and won't change.
Is there any way a member of Microsoft's team can view this post and escalate my case? It's now at a month and a half and this is starting to negatively effect my businesses daily operations.
In the meantime of escalation to Microsoft or Partner, you may consider below:
1. Avoid Creating Multiple Identities
- Creating new identities doesn’t reset the queue, it may actually complicate things. Stick with one and escalate that one.
2. Verify Document Format and Metadata
- Ensure your business registration documents:
- Match the organization name exactly as registered
- Include official government seals or signatures
- Are in supported formats (PDF preferred)
- Use the correct email domain associated with your business
Thanks for the tips! I'll avoid creating multiple identities. I know it isn't good procedure but I was hoping it would push the case along. The document format and metadata I can confirm were correct!
