A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Azure Artifact Signing sign operation returns status Failed with null signature, active Public Trust profile
Azure Artifact Signing / Microsoft.CodeSigning issue.
Account appears healthy, but every sign operation fails after the service accepts the request.
Environment:
- Region: East US
- Endpoint: https://eus.codesigning.azure.net/
- Account provisioningState: Succeeded
- Certificate profile: PublicTrust, provisioningState Succeeded, status Active
- Identity validation: Completed
- Active certificates are present
- Microsoft.CodeSigning provider is Registered
- Signing user has Artifact Signing Certificate Profile Signer role
- SignTool x64 and Azure.CodeSigning.Dlib 1.0.119 are installed
- .NET 8 runtime installed
Failure:
Sign request is submitted successfully, then operation resolves to:
{
"status": "Failed",
"signature": null,
"signingCertificate": null,
"counterSignature": null
}
Reproduced with:
- Bahast.exe
- Tiny throwaway test EXE
- SignTool + Azure.CodeSigning.Dlib
- .NET sign tool / Artifact Signing client
- With timestamping and without timestamping
- Minimal metadata and metadata with ExcludeCredentials
Recent operation IDs:
- PII
New Public Trust profile creation attempts also reached terminal provisioningState Failed, and failed profile deletes also failed.
Can the Artifact Signing backend team check whether this account/profile/identity validation is stuck, suspended, or blocked server-side?