Program Tools (non OSU) Ideas/Suggestions

Partner support area has no way for me to create a new case. Please tell me how to make a new case. 

For some CPOR claims we would like to have the option to set a flag that the claim/customer should not be moved into FTOP. Sometime we have customer where we provide services but are not providing any Fast Track services and it does not make much sense to track those customer in FTOP.

[Translated]
If the FRP registration of a company A is switched from another company to our company,
In addition, if you switch from our company to another company,

You can see service notes entered by other companies, or you can see our information.

Can't we improve here?

I think that it is good to see all the data as your company,

Information between partners is getting stuck.

--
あるA社のFRP登録が他社から弊社に切替となった場合、
また弊社から他社に切替となった場合、
他社が入力したサービスノーツが見れてしまう、または弊社情報がみられてしまう状況です。
ここは改善いただけないものでしょうか。
貴社としては全データがみれて良いのかと思いますが、
パートナー間の情報が駄々洩れになってしまっている状況です。

I was recently told that if I want to view the usage data from FTOP for sub-workloads for Teams Meeting, Phone Systems & Apps/Plat within FTOP I need to submit a CPOR claim for 'Teams Only'.  When will the workloads for Teams Meeting, Phone Systems & Apps/Plat flow into FTOP without having to also select 'Teams Only'?

I have seen some data missing in recent reports (random workloads) missing once data exported.  I take daily drops of the data for my own reporting and have seen this only this week.

I love that we have additional fields (QE/AE/AU at time of claim) and we have the new workloads (MIP, Teams Meetings, etc.) in the Performance by Usage Milestone tab!!  However...... I would like to request we add the bucket size back to this report please.  The Bucket Size field is quite useful for quickly identifying incentive amounts and forecasting. 

Previous Post on Yammer:

We thought we should share this with the rest of the partner community. We have raised a ticket in relation to this issue with FRPhelp and the data and Tools team is reviewing the following.

We have found that the S2500 customers are being identified or tracked using TPID. The problem is in a scenario where multiple customers share the same TPID, all of these customers are being flagged as S2500 customer. For example, we currently have one S2500 customer in an industry vertical and as it shares the same TPID with 15 other tenants, they are all being flagged as an S2500. We have reached out to most of the accounts team and got confirmation from them that not all of them are considered S2500 customers, rather the parent tenant is the S2500 customer.

We know we are not being measured on this currently, however, the non S2500 customers are skewing the data health results and also creating a bit of confusion on who the actual S2500 customers. In our opinion, FTOP should not be flagging child tenants of S2500 customers as a 'S2500' customer.

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.  

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