Pinned Posts
Forum Widgets
Latest Discussions
Unable to Register - "Legal Entity Already Exists" Error - Cannot Access Support
Hello, I'm trying to register for the Microsoft Partner Network to obtain an MPN ID for Azure app publisher verification, but I'm stuck in a catch-22 situation. The Problem: When registering through Partner Center, I receive this error: "A legal entity matching the request payload already exists when creating the legal entity" The Catch-22: I cannot create a support ticket because: - Partner Center help form requires selecting a workspace - I cannot create/access a workspace without completing registration - I cannot complete registration due to the duplicate entity error What I've Tried: - Searching for existing accounts within my organization - no one knows of any - Attempting to create a support ticket - blocked by the workspace requirement - Looking for alternative support channels - all redirect back to Partner Center What I Need: Either help locating an existing account for my company, obtaining the existing MPN ID, or resolving the duplicate registration issue. Has anyone successfully resolved this? Is there a direct contact at Microsoft Partner Support who can help? Any assistance would be greatly appreciated! Thank you.Applied Skills Missing in Training Report
As a Microsoft Solutions Partner (approx 400 employees) we are working on creating a dashboard for managers to see how we are faring from a skilling perspective. This also helps us in the tracking and working towards retaining our specializations and designations. So far we have used the Trainings Report derived from the downloads hub to feed our database with applicable certifications that are held by our employees. That database we then used to also report on our skilling requirements for the solution area's and the specializations. Recently Microsoft introduced new specializations (Copilot) and those specializations require Applied Skills to be held by employees. These applied skills do not show in the trainings report offered by Microsoft. (E.g. APL-4002: Prepare security and compliance to support Microsoft 365 Copilot,APL-7008: Create agents in Microsoft Copilot Studio or DW-101: Copilot for Microsoft 365 Deployment Workshop ) As such we're wondering whether Microsoft is working on including these applied skills in the trainings reporting?
Unable to receive questionnaire for Hardware Program application
We've finished all the steps in the application of Microsoft Hardware Program, the last step is to wait for a questionnaire in our email then answer the questionnaire. However we haven't received the questionnaire and have no idea how to solve this issue. Can someone look into this? Already created a support ticket, the number is #2511060010000740.
Unable to pass Employment Verifcation step in Partner Center
Hello everyone, I am stuck at the Employment Verification step while trying to enroll in the Microsoft Partner Center. I have already submitted the required documents, including the domain invoice and the assignment letter, but Microsoft responded with: "Based on the information you have provided to date, we have determined that your organization does not currently meet the requirements to pass verification." This leaves me very confused, as the reply does not explain what exactly is missing or what additional documents are required. I have carefully checked the documentation, but there is no clear guidance. As a company focusing on IT security, this is extremely frustrating. We recently shifted from Linux to Windows development, and without a Microsoft Partner account we are unable to proceed with building kernel-level antivirus solutions for our users. This has a devastating impact on our business. Could anyone please share their experience or advise on what specific documents or requirements Microsoft usually expects in order to pass Employment Verification? Any help would be greatly appreciated. Thank you!
Legal-entities and sub-units in Microsoft Partner Center terms
Hi, I represent several partners with Microsoft, and we are fast growing. In our enterprise, we do as several others, we move around locations, merge them, and restructure to improve efficiency and quality. Recently Microsoft also notified us to update and improve several of our MPN/CSP identifiers with updated information, which resulted in this post about missing features and hidden Microsoft data not available in Partner Center. Starting out as a partner, you add your company in Partner Center, creating your PGA and first PLA account. Your PGA now refers to your legal entity, and your PLA is now a sub-unit under your PGA. So far so good (for a CSP business, you have your PGA be the MPN id and your PLA the CSP id). As time goes by, your business grows and you start buying other MS partner companies. In comes account merge in partner center to the rescue. This will merge your MPN (not CSP, I know, atleast not in terms of your GDAP or customer relationships, but everything else), so that all your competencies, reports and information is updated accordingly. The company you have bought and merged now still has their CSP business, but reporting under your PGA. Both their original PGA and PLA accounts are now PLA under you PGA. So far this seems to be good, but now you are missing out on some data hidden internally in Microsoft, that is nowhere to be seen, and impossible to update: this original merged PGA still refers to the original legal-entity, and the PLA is still NOT connected to your PGA, but the original PGA, which is now a PLA under your PGA. So, something like, Your PGA --> The merged PGA (which is now a PLA) --> The merged PLA. Confused yet? Now, this merged company should at some point in time become something else, maybe a department or separate location of your company. Or maybe you even move that as a department or location below some other company you have in your enterprise portfolio. Now comes the headache of updating your CSP - PLA identifiers with correct legal information. There is currently nowhere you can read what PLA id-s are considered as legal entities, and nowhere your PLA says which legal entity they are connected to. Even filing this with MS partner support is a no-go, this information is hidden so far behind support/MCAIPP/CSP/direct/indirect/vetting/engineering/developers and god knows what, that it is currently not possible to update any of it. Not even getting to read the structure of the identifiers is possible. I hope Microsoft can understand this is a big compliance issue over time. How many tax forms or payout accounts do you need? How many are using the same legal info for the same tax forms? Regardless of being a direct or indirect partner, who should really receive the bill? Who ends up as the owner of the different agreements? (I know this usually works out one way or another, but how many hours could have been saved on partner support if this was not a headache?) We need to be able to see where each identifier is connected in terms of sub-units and legal-entities. Whether by self-service or MS partner support, we need to be able to provide updates on this structure. We need to be able to change any PLA between being a legal entity or a sub-unit, and telling which legal-entity owns the sub-unit or parent legal-entity. Different partners have different setups, we have an enterprise setup where one company fully owns all the others and plan to fully merge them within a single legal entity, but still owned by the enterprise. Others have separate companies working together sharing Microsoft competencies and benefits under one umbrella. Having a way to let Microsoft know about structural changes and having this information visible and correct in partner center is crucial when working as a partner over time. Bonus tip: Most countries, even Norway has officially available records on all companies registered, on official website or by official APIs - by looking up any company registration id, you can have the 100% accurate information for all legal entities, and all sub-units, we even give you the company registration id inside partner center for your benefit.
Application Developer Agreement v8.10 is missing from the list of agreements in Partner Center
Hello, I received a message from Microsoft regarding the need to accept changes to the "Application Developer Agreement." However, when I go to my Partner Center under the Agreements section, I do not see the updated Application Developer Agreement version 8.10: https://partner.microsoft.com/en-us/dashboard/account/v3/settings/agreements Could you please advise how I can sign the updated agreement? The email address provided in the message has not responded to my inquiries. Thank you in advance for your help.
Employment Verification Stuck – Need Help
My Partner Center account keeps getting stuck at the Employment Verification step. Account type: Company Verification status: Rejected at Employment Verification I have already submitted all required documents (business registration, domain invoice, ID proof). My company name matches across Partner Center, domain invoice, and WHOIS (privacy disabled). Email and identity verification were completed successfully. But the system still rejects the Employment Verification without giving details. The Fix Now button just shows rejection with no clear reason. Also it is showing Document uploaded successfully, please wait 3-5 business days for verification of your documents. But its been more than 8 days now. Can someone please let me know how can i contact verification team as i don't have option to created support ticket. Thanks in advance!
Access restricted
I was banned from the system without any justification. I spent six months struggling to get approval without ever using the service once. Now I face another six months trying to get my ban lifted, and they're telling me that if I pay $16,500 annually for support services, they'll help me. This system is absolutely ridiculous. When I was banned, I received no notification, no message, no email, nothing. I only got a response after submitting four support tickets. Now I suppose I'll need to submit another 50 tickets just to try to get my ban reversed. Microsoft is truly a terrible company
