A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
A U.S. LLC formed on November 19, 2026 should not create a paid Artifact Signing account for Organization Public Trust yet, because Microsoft’s current MSIX guidance requires organizations to have at least three years of verifiable tax history, and Microsoft Q&A documents rejection of organizations incorporated less than three years ago.^1^^2^
Minimum business history
There is a documentation inconsistency:
- The Artifact Signing quickstart lists supported regions and the organization-validation fields, but its current prerequisites do not state a minimum organization age.^3^
- The current MSIX signing overview explicitly says organizations must have three or more years of verifiable tax history.^1^
- A closely matching Microsoft Q&A case says onboarding could not proceed because the organization was incorporated less than three years earlier.^2^
An EIN, D‑U‑N‑S record, domain, and monitored mailboxes help establish and verify the entity, but the available Microsoft material does not say that they waive or replace the three-year history requirement.
If signing under the owner’s personal legal identity is acceptable, Individual Public Trust is available to developers in the United States. That is a separate validation path: the certificate identity is the individual rather than the LLC, and the associated Azure billing account must have an Individual account type with a legal name and sold-to address matching the government ID.^3^
Business Identifier
Microsoft’s current Artifact Signing quickstart only says to enter “a business identifier for the legal business entity.” It does not define whether a U.S. LLC must enter its:
- EIN,
- D‑U‑N‑S number, or
- state registration/Secretary of State number.^3^
Therefore, there is no supported basis for declaring one of those identifiers mandatory for a U.S. LLC. Do not guess before paying or submitting. Open an Azure support request and ask Artifact Signing support to confirm the accepted U.S. identifier type for the organization-validation form; the FAQ identifies Azure Support as the official assistance channel.^4^
When eventually submitting, ensure that the legal name and address match the selected public record exactly. Other Microsoft company-verification guidance recognizes government registries, tax records, D‑U‑N‑S records, state registries, financial-institution statements, and utility statements as verification evidence, but that page does not establish which identifier Artifact Signing specifically requires.^5^
Documents to prepare
Artifact Signing does not publish a fixed document package for every new U.S. LLC. The documented workflow is:
- Submit the legal entity name, business address, website, business identifier, representative’s legal name, and two monitored addresses on the organization’s email domain.
- Complete the representative’s individual identity verification when the status becomes Action Required.
- If additional organizational evidence is needed, Microsoft sends an email and changes the request to Action Required.^3^
Prepare current documents that consistently show the LLC’s exact legal name and address, such as:
- North Carolina formation or registration record.
- IRS EIN confirmation or tax record.
- D‑U‑N‑S record after it becomes publicly verifiable.
- Business bank or utility statement, if available.
- Domain ownership or registration record.
- Government-issued ID for the representative.
The first four categories are examples of records used in Microsoft company verification generally, not a guarantee that Artifact Signing will request or accept every item.^5^
Keep public records synchronized before submission. Corrections require deleting and recreating the identity-validation request, and only three additional-document attempts are available before onboarding cannot continue.^4^
Practical alternatives
Until the LLC meets organization eligibility:
- Use Individual Public Trust if displaying the owner’s personal validated identity is acceptable.
- For Microsoft Store distribution, submit the package unsigned by your own production certificate; the Store signs it during submission.^6^
- For non-Store production distribution under the LLC name, obtain an organization-validation code-signing certificate from a public certificate authority, subject to that authority’s validation rules.^6^
References