-
Ability to be informed that other partner has submitted POE for the customer we are working with
Suggested by – Completed – 1 Comments
There is an alert informing about customer association termination. However there are situations when we are still working with customer (i.e. partner sent POE with all the available workloads when they are in fact working on just a few of them) and we have to resumbit POEs for the workloads we are still working on. Therefore it would be beneficiary to have alert informing us that the POE from other partner has been submitted and we have ability to agree with customer on which workloads we are still working on and get the POE from this customer on those workloads. -
Notification message if claim is lost
Suggested by – Completed – 0 Comments
We did see that we are lost some workloads in OSU to another non-FRP partner that were approved claims for our organisation.
We would expect that we would have receive a message that another partner is claiming so we could proof our engagement. As we never got such message, we were surprised.
We would like to know if other partners also experience this kind of issues, so MSFT could improve the process of communication. -
About FTOP's Service Notes (FTOPのサービスノーツに関して)
Suggested by – Completed – 0 Comments
[Translated]
If the FRP registration of a company A is switched from another company to our company,
In addition, if you switch from our company to another company,
You can see service notes entered by other companies, or you can see our information.
Can't we improve here?
I think that it is good to see all the data as your company,
Information between partners is getting stuck.
--
あるA社のFRP登録が他社から弊社に切替となった場合、
また弊社から他社に切替となった場合、
他社が入力したサービスノーツが見れてしまう、または弊社情報がみられてしまう状況です。
ここは改善いただけないものでしょうか。
貴社としては全データがみれて良いのかと思いますが、
パートナー間の情報が駄々洩れになってしまっている状況です。 -
FastTrack Referrals Criteria
Suggested by – Completed – 2 Comments
We love the focus on referrals for OneDrive for Business, but we received some regular FastTrack Referrals that should be Non Incentive Referrals instead.
As example: we received a regular referral for a customer in size Extra Small for ODFB. We already deployed SharePoint Online, so there would be no incentive for this left. The customer was asking for file migration to ODFB, but the customer is not eligible for the Migration Benefit.
We would like to understand why the RFA Gateway is approving such RFA and send this as regular referral. We understand that some areas around RFAs/Non-Incentive RFAs are a little cloudy woul dlike to have documentation that outlines and confirms the conditions that a RFA must meet, in order to be considered as a Request for Assistance, as opposed to a Non-Incentive Referral.
So two questions:
1. Are there any other FRP's facing this unclear situation?
2. Could MSFT share documentation that outlines and confirms the RFA conditions? -
Localization request - increase content in Japanese (日本語の内容を増やしてほしいです。)
Suggested by – Completed – 1 Comments
[Translated] Currently, with Microsoft 365 Specialty Partner Hub, I'm looking into FastTrack.
However, items that are supported in Japanese are FastTrack Playbook and Operations Guide are few and far between. I want to have a better understanding of FastTrack. To that end, including FastTrack Ready Partner academy, Please support Japanese content for items that do not yet support Japanese content.
--
現在、Microsoft 365 Specialty Partner Hubを利用して、
FastTrackについて調べています。
しかし、日本語対応されている項目が、
FastTrack PlaybookとOperations Guideと少ないと思っています。
私は、FastTrackについての理解をより深めたいと考えています。
そのために、FastTrack Ready Partner Academyをはじめとした、
まだ日本語対応していない項目の日本語対応をお願いいたします。 -
CPOR Claim for Teams Meeting, Phone & Apps
Suggested by – Completed – 0 Comments
I was recently told that if I want to view the usage data from FTOP for sub-workloads for Teams Meeting, Phone Systems & Apps/Plat within FTOP I need to submit a CPOR claim for 'Teams Only'. When will the workloads for Teams Meeting, Phone Systems & Apps/Plat flow into FTOP without having to also select 'Teams Only'? -
Localization request - provide latest incentive guide in Japanese (最新のインセンティブガイドを提供いただきたい)
Suggested by – Completed – 1 Comments
-
API Access to FTOP
Suggested by – Completed – 1 Comments
It would be nice to see API access in to the FTOP and deeper reporting web tools, to allow partners to extract and manipulate the data. -
Missing DATA in reporting
Suggested by – Completed – 0 Comments
I have seen some data missing in recent reports (random workloads) missing once data exported. I take daily drops of the data for my own reporting and have seen this only this week. -
Granularity access option for the OSU M365 insights and recommended actions
Suggested by – Completed – 0 Comments
On Partner Center, the OSU M365 insights, the recommended actions per each workloads, as well as what workloads are claimed per each tenant provide very useful information for technical people engaged with the customer.
Currently there is no granularity that would enable us to provide access only to specific data, or to specific customer tenants or workloads for OSU Incentive program. We need to assign the "Incentive user" role ("incentive read only role" is not enough). This provides too much insights to our technical people that need only usage insights and customer status and do not require access to all other different Incentive programs, payments etc. or receiving any notifications regarding other incentive programs.
A granular assignment of roles to specific people at service or tenant level in Partner Center would help. Also the ability to assign only specific customers to specific technical engineers from our company.
Also a log activity with filters and access roles assigned to personnel would be of help. We like to assign responsibilities to persons on a workload - customer basis In FTOP it is possible to do this when the engineer or FastTrack partner Program Manager contact is associated on the customers tenant level. This feature would be useful to have in CPOR also.
FPC Program Ideas/Suggestions
Share insights/feedback, ideas and requests related to the FRP Program.
