Question concerning Azure Artifact Signing

A Quebec sole proprietorship may apply through Organization/DBA Public Trust validation using “D2RLoader Software,” but the name will appear as the publisher only if Microsoft validates that registered trade name as the legal business identity; incorporation is not explicitly required, while an NEQ alone is not documented as guaranteeing approval. ^1^

Recommended approach

1. Register the sole proprietorship and trade name first.
   • Ensure Quebec’s public business records show D2RLoader Software exactly as the registered business/trade name.
   • Keep the name, address, website, and contact information consistent across the registry and supporting documents. Microsoft advises keeping public records for the legal business entity current. ^2^
2. Use Organization/DBA validation—not Individual validation.
   • Azure portal → Artifact Signing account → Identity validations.
   • Select Organization → New Identity → Public.
   • Enter D2RLoader Software as Organization Name, but only if that exact name appears in the official registration.
   • Supply the NEQ as the Business Identifier where appropriate, plus the registered business address, business website, and two monitored email addresses on the business domain.
   • The primary mailbox must accept external messages containing links; verification links expire after seven days. ^2^
3. Use Certificate subject preview before submitting.
   • The validation form provides Certificate subject preview, showing the information intended to appear in the certificate.
   • Do not submit if the preview identifies the publisher incorrectly; changes after creation require a new validation request. ^2^
4. Complete the representative identity check.
   • Organization validation still asks for the representative’s legal first and last name and government-issued identification.
   • That identifies the person authorized to represent the business. The certificate subject attributes come from the verified organization identity, not from freely entered publisher text. ^3^

What should appear as the publisher?

If Microsoft accepts D2RLoader Software as the validated business identity, that validated name should supply the certificate’s organization/common-name attributes. The representative’s personal details are required during validation, but the certificate subject is derived from the identity validated for the profile. Check the subject preview to confirm the actual result before submission. ^2^ ^3^

Artifact Signing does not permit an arbitrary custom CN or O. Those values must be the validated legal-entity name. Consequently, merely using “D2RLoader Software” as a brand, without an official registration that Microsoft can verify, is insufficient. ^4^

Is incorporation required?

The published workflow expressly supports an identity request for an “Organization or a DBA” and does not state that the applicant must be incorporated. A registered Canadian sole proprietorship is therefore potentially eligible for the organization path. ^2^

However, Microsoft’s public documentation does not provide a Quebec-specific rule confirming that:

• an NEQ by itself is sufficient;
• every registered sole proprietorship qualifies; or
• a particular Quebec registration document will always be accepted.

Final acceptance depends on whether the validation team can verify the legal business identity and its connection to the trade name, address, website, email domain, and representative.

Before consuming limited document-submission attempts, open an Azure Support ticket under Artifact Signing and ask whether your specific Quebec registration and NEQ establish “D2RLoader Software” as the certifiable entity. The FAQ identifies Azure Support as the official assistance channel for identity-validation questions. ^4^

If organization validation is rejected

Your practical alternatives are:

• Individual Public Trust validation: available in Canada, but the legal name and sold-to address come from the individual Azure billing account and appear in the certificate profile—so this does not meet the requirement to hide the personal legal name. ^2^
• Traditional OV code-signing certificate: ask a public certificate authority whether it can validate the registered Quebec trade name as the organization identity. OV certificates are the documented alternative to Artifact Signing, although the issuing CA applies its own validation requirements. ^5^
• Incorporation: this creates a more clearly distinct legal entity, but it should be considered only if the validation team confirms that the sole proprietorship cannot be validated—not as a documented Artifact Signing requirement.

References

1. Azure Artifact Signing questions: Sole proprietor company name ...
2. Quickstart: Set up Artifact Signing | Microsoft Learn
3. Artifact Signing resources and roles | Microsoft Learn
4. Artifact Signing FAQ
5. Code signing options for Windows app developers