Deleted Public Trust certificate profile still counts against Basic tier limit

Set Certificate Profiles → Status: All; if the deleted profile is absent, open an Azure support request for Artifact Signing backend quota cleanup rather than retrying deletion or profile creation.

1. Check for a hidden profile state

In the Azure portal:

1. Open the DrumOne Artifact Signing account.
2. Select Certificate Profiles.
3. Change the status filter to All.
4. Check whether DrumOnePublic appears in a nondefault state such as deleting or deleted.

Microsoft specifically documents using Status: All to expose profiles relevant to Basic-tier limits. Basic permits one profile of each type.^1^

Since the normal list is already empty and creation remains blocked after more than 24 hours, do not repeat the deletion. If Status: All is also empty, the portal offers no remaining profile that you can remove.

2. Request backend quota cleanup

Microsoft Q&A cannot access the subscription or reset the quota. Open the request from:

DrumOne → Support + Troubleshooting → Create a support request

If that route does not expose an Artifact Signing category, use the Azure portal’s global Help + Support → Create a support request workflow. Microsoft documents both entry points and recommends including the affected resource, start time, reproduction steps, and diagnostic material.^2^

Use wording such as:

Artifact Signing Basic Public Trust certificate-profile quota remains consumed after deletion

Account: DrumOne
Region: East US
SKU: Basic
Deleted profile: DrumOnePublic
Deleted: 2026-10-22, with exact UTC timestamp attached
Current state: Certificate Profiles with Status set to All is empty
Operation attempted: Create Public Trust profile ProdByMaiPublic
Error: “You have reached maximum limit of certificate profiles of selected type in this account”
Session ID: 668fe314a935495eab1cba0678cc21e6
Identity validation: Organization/Public, Completed

Please route this to the Artifact Signing service team to inspect and clear the stale Public Trust certificate-profile quota state.

Attach or provide privately:

• Subscription ID and resource ID.
• Identity validation ID.
• Exact UTC deletion and failed-creation timestamps.
• Activity Log event for the failed certificateProfiles/write.
• Correlation/request ID, if shown.
• Screenshot showing Status: All with no profiles.
• The error and session ID already captured.

Do not post subscription or validation identifiers publicly. A closely matching Basic-tier incident reports an empty profile list followed by the same maximum-limit error, including cases across multiple accounts, which is useful to reference in the ticket.^3^

Temporary workaround

If signing is urgent and the additional cost is acceptable, upgrading DrumOne to Premium raises the documented limit from one to ten profiles of each type:

DrumOne → Overview → SKU (Pricing tier) → Premium → Update

SKU updates take effect beginning with the next billing cycle, so this might not unblock the operation immediately.^1^ Keep the support request open because upgrading does not correct the underlying stale count.

After the replacement profile is created, account for its new durable identity/EKU: deleting and recreating a certificate profile assigns the new profile a different EKU, so any application or policy pinned to the old profile EKU must be updated.^4^

References

1. Change an Artifact Signing account SKU (pricing tier)
2. Create an Azure support request
3. Artifact Signing Basic: Public Trust profile quota still reached after ...
4. Artifact Signing certificate management