Azure Artifact Signing requests accepted but fail internally after subscription reactivation

I’m having an issue with Azure Artifact Signing after my subscription was temporarily placed in a warning/billing state and then reactivated.

Current state:

• Subscription status: Active
• Artifact Signing account: gwospactsigning
• Region: East US
• Certificate profile: pact-desktop-code-signing
• Profile type: Public Trust
• Certificate profile status: Active
• Correct Artifact Signing signer role is assigned
• Account endpoint: https://eus.codesigning.azure.net/

Signing requests are successfully accepted by Azure and return an operation ID, but the operation then fails internally and the executable remains unsigned.

Example failed operation ID: f7995f43-9780-41d2-9fec-a59e4d8f2684

Azure Activity Log shows the certificate profile operations succeeding and does not show an ARM/control-plane failure corresponding to the signing operation.

This started after the subscription billing warning/reactivation event. The subscription, Artifact Signing account, and certificate profile now all appear healthy in the Azure Portal.

I have not deleted or recreated the signing account/profile because there is no visible configuration failure.

Could someone from the Artifact Signing team check the backend state for this account/operation ID and confirm whether the signing service needs to be resynchronized after the subscription reactivation?