Pre-Sales Funded Engagement - Business Apps - CRM Vision & Value - Eligibilty
Hi community we are studying the delivery guide for funded engagement CRM Vision & Value. We have some customer eligibility related questions, so I appreciate some clarification from Microsoft. Thanks! Ralf The provided TCO calculator and the Delivery Guide gives the impression that funding is ONLY available if our prospect migrates from Salesforce to D365 CRM. What if our prospect is ..... 1. ... using Excel sheets to manage support tickets - not eligible for funding? 2. ... using Monday.com, or hubspot to manage sales - not eligible for funding? 3. ... using a self-made application to manage campaigns - not eligible for funding?BizApps D365 Specialisation SMB
Hello community and MS folks, As per partner portal you need 5x MB800 certifications to meet the BC skills requirements. Could it be that MS has forgotten to add the advanced certification MB-820 to the list of eligible certifications? It wouldn't make sense to exclude MB-820 from this list would it?
Licensing guide query for Business performance planning (FP&A/xP&A)
Team, I can see that an Ops-Activity license has ‘restricted Access/Inputs’ for the new BPP process. How can I find out exactly what the difference is between what an Ops/Activity license can do and what a Finance license can do in terms of ‘Restricted Access/Inputs’.
Two MS partners supporting one customer, but only one gets recognition for MAU growth !!
Hi community, I was very surprised to learn that for the given scenario below, a MS partner will get not any recognition for deployment and MAU growth. This was confirmed by MS Partner Support. Do you have similar experiences? Ralf Scenario: 1. Customer C has two MS partners: partner p1 provisions all licences, partner p2 deployed the D365 CE solution and provides ongoing enhancements and BAU support. 2. The license agreement is CSP (not EA!) Recognition of each partner's work: 1. Partner p1 gets recognition for Net Customer Add (CSP) and for MAU growth (that's ok) 2. Partner p2 gets no recognition at all, neither for deployment nor for MAY growth (surprise, surprise) In other words: The work partner p2 is doing to drive adoption and growth is not viable from a partner's membership perspective; partner p2 should consider handing over the work to another partner.
