FPC Program Ideas/Suggestions

It would be great if we could select multiple workloads when we raise a customer association claim request in Partner Center. Currently there's a cap at 4 workloads, meaning that sometimes we need to raise up to 4 claim requests for just 1 customer. This is quite time consuming. 

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

In July, we experienced a large claw back of incentives due to an overpayment from Microsoft in May for the Microsoft Information Protection workload.  The reporting errors not only impact us financially, but it negatively effects our internal sales force's quota goals and confidence in the reporting structure of the OSU and FastTrack program.  This is not the first and only incident. A similar error has happened last year.

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

When submitting SOW/POE for CPOR association, customers sometimes feel uncomfortable to sign several SOW/POE with same contents with the only differences in the ticked workloads. Is it necessary to have the maximum of four workloads for per SOW/POE, any possibilities to remove this limit? 

Having a search bar on the customer associations tab on Partner Center can really help the FRPs search submitted claims by - claim ID/ customer domain name. Currently the only way to retrieve a past claim details is to export the entire claims record. Through this search bar, we as a FRP, can get more granular with our search for a particular claim.

We'd like to flag or not have OSU start tracking the usage for entitlements that have less than 150 entitlements (requirement). For example, if a customer 1000 seat customer has 10 licenses of EMS E3 and they are testing Intune and they deploy the 10 entitlements, the usage will be 100% and we would NOT be eligible for any incentives when the usage is already at 100% and we submit a CPOR claim. This is common especially with CSP customers who do not want to invest in the cost of the entire license cost while they are testing.  It's challenging to track to watch when the customer will make the rest of the license purchase when you have hundreds of customers. Changing the tracking of customers with less than 150 entitlements will allow partners to assist customers with less than the 150 requirement with the intent to purchase more after testing is complete. 
 

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.