Forum Discussion
Additional updates to Solution Partner for Business Applications designation
Alongside the 4 new Business Applications Specialisations, there is an important Rate Card change for Dynamics 365 Customer Engagement & the threshold changes for SMB Biz Apps Designations. ...
rebecca1475
Microsoft
MicrosoftHi Anil thank you for your question - I would be happy to jump on a Teams call to discuss through in more detail to better understand.
a good resource for all solution designation is
https://learn.microsoft.com/en-us/partner-center/solutions-partner-business#monthly-consumption-value
However, as far as I was aware this is not a dollar amount, but a weighted calculation based on active customer usage.
For Business applications, varied workloads have varied usage units: monthly active users, profiles, and so on.
To enable measurement and assessment of success across all these workloads, the monthly consumption value is defined as:
Monthly consumption = (monthly active users or capacity) * consumption rate
See the following table for the current rate card.
Monthly consumption value is used instead of monthly active users to include capacity-based workloads (such as Customer Insights) and to include a workload-based weighting using the consumption rate. This rate addresses the differences in expected workload deployment sizes. The calculation ensures that partners of all workloads can reach the point requirements without including a workload-specific threshold.
a good resource for all solution designation is
https://learn.microsoft.com/en-us/partner-center/solutions-partner-business#monthly-consumption-value
However, as far as I was aware this is not a dollar amount, but a weighted calculation based on active customer usage.
For Business applications, varied workloads have varied usage units: monthly active users, profiles, and so on.
To enable measurement and assessment of success across all these workloads, the monthly consumption value is defined as:
Monthly consumption = (monthly active users or capacity) * consumption rate
See the following table for the current rate card.
Monthly consumption value is used instead of monthly active users to include capacity-based workloads (such as Customer Insights) and to include a workload-based weighting using the consumption rate. This rate addresses the differences in expected workload deployment sizes. The calculation ensures that partners of all workloads can reach the point requirements without including a workload-specific threshold.
Thank you Rebecca. I appreciate your update.
My main query is around why Microsoft has decided that the rate card is 100 points for D365 Finance, 200 points for CRM (dataverse) and 1000 points for D365 Business Central and other apps like Talent.
Basically, this causes an artificial lower MCV for D365 Finance while a very high MCV for BC. Eventually this impacts our performance criteria for getting specializations like Finance, Sales, SCM etc.
My observation on the dollar amount was just an observation in addition to the above- that basically a partner generating more revenue for Microsoft gets less MCV points.
I would really appreciate a quick 20 mins teams call. I have shared the invite for 12pm GMT on 24th May. Does that work for you? Thank you.
My main query is around why Microsoft has decided that the rate card is 100 points for D365 Finance, 200 points for CRM (dataverse) and 1000 points for D365 Business Central and other apps like Talent.
Basically, this causes an artificial lower MCV for D365 Finance while a very high MCV for BC. Eventually this impacts our performance criteria for getting specializations like Finance, Sales, SCM etc.
My observation on the dollar amount was just an observation in addition to the above- that basically a partner generating more revenue for Microsoft gets less MCV points.
I would really appreciate a quick 20 mins teams call. I have shared the invite for 12pm GMT on 24th May. Does that work for you? Thank you.