Organization identity validation stuck In Progress 12+ days (EU entity, meets all criteria)

Alex Bickov 20 Reputation points
2026-07-22T09:50:45.9633333+00:00

My Artifact Signing (Trusted Signing) organization identity validation has been In Progress for over 12 days with no update.

Entity: MEDIAPLANS, Latvia (EU), incorporated 2008. It meets both stated criteria: the EU is supported for Public Trust certificates, and the company is well past the 3-year minimum.

History:

  • Attempt 1 returned Failed, with no reason shown and no verification email ever received (checked spam; the address accepts external mail with links).
  • Attempt 2 was resubmitted with the exact registered legal name and has been In Progress since around July 10.

Questions:

  1. Can someone check the current request and why it's stuck?
  2. Was a verification email sent for either attempt, and to which address? I never received one.
  3. If attempt 1 failed on a data mismatch, which field was it, so attempt 2 doesn't repeat it?

Current validation request ID: df629675-258d-4777-989b-3899452fbd4f Account: slimsnap-signing (North Europe). On a Basic support plan, so I can't file a technical ticket, which is why I'm here.My Artifact Signing (Trusted Signing) organization identity validation has been In Progress for over 12 days with no update.

Entity: MEDIAPLANS, Latvia (EU), incorporated 2008. It meets both stated criteria: the EU is supported for Public Trust certificates, and the company is well past the 3-year minimum.

History:

  • Attempt 1 returned Failed, with no reason shown and no verification email ever received (checked spam; the address accepts external mail with links).
  • Attempt 2 was resubmitted with the exact registered legal name and has been In Progress since around July 10.

Questions:

  1. Can someone check the current request and why it's stuck?
  2. Was a verification email sent for either attempt, and to which address? I never received one.
  3. If attempt 1 failed on a data mismatch, which field was it, so attempt 2 doesn't repeat it?

Current validation request ID: df629675-258d-4777-989b-3899452fbd4f
Account: slimsnap-signing (North Europe).
On a Basic support plan, so I can't file a technical ticket, which is why I'm here.

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments
Answer accepted by question author
Allan Solomon Mejia 9,000 Reputation points
2026-07-28T18:34:23.39+00:00

Hello @Alex Bickov

Based on your description, this appears to require investigation by the Artifact Signing / Trusted Signing identity validation team rather than additional client-side troubleshooting.

A few observations:

  • Your organization appears to meet the published eligibility requirements (EU entity and incorporated well beyond the minimum age requirement).
  • A validation request remaining in "In Progress" for more than 12 days without any status change is not typical.
  • Since the first attempt failed without exposing a reason and the second attempt has remained pending, there isn't enough information available from the portal to determine whether the request is waiting for manual review, blocked by a validation issue, or awaiting an external verification.

Unfortunately, the Trusted Signing portal does not expose:

  • The detailed validation failure reason.
  • Whether a verification email was sent and to which address.
  • The current backend validation stage or estimated processing time.

At this point, I recommend that a Microsoft moderator escalate the validation request to the Azure Trusted Signing / Artifact Signing team and verify:

  1. Whether the current validation request is still actively processing or is stuck in a pending state.
  2. Whether a verification email was generated for either submission, and which contact address was used.
  3. If the first attempt failed because of a data mismatch, which specific field (for example, legal entity name, registration information, or business details) caused the failure.
  4. Whether any additional action is required from the customer or whether Microsoft needs to reset or resume the validation workflow.

For security reasons, I also recommend editing your post to remove the validation request ID, as it may be considered sensitive information. If the Microsoft team needs it, they can request it through a private message or secure support channel.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

Was this answer helpful?

1 person found this answer helpful.
0 comments

1 additional answer

Sort by: Oldest
Most helpful Newest Oldest
  1. Alex Bickov 20 Reputation points
    2026-07-28T19:07:36.5733333+00:00

    Update: resolved. The validation completed after I found the verification email in spam.

    For anyone hitting the same thing: the verification email does not come from the same address as the other Azure notifications. It comes from a different sender, so my mail filters trusted all the regular notifications and sent the one email that mattered to spam. That is why attempt 1 failed with no visible reason, the message was sitting in spam the whole time.

    Two things that would help from the Microsoft side: send the verification from the same domain as the rest of the notifications, or show the exact sender address in the portal so people know what to search their spam folder for.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.