In this article: MCI Workshop Eligibility | License Explorer | Feedback  

Following is an overview of the new features and data available in the latest release of FastTrack Partner Center Experience (FPX). For any issues or questions, please reach out to https://aka.ms/FPXSupport. You can also submit feedback at any time using the thumbs up/thumbs down feedback buttons in FPX.

MCI Workshop Eligibility 

In this new release, we introduce the ability to easily find eligible customers for MCI engagement alongside growth propensity data within the Opportunities tab.

Eligibility is displayed in two places – in the details of the summary card and as a column in the data grid. The column displays the number of eligible MCI engagements that map to the relevant workload and tenant in the data grid.

Eligibility is determined as follows:

• Partner eligibility: Partner is enrolled in the appropriate programs and has the qualifications/designations for the for the specific MCI workshop. 
   
• Customer (Tenant) eligibility: Meets monthly active usage (MAU) and paid available users (PAU), along with all other prerequisites as described in the https://aka.ms/incentivesguide to be eligibility for the MCI workshop.
   
• Partner and customer are in the same geographical area.

1. MCI eligibility: Summary card definitions

Eligible MCI Engagements: This metric refers to the number of partner and customer eligible workshops across all associated tenants for each Microsoft 365 SKU bucket (e.g., O365, ME3 or ME5). Clicking this field will filter the data grid below to only the tenant workload combinations that have eligible MCI workshop(s).
Note: This metric doesn’t count workshops twice that map to multiple workloads (e.g., Threat Protection maps to Entra ID P2 and Microsoft Defender for Endpoint).
 

2. MCI eligibility: Data grid

In the data grid, refer to the MCI eligibility column to view the workshops are eligible to claim for the relevant tenant and workload. If there is an eligible workshop, the field will state “Eligible” and provide number of workshops. Click to view further details.
Note: Potential Earnings column (to the right of the MCI and CPOR columns) only includes CPOR (usage based) potential earnings estimates, as usual. MCI potential earnings are available in the MCI eligibility info pane. In a future release we will add MCI potential earnings together with CPOR potential earnings in this column.

If there are no eligible workshops, the field will say “Not Eligible". This will not be a clickable field unless there are already claimed workshops for this relevant tenant workload. In that case, you can click to view further details.
 

3. MCI eligibility: Info pane column definitions

The MCI flyout page makes it easy to view all claimable workshops with direct links to the workshop summary and claims page within your MCI Microsoft Partner Center Program page. 

• Engagement Name: Name of workshop, with link to engagement summary page in Partner Center Incentives page
   
• Incentive: Indicates if eligible engagements are Modern Work (MCI) or Security (CSI) related.
  Note: In this release we only include Modern Work (MCI) eligibility with a few security related engagements (like Data Security and Threat Protection) that are part of MCI, however full Security workshop CSI eligibility will be added in a future release.
   
• Status: Shows if you have currently claimed an engagement (aka workshop).
   
• Claim: This field shows the details of the MCI workshop claim. If you haven’t claimed a workshop, this field will link to the Partner Center Incentives claims page for that specific workshop. If you have already claimed this workshop, it will show the claim ID and link to the claim details page. If a workshop has been claimed by another partner, it will not be displayed.
   
• Customer Eligibility Start Date: Defines the start date from which the engagement can be claimed.
   
• Customer Eligibility End Date: Defines the date after which the engagement cannot be claimed. Please keep note of this date before beginning the claims process.
   
• Potential MCI Earnings: The estimated payout rate of the workshop is based on published rate cards https://aka.ms/MCI. These are estimated potential earnings and are dependent upon claim approval by the MCI Program Team.
   
• Segment: The Customer Tenant segment (e.g., Enterprise, SMC, etc.).
   
• Area: Geographical area of the tenant and partner used to determine the boundaries of eligibility. Only tenants within your area and those who meet tenant eligibility criteria will have claimable workshops in the flyout pane.
   
• Subsidiary: A more specific geographical area of the tenant. 

License Explorer

Customer licensing profile data can be accessed by clicking on Tenant Name in the Opportunities tab or in the Tenants tab. This data is a record of active licenses for a tenant at the subscription level. This data is a comprehensive view of all customer SKU/licenses, including details such as quantity, status, subscription end dates, grace periods, and trial licenses. Search, export, and filter customer license information directly within FPX.

 


Columns in the customer profile licensing view: 

• SKU Name: Name of the Microsoft product associated with the offer/subscription.
   
• Status: Current state of the subscription – in grace period or active.
   
• Current State End Date: The end date of the current subscription state.
   
• Included Quantity: Number of seats in the subscription.
   
• Subscription ID: Unique identifier of the subscription.
   
• Start Date/End date: Start and end date of the subscription.

Navigating the Subscriptions tab

The following functionality is available to work is available in the Subscriptions tab:

1. Download: Export current table view and data to CSV.
2. Filter: Filters table data by SKU name. 3. Search: Search for SKUs by SKU name.

Known limitations:

• The MCI eligibility data currently excludes workshops from the CSI Program. This is on our roadmap, and we are planning to deliver the data later this summer.
   
• Data refresh of the MCI eligibility and workshop details data is generally 1 to 2 days behind due to internal data pipeline constraints.
   
• The customer details view in FPX shows only M365, Security, Copilot, and Windows SKUs, excluding Dynamics, Power Platform, Azure, and other minor or legacy SKUs. If any SKUs are missing or you wish to view additional license SKUs, please inform us or your PSM so that they can be considered for inclusion in the next release.
   
• Currently, we leverage CPOR associations to surface new opportunities, including MCI eligibility. In the roadmap for this fiscal year, we plan to expand our scope to include MCI, CSP, and other associations. Please stay tuned for further updates.

Feedback

For any issues or questions, please reach out to https://aka.ms/FPXSupport. You can also submit feedback at any time using the thumbs up/thumbs down feedback buttons in FPX. We review feedback on a weekly basis and would appreciate your input on what is effective and what can be improved.