Program Tools (non OSU) ideas/suggestions

Refresher needed regarding ASPX data sharing both internal and external with partners. Would like to have formal guidance to ensure we stay compliant with corp rules.

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

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. 

Request to Include CSP Revenue to PIIR in PSM Dashboard to measure the partner contribution across CSP deals

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.

I would like to request the addition of a customer segment filter in FPX. Our partners are strategically focusing on SMC customers. However, FPX currently includes both Enterprise and SMC segment customers, which requires manual extraction of SMC data. This process is time-consuming and has become a blocker for FPX adoption.

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.