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

  • 1

    Less Paperwork for the MW Deployment Offer

    Suggested by Jami Styx – Completed  – 1 Comments

    For the MW Deployment Offer is there a way to consolidate the paperwork?  Right now, partners must enter (copy & paste) some of the customer information 4 times (voucher #, entity name, tenant ID, email etc.)

    For example:
    1) I generate info into the initial SOW 
    2) Then I have to submit the initial SOW into the portal.  The portal requires that I enter the voucher #, customer name and tenant ID # that is already in the SOW.  Additionally, I have to populate the Program Membership, why can’t it just auto populate?  I only have one program?
    3) Then I copy and paste the same information from the SOW over to POE 
    4) Then for the 4th time I required to re-enter information (voucher #, entity name, tenant ID, email etc.) into portal coping and pasting the info again from the SOW and POE for final submissions.   

    A lot of coping and pasting of the same information over and over. 

    Is there any way this can flow into Partner Center (PC) where it can be more automated like other program such as AMM or the MCI offers.  Yes, we may have to submit the initial information, but the tool would allow us to add information such as voucher #, entity name, tenant ID, email & load SOW initially to a claim.  Then when engagements is completed, like other programs such as AMM and MCI it allows partners to send consent emails (directly from PC) as POE which would be great replacement for the final POE document.

  • 1

    Advising when FastTrack partners already associated have claimable vouchers

    Suggested by Eric Fugère – Rejected  – 3 Comments

    When a client has Fasttrack vouchers earned via renewals or other means and they're associated to partner could we have a field in FTOP or Partner indicating so? 

  • 1

    Add Statement to "Notice of FastTrack Assignment" Emails to Customers

    Suggested by Oscar Goco – Rejected  – 2 Comments

    After a partner accepts the customer referral, a "Notice of FastTrack Assignment" email is sent to customer that has the partner's name, email address and domain name.
     
    Please add a statement in the Notice of FastTrack Assignment email to include the partner's domain name to the customer's Safe Sender list or Allow list.
    This will prevent the email sent from the partner to the customer from being quarantined or delivered into the customer's Junk folder and thus the customer never sees the email.
     
    I have several customer not receive my emails and had to get my FRM involved to contact either the Microsoft account member of customer to add my email to their Allow list.
     
    With heightened email security, some customer email systems are filtering emails and mistakenly being flagged as spam or phishing.

  • 1

    Communication of change in benefit FY23/24

    Suggested by RONNIE ALTIT – Completed  – 2 Comments

    Communication of change in benefit FY23/24

  • 1

    Customer Eligibility for M365 Customer Success Offer

    Suggested by Pavan Verma – Completed  – 2 Comments

    Hi Team, 
    M365 Customer Success Offer - Customers who own Office 365 licenses (E1, E3 and E5) are matched with an eligible FastTrack Ready Partner (FRP) and are granted the right to receive a voucher with a maximum value.
     
    But how partner get to know if any of our existing customers are eligible for this offer or not, It would be great if this insight is available so that we can connect with Microsoft Team for the nominating eligible clients.
     
     

  • 1

    Praise about the FastTrack Manager

    Suggested by Rogerio Molina – Completed  – 1 Comments

    We would like to highlight the excellent work carried out by FTM Nelson Villarreal at the head of FastTrack partner management. His dedication has helped us a lot in the evolution of the team and in the conquest of new challenges.

  • 1

    Praise about the program

    Suggested by Rogerio Molina – Completed  – 1 Comments

    Talking to the Mateus Group team, we received feedback that the FastTrack program allowed the project that had been on hold for almost 2 years to finally be carried out. The use of the benefit and also the support of FunctionOne's technical team allowed the difficulties to be overcome and the main objective, which was to create collaborative communication for the entire organization, to be achieved.

  • 1

    Editing a CPOR Claims to remove a workload after approval

    Suggested by Chris Radcliffe – Completed  – 1 Comments

    It would be great if the CPOR Claim could be edited after approved or in the case of a Partner Conflict to allow the original claiming partner to remove a workload that might be in question.
     
    I've seen a few times now where multiple Teams workloads are claimed under one Association, however over time another partner has a competing claim for one of the many workloads included. 
     
    Rather than cancelling the entire original partner claim, it would be ideal if the Partner could evaluate and possibly deselect a workload if they believe in fact they are not driving adoption for it anymore. 
     
    That would save a TON of time, effort and likely cost to Microsoft if it didn't trigger a third unnecessary claim process that is trying to then re-claim the workloads that are still technically covered under the original association.  That's a waste of time and big annoyance for both the original Partner and Customers that are trying to figure out what all the claiming nonsense is all about.

  • 1

    Conflicting CPOR Claims

    Suggested by Chris Radcliffe – Completed  – 1 Comments

    These days, it seems like every week we are getting notified of another claim that is being contested as another partner has submitted a CPOR Association request for a workload we had previously secured. If I understand how it works, if the new partner shows adequate POE that is newer than the POE we provided, then we become disassociated and lose the AU growth for that customer and workload.  
     
    I'd like to suggest an alterative approach: AU Growth Sharing for 1-year to a maximum of two partners
     
    It seems crazy that two partners aren't both rewarded with AU Growth incentive and metrics if they both in fact helped the customer drive adoption.
     
    Rather than only having one Partner of Record, Microsoft should allow two partners to both share in the credit and track the AU growth accordingly for a period of at least 1-year from the time the original POE was accepted. That way, the Partner isn't negatively impacted with its Solutions Designation score if a new partner also joins into the mix to support the customer. 
     
    If two or three years has passed, its highly unlikely the partner is still engaged. But if it is within 1 year, then that original partner should still share in the benefit of the AU Growth attribution.
     
     

  • 1

    FRP Partner of the Year Awards.

    Suggested by Xavier Alegria – Completed  – 1 Comments

    Have had a few partners voice their concern on qualifying for the partner of the Year Award based on the requirements set forth. Specifically addressing the Badges, since they are not a requirement stated and/or noted in the T&Cs.
Suggest a new idea
    Please sign in to provide feedback in this idea forum.

    Search Ideas