Program Tools (non OSU) ideas/suggestions

[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.

We don´t have access of the Portal informations Claims, we don´t have access to basics information kind of MAU evolutioin´s customer We can´t to see how te be the status of the customer. We lost a lot of access data that has not yet returned and this is causing great difficulties for our relationship with Microsoft customers.