Forum Widgets
Latest Discussions
Joining the Microsoft 365 Developer Program
Our company is a Microsoft Partner, and we have Partner Success Expanded Benefits. I learned that we are eligible E5 developer accounts, but I have not been able to get them going. I reached out to our Microsoft representative, and he directed me here to find help. It seems like we need to be added to an allow list because we are an SMB seeking E5 accounts. Is anyone familiar with this process?
The product has been taken off the shelves??
What's the reason that our product is deleted from the Microsoft Store? From your report, we know that there are some problems with our keywords. However, you don't give us enough time to solve it. Please tell us what we should do and what information you need. We can't edit anything now, If it is convenient, please send us the SOP or reply us as soon as possible
Employment verification problem
Although we've sent a Cloudflare domain renewal invoice with: Domain name Exact company name Exact address My within 12 months I can't get past this employment verification step. I've tried "Fix Now" and exhausted that, and support thread provided no help. What should I do?Join the next IAMCP partner meeting January 23
You're invited to join us in-person or virtually on January 23! IAMCP's TOLA Chapter (Texas, Oklahoma, Louisiana, Arkansas) rotates monthly and hosts chapter meetings in Austin, Houston and Dallas. All meetings are hybrid and anyone is welcome to attend, no matter where you are! 😃 Join us online or in-person (lunch included) in Houston at the Microsoft office - 750 Town and Country Blvd., Ste. 1000 Houston, Texas 77024 11:00am-1:00pm CST Register Here >
CSP Partner Licensing Question - Dynamics / CRM Online Portal Additional Portal
Recently I was asked to locate a part number for the Dynamics 365 Enterprise Edition - Addnl Portal(QO) in the perpetual and NCE CSP price lists, but cannot find it. The PowerShell returned that they are being billed for a CRM_ONLINE_PORTAL 1d4e9cb1-708d-449c-9f71-943aa8ed1d6a. I believe the part number is a legacy sku that was moved to Dynamics 365 Portals, but then deprecated or moved to Power Pages, but the client is still getting billed and uses it. Any guidance/ assistance would be appreciated.Licensing around CRM Online/ Dynamics Portals/ Power Pages
Recently I was asked to locate a part number for the Dynamics 365 Enterprise Edition - Addnl Portal(QO) in the perpetual and NCE CSP price lists, but cannot find it. The PowerShell returned that they are being billed for a CRM_ONLINE_PORTAL 1d4e9cb1-708d-449c-9f71-943aa8ed1d6a. I believe the part number is a legacy sku that was moved to Dynamics 365 Portals, but then deprecated or moved to Power Pages, but the client is still getting billed and uses it. Any guidance/ assistance would be appreciated.PSA: Verified Publisher (Wrong) Assumptions
First and foremost, thank you, Nilesh Vishwakarma and Deepack, for sharing your internal knowledge to dispel the unnecessarily confusing topic of App Verified Publisher. I'll dive into the details of the issues, the confusion, and what I gathered during a few meetings with Microsoft Support. But first, for those seeking the simple TLDR guidance (specifically for the Verified MPN): The organization/tenant the App is under must have its own Partner Account; you can't come in with your own MPN for your clients; it needs to be their (your clients') MPN Account. Even if you created the App (the App Owner), you need some sort of Global Admin type access, and it seems like you also need some access in the associated MPN account. VERY IMPORTANT: Even if you can see and click on the Verified Publisher link to add an MPN ID, any errors you encounter are likely due to lacking rights in one or both systems. VERY IMPORTANT: The Microsoft documentation for troubleshooting this issue may lead you astray. After several days of troubleshooting on my own—reading, researching, and even involving Microsoft Support—the issue was finally resolved when my client created an MPN account, logged into Entra, clicked the Verify link, and entered their MPN ID. The takeaway here? Assume you're at the mercy of the zero trust hammer, and for something as simple as single sign-on authentication, your clients must become Microsoft Partners. For those not interested in the juicy details or listening to a grumpy gray beard rant, you are hereby released; the above are the main points to remember when applying a Verified Publisher to your App. For the rest of you, read on, and hopefully, you'll pick up more details and maybe even find it entertaining... First, if you are creating a simple App for SSO (work/school) for use on your client's website, you need to create the App on the tenant that holds the AD/Entra accounts. This makes sense. Furthermore, a publisher is required to be on the hook for and prove the validity of the App, visible to users during the consent. This also makes sense. However, what doesn't make sense is that the App Owner cannot assign the MPN ID, and even more so, anyone who is creating that App for their client needs also to have access to their client's MPN Account, and, for that matter, that the client should even need that MPN Account. Let's start with an extreme example... I'm building a website for a construction company that doesn't have an IT team. Because they have AD/Entra and I'm a loyal "Microsoft Partner" (see what I did there), we decided to go with Azure and Entra. First, I need to explain the access I think I need to the client (who is not technical). I'm on my way, creating the App and website, and I get to this Verified Publisher thing. Okay, no problem... I can click on this link to add my MPN ID. Nope, that's the first error. After finally figuring out that they need to become a Microsoft Partner, you help walk your (again, non-technical) client through this process. Okay, so you are back at the Verified Publisher with your (ahem, I mean their) new MPN ID. Again, you click on the link and add their MPN ID, and another error occurs: "The MPN ID you provided does not exist, or you do not have access to it. Please provide a valid MPN ID and try again." Okay, first, the MPN ID is valid; second, it exists; and third, what access do I need? This kitchen sink error message is not very helpful. But hey, there's a "learn more" link. Okay, so you go through hours of rummaging through the docs, and nothing is really apparent, but look at this—there's a Troubleshooting section. On the first bullet point, step four provides a link to verify the MPN (https://partner.microsoft.com/en-us/pcv/accountsettings/connectedpartnerprofile), but this reveals a "Sorry, something went wrong. Please try again later" error page. With humility, you create one of your two allowed support tickets... and when going through the same steps, they mention something about access and start naming the people that could apply the Verified Publisher... so, we have to call our (non-technical) client again to come on the chat to be walked through how to add the MPN ID, and boom, it works. At this point, you're probably part happy, part embarrassed (for no reason), and part angry. Here's the problem—well, one of them. If you don't have access to do something, we are all trained to see disabled buttons/links; if the developers are really good, they change the CSS/cursor on hover, and if they're really, really good, they provide a tooltip explaining the access that is needed to click the button or link. BUT, for all that is good, don't provide a clickable link, a non-disabled textbox, and a non-disabled button to add something we can't add in the first place. Furthermore, do not provide an overly elaborate yet somehow vague validation message. I expect more from Microsoft. Secondly—and this is a self-preservation thing—requiring our clients also to become Microsoft Partners dilutes the value of being a Microsoft Partner. I see a cartoon of a word bubble above a technical person saying, "I'm a Microsoft Partner," and in the next frame, it shows a roofer, a janitor, a homemaker, and a plethora of a thousand people, all with the same word bubble saying, "Yeah, so are we!!!" Although this is a funny view of it, the reality is that it was hard enough to explain to clients why you want to add your MPN ID to their Azure subscription or what that means... but now, why would they, when they have that same feeling of ownership as with the App, and now armed with their own MPN ID? It truly is diluting the value of a Microsoft Partnership and, further, making it harder to justify adding our MPN ID to signal to MS who we are serving. This is directly tied to how we can obtain a Silver or Gold Partnership. This seems to have been built without consideration for agencies, small businesses, and clients outside the tech field.
Purchase OR Sign In Authentication of MS 365 Subscription
We are a software provider that offers completely secure and private Remote Desktop solutions to consumer and business customers. What is the authentication process for a customer that uses our software to access their desktop remotely AND either purchases a Microsoft 365 subscription while within our software (servers)?
