Please submit all support and access issues to https://aka.ms/PXPartnerSupport.
-
[PSM Dashboard] Include Tenant Purchase align with Completed Workshop list in the PSM Dashboard
Suggested by Alfira Fitrananda – Accepted – 0 Comments
We need to know if the utilizing FRP MXP Dashboard to do MCI workshop through Eligible MCI lead to upsell.Currently there's no visibility except to know that. PSM ask manually to partner what deal happened, which MCI worshop that comes from the deal. It leads to very long time because There are multiple layer and many team involved ( might ask CSM need to ask AE/ Ask regional alliance manager, need to check in country/account level)The FRP doing the workshop might be different than the one close the deal, potentially not aware Having dashboard showing possibility ofWhich workshop completed by partnerWhich customer completed workshop by tenant ID and if there's license purchase to trackInclude Tenant Purchase align with Completed Workshop list in the PSM Dashboard -
PSM Dashboard | Include CSP Revenue in PIIR
Suggested by Manfred Cheng – Completed – 0 Comments
Request to Include CSP Revenue to PIIR in PSM Dashboard to measure the partner contribution across CSP deals -
Include Customer Sub Segments in all reports
Suggested by Manfred Cheng – Accepted – 0 Comments
Request to Include Customer Sub Segments in all Reports (MPX and others) -
[MPX] Request Graph of usage details with timeline per tenant with timeline in one view (like Lynx Usage details view)
Suggested by Alfira Fitrananda – Accepted – 0 Comments
[MPX] Request Graph of usage details with timeline per tenant with timeline in one view (like Lynx Usage details view) Background : Tracking of all products usage is difficult to use as it's spread in multiple rows in the tabDifficult to measure the usage impact based on timeline after the CPOR is claimed. ( partner want to know since the cpor is claimed / workshop done, how's the usage impact or gap) Request : Have usage details view similar like in Lynx Microsoft that shown the workload usage in graphs/ one page view instead of separate in rowsAsk: to have it's in the page of the tenant (together with the subscriptions they have) -
MPX | Count all eligible customer seats as whitespace in Copilot opportunities.
Suggested by Jesudass Mouttappa – Accepted – 0 Comments
Request to enhance MPX by including the count of all eligible customer seats as whitespace in Copilot opportunities. This will enable better prioritization based on customer size and improve opportunity targeting. Current Limitation: Whitespace is calculated as Paid MAU - Free Chat MAU, which doesn’t reflect total customer potential.Partner Impact: Partners currently need to manually analyze license data to estimate customer size, which is time-consuming and inconsistent.Currently partner need to understand customer size by analyzing the existing license -
MPX | [INTERNAL ONLY] Add details information for MAU > PAU in LXP Dashboard
Suggested by Alfira Fitrananda – Accepted – 0 Comments
Situation: Some customer shows MAU > PAU Request : Add details Needs clarity of reason why? is it data error? is it counting trial license? is it possible technically MAU>PAU . Happen in many customers in various security workloads Add suggestion talking point what to discuss with customer based on the reason. -
More granular MCI eligibility filtering in MPX
Suggested by Ben Tappenden – Accepted – 0 Comments
Currently in MPX a user is able to filter on MCI by selecting either 'Eligible' or ‘Ineligible’. To allow for better targeting depending on the specific campaign or motion a partner is looking to run, it would be useful if the filtering was more granular. For example, the ability to filter on Copilot eligibility, Data Security etc. -
FPX: Enable the ability to retain the Change Columns settings in the FPX
Suggested by Ryota Tsuji – Accepted – 0 Comments
Currently, the Change Columns button in the FPX customer data area allows users to add or remove data fields displayed. However, these settings are not saved, so every time we access FPX, we must reconfigure the columns. While this may seem like a small task, it becomes a repetitive burden over time. If the Change Columns configuration could be retained, it would significantly reduce wasted time in the long run and greatly improve the usability of FPX. As an advanced enhancement, allowing users to save multiple personalized views e.g., My Views would be even more powerful. This would enable instant switching between different perspectives for analysis, making workflows faster and more efficient. -
PIIM and PIIR Data Inconsistencies
Suggested by Ashwini ashwini – Accepted – 0 Comments
igures for PIIM and PIIR vary across multiple reports within the same dashboard. Example the PSM scorecard PIIM and PIIR data - differs from Partner Insights Data. -
CSP Deployment Accelerator for ME3/ME5 MCI eligibility could be miss-leading and confusing for partners
Suggested by Ben Tappenden – Accepted – 1 Comments
The CSP Deployment Accelerator for ME3/ME5 engagement offered via the MCI program is a great initiative, however I believe there could be confusion with partners who are seeing some customers as eligible, who in fact aren't. Because of the nature of this engagement, it must be linked to a CSP purchase within the same month as the claim and that is clearly documented in the MCI guide. However, because in theory most tenants COULD be classed as an opportunity for a purchase, partners are seeing a high number of customers appearing as eligible for this engagement both in the MCI portal and also within MPX. This allows them to claim without actually having an open opportunity, or a purchase within the last month to make the tenant qualifying. This presents a risk to the partner that they could potentially invest effort into driving work with the customer, but then not getting paid due to the customer not actually being eligible. To better define ths potential risk, the below is a direct quote received from Thomas Viertler regarding this engagement: The MCI engagement was set up so to allow a partner to select customer tenant IDs with at least 300 Entra ID seats (that have or not made an eligible transaction, as defined in the MCI customer eligibility section) - this is why partners see a large number of tenants in MCI . This does not mean that every tenant has done the required purchase and can be claimed. There are a couple of potential asks here:MCI portal, and MPX, be adjusted to show only true eligible tenants based on recent CSP purchase history. Thomas advises that the MCI team are looking into the feasibility of this - this could take many months to implement (if at all)There is a Power BI report which shows the eligible tenants for the engagement based on purchase history - FY26 ME3/5 CSP Deployment Accelerator CE Report (MCI Ops) - Power BI. This PBI is not currently open without requesting access. It would be useful if the program team could work with the report owner to have it opened up for all PSMs to access, and then perhaps pin it to the PSM Reporting Zone in the M365 G&I Reporting Center. This will allow PSMs to then provide accurate guidance to their partners on customers they have in their portfolio who are eligible, and minimise the risk of partners claiming and not getting paid for delivery due to customer non-eligibility. I attach a copy of the specific engagement as per the latest MCI Incentives Guide dated 22nd August.
