FPC Program Ideas/Suggestions

I think that FastTrack should include the Microsoft Viva Connections, Insights, Topics and Learning as workloads within CPOR association. Is there a forecast date when this update will be made?

I would like to request for further information on customer feedback.
KB-01140  · M365 Specialty Partner (powerappsportals.com)

1. What will be the subject and sender's e-mail address?
2. Will it be sent only in English?
3. For example, if the customer exceed 15% on three workloads at once, will three emails be sent?
4. If the WL already above 15% at the time of CPOR registration, will the survey not be sent?

Thank you.

Hi FT Program teams,

Good days!

 I would like to bring to your attention that through our MCAP eligibility check on the MCAP portal for workshop nomination up to today on 20 Oct 2021, all our existing EDU customers from Malaysia (53), Indonesia (3) and Philippines (7) do not have entitlement to any of the 14 MCAP workshops. 
M365 Accelerator Program (m365partneraccelerator.azurewebsites.net)

This is a great opportunity loss not only to E5/A5 upsell possibilities for Microsoft, but also a potential revenue loss for FRP like Alfa Connections (63 x 14 x $3500).

Seeking your assistance to look into this immediately as my teams ready to drive more MCAP in FY22.  Your help would be greatly appreciated.

Thank you.

Best Regards,
Intan Nurbaizura Binti Mohd Zulhilmi | Operations cum FastTrack Assistant

 

Understanding there are future plans for transitioning from FTOP to PC for data purposes I have a question about Overall Status Notes (OSN).  When previously asked, the answer was that they would likely go away and not be required anymore.  However, (as much as I cannot believe I am saying this) I feel the OSN history of a customer's FT engagement(s) can be quite valuable.  Some customers have been around FT for years.  Having a history of previous engagements can save a lot of time and headache.  As a regular part of our process, we review the OSN history for every new customer in FTOP.  Sometimes we find out information the customer may have forgotten to share that could have a significant impact.  Being aware of certain information helps us provide a better experience for the customer, which is very important to our team.
With all that being said, I am wondering if the program team will take into consideration the value of the OSN and provide FRP a way to still utilizing the tool.

Hey Team,

It has been a while since we have had any updated deck describing the workloads and description of guidance provided around the workloads. I have asked our FPM and it seems that the most recent one is very outdated and missing workloads. Is this something that is on the roadmap or something that has been released and I just have not been able to access. Please let me know if available or when an updated one will be available.

Does the FTC send Customer Satisfaction Surveys to FRP customers?  If not, would this be something they would consider?  On occasion, we request a SME from the FTC.  Most times the customer has a very positive experience, but not always.  I feel it would be beneficial for the FTC to know who is doing a great job representing Msft and who may need a little additional training.
 

We have found that the PAU occasionally differs from what we expected.

We recognize that the values in FTOP reflect the data on Partner Center, of which we inquired why the difference sometimes occurs, and they answered they were "system bugs."

 When the same event occurred around May 2020, you responded as follows:

We considered FTOP as the provider of legitimate data; however, we are afraid to say that no values are considered legitimate because we have found the source data for Partner Center and FTOP are the same at present.

We think this problem should be fixed, although it is systematically hard to fix.

=================

Entitlement (number of licenses), the basis for incentives and AU are based on information from Partner Center. Therefore, the data in Partner Center should be treated as the right number.　When FTOP and Partner Center show different numbers, some numbers are doubled. we simply think it will occur again especially when expiration of a license is coming as below and the number is shown double and then combined for a certain period of time. As you can see the numbers below, the entitlements in FTOP return to the original number after May 30th.  Please understand this is the way it goes. Unfortunately, this is something we cannot help improved by any means.

FTOPのPAUが、想定される数値と異なることが時折発生します。
FTOPの数値はPartnerCenter側のデータを反映していると認識しており、PartnerCenterに問い合わせたところ、「システムのバグ」と回答を頂きました。

2020年5月頃に同事象が発生した際は、貴社に下記のように回答いただきました。
今まではFTOPを正と認識しておりましたが、現状はPartnerCenterとFTOPのデータソースが同じなので、どこにも正と出来る数値が存在しないことになります。
システム的に難しいことなのかもしれませんが、改善をお願いいたします。
=================

インセンティブの計算の元となるEntitlements(ライセンス数) 、AU共にパートナーセンターの情報がベースとなります。よって、パートナーセンターの数字を正としてください。

FTOPでパートナーセンターの数字が異なるのは、単純に数字が2倍で表示されることは今までも今後も続きます、これは例えば下記のようにライセンスが切れる時期が近くなるとこちらのシステム上一定期間2重表記され合算されて表示される期間があります。下記数字をみると想像できるように5/30過ぎると重複しないためFTOP上のEntitlementsは元の数字に戻ります。こちらはこういうものだと理解していただけますようお願いいたします。これはどうしても改善は出来かねるものです。
======================

[Translated]
When a customer has an MPSA contract, only MAUs are shown on PartnerCenter/FTOP, and PAUs don’t count.

I understand that PAUs are not viewed for MPSA contract as it is not eligible for incentives; on the other hand, I do not understand why we still can submit a claim via CPOR. Therefore, we suggest any submission by the customer with MPSA contact should not be allowed.

Also, I hear that Microsoft Cloud Accelerator Nomination is determined based on the data from PartnerCenter.

License types do not affect the Microsoft Cloud Accelerator criteria. However, the licenses for the MPSA contract do not count in PAU, which might not be able to be nominated as the number does not reach the requirement.

We hope these two issues are fixed for a better partner/customer experience.
--

お客様がMPSA契約の場合、ライセンス数がPartnerCenter/FTOP上でPAUはカウントされず、MAUのみ表示されてしまいます。
MPSA契約の場合、インセンティブ対象外なのでPAUが表示されないことは理解できますが、であれば、CPOR申請のタイミングでMPSA契約の場合は申請できないようにしていただけないでしょうか？

また、Microsoft Cloud AccerelatorのNoimnitaion可否はPartnerCenter上のデータを基に判断されていると聞いています。
Microsoft Cloud Accerelatorのクライテリアにはライセンスの契約形態は関係ありません。ですが、MPSA契約のライセンス数はPAUにカウントされず、ライセンス数不足のためノミネーション不可になってしまうことがあります。

上記2点に対して改善をしていただきたいです。

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

Translation provided by FPM Tamami Mitani
 

The FRP would like MS account team to know which FRP are engaged with their customers so that they won’t ask non-FRP partners to support their customers.

It seems there have been cases where MS Sales introduced non-FRP partners to their users who the FRP claimed CPOR for.

I think the point is we need to raise FRP awareness internally and provide those kind of information with sales team.

Also we have to recommend the FRP should reach out account team proactively with utilizing contacts information in FTOP.

S2500のユーザはSMEやMWAと情報共有等することができています。
S2500ではないユーザは、SMEやMWAがいません。
また、S2500ではないユーザは、MS営業はFRPがアサインされているかどうかも知りません。
そのため、FRP登録したユーザに対して、MS営業がFRP以外のパートナーを紹介するケースが出ています。
S2500ではないユーザに対してFRPが登録されている情報を、
貴社営業と共有する仕組みを検討ください。
FRP登録したメリットがなくなるのは残念です。