Reminder: Use aka.ms/frphelp for support
We are excited by the positive feedback and engagement we have had through the new Partner Support tool (https://aka.ms/frphelp). Note: The frphelp@microsoft.com email address is retired as of July 9, 2021.
Moving forward, please send all questions, access requests, issues, and program bugs to the Support Teams through the Partner Support tool (https://aka.ms/frphelp) for:
- Easy ticket submission and automatic ticket number creation.
- Communication with Support team members and to track status (in one place).
- Option to attach documents in the form to share additional information.
Please review the blog.
● ● ●
July FRP Dashboard updates
Add usage data for Teams sub-workloads
As of July 1, 2021, partners are now able to view Teams Phone System, Teams Meetings, and Teams Platform workloads on the FRP Dashboard. This update allows partners to see the usage information on these tenants/workloads even if the tenants are not assigned to the FRP in FTOP.
Note: There are no plans to add Teams Meetings and Teams Platform to FTOP at this time; the FRP Dashboard is the only way to see usage for those Teams sub-workloads. There will be an update on July 14, 2021, to allow assignment of the Teams Phone System workload in FTOP.
Please review the blog.
OLM removed from Data Health
Starting July 2021, the Exchange: Outlook Mobile (OLM) workload will be removed from the Data Health Calculation.
Please review the blog.
● ● ●
Update: Fix in place for FTOP Save issue reported on July 1, 2021
A fix is in place to address the intermittent issue partners experienced when saving changes in FTOP. If this issue resurfaces, please include the following information and open a ticket:
- FTOP Username (account used to log into FTOP)
- TenantID
- Actions performed when error occurred (e.g. assigning user to tenant, updating status notes, updating forecast information, etc.)
- Screenshot of error
- Time of error
Note: Clicking the Save button a second time typically resolves this issue. This is not the expected behavior. However, this may save the input changes. If this action works, we would still like to have the issue reported.
Please refer to the Yammer post.
● ● ●
June statement update
June FRP statements were delivered to partners on Wednesday, June 30, 2021. Please download the FRP Incentive Statement Summary for clarity by workloads to review expected payments in the June statement.
If you have noticed a discrepancy between your records and the Proof of Execution (POE) statement you receive, you may submit an appeal to the FRP Payment Disputes site for review. Disputes are reviewed during the 1st - 14th day of every month.
Questions regarding your statement? Please use https://aka.ms/frphelp for assistance.
Please view the blog.
● ● ●
FastTrack Migrations is adopting a T minus 24 hours for all Content Migrations
FastTrack Migrations will adopt T minus 24 hours (T-24) for all events for all content migration types (Box, DropBox, Google Drive, and File Share). Customers will have the capability to schedule an event 24 hours from the point an FRP schedules an event.
This change does not apply to mail migrations (Exchange or Gmail).
Impact:
Change will go into effect July 15, 2021.
How it will work:
Customer schedules an event at 3 PM PT on Wednesday. The event will be run at 3 PM PT on Thursday at the earliest, or 24 hours later. No blackout dates.
If you have any questions, please respond to the Yammer announcement or email manny.acevedo@microsoft.com.
