Artifact Signing account creation fails - ResourceCreationValidateFailed - EU organization (Greece)

Artifact Signing supports paid Azure subscriptions and is available for Public Trust certificates to organizations in the European Union, so a Microsoft Customer Agreement (MCA) subscription in the EU is supported in principle and a different subscription type is not required solely because the organization is in Greece.

However, Artifact Signing has these key constraints from the provided context:

1. Subscription type requirements
   • Artifact Signing does not support free, trial, or sponsored subscriptions. A paid subscription (such as an MCA-based pay-as-you-go or enterprise agreement) is required.
   • If an unsupported subscription type is used, the Azure portal shows an error when creating the Artifact Signing account or certificate profile.
2. Regional and identity requirements
   • For Public Trust certificates, Artifact Signing is available to organizations in the European Union, among other regions.
   • Identity validation details for Public Identity are automatically sourced from the Azure billing account under the subscription. The legal name, address, and organization details must exactly match what should appear on the Artifact Signing Public Trust certificate profile. Any discrepancy can cause issues in the onboarding/validation flow.
3. Other common blockers
   • The Microsoft.CodeSigning resource provider must be registered on the subscription before using Artifact Signing.
   • Identity validation can only be completed in the Azure portal, and the user must have the Artifact Signing Identity Verifier role to create identity validation requests.

Given the error ResourceCreationValidateFailed and that the subscription is an MCA (which is a supported paid model), the failure is more likely due to:

• A validation issue with the billing account data (for example, mismatch between legal entity name/address and what Artifact Signing expects for Public Trust), or
• A backend validation or account flag that requires Azure support intervention.

Recommended actions:

1. Confirm subscription eligibility
   • Ensure the subscription is not a free, trial, or sponsored type. It must be a fully active paid MCA subscription.
2. Verify billing account details
   • In the billing account associated with the subscription, verify that:
     • Legal name, address, and organization details are correct and match exactly what should appear on the certificate.
   • If needed, update billing account information as described in the billing account management documentation and then retry creating the Artifact Signing account.
3. Check Artifact Signing setup prerequisites
   • Ensure the Microsoft.CodeSigning resource provider is registered on the subscription (via the subscription’s Resource providers pane).
   • Use a supported region for the Artifact Signing account location.
4. Contact Azure support with the correlation ID
   • Because the error is a server-side validation failure, open a support ticket in the Azure portal, include the correlation ID, and ask support to review why ResourceCreationValidateFailed is being returned for Artifact Signing account creation on this MCA subscription.

A different subscription type is not required for EU organizations if the subscription is a paid, supported Azure subscription; resolving the validation failure will require checking billing/identity details and, if necessary, Azure support.

References:

• Artifact Signing FAQ
• Quickstart: Set up Artifact Signing
• az artifact-signing create
• Troubleshoot issues when you sign up for a new account in the Azure portal