Create the certificate profile with Azure CLI to bypass the failing CertificateProfilesList.ReactView portal page, then check Azure Service Health for a recognized service incident.
Create the certificate profile outside the portal
Artifact Signing certificate profiles can be created and managed through the artifact-signing Azure CLI extension. Azure CLI 2.75.0 or later is required, and the extension installs automatically when the command is first used.^1^
- Open Azure Cloud Shell or a terminal with Azure CLI installed.
- Sign in and select the subscription containing the Artifact Signing account.
- Replace the example values and run:
az login
az account set --subscription "<subscription-name-or-id>"
az artifact-signing certificate-profile create \
--resource-group "<resource-group>" \
--account-name "<artifact-signing-account>" \
--profile-name "<new-profile-name>" \
--profile-type PublicTrust \
--identity-validation-id "<completed-validation-id>"
- Verify that the profile was created:
az artifact-signing certificate-profile show \
--resource-group "<resource-group>" \
--account-name "<artifact-signing-account>" \
--profile-name "<new-profile-name>"
az artifact-signing certificate-profile list \
--resource-group "<resource-group>" \
--account-name "<artifact-signing-account>" \
--output table
Valid profile types include PublicTrust, PublicTrustTest, PrivateTrust, PrivateTrustCIPolicy, and VBSEnclave.^1^
You need a completed identity validation matching the profile type. Its ID is normally available under:
Artifact Signing account → Objects → Identity validations → select the validated entity → Identity validation Id
Microsoft’s quickstart documents both the CLI and PowerShell creation methods.^2^
If the Identity validations page is also inaccessible and the ID was not previously recorded, the CLI workaround cannot supply that required value; proceed to the incident/support path below.
Check whether Microsoft has recognized an incident
In the Azure portal, go to:
Service Health → Service issues
Filter for the affected subscription, region, and Artifact Signing. Service Health provides subscription-specific incident information and is more precise than the global Azure Status page.^3^
- If an incident is listed: follow its updates rather than opening repeated requests. Microsoft states that the latest information is provided through Service Health when an incident is already being communicated.^4^
- If no incident is listed: open a support request and explicitly describe it as an apparent Azure service disruption affecting the Artifact Signing certificate-profile blade—not as help configuring a certificate.
Include:
- Error/component:
CertificateProfilesList.ReactView
- UTC timestamp and region
- Subscription ID, resource group, and Artifact Signing account name
- Screenshot and full error text
- Browser request/correlation ID, if displayed
- Whether CLI
list and create succeed or fail
- Business impact: unable to create a required signing certificate profile
Azure normally requires a support plan for technical support; free subscription-management support does not generally cover product technical failures.^5^ However, Microsoft states that customers affected by a service disruption can raise a free support ticket for up to 72 hours after the incident is mitigated.^4^ That exception depends on Microsoft recognizing the event as a service disruption; a portal error by itself does not establish that status.
References
- az artifact-signing certificate-profile | Microsoft Learn
- Quickstart: Set up Artifact Signing
- Azure Service Health FAQ
- What to do during an Azure service disruption
- Create an Azure support request
