Azure Artifact Signing Basic: SignCompleted returns Success with empty timeseries — how to verify monthly usage?

Tag: Artifact Signing

We use an active Azure Artifact Signing Basic account with a Public Trust profile for signing a Windows application. We need an authoritative, read-only way to determine monthly signing operations before building a validation candidate, to avoid exceeding included usage.

When querying Azure Monitor's SignCompleted metric with Total aggregation for the current UTC month-to-date, the API responds with errorCode: Success but timeseries: []. We reproduced this with hourly and daily intervals. We did not interpret empty telemetry as zero usage. No diagnostic settings exist for the resource. The account's owner believes fewer than 50 signatures have been used this month, but this is not verifiable from the returned metrics.

Could Microsoft clarify:

1. Is an empty SignCompleted timeseries an expected result for active Basic accounts, including when some signatures have already been completed?
2. Is there a supported authoritative read-only usage or billing API, Portal counter, or log that shows cumulative monthly signature operations without requiring a new chargeable diagnostics destination?
3. Does Azure Monitor provide a supported method for reconstructing a complete month-to-date total when datapoints are missing, or should signing remain paused until support confirms usage?
4. Are there telemetry propagation delays or specific permissions/configuration needed for this metric?

We are not requesting certificate or credential changes. We have paused all new signing operations until we can account for usage reliably. Thanks.