Artifact Signing Identity Verifier role is effective, but Identity validations shows “Unable to fetch data”

Question

Artifact Signing Identity Verifier role is effective, but Identity validations shows “Unable to fetch data”

Hiren Desai 0

I am setting up Azure Artifact Signing organisation identity validation. The Identity validations page keeps the “New identity” button disabled and displays:

“Please ensure you have the ‘Artifact Signing Identity Verifier’ role assigned.”

“Unable to fetch data.”

Access Control (IAM) and “View my access” confirm that:

The built-in Artifact Signing Identity Verifier role is assigned directly to my user at the Artifact Signing account scope.

I have inherited access at the subscription level.

There are no deny assignments.

The Artifact Signing account is in East US.

The required tsvettinggateway.portal.codesigning.azure.net endpoint is reachable directly.

The organisation is based in New Zealand, which Microsoft lists as a supported country for Public Trust organisation identity validation.

I have refreshed the page and signed out and back in, but the problem remains.

Could Microsoft please confirm whether this is a backend role-mapping or Identity Validation API problem and advise how to restore access without recreating the account?

kagiyama yutaka 5,330 Reputation points

2026-09-01T23:23:02.7833333+00:00

I think the Verifier role at the Artifact‑Signing‑account scope already satisfies what the portal checks, and “Unable to fetch data” means the identity‑validation list didn’t load because the backend validation API isn’t responding. Azure treats this as a backend issue, and Artifact Signing onboarding failures can be raised through the free “service not working” path. When the validation API doesn’t respond, the portal keeps “New identity” disabled until the backend is fixed.
Hiren Desai 0 Reputation points

2026-09-02T02:35:25.5066667+00:00

Thank you. I tried the “service not working” path in the Azure portal. It correctly classified this as Artifact Signing → Identity Validation - Organization → Submitting Validation Request, but the Additional details page said my Basic plan covers only billing, subscription management and quota requests. It required a paid support plan starting at US$29 per month. So this path is not free for my subscription. It seems unreasonable to pay US$29 per month for support for a service costing about US$9 per month, especially when identity validation will not load and the service cannot yet be used.
kagiyama yutaka 5,330 Reputation points

2026-09-02T03:22:37.7133333+00:00

Thanks for updates, I think the Basic‑plan banner is generic. Artifact Signing onboarding failures are still free under “service not working”, and you can still submit the ticket without a paid support plan.
Hiren Desai 0 Reputation points

2026-09-02T04:56:17.88+00:00
Here is the exact path I took:

Azure portal → Support + troubleshooting → Create a support request.

Issue type: Technical; Service: Artifact Signing.

Problem type: Identity Validation - Organization.

Problem subtype: Submitting Validation Request.

I continued past Recommended solution.

Additional details said Basic covers only billing, subscription management and quota requests; technical support requires a paid plan from US$29/month; and Next was disabled.

The screenshots exclude subscription, resource and account identifiers. Where exactly should I click to submit without a paid plan? Please share the specific step or official Microsoft documentation.
kagiyama yutaka 5,330 Reputation points

2026-09-02T07:43:49.75+00:00

so Sorry for the confusion. my support‑plan guidance was incorrect. Mohammad’s answer is the correct one. Artifact Signing issues aren’t covered under the free “service not working” path, so Basic support can’t submit technical tickets.

1 answer

Your answer

kagiyama yutaka 5,330 Reputation points

2026-09-01T23:23:02.7833333+00:00

I think the Verifier role at the Artifact‑Signing‑account scope already satisfies what the portal checks, and “Unable to fetch data” means the identity‑validation list didn’t load because the backend validation API isn’t responding. Azure treats this as a backend issue, and Artifact Signing onboarding failures can be raised through the free “service not working” path. When the validation API doesn’t respond, the portal keeps “New identity” disabled until the backend is fixed.
Hiren Desai 0 Reputation points

2026-09-02T02:35:25.5066667+00:00

Thank you. I tried the “service not working” path in the Azure portal. It correctly classified this as Artifact Signing → Identity Validation - Organization → Submitting Validation Request, but the Additional details page said my Basic plan covers only billing, subscription management and quota requests. It required a paid support plan starting at US$29 per month. So this path is not free for my subscription. It seems unreasonable to pay US$29 per month for support for a service costing about US$9 per month, especially when identity validation will not load and the service cannot yet be used.
kagiyama yutaka 5,330 Reputation points

2026-09-02T03:22:37.7133333+00:00

Thanks for updates, I think the Basic‑plan banner is generic. Artifact Signing onboarding failures are still free under “service not working”, and you can still submit the ticket without a paid support plan.
Hiren Desai 0 Reputation points

2026-09-02T04:56:17.88+00:00

Here is the exact path I took:

Azure portal → Support + troubleshooting → Create a support request.

Issue type: Technical; Service: Artifact Signing.

Problem type: Identity Validation - Organization.

Problem subtype: Submitting Validation Request.

I continued past Recommended solution.

Additional details said Basic covers only billing, subscription management and quota requests; technical support requires a paid plan from US$29/month; and Next was disabled.

The screenshots exclude subscription, resource and account identifiers. Where exactly should I click to submit without a paid plan? Please share the specific step or official Microsoft documentation.
kagiyama yutaka 5,330 Reputation points

2026-09-02T07:43:49.75+00:00

so Sorry for the confusion. my support‑plan guidance was incorrect. Mohammad’s answer is the correct one. Artifact Signing issues aren’t covered under the free “service not working” path, so Basic support can’t submit technical tickets.

Answer 1

Mohammad Wasi Haider 165

Hi Hiren,

Based on what you have already verified, this does not look like a normal RBAC configuration issue. The Artifact Signing Identity Verifier role is the correct built-in role for managing identity validation, and New Zealand is supported for Public Trust signing.

Since IAM recognizes the assignment but the Identity validations blade still returns “Unable to fetch data” and keeps “New identity” disabled, I would treat this as an Artifact Signing portal/backend validation issue rather than recreate the account.

Please open an Azure support request for Artifact Signing and include the Artifact Signing account resource ID, tenant ID, UTC timestamp of the failure, screenshot, and any correlation/request ID shown in the browser or Activity Log. Microsoft support can check the backend identity-validation request and role evaluation.

I would not delete or recreate the Artifact Signing account at this stage.

Thank you, and feel free to respond back for more assistance.

Hiren Desai 0 Reputation points

2026-09-01T22:48:27.5766667+00:00

Thank you. Am I understanding this correctly: to get help with a backend or portal failure affecting an Artifact Signing service that costs about US$9 per month, I would need to purchase a separate support plan? The US$29 per month Developer plan appears to provide prioritised Q&A responses, while direct one-to-one technical support starts at US$100 per month. Is there a no-cost escalation route specifically for Artifact Signing identity-validation or onboarding failures when the service cannot yet be used? It sounds silly to pay $29 to get support for $9 service that is potentially misconfigured!