Jami Styx
Joined: 9/28/2019
-
CPOR Claim for Teams Meeting, Phone & Apps
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'? -
Unclaimed and Milestone Opportunity
Within Power BI - Unclaimed and Milestone Opportunity tab can you please add customers TPID? -
Customer Contact OSU-M365 to FCU
As Microsoft looks to transition to PC (FastTrack Ready) is there a way to automatically update the customer contact to be the same as the customer contact listed in the OSU-M365 claim submission? -
FCU features - Partner Contact from CPOR claim
Can I please suggest additional FCU features? In the add contact sections, is there a way to default the Country/Region to United States so we don’t have to select it every time? I understand that partners no longer have to add ourselves to the assignment to make updates, however is there a way for Microsoft to add & default the partner contact name based on who submitted the CPOR claim? And then if someone else needs to be listed we can change it? -
Less Paperwork for the MW Deployment Offer
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. -
Less paperwork for Voucher Programs
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.