A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
That message usually means the role assignment has not taken effect yet, or the role was not assigned at the correct scope.
- In the Azure portal, open the Artifact Signing account.
- Verify that the signed-in user has the Artifact Signing Identity Verifier role on the Artifact Signing resource.
- This role is required to create or manage identity validation.
- Identity validation can be done only in the Azure portal, not through Azure CLI.
- If the New identity button is still dimmed or the step does not progress, wait for RBAC propagation.
- Role assignment changes can take up to 10 minutes to take effect.
- Sign out of the Azure portal and sign back in to force a refresh.
- Also confirm the account has at least Reader role at the subscription scope, because users assigned Artifact Signing Identity Verifier must already have at least Reader at subscription scope.
- Then go to the Artifact Signing account Overview or Objects > Identity validations and try again.
If the button remains inactive after the role is visible and enough time has passed, create a support ticket in the Azure portal.