Josh Elmore

Problem: Microsoft-provided turnkey content for security programs lacks actionable depth and requires heavy customization. Context: Feedback from Alison and team indicated that current materials do not support effective customer engagements and lack updated enablement documentation.Impact: Reduces partner efficiency and slows time-to-value in security engagements.Idea: Co-develop modular, scenario-based content with partners that includes real-world use cases and flexible templates.Business Impact: Improves partner enablement, accelerates security solution adoption, and supports strategic OKRs.

Subject:During our Rhythm of Business call with BDO on Tuesday, we explored the comparative value of the MPX data set versus Spark and Ascent. The conversation revealed a recurring blocker: partners are unclear on how MPX differs from Spark/Ascent and what unique insights it offers for execution. This confusion is slowing adoption and limiting the impact of MPX in partner planning.BDO expressed interest in using MPX more deeply but requested a walkthrough of the portal and a clearer articulation of the outcomes MPX supports. They also asked for help identifying three specific outcomes they should be driving from these meetings, indicating a need for more structured guidance on how MPX can be operationalized.This presents an opportunity to:Create a simple comparison framework between MPX, Spark, and Ascent.Highlight MPX’s unique value in surfacing partner-specific execution signals.Provide outcome templates or examples to guide partner usage.Improving clarity here could accelerate MPX adoption, reduce friction in partner meetings, and improve alignment on execution priorities.Program (Optional): MPX Partner API / Partner Execution Enablement

Subject: Critical Start sellers are hesitant to enter opportunities into MSX due to repeated instances where Microsoft sellers have undercut them with competitive offerings after referrals were submitted. This behavior has created distrust and discouraged pipeline transparency, limiting Microsoft's ability to surface actionable data and justify continued FastTrack program participation. Recommend establishing clearer referral protection protocols and seller alignment guidelines to restore partner confidence and encourage MSX usage. This also will hamper future ASPX data when MSX becomes an attribution signal. For channel heavy partners CPOR can be an additional challenge and MSX can be a great solution to the attribution challenge. Impact: Improves partner trust, increases MSX pipeline visibility, and strengthens GTM collaboration.Notes: This is a very similar challenge that BlueVoyant has voiced. However, the additional insights on MSX attribution I feel is worth calling out and being considered.