Artifact Signing sign returns Failed / null signature after subscription reactivation

Question

Subscription was disabled for non-payment, then reactivated. Certificate

profile Luphia-Voice-PublicTrust is Active. Account ARM looks healthy:

/subscriptions/360347f3-9da5-4f4d-b9c7-ae60ff4f6853/resourceGroups/Luphia.ai/providers/Microsoft.CodeSigning/codesigningaccounts/Luphia-Voice

provisioningState: Succeeded

location: eastus

accountUri: https://eus.codesigning.azure.net/

GitHub Actions authenticates and Azure accepts the sign (HTTP 200,

OperationId InProgress), then:

{"status":"Failed","signature":null,"signingCertificate":null,"counterSignature":null}

Operation IDs:

58330cc5-2e3b-4bbc-940b-a84af3df4986 (2026-08-19 15:56:20 UTC)

56bcccad-34db-46ad-a685-d8d97678b8b8 (2026-08-19 16:28:56 UTC)

Same pattern as Q&A 5915363 and 5972241. Portal will not let me file a

technical support ticket (Basic SKU, no support plan). Please escalate

to Artifact Signing engineering to reset the account state.

Answer 1

Hi,

The symptoms you described strongly suggest a backend/account-state issue rather than a GitHub Actions, RBAC, or certificate-profile configuration problem.

There are recent Microsoft Q&A cases with the same pattern: the subscription was disabled and subsequently reactivated, authentication began succeeding again, but signing operations continued to complete as:

{
  "status": "Failed",
  "signature": null,
  "signingCertificate": null,
  "counterSignature": null
}

In one similar case, Microsoft confirmed it was a backend issue and signing subsequently started working again. Another recent case specifically involving subscription reactivation was directed to the Artifact Signing team for backend investigation.

Given that your account is Succeeded, the certificate profile is Active, the sign request is accepted with HTTP 200, and the operation subsequently fails without an errorResponse, I would avoid making further configuration changes for now.

I recommend escalating this to Microsoft with the operation IDs you provided:

• 58330cc5-2e3b-4bbc-940b-a84af3df4986

56bcccad-34db-46ad-a685-d8d97678b8b8

Ask the Artifact Signing team to check the server-side signing/certificate issuance state following the subscription reactivation.

If you don't have a technical support plan, a previous Microsoft Q&A response suggested trying an Azure Billing support request, since Billing support may be available even when a technical support request isn't.

I would include the following in the escalation:

Subscription was disabled for non-payment and later reactivated.

Artifact Signing account is Succeeded.

Certificate profile is Active.

Sign requests are accepted but finish with status: Failed.

signature, signingCertificate, and counterSignature are null.

No useful errorResponse is returned.

The issue occurs consistently after reactivation.

Include the operation IDs and UTC timestamps.

This looks much more consistent with a service-side state that needs to be repaired/reset than with a problem in your signing command or GitHub authentication.Hi,

The symptoms you described strongly suggest a backend/account-state issue rather than a GitHub Actions, RBAC, or certificate-profile configuration problem.

There are recent Microsoft Q&A cases with the same pattern: the subscription was disabled and subsequently reactivated, authentication began succeeding again, but signing operations continued to complete as:

{
  "status": "Failed",
  "signature": null,
  "signingCertificate": null,
  "counterSignature": null
}

In one similar case, Microsoft confirmed it was a backend issue and signing subsequently started working again. Another recent case specifically involving subscription reactivation was directed to the Artifact Signing team for backend investigation.

Given that your account is Succeeded, the certificate profile is Active, the sign request is accepted with HTTP 200, and the operation subsequently fails without an errorResponse, I would avoid making further configuration changes for now.

I recommend escalating this to Microsoft with the operation IDs you provided:

58330cc5-2e3b-4bbc-940b-a84af3df4986

56bcccad-34db-46ad-a685-d8d97678b8b8

Ask the Artifact Signing team to check the server-side signing/certificate issuance state following the subscription reactivation.

If you don't have a technical support plan, a previous Microsoft Q&A response suggested trying an Azure Billing support request, since Billing support may be available even when a technical support request isn't.

I would include the following in the escalation:

Subscription was disabled for non-payment and later reactivated.

Artifact Signing account is Succeeded.

Certificate profile is Active.

Sign requests are accepted but finish with status: Failed.

signature, signingCertificate, and counterSignature are null.

No useful errorResponse is returned.

The issue occurs consistently after reactivation.

Include the operation IDs and UTC timestamps.

This looks much more consistent with a service-side state that needs to be repaired/reset than with a problem in your signing command or GitHub authentication.