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

    Customer Referral Notes History Difficult to Read

    Suggested by Oscar Goco Completed  3 Comments

    Going to Partner Center > Insights > FastTrack > Referrals > customer name > Notes History, it shows the notes with no formatting:
    NOTE: replaced customer information with xxxxx characters
     
    "10/30/2023 - xxxx@microsoft.com RFA # 83643. 10/30/2023; Request approved for Microsoft Purview Data Lifecycle Management. Assigned to FTCQ FRP • EDU Licenses: No• Nonprofit Licenses: No• Non-FRP Engaged: No• FRP involved: No• GCC: No    Partner/MCS listed in RFA: false   Contacts:   • Customer contact information: xxxxx.xxxx, IT Administrator, xxxxx.xxxxx@contoso.com, 18001234567 • Requestor contact information: xxxxx, IT Administrator, xxxxx@contoso.com, 1801234567     Service Location and Language: • City: xxxxxx• State: Illinois• Country: united states• FT Supported Language: english (united states)   The following entitlement counts reflect the entitlements confirmed by the RFA eligibility engine. These entitlements may differ from FTOP due to latency or other issues but please move forward with the RFA based on the eligibility verified by the On-Demand Team.   RFA Approved Workloads:   • Purview DLM: xxxx Entitlements   RFA name: Request M365 assistance: Email retention policy setup   Additional information that may impact the project: We plan on implementing Email retention polices for the company and need help to ensure we are setting them up correctly.   RFA Form URL: "   
     
     
    An improved formatting would make this information easier to read:
    10/30/2023 -xxxxxx@microsoft.com
    RFA # . 10/30/2023; Request approved for Microsoft Purview Data Lifecycle Management. 
     
    Assigned to FTCQ FRP 
    • EDU Licenses: No
    • Nonprofit Licenses: No
    • Non-FRP Engaged: No
    • FRP involved: No
    • GCC: No    
    Partner/MCS listed in RFA: false   
     
    Contacts:   
    • Customer contact information: xxxxx, IT Administrator, xxxxxxx@contoso.com, 18001234567 
    • Requestor contact information: xxxxx, IT Administrator, xxxxxxx@contoso.com, 18001234567     
     
    Service Location and Language: 
    • City: xxxxx
    • State: Illinois
    • Country: united states
    • FT Supported Language: english (united states)   
     
    The following entitlement counts reflect the entitlements confirmed by the RFA eligibility engine. These entitlements may differ from FTOP due to latency or other issues but please move forward with the RFA based on the eligibility verified by the On-Demand Team.   
     
    RFA Approved Workloads:   
    • Purview DLM: xxxx Entitlements   
    RFA name: Request M365 assistance: Email retention policy setup   
     
    Additional information that may impact the project: We plan on implementing Email retention polices for the company and need help to ensure we are setting them up correctly.   RFA Form URL:    
  • 1

    Verbiage in Referral AU% tab incorrect

    Suggested by Oscar Goco Needs Votes  1 Comments

    When reviewing the customer referral in Partner Center > Insights > FastTrack > Referrals > customer name > AU% tab. The screen states:
    "There is currently no Active Usage Data for this tenant.
    To view the Active Usage Data, please visit the FRP Dashboard"
     
    Going to the Partner's FRP Dashboard, the customer is not even listed thus no AU data is available.
     
    I suspect this is because the partner does not have an approved CPOR association to view the Active Usage data. 
    If so, the verbiage should state that the AU% is not available until a CPOR association is established.  
     
    However, it would be best to have the AU% data available and visible to provide insight to the customer deployment status.
  • 2

    Referral process improvements

    Suggested by David Nudelman Completed  2 Comments

    The referral process is telling a customer, that we have been engaged for a long time and have CPOR for the workloads in question, that we are not endorsed for these workloads.
     
    If we have a CPOR claim, the process should stop there, the customer gets referred back to us.
     
    Also, during the request the customer asked us t be the designated partner. That should also bypass the referral workflow that is in place now. We were always told that the customer has the right to choose their partner.
     
    I believe the correct order should be:
    1. CPOR
    2. What the customer wants
    3. The referral workflow
    Also you should improve the language used in the program, it sounds very negative to partners.
     
    Customers new to FT with no valid CPOR claim should go straight to #3.
  • 1

    FPR - Steeves and Associates

    Suggested by Lily Cui Completed  3 Comments

    Endorsement model: Smaller partners are not able to obtain as many Endorsements even though they may be qualified to do the work. Steeves and Associates is an example of this where they have strong competencies and can deliver in many workloads, however they only qualify for ACM. 
     
  • 1

    Reporting on Front Line Worker Teams in Partner Center and/or FRP Dashboard

    Suggested by Garrison Rose Completed  1 Comments

    Reporting on Front Line Worker Teams in Partner Center and/or FRP Dashboard
  • 0

    Communication of change in benefit FY23/24

    Suggested by RONNIE ALTIT Completed  2 Comments

    Communication of change in benefit FY23/24

Suggest a new idea