Skip to Main Content
  • Viva Workloads in CPOR

    I think that FastTrack should include the Microsoft Viva Connections, Insights, Topics and Learning as workloads within CPOR association. Is there a forecast date when this update will be made?
  • Conflicting CPOR Claims

    These days, it seems like every week we are getting notified of another claim that is being contested as another partner has submitted a CPOR Association request for a workload we had previously secured. If I understand how it works, if the new partner shows adequate POE that is newer than the POE we provided, then we become disassociated and lose the AU growth for that customer and workload.  
     
    I'd like to suggest an alterative approach: AU Growth Sharing for 1-year to a maximum of two partners
     
    It seems crazy that two partners aren't both rewarded with AU Growth incentive and metrics if they both in fact helped the customer drive adoption.
     
    Rather than only having one Partner of Record, Microsoft should allow two partners to both share in the credit and track the AU growth accordingly for a period of at least 1-year from the time the original POE was accepted. That way, the Partner isn't negatively impacted with its Solutions Designation score if a new partner also joins into the mix to support the customer. 
     
    If two or three years has passed, its highly unlikely the partner is still engaged. But if it is within 1 year, then that original partner should still share in the benefit of the AU Growth attribution.
     
     
  • Editing a CPOR Claims to remove a workload after approval

    It would be great if the CPOR Claim could be edited after approved or in the case of a Partner Conflict to allow the original claiming partner to remove a workload that might be in question.
     
    I've seen a few times now where multiple Teams workloads are claimed under one Association, however over time another partner has a competing claim for one of the many workloads included. 
     
    Rather than cancelling the entire original partner claim, it would be ideal if the Partner could evaluate and possibly deselect a workload if they believe in fact they are not driving adoption for it anymore. 
     
    That would save a TON of time, effort and likely cost to Microsoft if it didn't trigger a third unnecessary claim process that is trying to then re-claim the workloads that are still technically covered under the original association.  That's a waste of time and big annoyance for both the original Partner and Customers that are trying to figure out what all the claiming nonsense is all about.