Public Trust organization validation — eligibility of a 3-month-old US LLC, and which domain document qualifies

A three-month-old Utah LLC is not excluded by any minimum-age requirement in the current published Artifact Signing requirements, but Microsoft does not publish enough detail to confirm that the personally billed registrar invoice will satisfy domain ownership validation.

Organization age

The former public-preview requirement for three years of verifiable history does not appear in the current Artifact Signing quickstart or FAQ. The current requirements list organizations in the United States as eligible and require submission of the legal entity’s name, business identifier, address, website, and organization-owned email domain; they state no minimum operating history.^1^

Therefore:

• The LLC’s age is not a published eligibility blocker.
• This does not guarantee approval. Microsoft advises keeping the legal entity’s public records current so the validation team can verify it.
• Enter the LLC’s legal name and address exactly as recorded by Utah, along with a verifiable business identifier.

The earlier three-year answers applied to the restricted public-preview onboarding rules and should not be treated as the current requirement.^2^

Domain evidence

Current Artifact Signing documentation requires:

• A website belonging to the legal business entity.
• A monitored primary email address on a domain owned by that entity.
• A different secondary email address whose domain matches the primary address.
• Mailboxes that accept external messages containing verification links.^1^

It does not publish a definitive rule stating whether:

• An invoice billed to the sole member personally is acceptable when registrar contacts identify the LLC.
• Private WHOIS is acceptable.
• WHOIS privacy must be disabled.
• A particular registrar invoice or certificate guarantees approval.

Consequently, the existing invoice cannot be confirmed as qualifying evidence from the published requirements.

What to change first

Before paying for the service or consuming any document-review attempts:

1. Ask Azure Support for a pre-submission determination. Describe the personally billed invoice, private WHOIS, LLC-named registrar contacts, and Utah certificate of organization. The FAQ identifies Azure Support as the applicable assistance channel for identity-validation questions.^3^
2. As risk reduction—not a documented guarantee—ask the registrar for a receipt, ownership statement, or account record issued to the LLC’s exact legal name and registered address. It should identify the exact domain. This provides a clearer entity-to-domain link than an invoice addressed only to the member.
3. Do not disable WHOIS privacy merely to satisfy an assumed requirement. Artifact Signing documentation does not state that public WHOIS is mandatory. Disable it only if the validation team requests public WHOIS evidence and the privacy implications are acceptable.
4. Keep the Utah certificate of organization available and ensure these values match across the submission and supporting records:
   • Exact LLC legal name
   • Registered address
   • Business identifier
   • Website domain
   • Primary and secondary email domains

Before creating the validation request

Artifact Signing requires a paid Azure subscription; free, trial, and sponsored subscriptions are unsupported.^3^ When ready:

1. Assign the submitting user the Artifact Signing Identity Verifier role.
2. In Azure portal, open Artifact Signing account → Objects → Identity validations.
3. Select Organization → New Identity → Public.
4. Enter the exact legal-entity information and domain-based email addresses.
5. Monitor both the portal and primary mailbox. Verification links expire after seven days, and additional-document requests appear as Action Required.^1^

Avoid speculative submissions: if additional documents are requested, the FAQ states that all three attempts can be exhausted, after which onboarding cannot continue.^3^

References

1. Quickstart: Set up Artifact Signing | Microsoft Learn
2. Azure Trusted Signing - Can't Create an Individual Identity Validation - Microsoft Q&A
3. Artifact Signing FAQ | Microsoft Learn