Suggested by Chris Radcliffe – Completed
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.
-
Hello: Thank you for your excellent suggestion surrounding the POE Claims process used by the OSU-M365 Program. We have shared your feedback with the OSU Management Leads and Business Owner for their review and consideration for future iterations of the Claiming tool. Thank you for your well thought out suggestion. We have shared this suggestion with the OSU-M365 Program Launch Team and Business Leadership for their review. In the future, all new ideas or feedback on the OSU program or process should be sent directly to your Partner Development Manager (PDM). They will raise this feedback directly with the CPOR/OSU team for triage and update you on the status. If you would like to learn more about the various avenues you can learn more surrounding the OSU-M365 program or Partner Center issues, please copy and paste this link into your browser: https://learn.microsoft.com/en-us/partner-center/support-from-microsoft