Artifact Signing Public Trust eligibility for an Israeli osek patur (sole proprietor) before paid setup

Israel is supported for Organization Public Trust validation, but Microsoft’s published policy does not confirm that every Israeli osek patur automatically qualifies; obtain a case-specific determination through Azure Support before creating the Artifact Signing account.

What the documentation confirms

• Geographic eligibility: Organizations in Israel can apply for Public Trust validation. The U.S./Canada restriction applies to the separate Individual Developer workflow, not to the individual identity check performed as part of organization validation.^1^
• Organization/DBA workflow: The portal supports an identity-validation request for an Organization or DBA. It asks for the legal organization name, business identifier, business address, website, two business-domain email addresses, and the representative’s identity information.^1^
• Billing-account type: Organization validation does not require the Azure billing account itself to have an Organization account type. The billing-account matching rules documented in the quickstart apply to Individual Developer validation.^1^

These points establish that the Organization/DBA route is the applicable route to investigate. They do not establish that osek patur registration necessarily satisfies the underlying legal-business validation.

Records and identifiers

The Artifact Signing documentation does not publish an Israel-specific list of accepted:

• osek patur records;
• VAT/tax identifiers;
• business-registration numbers;
• trade-name registrations; or
• equivalent registry extracts.

The organization form requires a Business Identifier, and Microsoft advises keeping public records for the legal business entity current. If automated validation is insufficient, the request can move to Action Required, and the validation team may request documents privately.^1^

The directly matching Microsoft Q&A discussions about sole proprietors and government business-registration evidence do not contain an accepted or platform-recommended answer establishing a definitive document list.^2^^3^

Consequently, it cannot be confirmed publicly whether a VAT exemption certificate, Israeli Tax Authority registration, trade-name record, or another specific document is sufficient.

Certificate name and trade name

Artifact Signing does not permit an arbitrary Common Name (CN) or Organization (O) value. The certificate uses the identity validated by Microsoft, and the FAQ states that the CN must be the legal entity’s validated name.^4^

Therefore:

• The proprietor’s legal name will be used if that is the identity Microsoft can validate.
• A trade name may appear only if Microsoft accepts and validates that name through the Organization/DBA process.
• A product or brand name cannot simply be selected as a custom certificate subject.
• Use Certificate subject preview before submitting the request to inspect the proposed certificate identity.^1^

The public documentation does not specify what Israeli evidence is sufficient to connect “Odyon” to the proprietor.

Website, email, and domain requirements

For Organization Public Trust validation, the documented inputs are:

1. Website URL: A website belonging to the legal business entity.
2. Primary email: A monitored mailbox on a domain owned by that entity. It must receive messages and links from external senders.
3. Secondary email: A different address whose domain matches the primary email’s domain. Distribution lists are accepted for this field.
4. Email verification: Verification links are sent to the primary address and expire after seven days.^1^

Microsoft does not publicly define the precise domain-ownership evidence used for an Israeli sole proprietor. The validation process may rely on public records or request additional documentation.

Confirming eligibility before billing

Microsoft does not document a self-service prequalification check for a particular legal form. Creating an Artifact Signing account starts billing immediately, and the selected SKU is billed for the full period rather than prorated.^5^

Before creating the Basic account:

1. In the Azure portal, open Help + support.
2. Select Create a support request.
3. Choose the Artifact Signing/service setup or identity-validation category available for the subscription.
4. Ask for a written determination covering:
   • whether Israeli osek patur is accepted under Organization/DBA validation;
   • the accepted Israeli business identifier and records;
   • whether the registered trade name can be the validated certificate subject;
   • acceptable domain-ownership evidence.
5. Provide identifiers or documents only through the private support case when requested.

The FAQ identifies Azure Support as the official channel for Artifact Signing setup and identity-validation assistance.^4^ It does not guarantee that support will issue a binding eligibility decision before resource creation, but no more specific private preapproval channel is publicly documented.

References

1. Quickstart: Set up Artifact Signing
2. Azure Artifact Signing questions: Sole proprietor company name ...
3. Artifact Signing (Trusted Signing) Public Trust identity validation for ...
4. Artifact Signing FAQ
5. Artifact Signing pricing