Hardware program access suspended

Question

Our access to the hardware development program has been suspended without being notified. Apparently there was a decision to re-validate identities last year, but we were not informed.

We followed the AI instructions and completed all identity verification required, accepted all agreements, and uploaded a new EV code signing certificate, then opened several support tickets requesting reactivation. All we received were canned responses, telling us to consult copilot.

We nevertheless open new support requests, re-open existing ones, does not lead anywhere - no reply except for ask copilot and silently having the request closed a day or two later.

We are unable to sign LSA filters and we cannot provide our customers with updates until this problem is resolved.

Everything is green - Legal Info / Partner, Reseller, Developer = Authorized; EV certificate is Active.

What can we do to restore access to the program?

Answer 1

Based on the available information, the account and identity side of the Partner Center enrollment appears complete (all Legal info statuses Authorized and EV certificate Active). At this point, restoration of Hardware program access requires direct Partner Center support and, if needed, escalation, not further self-service actions.

Use the following path to push a resolution:

1. Confirm Hardware program enrollment and verification
   • In Partner Center, go to Settings (gear) > Account settings > Legal info.
   • Under Developer programs, confirm that Hardware shows as Authorized and that there are no pending actions in the View verification summary page.
   • Ensure the primary contact and global admin mailboxes are valid and monitored, as they receive questionnaires and approval emails for Hardware and identity verification.
2. Reconfirm EV certificate and identity requirements
   • In the Hardware dashboard, open Manage certificates and verify that the EV code signing certificate is uploaded and shows as Active, as required for Hardware Developer Program approval.
   • For Hardware developer accounts, only the primary contact can complete identity verification. Confirm that:
     • The primary contact is an individual (not a group alias).
     • The primary contact’s company email matches the identity used during verification.
3. Check for pending identity verification actions
   • In Account settings > Legal info > Legal business profile, select View verification summary.
   • If any identity verification step is still required (for example, a prompt to Resolve identity verification), complete it using the Microsoft Authenticator flow and a valid government ID.
4. Escalate through official support channels
   • Because tickets are being auto-closed with generic responses, request escalation specifically for:
     • “Hardware Developer Program access suspended despite Authorized status and active EV certificate.”
   • Include in the ticket:
     • Screenshots of Legal info showing Authorized for Developer programs / Hardware.
     • Screenshot of Manage certificates showing the EV certificate as Active.
     • Confirmation that identity verification for the primary contact is completed.
   • If standard support continues to close tickets without action, ask explicitly for:
     • Escalation to the Partner Center back-end/engineering team or
     • Engagement of the Data Protection or account recovery team (similar to tenant lockout scenarios) to review the tenant’s Hardware program status.
5. Monitor primary contact and global admin mailboxes
   • Ensure spam/junk filters are checked for:
     • Questionnaires about business verification.
     • Notices about Hardware program suspension or additional required documentation.
   • If no such mail exists, mention this explicitly in the support ticket to help support focus on a back-end state issue rather than missing documentation.
6. If driver signing is blocked in the interim
   • For issues specifically with signing drivers (for example, LSA filters) via WHCP or attestation, open a technical support incident under Driver Development and Testing/Certification via Windows developer support, and provide the same tenant and Hardware account details so they can correlate the signing failure with the Hardware program suspension.

These steps ensure that all verifications required for Hardware are complete and documented, and they give support the information needed to escalate a back-end correction of the Hardware program status so that driver signing (including LSA filters) can resume.

---

References:

• Register for the Microsoft Windows Hardware Developer Program
• Verify your account information when you enroll in a new Partner Center program
• Get verified credentials from a trusted ID verification vendor
• Deprecation of software publisher certificates, commercial release certificates, and commercial test certificates
• Artifact Signing FAQ
• Severity A Situation - Locked out of global admin account (MFA) - business down - Microsoft Q&A
• Trusted signing for other countries. - Microsoft Q&A