Artifact Signing: Certificate profiles blade fails to load ("An error occurred while loading the certificate profiles")

Create and manage the certificate profiles through Azure CLI or Azure PowerShell; the exact CertificateProfilesList.ReactView/BatchCallFailed 404 failure is not publicly documented as a known issue, and there is no documented client-side fix for that portal blade.

Artifact Signing officially supports the portal, Azure CLI, and Azure PowerShell for certificate-profile management. Because your profile succeeds through ARM and opens directly, while only the collection blade fails—even when the account contained no profiles—the supported non-portal path is the practical workaround rather than more browser or identity-validation troubleshooting.^1^

Create and verify a profile with Azure CLI

Use the completed organization validation’s Identity validation Id, available under Artifact Signing account → Objects → Identity validations → your completed validation.

az login
az account set --subscription "<subscription-id>"
az extension add --name artifact-signing

az artifact-signing certificate-profile create \
  --resource-group "<resource-group>" \
  --account-name "<artifact-signing-account>" \
  --name "<profile-name>" \
  --profile-type PublicTrust \
  --identity-validation-id "<identity-validation-id>"

az artifact-signing certificate-profile show \
  --resource-group "<resource-group>" \
  --account-name "<artifact-signing-account>" \
  --name "<profile-name>"

To bypass the broken portal list and enumerate profiles directly:

az artifact-signing certificate-profile list \
  --resource-group "<resource-group>" \
  --account-name "<artifact-signing-account>" \
  --output table

A profile name must contain 5–100 alphanumeric characters, start with a letter, end with a letter or number, contain no consecutive hyphens, and be unique within the account.^1^

Because your ARM-created profile is already Succeeded/Active, do not recreate it merely to work around the list blade. The CLI show and list operations can manage and inspect the existing resource.

PowerShell alternative

New-AzArtifactSigningCertificateProfile `
  -AccountName "<artifact-signing-account>" `
  -ResourceGroupName "<resource-group>" `
  -ProfileName "<profile-name>" `
  -IdentityValidationId "<identity-validation-id>" `
  -ProfileType PublicTrust

Get-AzArtifactSigningCertificateProfile `
  -AccountName "<artifact-signing-account>" `
  -ResourceGroupName "<resource-group>" `
  -ProfileName "<profile-name>"

A completed matching identity validation is required before creating a certificate profile. Owner and Contributor can manage certificate profiles; the Artifact Signing Certificate Profile Signer role authorizes signing but does not itself grant profile management.^2^

Portal resolution and escalation

There is no public Microsoft notice confirming this exact extension error as a known portal incident. The successful ARM operation demonstrates a narrower portal-listing failure, but only Microsoft support can determine whether its 404 responses come from the portal extension, service routing, or account/resource state.

Open the affected Artifact Signing account and select Support + Troubleshooting under Help. If the suggested diagnostics do not resolve it, select Create a support request.^3^

Include:

• Session ID and UTC timestamp of a fresh reproduction.
• Extension: Microsoft_Azure_CodeSigning.
• Content: CertificateProfilesList.ReactView.
• Console message: CertificateProfilesList BatchCallFailed: getAllCertificateProfiles api failed.
• A HAR/browser network trace showing the failing requests, response bodies, request/correlation IDs, and 404 endpoints.
• Subscription, resource group, account name, East US region, and Basic tier.
• The successful ARM deployment operation/correlation ID and API version.
• Output from CLI list and show.
• The fact that the failure predates profile creation and persists while the existing profile is Succeeded/Active.
• Confirmation that Identity validations loads and the organization validation is Completed.

Avoid posting the HAR, access tokens, subscription identifiers, or validation identifiers publicly; attach them privately to the support case. Microsoft’s support guidance specifically recommends supplying reproduction timing and allows a browser trace or compressed diagnostic file to be uploaded.^3^

References

1. Quickstart: Set up Artifact Signing | Microsoft Learn
2. Artifact Signing resources and roles
3. Create an Azure support request