Forum Discussion
Solved
CSP Verification Issues Continue
Can someone please decipher the below and tell me what the verification team is actually asking for or what they mean by "the domain provided in your submission is insufficient for the requirements o...
Hi partners, 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 subcription 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 compnay 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 reachout on mailto:email address removed for privacy reasons if you need any further information or direct message
Going through the same issue. What boggles my mind is that they ask for something dated within the past 12 months. Luckily, my last purchase was late last year. But I do purchase in 3 year increments. What if I was on year 3? Would that be rejected? I've been a MP since 2007 and I haven't been able to renew this year. If I have to delete anything. I'm not coming back.
jadewire SamuelRoach or anyone else, please do not delete your azure tenants if they are connected to other services...i deleted mine because it wasn't connected to any other service. i had to delete because even when i deleted my partner account to start from scratch, the system would remember me and throw an error. so i advise that you open tickets regarding deleting and reopenning mcpp accounts as i am not among the microsoft support team but just thought of sharing what really worked for me
- I am battling the same issues so from what I'm reading the only successful way has been to delete Azure AD and start completely from scratch. Emails, SharePoint teams etc all over again? I'm sure I'm uploading the right documents just seems like no Humans actually read the ticket notes and take way longest that the advertises 3-5 working days to review. MPN verification is a nightmare at the moment. Does using the microsoft developer subscription have any potential adverse effects in the future?
- My approval finally came through this evening. I didn't do anything different; I just left it in its rejected state for the past few days so, unfortunately, I can't give any substantive advice on how to resolve the issue. Perhaps, the backlog the support team is dealing with is part of the issue but there's clearly more that needs to be done to alleviate the frustrations we've been experiencing.
The more we can shed light on this issue, the more the relevant powers that be within Microsoft can understand the scale of the problem.
