Azure Trusted Signing cannot currently be used instead of an EV code signing certificate for registration and driver submission in the Windows Hardware Developer/Hardware Dev Center program.
For the Hardware Developer Program and for submitting drivers (including attestation signing) through the hardware dashboard/Dev Portal, an extended validation (EV) code signing certificate is explicitly required:
- To register for the Hardware Developer Program, an EV code signing certificate is required; it must be uploaded on the Manage certificates page for the registration request to be considered for approval.
- To establish a Hardware Dev Center/Partner Center hardware dashboard account (needed for driver signing via the Dev Portal), an EV code signing certificate is required.
- For attestation signing of drivers, the prerequisites explicitly state that an EV code signing certificate is required; if the organization does not have one, it must purchase an EV certificate from a supported certificate authority.
Trusted Signing is not mentioned as an accepted alternative in the Hardware Developer Program registration or driver signing requirements. The documented path for getting approved and submitting drivers is to obtain and use an EV code signing certificate from a supported CA and associate it with the Partner Center hardware account.
References: