Loredana Munteanu Partner Success Manager (PSM)

One of my partners, Exakis, shared with the an improvement Idea for FPX (soon MPX). He said that when they export the Opportunities in an Excel file, the CPOR eligibility column does not exist, as it is in the Table view (before export). Instead, they have 2 columns: Claim ID and Claimed by Others (True/False). When the Claim ID is referenced- this means the partner has already a CPOR claim on that tenant. When the Claim ID is blank and the Claimed by Others shows “True”, it means there is a claim submitted by another partner. But When the Claim ID is blank, and Claimed by Others  shows “False”, in theory, there is a CPOR opportunity for the partner but additional verifications should be done by them to see if they can proceed with the CPOR claim. It can be that some workloads do not exist as they are mentioned in the Opportunities, to be further claimed. Example: DNR P1+P2, MIP P1+ P2, DLM P1+P2, etc. So it is not straight forward for them to identity a CPOR opportunity,Their ask is to have the same information/column in the Excel file export, CPOR eligibility (Yes/No).

Partners who were offboarded from the Program, did not receive automatically the T&Cs for Deployment Vouchers to be signed so that they could continue to redeem the Vouchers. I was contacted by different partners who did not continue in the Program, to provide the guidance on the next steps (reach out to the PXPartner Onboarding team, to check eligibility for the Deployment Voucher Program and to send the T&Cs to the partner to be signed).The same scenario could happen for Global partners, where some other subsidiaries that are not in the Program, may want to start redeeming vouchers and there is no process shared with them. Ask: Please publish the official guidance for partners that are no longer FastTrack Ready on how to redeem deployment vouchers. 

In FY26, SharePoint and Exchange workloads have been removed from the scope of the FastTrack benefit. As a result, partners are no longer expected to support customers with migration prerequisites, such as readiness assessments. To ensure clarity around the updated requirements, it would be great to develop a concise OnePager or a formal Knowledge Base article. This resource should outline the FY26 changes, include visual aids, and guide partners on how to position their value-added services (VAS) and assist customers in initiating their migration projects.

When presenting to Wakers partner the different scenarios in MPX (ASPX) to drive Secure AI Productivity, Security and Copilot upsell opportunities and when checking the End date of the Subscriptions (they are not an LSP, and they do not have access to EA renewal date), they noticed a potential improvement that could be added to the tool.They mentioned some customers have automatic renewal enabled for their licenses, so for this type of contract, it is not useful to check the End date of the Subscription and initiate specific actions on customer side to secure the renewal. They would like to see this option ("Auto Renew Opt-in") flagged in the Subscriptions page. *The “Auto Renew Opt-In” must be selected before the contract is signed to activate automatic renewal. Business Impact: Reduce the efforts of the Partner Sales Teams to get in touch with customers prior to renewal and drive renewal conversation while the renewal will be done however automatically.  Help the partner prioritize even better the customers who need to be targeted for renewal conversations.