Employment verification failed - Fix Now - Not Working
Fix Now button does nothing, or at least not as pictured in your own guide article. Account Verification side-screen is NOT showing up after clicking on the Fix Now button, as depicted the image in your own article. https://learn.microsoft.com/en-us/partner-center/enroll/verification-responses Fix Now button just restarts the process of verification, which fails constantly, without specifying what is wrong. This is an issue that needs to be resolved by Microsoft, there are multiple such reports.
Employment verification and support tickets
We have problems with Employment verification. I think we did everything we found on blogs and even what I got back in two emails from Microsoft, which are the same, it looks like copy and paste. The funny thing is that they tell me that I have to use an email that is not info, sales, marketing for the contact email and they write me to my personal email mailto:email address removed for privacy reasons When I want to upload another support ticket they tell me that I can't upload another ticket for the same topic, that I have to provide more information in the one I already have open. When I want to open it I get an error and it tells me that it is not possible to get the ticket data. This is unbelievable, with Android and Apple we didn't have even half of the problems we are having with Microsoft. It's quite frustrating. Grateful if anyone can help us.
Verification for partner very difficult, no response from support at all
Hi, I'm an MSP, trying to get verified on Microsofts programs, to be able to support and supply my users through distributors. Unfortunately, this is where it ends, I did everything Microsoft asked me: Sign up as a partner Filled in the details Received a rejection, was asked to supply domain verification, supplied this Then now am denied as followed: "Your verification is rejected because of usage of restricted domain. Please update your email in Profile Info section with company domain address to get it verified." So, first I had to supply domain details, then, after this, now you're still rejecting this based on what? No proper feedback, neither is anyone replying to the tickets I've opened relating to this. Ticket #s: 2307250040004588 2307270040001544 2308050040001621 So, the deal is as followed: I'm registered as Dyk Media, and I do business as DykIT. So, my registration is showing Dyk Media in the CRO here in Ireland, and this is what I have explained in the documentation provided.. + I provided utility bill, but, again this is denied without any option to talk to someone, nor, being able to understand the denial. Why doesn't anyone read ticket, or, read the attached documentation. This is so frustrating, it almost makes you not want to deliver any MS products, and being able to supply users/companies, with the right support structures as an MSP. Mike ---- UPDATE: As my company name was slightly different, this was the cause of it not being accepted. Since adjusting this correctly, I resubmitted it, and it's now accepted and approved. I think this is beneficial information for others, as it really has to match up everything that is within your registered details.
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.Developer Verification 23. Nov 2024
Another week has passed, our current status - Verification Cancelled ... by whom? No one knows. Before we received this email: Afterwards I checked our status in the portal: Yesterday's status: I ha.te this so much ... since September we are doing this nonsense, 2 days ago I was asked to verify our company email..... there should be a button send verification .. well it was just not in our portal account. They added more nonsense to this we had to modify the domain name entry and add some MS specific information to it... good we did it but ...WHAT FOR?? We just want to release a signed driver nothing else. How many years will this go on? Now we're heading to 3 months with this Microsoft Partner Portal sh.it. Developer Verification 16. Nov 2024: https://techcommunity.microsoft.com/discussions/partnercomplianceforum/developer-verification-16th-november-2024/4299182 Developer Verification 9. Nov 2024: https://techcommunity.microsoft.com/discussions/partnercomplianceforum/developer-verification-9th-november-2024/4289632Unable to enter Hardware Program to submit HLK package
Hi, we are currently trying to submit HLK package and attempted to access Hardware program, which we registered quite some time ago. Unfortunately, we are getting error "Your organization already has an account. The Microsoft Entra tenant you are signed in to (email) is already associated with a Windows Hardware Developer Program account. If you need access to this account, contact your administrator.", which makes sense, since I am not the the administrator. The problem is, that the person who initially registered us and is presumably the administrator left our company few years ago and we can't really access his account. We tried creating ticket with partner support, but the response we got back was "This account XXX has been suspended due to non-compliance with the hardware program. All partners are required to accept our current agreements and complete Account Verification successfully to be compliant. If you believe your account was suspended in error or can demonstrate your account is compliant, please provide evidence." When we asked for clarification what evidence we should present (and all the 4 consequent responses we sent), we got the identical message back basically getting us nowhere. AFAIK, the "agreements" can be accepted only from the Hardware program interface, which we obviously can't get into. Our Account Verification seems to be correct, because I can see we are authorized in all categories in our Account settings > Legal info. Do you have any idea what any of this means and what do we actually need to do? Best regards, David
CSP/MCPP EnrollMENT issues for partner center
Hi All, its Edris from CirroCloud Solutions.... I have had the same issues for domain ownership verification for a while now and i have finally solved my issue in the following steps while starting from Scratch. Delete the partner accounts and clear up your partner center i have also gone ahead to delete my azure active directory tenant connected to my custom domain Starting from scratch, i created a Microsoft developer subscription and connected my custom domain to that tenant. i verified my domain and added DNS records for emails to point to office 365. Therefore my tenant was verified with Microsoft and had an azure active directory tenant. I then signed into the partner website using my azure tenant email address then started the procedure for becoming a Microsoft partner using that tenant. after going through the procedure and adding details for my company i landed on the page for legal info and was at the stage of email verification. i received the email and verified email and the verification stage verified the employment verification stage automatically as my domain was automatically detected by Microsoft. please note that Microsoft looks at the azure active directory therefore make sure the tenant name has your company name and the technical contact in azure and primary contact and security contact in the partner center match the ones in azure active directory. Copilot i think compares values in azure active directory and matches them with values in partner center to determine domain ownership after you have added domain records (MX,cNAME,TXT) into your cPanel (not so certain on this but just my thought). Then all i am left with is business verification where i just share my certificate of incorporation or company registration documents and that process would be done Please make sure you verify the domain and point your DNS records to Microsoft before signing up for the Microsoft partner program (something the support team doesn't mention which smoothens the verification process because no document submitted will ever be enough for verification as i think the the azure details matching your partner account details You can reach out on mailto:email address removed for privacy reasons if you need any further information or direct messageIdentity verification rejected, no Fix now option – ticket 2610230010000294
We’re an Australian MSP enrolling in the CSP Reseller program. Our current verification status is: Contact verification: Verified Identity verification: Not Verified (no Resolve or Fix now button, so we can’t appeal) Business verification: In Progress – Microsoft Action (ETA was 28 Oct, still pending) I opened ticket 2610230010000294 on 23 Oct but haven’t been contacted yet. Could someone please review the ticket and re-trigger identity verification? We’re happy to provide ID and business registration documents that match our account details. We’d also like to know why identity verification failed, so we can fix the cause and avoid another rejection. Thanks in advance.
CSP Program enrollment was DEACTIVATED
We are an active Microsoft reseller in the AI Cloud Partner Program. We were also enrolled in the CSP Indirect Reseller Program. Last year, our CSP enrollment was DEACTIVATED (not SUSPENDED and not TERMINATED). Of course, we got the typical response on our tickets when asking WHY we were deactivated stating that MS can walk away with no explanation. We BELIEVE it is because we had not sold at least $1000 in the previous 12 month period. Everything I read states that we can re-enroll 12 months after our "onboarding date" which I am not sure what that date is. We were deactivated around October 2025. The "Learn More" link doesn't really help, and focuses mostly on SUSPENSIONS which I believe is different. Even using that link, none of the reasons for a suspension apply to us other than the "program requirements" which is where the $1000 minimum comes from. Can anyone offer some additional guidance here? Thanks!
