Forum Discussion

SallyGreen's avatar
SallyGreen
Copper Contributor
Mar 12, 2026
Solved

CPOR Association for Incentives and Recognition

CPOR Association for Incentives and Recognition

As I am sure you are all aware we all need to claim CPOR when we are not the billing partner. 

I have seen some changes to this process in recent months and wanted to get some clarification please

  • Build Intent  - Advisor (Pre-sales)
    • We have recently been told that this is only for incentives
      • So now Msft will pay you for workloads that you are not recognised for ??
  • Influenced Revenue Recognition - Non Incentivised
    • This will get you association and recognition for the workloads
  • Usage Recognition - Non Incentivised
    • This will get you association and recognition for the workloads
    • You appear to only be able to claim this if you use the Msft template. 
      • All other signed documentation appear to be rejected

My questions are

  • When did Msft make these changes and why
  • What is the difference between Influenced and Usage Recognition
  • Why MUST we use the template, and not be able to use a signed SoW with the details included
  • We are now potentially making 3 claims per customer to ensure that they are fully associated to our Solution Designation scores

 

BizApps
CPOR
Customer Insights
dynamics 365
incentives
power platform
Sales Copilot
  • MartijnElfers's avatar
    MartijnElfers
    Apr 13, 2026

    Hi Sally,

     

    Regarding the 3 types of CPOR, I think this explains it very well on when to use which. As you can see, some are Bus. Apps. exclusive, or EA customer exclusive. 

     

    Eg. the Build Intent (old OSA incentive) is only applicable for Bus. Apps. customers purchasing thru EA. Than you get a one-time incentive for every High-Water Mark growth (basically every license add). 

     

    To answer your questions: 

    • When did Msft make these changes and why
      • A few years ago already. I believe with the introduction of the Designations, etc (or shortly after). 
    • What is the difference between Influenced and Usage Recognition
      • The license channel that the customer buys. Either an EA customer (Usage), or CSP customer (Influenced). 
    • Why MUST we use the template, and not be able to use a signed SoW with the details included
      • Only MSFT can answer this on why they do it. I'd assume it's to standardize the POE process and documentations. As MSFT has thousands of partners, each having their own SoW template. That would not be workable for MSFT. 
    • We are now potentially making 3 claims per customer to ensure that they are fully associated to our Solution Designation scores
      • Not really a question, but yes this could be, but probably not. See also screenshot above.  

     

    Cheers,

    Martijn

2 Replies

  • MartijnElfers's avatar
    MartijnElfers
    Bronze Contributor
    Apr 13, 2026

    Hi Sally,

     

    Regarding the 3 types of CPOR, I think this explains it very well on when to use which. As you can see, some are Bus. Apps. exclusive, or EA customer exclusive. 

     

    Eg. the Build Intent (old OSA incentive) is only applicable for Bus. Apps. customers purchasing thru EA. Than you get a one-time incentive for every High-Water Mark growth (basically every license add). 

     

    To answer your questions: 

    • When did Msft make these changes and why
      • A few years ago already. I believe with the introduction of the Designations, etc (or shortly after). 
    • What is the difference between Influenced and Usage Recognition
      • The license channel that the customer buys. Either an EA customer (Usage), or CSP customer (Influenced). 
    • Why MUST we use the template, and not be able to use a signed SoW with the details included
      • Only MSFT can answer this on why they do it. I'd assume it's to standardize the POE process and documentations. As MSFT has thousands of partners, each having their own SoW template. That would not be workable for MSFT. 
    • We are now potentially making 3 claims per customer to ensure that they are fully associated to our Solution Designation scores
      • Not really a question, but yes this could be, but probably not. See also screenshot above.  

     

    Cheers,

    Martijn