Stuck identity validation ID 551f1314-9946-4116-a064-6cae398ca3d6

Benjamin Frenkel 0 Reputation points
2026-11-05T05:11:25.89+00:00

Title Stuck identity validation ID 551f1314-9946-4116-a064-6cae398ca3d6

Service Microsoft.CodeSigning / Trusted Signing

Severity C - Minimal business impact (Use B if signing is blocked for production/release timelines.)

Problem summary Identity validation appears stuck and is not progressing for validation ID 551f1314-9946-4116-a064-6cae398ca3d6.

Subscription Sign Binaries (098a426d-73c3-44c6-a41a-fae6d1981a3f)

Resource /subscriptions/098a426d-73c3-44c6-a41a-fae6d1981a3f/resourceGroups/SignBinariesResourceGroup/providers/Microsoft.CodeSigning/codeSigningAccounts/InstallZeroLLC

Description We are unable to complete identity validation for our Trusted Signing / Code Signing setup. The validation request with ID 551f1314-9946-4116-a064-6cae398ca3d6 appears stuck and has not progressed.

Please investigate:

Current backend status of identity validation ID 551f1314-9946-4116-a064-6cae398ca3d6

Whether the request is blocked, failed silently, or requires manual intervention

Any missing validation artifacts or actions required from our side

Whether the validation can be retried or cleared safely without creating duplicate/conflicting requests

Observed behavior

Validation remains stuck

No clear completion or actionable error is visible in the portal

This is blocking progress with Code Signing / Trusted Signing setup

Requested outcome

Confirm the exact state of validation ID 551f1314-9946-4116-a064-6cae398ca3d6

Unblock or reset the validation if needed

Advise next required steps

Include attachments if available

Screenshot of the validation status page

  • Timestamp when the validation was submitted

Any correlation ID, operation ID, or portal error text shownTitle

Stuck identity validation ID 551f1314-9946-4116-a064-6cae398ca3d6

ServiceMicrosoft.CodeSigning / Trusted Signing

SeverityC - Minimal business impact(Use B if signing is blocked for production/release timelines.)

Problem summaryIdentity validation appears stuck and is not progressing for validation ID 551f1314-9946-4116-a064-6cae398ca3d6.

SubscriptionSign Binaries (098a426d-73c3-44c6-a41a-fae6d1981a3f)

Resource/subscriptions/098a426d-73c3-44c6-a41a-fae6d1981a3f/resourceGroups/SignBinariesResourceGroup/providers/Microsoft.CodeSigning/codeSigningAccounts/InstallZeroLLC

DescriptionWe are unable to complete identity validation for our Trusted Signing / Code Signing setup.The validation request with ID 551f1314-9946-4116-a064-6cae398ca3d6 appears stuck and has not progressed.

Please investigate:

Current backend status of identity validation ID 551f1314-9946-4116-a064-6cae398ca3d6

  Whether the request is blocked, failed silently, or requires manual intervention
  
     Any missing validation artifacts or actions required from our side
     
        Whether the validation can be retried or cleared safely without creating duplicate/conflicting requests
        
        **Observed behavior**
        
           Validation remains stuck
           
              No clear completion or actionable error is visible in the portal
              
                 This is blocking progress with Code Signing / Trusted Signing setup
                 
                 **Requested outcome**
                 
                    Confirm the exact state of validation ID 551f1314-9946-4116-a064-6cae398ca3d6
                    
                       Unblock or reset the validation if needed
                       
                          Advise next required steps
                          
                          **Include attachments if available**
                          
                             Screenshot of the validation status page
                             
                                Timestamp when the validation was submitted
                                
                                   Any correlation ID, operation ID, or portal error text shown
Artifact Signing
Artifact Signing

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

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-11-05T05:12:29.1133333+00:00

    Only the Artifact Signing validation team can confirm or change the backend state of this specific In Progress request, so open an Azure support request against the affected Artifact Signing account and ask for routing to that team; do not create a duplicate validation request.

    Open the support request

    1. In the Azure portal, open the affected Artifact Signing account.
    2. From the resource menu, select Support + Troubleshooting.
    3. Complete the prompts and, if the suggested solutions do not resolve the issue, select Create a support request. Alternatively, use the portal’s ? menu to start the request. ^1^
    4. Select:
      • Issue type: Technical
      • Service: Artifact Signing or Trusted Signing, whichever the portal displays
      • Resource: The affected signing account
      • Severity: C for minimal impact; select B if signing is blocking a production or release deadline and your support plan offers it.
    5. Request these specific actions:
      • Inspect the server-side state and latest transition of the validation.
      • Confirm whether it is awaiting manual review, email verification, documents, or another action.
      • Identify any notification that was generated but not delivered.
      • Route the case to the Artifact Signing identity-validation team.
      • Reset or clear the request only if the validation team confirms that doing so is safe.
    6. Attach:
      • Screenshot of the validation details page, not only the account overview.
      • Submission date and current status.
      • Any correlation ID, operation ID, incident ID, or portal error.
      • Dates when documents or verification steps were completed.
      • Browser trace, if the portal itself fails to load or submit an action.

    Creating a technical support request requires an eligible support plan and an appropriate subscription role: Owner, Contributor, Support Request Contributor, or a custom role containing Microsoft.Support/*. ^1^

    Microsoft also identifies Azure Support or Microsoft Q&A with the Artifact Signing tag as the supported assistance channels for identity validation. ^2^

    Do not reset or duplicate the request yet

    Microsoft states that creating additional identity-validation requests for the same entity while one is in progress does not help, and validation requests cannot be expedited. ^2^

    The documented deletion operation is available only when a validation is not in the In Progress state. Deletion is irreversible and can stop renewal for linked certificate profiles, affecting signing. ^3^

    Therefore:

    • Do not create another request while this one remains In Progress.
    • Do not delete the Artifact Signing account as a reset attempt. Identity validations are subscription-scoped and remain after account deletion, while deleting the account removes its certificate profiles and stops associated signing. ^4^
    • If this is a renewal, the documented full review can take 1–20 business days. If it has exceeded that range without an actionable status, include that fact in the support case. ^3^

    Check the request details once for an outstanding action

    Open Artifact Signing account → Objects → Identity validations → affected validation. The documented workflow is:

    • In Progress: review is continuing.
    • Action Required: complete the displayed instruction; an email may also have been sent.
    • After the requested action is completed, the request can return to In Progress.
    • Completed or Failed: final result, accompanied by an updated-status email. ^4^

    If the details specifically request email verification, check the primary mailbox and its spam/filtering controls. Verification links expire after seven days and cannot be resent on the same request; an expired link requires a new request. Because the current request is still In Progress, obtain validation-team confirmation before attempting replacement. ^2^

    Avoid posting subscription, resource, validation, or correlation identifiers publicly; provide them through the private support request.

    References

    1. Create an Azure support request
    2. Artifact Signing FAQ
    3. Renew or delete Artifact Signing Identity Validations
    4. Quickstart: Set up Artifact Signing
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.