A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
A newly registered U.S. LLC can currently submit an Artifact Signing Public Trust organization validation: the most recent Microsoft moderator answer addressing this exact case states that Artifact Signing has geographic onboarding prerequisites but no minimum organization-age restriction.^1^
Current-rule discrepancy
The published pages are inconsistent:
- The current Artifact Signing quickstart lists the United States as supported for organization Public Trust onboarding and does not specify a minimum age or three-year tax history.^2^
- The August 17, 2026 Microsoft moderator response explicitly says there are “no minimum org age restrictions.”^1^
- However, the MSIX signing overview still says organizations require three or more years of verifiable tax history.^3^
For Artifact Signing onboarding, the product quickstart and newer, case-specific Microsoft response indicate that your September 2026 formation date does not by itself disqualify the LLC. The three-year statement on the MSIX page appears inconsistent with that current Artifact Signing position.
Because you specifically want confirmation before incurring charges, open an Azure Support request and reference the conflicting pages before creating the Artifact Signing account. The Artifact Signing FAQ identifies Azure Support as the official assistance path for identity-validation questions.^4^
Information and evidence to prepare
The organization-validation form requires:
- The LLC’s exact legal name.
- A website belonging to the LLC.
- A monitored primary email address on the LLC-owned domain.
- A different secondary email address whose domain matches the primary address.
- A business identifier.
- The LLC’s legal address.
- The exact government-ID name of the representative completing individual identity verification.^2^
The quickstart does not publish a definitive U.S.-specific document checklist. It says the request can move to Action Required, at which point the validation team sends instructions if additional documents are needed. Prepare documents that consistently establish:
- The LLC’s legal formation and active registration.
- Its legal name and address.
- Its business identifier, such as EIN or D‑U‑N‑S.
- Ownership or control of the website domain.
- The authorized representative’s government identity.
Do not assume that supplying extra documents overrides validation: if Microsoft cannot validate the submitted information, onboarding can fail, and only three document-submission attempts are available.^4^
Ensure the legal name, address, business identifier, website, domain email, and public government records all agree before submitting. Artifact Signing does not permit a custom certificate Organization value; the certificate uses the validated legal-entity name.^4^
Before creating the billable account
- Open an Azure Support ticket under Artifact Signing / Identity validation.
- State that the LLC was formed in September 2026 and request written confirmation that the current “no minimum organization age” rule applies.
- Include the conflicting MSIX eligibility page and the August 2026 Microsoft moderator answer.
- Ask whether the validation provider requires any specific U.S. documents beyond state registration, EIN/D‑U‑N‑S evidence, domain evidence, and the representative’s ID.
- Create the account only after receiving confirmation.
Artifact Signing requires a paid Azure subscription; free, trial, and sponsored subscriptions are unsupported.^4^ If validation later fails and Microsoft cannot determine the organization’s identity, the FAQ recommends deleting the Artifact Signing account to avoid charges for an unused resource.
References