Share via

Can't create a new Trusted Signing Individual identity because my country is not available

Sébastien 20 Reputation points
2026-03-06T09:58:16.4+00:00

Hello,

My country (France) is not available under Country/Region in the new individual validation form (it is a public individual identity in Trusted Signing / Artifact Signing Account) and cannot be written manually. Only 4 countries are available (see screenshot). Is that a bug? Thanks in advance for your help.Image

Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments
Answer accepted by question author
  1. Q&A Assist
    2026-03-06T09:58:30.98+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    France not appearing in the Country/Region list for a new public Individual identity in Trusted Signing is expected behavior and not a bug.

    According to the Trusted/Artifact Signing public preview requirements:

    • For Public Trust certificates, Artifact Signing is currently available only to:
      • Organizations in the USA, Canada, the European Union, and the United Kingdom
      • Individual developers in the USA and Canada

    For individual developers, onboarding has been limited further during the public preview. A recent update states that the service is now restricted to new customer subscriptions from organizations based in the United States and Canada with at least three years of verifiable history, and individual developer onboarding has been paused. As a result, tenants outside the supported geographies (including France for individual developers) cannot submit new public individual identity validation requests.

    To proceed, the available options are:

    1. Use Artifact Signing only for Private Trust scenarios (these limitations do not apply to Private Trust certificates) if that meets the signing requirements.
    2. If an organization in a supported country/region meets the onboarding criteria, create an organization public identity validation instead of an individual one.
    3. Monitor Microsoft communications and the Trusted Signing documentation for updates on expanded regional support or resumption of individual developer onboarding.

    If eligibility is still unclear or the tenant should meet the stated criteria, open a support ticket from the Azure portal for confirmation and any tenant-specific guidance.

    References:

    0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.