A Microsoft Partner of eight years experienced an unexpected Identity Verification trigger on their Partner Dashboard. This verification, handled by AU10TIX, failed because the VerifiedID issued by the platform was missing the partner's last name. Consequently, the Identity Verification status changed to Rejected. The partner is now unable to retry the verification process as the "Resolve" button is no longer accessible. Two support tickets have been opened, but the first was closed prematurely. The second ticket has received no response within the stated SLA. This issue is preventing the renewal of the company's partner benefits package. It is also blocking the publication of their ISV offering on the Microsoft Marketplace. The partner is concerned about how the retry process will function given the previous failure. There is uncertainty about whether AU10TIX will issue a new VerifiedID or indicate that one has already been issued.