Using a registered business name for code signing instead of

Artifact Signing cannot replace the partnership’s validated legal name with an arbitrary registered business or trading name in the public certificate’s CN/O fields; to display the trading name, Microsoft must accept and validate it as the certificate’s legal entity name.

The completed identity validation supplies the attributes used for the certificate profile’s Subject Distinguished Name. When creating a profile, Verified CN and O are selected from that validation and the remaining subject values are populated automatically.^1^

Microsoft also states explicitly that:

• Public identity validation’s Organization Name must be the legal business entity to which the certificate is issued.
• Custom Common Name (CN) and Organization (O) values are unsupported.
• For publicly trusted code-signing certificates, the CN must be the validated legal entity name.^2^^3^

What “Organization or DBA” means here

The quickstart describes the workflow as applying to an Organization or DBA, but the same instructions still require the organization name, identifier, website, email domain, and address to belong to the legal business entity. It does not document a DBA/trading name as a freely selectable replacement for the validated legal name.^2^

Therefore, do not create another validation using only the registered business name unless Azure Support confirms that Microsoft can validate that Australian business-name registration as the public certificate identity associated with your ABN.

Recommended next step

1. In the Azure portal, open Help + support and create an Azure support request for Artifact Signing identity validation.
2. State that the current organization/public validation is completed under an Australian partnership’s legal name.
3. Provide the registered business name and explain that it is registered to the same partnership and ABN.
4. Ask whether that specific Australian registered business name can be validated as a DBA for the certificate’s CN/O, and what documents are required.
5. Before submitting any replacement request, inspect Certificate subject preview. That preview shows the information intended to appear in the certificate.^2^

The FAQ directs identity-validation questions to Azure Support. A new validation should not be treated as a way to customize CN/O; it must itself pass public identity validation.^3^

Is forming a Pty Ltd company required?

Not necessarily, until Microsoft answers whether the registered business name qualifies under its DBA validation path. However, if Microsoft will validate only the partnership’s legal name, then a separate company whose legal registered entity name is the desired publisher name is the clear supported route.

That company would require its own organization/public identity validation; the existing partnership validation cannot simply be relabeled because certificate subject data comes from the selected verified identity. Forming a company solely for this purpose also has Australian legal, tax, and compliance consequences, so those should be assessed separately.

References

1. Artifact Signing resources and roles | Microsoft Learn
2. Quickstart: Set up Artifact Signing
3. Artifact Signing FAQ