Program Tools (non OSU) Ideas/Suggestions

1. Describe the scenario briefly (what is the feature? how will it work as a partner i can do X so that i can achieve Y)  We propose adding a new column in the Customer Details section of Copilot Opportunities Insights that displays the growth potential for Copilot Chat. This metric would be calculated as: Total number of M365/O365 SKUs owned by the customer – Current Copilot Chat MAU. As a partner, I can quickly identify customers with high growth potential and prioritize proposing Copilot + Power Accelerate, enabling faster engagement and deeper adoption.   2. Describe the business problem or pain point (why is this feature needed?) Currently, partners lack a clear, data-driven method to evaluate the growth potential of Copilot Chat. Without this insight, decision-making is delayed, potentially missing opportunities to upsell Copilot + Power Accelerate. Partners are spending extra time manually estimating potential, which is hindering the adoption of Copilot Opportunities Insights. Adoption of ASPX is accelerating. Improved productivity: Reduces manual analysis time by delivering actionable insights directly within MPX. Faster decision-making: Enables partners to prioritize high-potential customers immediately. Drives revenue growth: Facilitates targeted proposals for Copilot + Power Accelerate, boosting adoption rates. 3. Describe the expected impact (quantify the impact e.g. improves productivity, reduces manual toil) Partners' adoption of ASPX will advance through the following improvements:     • Productivity gains: Reduce manual analysis time by delivering actionable insights directly within MPX.     • Faster decision-making: Enable partners to instantly prioritize high-potential prospects.     • Accelerated revenue growth: Facilitate targeted proposals for Copilot + Power Accelerate and boost adoption rates. 4. How many partners asked for it? (quantify the ask) At least 7+ partners have raised this need. 5. What is the urgency? High/Medium/Low High – Partners are actively seeking ways to accelerate Copilot adoption, and this feature directly supports FY26 growth priorities. 6. How does success looks like? (success criteria, measurable outcomes, KPI) Success Criteria: Columns are available in MPX Customer Details for all partners. Accurate calculation of growth potential based on SKU and MAU data. Measurable Outcomes/KPIs: ・Promotion of ASPX adoption by partners. ・Partners plan campaigns using Copilot Opportunities Insights within 3 months of launch. ・Improvement in partner satisfaction scores in MPX usability surveys.  

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

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) 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)

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

I would like to request the addition of a CSP Renewal column to the customer data section in FPX. Currently, FPX includes the EA Renewal column, but it would be helpful to also have the CSP Renewal column. Partners take different approaches depending on whether a customer has an EA or CSP agreement, so they need visibility into the type of agreement and its renewal timing within FPX. When prioritizing customers, partners first check the agreement type and renewal timing.

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. 

Request to add the information of the incentive, from CPOR, MCI , Deployment Offer earned together in the Land and Expand dashboard. Background; leadership team to utilize the MPX dashboard consistently, having motivation that it will help doing renewal, upsell, incentive, when they use the dashboard they want to actually see the immediate impact of which and if the effort resulted in the revenue, without having to spend too much manual effort cheking one by one currently

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.

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.