Share insights/feedback, ideas and requests related to the FRP Program.
  • 9

    Information about the CPOR API Framework in PartnerCenter

    Suggested by Needs Votes  1 Comments

    In coming period, MSFT will migrate from FTOP to Partner Center (OSU-M365).
    It would be very helpfull if MSFT could share then API Framework (or future enhancements) to partners so they can integrate their internal systems.
    If it would be possible to have a 2-way API that would even be super (for downloading and uploading relevant data).
  • 1

    Microsoft 365 Specialty Partner Community(本サイト)上で探しているPlaybookが見つからない

    Suggested by Completed  3 Comments

    >FTOP Task Details<上で掲載されている資料を>Microsoft 365 Specialty Partner Community<で検索しても見つかりません。
    ※以降、下記と表現します。
    >FTOP Task Details<:①
    >Microsoft 365 Specialty Partner Community<:②

    これまでPlaybookは①で探していました。
    しかし①のドキュメントは、今後は②に集約していくと認識しています。

    ①にあった資料の"タスク番号"を②で検索しても資料が見つかりません。
    推奨の探し方、もしくは今後も①で資料を確認すべきなのか知りたいです。

    また、英語版資料がローカライズされたタイミングや既存資料が更新されたタイミングで、Heads upで全ての資料が周知されるようになっているでしょうか?
    もしくは、>Playbook Task Reference List<で今後も確認していくのがいいのでしょうか?
  • 8

    Partner Center Enhancements - show which partner has claimed workloads

    Suggested by Needs Votes  2 Comments

    Today there is a FRP PowerBI dashboard that shows what other partners have claimed workloads for a customer that you have claimed a workload with. That information would ideally be available in Partner Center!
  • 9

    Partner Centre Enhancements - show the MS Account Team for Customer Accounts

    Suggested by Accepted  1 Comments

    It would be ideal if we could see the Microsoft Account Team assigned to our customers, especially the MWA for S2500 Customers. 
     
  • 13

    Ideas for evolving CPOR registration

    Suggested by Needs Votes  3 Comments

    More and more, we are finding that customers don't want to register or associate a different partner for a CPOR workload. Too often it is controversial, or another partner (LAR) might have a deal to have them all associated with them, or there might have been another partner that "also" had a role driving MAU and they don't want to switch. 

    The net effect is that we aren't getting proper attribution for our role driving adoption and our monthly/quarterly/annual performance looks underwhelming. This also impacts how we are rewarded through the incentive model and can negatively impact how we are graded from a compliance standpoint. This may not be impacting all partners, but at last count we've only been able to register 1/20 engagements in the last 3-4 months where technically we are driving adoption or advancing the cause! In my experience, the friction is real and causing the whole CPOR registration to not work for us. 

    I have a few suggestions to consider:
    1. Perhaps it is time to reconsider the business rule that only one partner can be associated to a workload. What if by design, rather than by exception, multiple partners could be assigned to a workload? That would remove some of the friction that customers face accepting a new request.

    2. What if there was a simpler way to confirm a partner is engaged? Currently, we need to either have a customer sign a document or we need to submit a signed SOW as POE. As a partner, we often don't feel comfortable submitting an entire SOW as it contains a lot of detail that is under NDA.

    Secondly, we worry that if we just submitted the SOW without first talking to the customer, they would be upset receiving the email notification from Microsoft as it is confusing and possibly triggers the multi-partner association issue. Instead of it being a "notification of partner association", perhaps it could be reworded to "Confirmation of Partner Engagement" and the language could say, "Congratulations, we understand you have retained the support of <partner name> and in your work together you may be driving the adoption of the following areas: <list the areas> 
    To support your work together, we will provide limited adoption data of these workloads with your partner. If you would prefer not to disclose this data, or have the partner associated in our records as providing support, please click here. Otherwise, nothing is required in response.  

    3. Another great option would be for Microsoft CSM or Modern Workplace Specialist to be allowed to "vouch" for our engagement. Perhaps the partner could request someone on the Account Team to confirm that the partner is engaged and is driving adoption/MAU. 

    4. I'd recommend that any MCAP POE count as CPOR POE for key workloads that relate to the engagement. We've had many MCAP engagements that were influential at moving a customer forward, but for various reasons we weren't able to get associated to that customer for the workloads in question. 
     
  • 1

    Viva Workloads in CPOR

    Suggested by Completed  2 Comments

    I think that FastTrack should include the Microsoft Viva Connections, Insights, Topics and Learning as workloads within CPOR association. Is there a forecast date when this update will be made?
  • 2

    1-hour timeout in FTOP

    Suggested by Rejected  2 Comments

    The new 1-hour timeout feature in FTOP is a killer.  I understand the security reason behind this change, but the timeout session is just too short; same w/ the PBI timeout session.  Is it possible to have the timeout sessions for both FTOP & PBI extended to at least 2 hours?  
  • 1

    Requiring for information on customer survey

    Suggested by Completed  3 Comments

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

    Dispute or Clarification button at workload level in Partner Center

    Suggested by Needs Votes  1 Comments

    When opening a case we are required to enter a lot of redundant data that already exists in the system, like: chose program, enter MPN ID, enter claim ID, customer tenant ID, workload etc. and also our contact details. All this information is time consuming and could be automatically populated if a specific start a dispute or clarification button would be available at that specific Workload line in Partner Center.

    Additional small remarks:
    1. when the case is generated has the name "Case 5-0000xxxxxx has been opened for your request" instead of the issue or claim id that would help easier identify the emails. It would be useful if the case name would also be generated automatically or contain the problem summary
    2. if an incentive has been payed it would be easier if it would be listed as payed or earned at workload level with the respective earned amount so that we do not need to open a case just to find out this has been calculated. It would also help track all past earnings at customer level. The orange vs blue color that appears now only indicates if milestone was reached and not that we met program terms (ie. if it was reached and we claimed at 30% or 50% I think it shows the same as if we would have claimed it at 5%)

    Thank you!
  • 1

    Log a feedback on no MCAP to EDU customer especially for Malaysia, Indonesia & Philippines

    Suggested by Completed  1 Comments

    Hi FT Program teams,

    Good days!

     I would like to bring to your attention that through our MCAP eligibility check on the MCAP portal for workshop nomination up to today on 20 Oct 2021, all our existing EDU customers from Malaysia (53), Indonesia (3) and Philippines (7) do not have entitlement to any of the 14 MCAP workshops. 
    M365 Accelerator Program (m365partneraccelerator.azurewebsites.net)

    This is a great opportunity loss not only to E5/A5 upsell possibilities for Microsoft, but also a potential revenue loss for FRP like Alfa Connections (63 x 14 x $3500).

    Seeking your assistance to look into this immediately as my teams ready to drive more MCAP in FY22.  Your help would be greatly appreciated.

    Thank you.


    Best Regards,
    Intan Nurbaizura Binti Mohd Zulhilmi | Operations cum FastTrack Assistant