A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Artifact Signing does not allow custom Common Name (CN) or Organization (O) values and does not support arbitrary customization of the subject name. The CN in publicly trusted code signing certificates must match the validated legal entity name per CA/Browser Forum Code Signing Baseline Requirements, and Artifact Signing follows this rule.
If the Artifact Signing subject name differs from what is expected in a Windows app MSIX package, use the MSIX persistent identity guidance to handle name changes rather than trying to force a different subject name in Artifact Signing.
If the issue is related to identity validation (for example, needing a different primary email or another validation for the same organization), contact Azure support via the Azure portal as described in the Artifact Signing FAQ.
References: