Hardware enrollment: Employment Verification rejected, Resolve blocked, no case response

Hello JillArmourMicrosoft and the Partner Compliance community,

I am the owner of MORU, a registered sole-proprietor business in South Korea. We are completing a new Windows Hardware Developer Program enrollment to submit our virtual audio driver for Microsoft signing. This is a Hardware enrollment issue, not a CSP/reseller application. We have obtained an EV code-signing certificate.

I understand that this community is not the support team and cannot approve our enrollment. We are asking for guidance on a working escalation or private handoff route for our existing cases, because the normal support paths described below have not resolved the problem. We are not asking to bypass verification.

Current blocker

- Email Verification and Identity Verification have completed successfully. Earlier identity-verification difficulties were resolved; Employment Verification is the current blocker.

- Employment Verification shows "Rejected / Pending Partner Action." The displayed estimated date was October 8, 2026, and the issue remains unresolved on October 21.

- Resolve shows "Document submitted successfully," but offers no additional file-upload control and the Submit button is disabled. We cannot tell whether the outstanding action is a document issue, an unfinished review, or a portal-state problem.

- We do not yet have confirmation that all subsequent verification/enrollment steps are complete.

Evidence and support timeline (dates in Korea Standard Time)

- October 1: Government-issued business-registration evidence was submitted through Resolve. We have both Korean and English official documents.

- October 6: Our original Hardware enrollment support case was opened.

- October 8-13: We aligned the current GoDaddy registration details for voracall.com with MORU and the representative's name and official business address, then sent the registrar's original registration and purchase exports to the original case. A separate duplicate case was closed on October 13, so we continued the original case.

- October 14: Microsoft Vetting Operations requested an original paid domain-registration receipt showing the domain, owner, registration date, registration period and registrar, with at least two months remaining before expiration.

- October 15: We replied with the original GoDaddy receipt email as an EML file.

- October 17: We additionally sent the unmodified receipt PDF saved from the official GoDaddy order page and the original GoDaddy registration CSV to the same case. These show the one-year purchase and current domain registration expiring June 30, 2027. We also requested confirmation that the attachments were associated with the verification case and an exact description of any missing information.

- October 18: We opened a separate technical support case for the inaccessible support portal and explicitly requested that it be linked to the original enrollment case. We received its automatic receipt and supplied evidence of the account's administrator role.

- October 21: We still have no substantive reply to the October 17 evidence submission or the October 18 portal-access case. We checked the mailbox including spam. Calling the published Microsoft support number only directed us to aka.ms/prosupport and ended the call.

Document details already disclosed to support

MORU is my sole-proprietor business. The historical GoDaddy purchase receipt uses my personal name and an old billing postcode; the current registrar registration record uses MORU and the corrected official business address. We explicitly explained these differences and left the historical receipt unchanged. We have not received a response identifying whether these differences remain unacceptable or which registrar-issued document would resolve them.

Support portal access problem

We checked that the signed-in account belongs to our company tenant and is a Member. Partner Center User management displays "Global admin, Admin," and the user-detail page shows Global admin selected. Nevertheless:

- My requests displays no support requests.

- Organization requests says we do not have permission to view organization tickets.

- AI Assistant > Contact support shows "No results found" in the required Workspace field, preventing the normal support flow.

These observations establish the access problem; we do not know whether it shares a cause with the verification rejection. We have already used the official alternative support form for incomplete Hardware enrollment to create the October 18 case.

Requested assistance

Could a community manager help connect our existing cases to Hardware Enrollment/Vetting and the team responsible for Partner Center support access? Specifically, we need:

1. Confirmation of the current case owner/team and whether the October 17 PDF and CSV have reached the verification review.

2. The exact remaining mismatch or missing document, if any, and a working private submission route or restored Resolve upload control.

3. Investigation of the blank Workspace and inaccessible existing support cases despite the confirmed administrator role.

4. Confirmation of whether a Hardware enrollment business questionnaire remains outstanding. We asked support about this but have not established its completion status.

This prevents us from completing the Microsoft driver-signing submission process. We can provide both support-case numbers, Seller ID, screenshots, the full correspondence and original documents through an appropriate private support channel. Personal addresses, identity documents and financial documents are omitted from this public post.

Thank you for helping us reach the responsible team.

MORU