More and more, we are finding that customers don't want to register or associate a different partner for a CPOR workload. Too often it is controversial, or another partner (LAR) might have a deal to have them all associated with them, or there might have been another partner that "also" had a role driving MAU and they don't want to switch.
The net effect is that we aren't getting proper attribution for our role driving adoption and our monthly/quarterly/annual performance looks underwhelming. This also impacts how we are rewarded through the incentive model and can negatively impact how we are graded from a compliance standpoint. This may not be impacting all partners, but at last count we've only been able to register 1/20 engagements in the last 3-4 months where technically we are driving adoption or advancing the cause! In my experience, the friction is real and causing the whole CPOR registration to not work for us.
I have a few suggestions to consider:
1. Perhaps it is time to reconsider the business rule that only one partner can be associated to a workload. What if by design, rather than by exception, multiple partners could be assigned to a workload? That would remove some of the friction that customers face accepting a new request.
2. What if there was a simpler way to confirm a partner is engaged? Currently, we need to either have a customer sign a document or we need to submit a signed SOW as POE. As a partner, we often don't feel comfortable submitting an entire SOW as it contains a lot of detail that is under NDA.
Secondly, we worry that if we just submitted the SOW without first talking to the customer, they would be upset receiving the email notification from Microsoft as it is confusing and possibly triggers the multi-partner association issue. Instead of it being a "notification of partner association", perhaps it could be reworded to "Confirmation of Partner Engagement" and the language could say, "Congratulations, we understand you have retained the support of <partner name> and in your work together you may be driving the adoption of the following areas: <list the areas>
To support your work together, we will provide limited adoption data of these workloads with your partner. If you would prefer not to disclose this data, or have the partner associated in our records as providing support, please click here. Otherwise, nothing is required in response.
3. Another great option would be for Microsoft CSM or Modern Workplace Specialist to be allowed to "vouch" for our engagement. Perhaps the partner could request someone on the Account Team to confirm that the partner is engaged and is driving adoption/MAU.
4. I'd recommend that any MCAP POE count as CPOR POE for key workloads that relate to the engagement. We've had many MCAP engagements that were influential at moving a customer forward, but for various reasons we weren't able to get associated to that customer for the workloads in question.
The net effect is that we aren't getting proper attribution for our role driving adoption and our monthly/quarterly/annual performance looks underwhelming. This also impacts how we are rewarded through the incentive model and can negatively impact how we are graded from a compliance standpoint. This may not be impacting all partners, but at last count we've only been able to register 1/20 engagements in the last 3-4 months where technically we are driving adoption or advancing the cause! In my experience, the friction is real and causing the whole CPOR registration to not work for us.
I have a few suggestions to consider:
1. Perhaps it is time to reconsider the business rule that only one partner can be associated to a workload. What if by design, rather than by exception, multiple partners could be assigned to a workload? That would remove some of the friction that customers face accepting a new request.
2. What if there was a simpler way to confirm a partner is engaged? Currently, we need to either have a customer sign a document or we need to submit a signed SOW as POE. As a partner, we often don't feel comfortable submitting an entire SOW as it contains a lot of detail that is under NDA.
Secondly, we worry that if we just submitted the SOW without first talking to the customer, they would be upset receiving the email notification from Microsoft as it is confusing and possibly triggers the multi-partner association issue. Instead of it being a "notification of partner association", perhaps it could be reworded to "Confirmation of Partner Engagement" and the language could say, "Congratulations, we understand you have retained the support of <partner name> and in your work together you may be driving the adoption of the following areas: <list the areas>
To support your work together, we will provide limited adoption data of these workloads with your partner. If you would prefer not to disclose this data, or have the partner associated in our records as providing support, please click here. Otherwise, nothing is required in response.
3. Another great option would be for Microsoft CSM or Modern Workplace Specialist to be allowed to "vouch" for our engagement. Perhaps the partner could request someone on the Account Team to confirm that the partner is engaged and is driving adoption/MAU.
4. I'd recommend that any MCAP POE count as CPOR POE for key workloads that relate to the engagement. We've had many MCAP engagements that were influential at moving a customer forward, but for various reasons we weren't able to get associated to that customer for the workloads in question.
When asked for help from Microsoft field sales they always tend to say: it is the customer's right to refuse. if your customer doesn't want the association it is up to you to convince him to do so. Think of something you could offer the customer as an extra benefit. Why not share some of your incentive?
As an FRP we depend on the incentive so what could we possibly offer as an extra driver?
I agree that most of the times when we only offer user adoption services it is very hard to obtain an agreement from the customer to associate.
All changes to OSU and Partner Center tools and processes are shared via Microsoft Partner Communications and many are reposted via the FRP Heads Up Newsletter (subscribe in your profile page https://m365-specialty-partner.powerappsportals.com/). Most announcements are around the annual OSU program update in October of each year.