Forum Discussion

M_Z's avatar
M_Z
Copper Contributor
Aug 22, 2025

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 statu...
azure
SoaebRathod's avatar
SoaebRathod
MCT
Aug 23, 2025

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

  1. 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.

  1. 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.

  2. 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.
M_Z's avatar
M_Z
Copper Contributor
Aug 28, 2025

Identity Validation Request ID: 2cc1df60-4d03-4d8c-bdb0-aec913a4260c
Organization Name: Michael Zajner

I 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?

Resources