FPC Program Ideas/Suggestions

Hello,

We have several disputes about having a customer claimed in Bucket size XXS for a POC that is running. At time of claim the AU is over 20%.
In the current T&C this means a FRP will not be rewarded for supporting the customer achieving milestones in higher bucket sizes after additional licenses were purchased.

In this scenario the FRP is spending time to support the customer but will not get paid on this. This seems illogical and not fair.

Would like other FRP experiencing similar issues to like this idea, so MSFT Program Owners can update the T&C to become eligible for the effort spend.

FastTrack Ready Partner Hub上のPlaybookの下記資料をクリックするとエラー表示になり、ファイルが閲覧できません。
FrP側で表示できない場合、ファイルがそもそもないのか、FrPのみ表示できないのか判断が付かないため、分かるようにしていただきたいです。
※FPMの方は閲覧できるそうで、資料自体は共有いただきました。

■対象ファイル：Skype to Teams Transition Overview
■エラーメッセージ：このページは現在機能していません
fasttrack-docs.microsoft.com では現在、この要求を処理できません。
HTTP ERROR 500

[Translated] Power BI is currently covered by FastTrack.
In addition to Power BI, Power Platform
I want you to add it to the privilege target.
Best regards.

--

現在Power BIが、FastTrackの対象となっています。
Power BIだけでなく、Power Platfrom を FastTrack の
特典対象に追加して欲しいです。
よろしくお願いいたします。

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.