FPC Program Ideas/Suggestions

The title says it all. It was already difficult enough with submitting support tickets that required referencing claims, but now with the new programs requiring manual submission of disputes it's even more painful. I would love to be able to see them all in one page to make searching easier (CTRL + F) but if they could at least be 100 per page that would be a very nice Quality of Life improvement!

OLM-MAM report is currently not reporting on ALL tenants and a lot of tenants are missing (even though we have CPOR records correctly assigned).

We NEED visibility into usage for OLM-MAM for ALL of our tenants in FTOP. 

This has been on my radar for a while now, as I imagine it will be for many FRPS. 

The current EMS/0365 Remediation Checklist which is accessed via the playbook, is now out of date. The dates/references are in the last year. 

They do not contain any of the new workloads which have been introduced by the program. 

Is there any guidance, on when refreshed Remediation Checklists will be released to partners?

[Translated text]

Success story registration site (aka.ms/FRPStories)

We need to clarify these points:

1. Microsoft's goal (of collecting our success stories)
(We have already provided our success stories in PPT.) 

2. Merit of posting our practices on aka.ms/FRPStories

3. Partner’s benefit 
We think there will be more posts if we have benefit(s) like the following:
- When we as a partner post more, he can get higher priority in referrals (e.g., MS will assign more users to us)
- A partner with more posts will have more FRP incentive, for example, doubled.
- The point will be added by 0.1 of FRP incentives for each post to introduce one of our new practices.

4. Are there any benefits to customer from this?
Benefits like the following:
- Some workshops will be free of charge for customer.

I understand that the M365 Apps payments are on hold pending the updates to Partner Center in Q4. I am requesting 2 things:

1. A statement of all earned milestones for the workload through the 'on-hold' period (so, for instance, if the changes go into effect in April, the on hold period would be from October through February)
2. Commitment to pay the milestones in the same month as the Partner Center data update occurs -- we are already several months in arrears now on these earned milestones; I don't want us to have to wait an additional 45+ days for the Partner Center earnings calculations to take effect and show up in our payment.

The customer name needs to be included in the Disassociation Email.  Including the claim number only means that you have to click into Partner Center to see what was disassociated and completely removes any hope of searching your email box for what has happened with a particular customer.  And since the disassociations don't get written into the notes of the claim, the email is the only way to follow what has happened with the individual workloads.  

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.

For our customers in FTOP, we'd like the ability to add a couple of custom fields where Partners are able to enter information specific to our organization. For example, customer IDs that is specific to our organization, region, sales rep, etc. and the ability to include that that information with the service usage report.   This would simplify the process to run targeted campaigns within our organization. 

I feel it would be helpful if FRP implemented a policy requiring all FRP Dispute statuses to be updated at least every 7 days. We have open disputes that have are not getting updated. I know this will all be moving to OCP eventually, but until it does can we please get regular updates?

We have disputes opened in January (yes, they are M365 Apps) that have not been updated since they were put "In Review" status a week later (1/13/21). I have requested updates in the tool but have not gotten a response, so we had to ask our FPM to take time out of her already busy day to chase down statuses for us. She should not have to do that for us.
It is difficult to show the value of the program to leadership when I have to tell them we didn't get paid, but I filed a dispute. Then, not being able to report on the status of those disputes or where the money is for the work we completed, makes it even more challenging.
Additionally, we have disputes that were opened over a week ago that are still sitting in a "Submitted" status.
I sincerely ask that FRP Help please put a little more effort in updating our payment disputes.

Data health seems to be affected when usage drops even after a milestone has been reached (perhaps client purchased more entitlements). It would be nice if this could be controlled in some way. 

Example: recently a client was on track and had passed 15% milestone, but then purchased an additional ~200 entitlements which dropped the usage percentage. Its not easy to see if/when they had hit that milestone, and now it remains as additional work in data health.