Program Tools (non OSU) ideas/suggestions

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.

Requesting early access to the tools and reporting within Partner Center as FTOP makes the transition to Partner Center. Looking to be apart of a pilot, leveraging the portal before any go live dates.

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.

Hello,

I had earlier opened a support ticket with FRP help which was set to a resolved status. However the problem continues so i added a comment to the ticket . However the ticket is still in a closed ticket. Please enable the ability to partner to reopen closed tickets or wait for confirmation from partner to close a ticket

Thanks,

Vanitha

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は元の数字に戻ります。こちらはこういうものだと理解していただけますようお願いいたします。これはどうしても改善は出来かねるものです。
======================

Is there a way to automate the eligible workloads in the Customer Contact section w/i FTOP for CPOR approved workloads? 
To update the Customer Contact field in FTOP FRPs have to manually add the workloads eligible for survey.  Is it possible to have automation put in place that would auto-populate these workloads based upon approved CPOR? 
OR...... can the survey team pull the workloads from the CPOR Partner Information field (the FRP stamp) found w/i each workload under the Services tab of FTOP?  The query could look for fields not null & add those workloads to the survey eligibility report.

[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点に対して改善をしていただきたいです。

As lots workloads have officially changed the name to new workload name, could you please also change the names in Partner Center for them? Every time when we - partners are trying to submit CPOR association requests, or checking claim status in Partner Center, the old display names are really really confused. For example, Azure Advanced Threat Protection, which should be Microsoft Defender for Identity now, still using the old display name. This is confusing...

We've come across many examples where customers are fully deployed on a workload (such as Exchange at 99%), but when they are added to FTOP, the entitlement status is reflecting "Status Unknown" and we're having to update it to "In progress" to have it not show up on the non-compliance report. For workloads with active usage over 60%, it should automatically reflect as a new status "Adoption" and not "Status Unknown."  This is a lot of extra administrative work to update the entitlement status.  

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