A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
A newly formed Ohio LLC can submit an Organization/Public Trust validation request; the current Artifact Signing requirements list U.S. organizations as supported and do not state a minimum organization age or require three years of tax history.^1^
Approval is not guaranteed: Microsoft must be able to verify the LLC as a legal business entity from the submitted information, public records, and any subsequently requested evidence.
Which rule applies
The current onboarding requirements should control:
- Organizations in the United States are eligible to apply.
- The organization workflow requests a legal business name, website, business-domain email addresses, business identifier, legal address, and details for the representative.
- The published prerequisites and validation instructions do not impose a fixed three-year organization or tax-history threshold.^1^
- Public records for the legal entity should be current before submission. A very new entity may therefore be harder to verify automatically, but that is an evidence/verification issue rather than a documented minimum-age rule.
Public Trust is the appropriate model for a Windows installer intended for public distribution; its certificate profile is trusted by default on Windows for code signing.^2^
Business identifier and evidence for the Ohio LLC
Microsoft’s current form says to enter a business identifier for the legal business entity, but the available official instructions do not prescribe one specific identifier type or format for a U.S. LLC.^1^
Use an identifier that independently resolves to the LLC’s exact legal record:
- Prefer the LLC’s Ohio state entity/registration number if the portal accepts it and that number is publicly searchable.
- If the form or validation request specifically calls for a D‑U‑N‑S number, use the LLC’s D‑U‑N‑S record only after its legal name and address match the Ohio registration.
- Do not substitute a personal identifier. Enter Visualize Build LLC exactly as recorded by Ohio, including punctuation and suffix.
- Use the LLC’s registered business address consistently across the portal, public registry, website, and identifier record.
The current official instructions do not provide a definitive U.S.-specific document checklist. If the request changes to Action Required, Microsoft sends an email directing the representative to provide the required material. The workflow recognizes that additional documents might be requested before validation completes.^1^
Prepare current documents that establish the same legal name, identifier, and address, such as:
- Ohio formation or registration evidence;
- the LLC’s articles of organization or equivalent state filing;
- an identifier record, if using D‑U‑N‑S;
- evidence requested specifically by the validation team.
The accepted guidance for organization validation describes official business registration forms, charters, or articles of incorporation as supporting business evidence, although that answer concerns a Spanish business rather than a U.S. LLC and therefore does not establish a U.S.-specific mandatory list.^3^
Before creating the paid resource
Artifact Signing requires a paid Azure subscription; free, trial, and sponsored subscriptions are unsupported.^4^ However, the Azure billing account itself does not need an Organization account type for organization identity validation.^1^
Before submitting:
- Confirm the Ohio public registry shows the exact current legal name and address.
- Ensure the website belongs to the LLC.
- Create two monitored email addresses on the LLC’s domain; the secondary address must differ from the primary, and both must accept external messages containing links.
- Ensure the representative’s first and last names exactly match their government-issued identification.
- After creating the Artifact Signing account, assign the representative the Artifact Signing Identity Verifier role.
- Open Artifact Signing account → Objects → Identity validations → Organization → New Identity → Public.
- Submit once and monitor the request for In Progress, Action Required, Completed, or Failed.^1^
If validation fails for a reason other than a missed email, the FAQ says Microsoft could not make a determination from the supplied information. Do not repeatedly submit speculative variations: additional-document requests are limited to three attempts, and duplicate in-progress requests do not expedite validation. Use Azure Support for case-specific review.^4^
References