-
CPOR申請における同意書および資料の英語訳は必要なのでしょうか?
Suggested by – Completed – 0 Comments
CPOR申請が他パートナーからも同様の申請があったとの連絡いただいた際、下記のコメントをいただきましたが、日本の方に対して資料を全て英訳しする必要がなぜあるのでしょうか?
【事務局コメント】
申請頂きました本件に対して、他のパートナー様からも同製品/ワークロードの申請がございます。
本社の審査部門にて審査いたしますので、同意書および資料の英訳版を14日以内にご提出ください。
【CPOR申請】
ID: 1168652
件名:国立研究開発法人産業技術総合研究所様向けMicrosoft 365導入支援(FastTrack)TEAMS PLATFORM再申請 -
FastTrack Ready Program Partner priority on CPOR
Suggested by – Completed – 0 Comments
As FastTrack Ready Program Partner we are required to deliver services at no extra charge to our customers. Thanks to the CPOR-FRP association we get an additional incentive to cover for the services delivered under the program.
Recently we received a notice that for one of our customers another partner claimed several workloads so we where disassociated from the customer's workloads because of this. The other partner had contacts with the business at customer and entered an SOW for services that where not delivered (we understand this is difficult to prove).
Our FastTrack contact at the customer declined the new association because the other partner did not deliver any of the claimed services. Unfortunately, we appear to be no longer receiving the workload usage attribution for this customer. Since the customer will pass the 15% workload usage milestone soon, we will miss out on important FastTrack Ready Program incentives for which the work was delivered.
We have logged an incident for this over 2 months ago in order to reinstate Xylos immediately as CPOR-FRP partner for all previously associated workloads. Until now, without success. When there is a CPOR discussion between a FPR partner and a non-FRP partner the FRP partner should have the benefit of the doubt since other than non FRPs we are expected to deliver services at no cost.
-
Edge Incentive registrations has a redundant process
Suggested by – Completed – 0 Comments
The current process is you go to a website and fill in the customer information and the FRP information. After that the part that I do not understand, and it honestly seems like redundant work, is you have to fill out a form with the exact same information and mail it in to a specific email address.
I feel like the website that we filled in the information on in the first place should have a background process to fulfill this email portion of the process. Can you fix this process so it is more efficient?
Thanks,
JD
-
Data health - new FTOP report and update cycles
Suggested by – Accepted – 2 Comments
It would be great to add information about the update cycles and the last updated timestamp to the reporting - especially with regards to data health.
It is sometimes hard to figure out how up to date the reporting data is. -
PBI report - Performance by Usage Milestone tab - bucket size field
Suggested by – Completed – 0 Comments
I love that we have additional fields (QE/AE/AU at time of claim) and we have the new workloads (MIP, Teams Meetings, etc.) in the Performance by Usage Milestone tab!! However...... I would like to request we add the bucket size back to this report please. The Bucket Size field is quite useful for quickly identifying incentive amounts and forecasting. -
Partner Center - More than 25 claims per page
Suggested by – Accepted – 1 Comments
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 full access to report
Suggested by – Completed – 1 Comments
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. -
O365 & EMS Remediation Checklist Refresh
Suggested by – Completed – 3 Comments
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? -
Success story registration site (aka.ms/FRPStories)
Suggested by – Completed – 0 Comments
[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. -
M365 Apps - On Hold Payments
Suggested by – Completed – 1 Comments
I understand that the M365 Apps payments are on hold pending the updates to Partner Center in Q4. I am requesting 2 things:- 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)
- 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.
FPC Program Ideas/Suggestions
Share insights/feedback, ideas and requests related to the FRP Program.
