Is there any roadmap to be ESI partners with Microsoft?
Enterprise Skills Initiative (ESI) is an excellent Microsoft program that helps organizations accelerate skilling through benefits such as certification exam discounts, instructor-led training, learning resources, and more. Has anyone successfully enrolled their organization in ESI? I'd appreciate any guidance, best practices, or a roadmap for getting a company onboarded.From co-sell ready to closed-won: A practical playbook for your Microsoft co-sell motion
Achieving co-sell ready status is an important milestone. It means the offer is on Microsoft Marketplace, Partner Center is set up, sales collateral and contacts are on file, and the solution is exposed to Microsoft sales teams for co-sell opportunities. None of that, on its own, brings deals into the pipeline or moves them to closed-won. The operational work between status activation and revenue includes: Getting a Microsoft seller's attention for a specific opportunity, or making it easier for a seller to bring one in Engaging the Microsoft seller as soon as a co-sell opportunity is created or received Running joint discovery and technical validation with the customer Structuring the private offer at the right point in the deal cycle Closing through Microsoft Marketplace where a customer's Microsoft Azure Consumption Commitment (MACC) is in play Two common paths into the co-sell motion Deals reach Partner Center through two common paths once the solution achieves co-sell ready status. The early operating approach is different for each. The middle and close of the deal look similar. Partner-led co-sell: The software company originates and manages the opportunity from its own pipeline, creates the co-sell opportunity in Partner Center, and makes the deal visible to Microsoft sales teams. Microsoft sellers can be invited to participate when appropriate. Inbound referrals from Microsoft: A Microsoft seller identifies a fit in one of their accounts and sends the referral to the software company through Partner Center's Inbound tab. The main differences show up early on: Stage Partner-led Inbound from Microsoft Discovery Software company has already qualified the opportunity Software company gets up to speed on Microsoft’s account context Initial priority Give the Microsoft seller a clear reason to engage Qualify the referral and respond quickly Keep momentum Bring a qualified opportunity with a specific ask Confirm fit, ownership, and next steps Keeping deals moving after co-sell ready A few operational practices help turn co-sell ready status into an active, repeatable sales motion: Activate the co-sell motion consistently: Co-sell ready creates access to the motion, but momentum comes from actively engaging sellers, keeping positioning current, and continuously creating and responding to co-sell opportunities. Keep every registered opportunity moving: Clear ownership, visible next steps, and regular follow-through help move opportunities beyond the initial seller connection. Platforms such as SaaSify can help software companies manage co-sell opportunity information, ownership, and next actions. Prepare the private offer early: Bringing marketplace offer preparation into the deal cycle earlier gives teams enough time to align pricing, approvals, terms, and customer requirements before the opportunity reaches procurement. Align ownership across the deal: Giving account executives and partner teams shared visibility into customer conversations, Partner Development Manager (PDM) engagement, and next steps helps both sides coordinate around the same opportunity and move the deal forward. Positioning co-sell opportunities with Microsoft The approach is different for the two flows. Partner-led opportunities need the software company to position a specific deal for the Microsoft seller. Inbound referrals need preparation ahead of time and disciplined handling once a referral arrives. For partner-led opportunities A few practices can make a partner-led opportunity easier for Microsoft sellers to engage with. Map the opportunity to relevant Microsoft solution areas and sales plays: Microsoft's solution areas and sales plays change. Positioning the offer against the most relevant current areas helps make the opportunity easier for the seller to understand and position. Bring warm, qualified opportunities: An opportunity handed to a Microsoft seller with a defined buying committee, a known budget, and clear technical fit invites investment. An opportunity that still needs basic discovery asks the seller to do the software company’s qualification work. Make a specific, actionable request: "Please introduce us to the account executive at [customer]" with a clear deadline is a clear request. Generic invitations to collaborate on joint pipeline typically remain unactioned. Provide collateral written for the seller, not the buyer: Seller-facing collateral should make the elevator pitch, workload alignment, Marketplace path, and relevant commercial context immediately clear. For inbound referrals from Microsoft Being effective on inbound referrals means being easy for Microsoft teams to consider in the first place and handling each referral effectively when it arrives. A complete, current business profile in Partner Center: Keep the software company’s Partner Center information complete and current including solution categorization, industry expertise, customer proof points, relevant Azure workloads and sales plays. Qualify inbound referrals quickly, before mobilizing the full team: Not every inbound referral is a fit. Some fall outside the software company’s target profile, workload, or timing. A fast qualification step, handled by a named account owner before wider team mobilization, protects response quality on the referrals that do fit and directs the team's effort where it can contribute. A transactable Marketplace presence: A transactable offer gives customers a clear procurement path through Microsoft Marketplace and can support MACC-aligned purchasing. Active relationships with PDMs and specialist teams: Being known to Microsoft's PDMs, industry teams, and technical specialists creates additional pathways for the software company to be considered when the right opportunity appears. Running the co-sell opportunity through active pipeline Once a Microsoft seller is engaged, the middle of the deal is joint sales work. The joint pieces below are the ones that most consistently move the deal forward. Joint account planning at the start: Early in active pipeline, the software company and the Microsoft seller should align on the stakeholder map, Microsoft's context on the account (existing Azure spend, MACC status, previous partner engagements), the software company’s view of the opportunity, the commercial path, and named next steps with owners and dates. Aligning at the outset helps prevent a co-sell opportunity from going quiet in its early stages. Joint technical validation: For Azure workload solutions, the software company should bring a Microsoft solution architect or specialist into the architecture conversation with the customer. Microsoft technical specialists can add Azure platform context, address architecture questions, and help the customer evaluate fit across its broader Microsoft environment. Joint customer meetings with clear role definition: In a co-sell customer meeting, the software company leads on solution, use case, and business value. The Microsoft seller leads on Azure context, commercial path, and alignment with the customer’s Microsoft environment. Roles should be agreed before the meeting. Technical and commercial workstreams in parallel: Technical objections need Microsoft's specialist teams and the software company’s engineering. Commercial objections need finance on both sides and clarity on the marketplace path. Sequencing these badly, by completing all technical work before starting commercial, is where the private offer scramble at close typically originates. Underneath the joint work, three lightweight disciplines keep the deal visible and moving: Keep the Partner Center record current. Update it after stage changes, close-date shifts, competitive events, or stakeholder changes. Share regular updates with the Microsoft seller. Keep them short and focused on what changed and what is needed next. Use the PDM deliberately for escalations. Bring them in when their role or internal network can help move the opportunity forward. Advancing and closing deals through Microsoft Marketplace For customers with an active MACC, purchases of MACC-eligible offers through Microsoft Marketplace can contribute toward fulfillment of that commitment. Azure IP co-sell eligibility is a prerequisite for MACC eligibility, and MACC eligibility is determined at the offer level. A common operational issue is being unprepared to close on Marketplace when the customer is ready to buy. Being commercially ready in time means: A Marketplace listing that is fully transactable, with billing enabled. A private offer template with pre-approved pricing tiers, term options, and standard legal language. A sales team that can generate a customer-specific private offer without escalating each one to operations or finance. Finance visibility into pending marketplace transactions ahead of quarter close. Moving the private offer conversation into the discovery phase of the deal removes the closing-week scramble and keeps the deal moving smoothly toward close. Running co-sell at scale A handful of co-sell deals can be worked well through individual attention. Once co-sell becomes a meaningful percentage of pipeline, operational consistency becomes more important as volume grows: Deal data drifts between Partner Center, the software company’s customer relationship management (CRM) system, and internal reporting. Private offer creation often remains a deal-by-deal manual workflow, increasing operational effort as co-sell volume grows. No single view exists of where each co-sell deal stands across systems, whether it started partner-led or arrived as an inbound referral. A purpose-built cloud go-to-market platform can help software companies manage the operational side of selling across cloud marketplaces. SaaSify, for instance, helps software companies manage co-sell workflows and marketplace operations across Microsoft Marketplace and other hyperscaler ecosystems. Platforms of this kind help in multiple practical ways: Supporting co-sell workflows within the CRM and helping to keep deal information aligned between Partner Center and the software company’s CRM. Automating private offer creation and management within the software company’s CRM, helping reduce the manual effort required to create and manage private offers. Providing workflow visibility across marketplace transactions, private offer approvals, and payout reconciliation. Reducing operational load on the sales and partnership teams so senior time goes to seller relationships and deal strategy. A 90-day framework to move from co-sell ready to closed-won deals Days 1–30: Audit Review the current state honestly against a short set of questions covering both flows: Are co-sell opportunities updated in Partner Center consistently across the team? What is the response time to inbound referrals from Microsoft, from receipt to named account owner to first customer conversation? Is the Partner Center business profile complete, current, and mapped to relevant Microsoft solution areas and sales plays? Is the offer fully transactable on Microsoft Marketplace, or listed but not yet transactable? Are private offer workflows documented and templated, or reinvented for each deal? The output should be a short list of specific gaps, each with a named owner. Days 31–60: Activate For partner-led opportunities: engage the Microsoft sellers who cover the accounts and industries where the solution is strongest, and standardize the activation ask so every co-sell opportunity comes with a specific next step and date. For inbound referrals: implement an internal SLA for qualification and response and refresh the Partner Center business profile against relevant Microsoft solution areas and sales plays. Identify pipeline opportunities where Microsoft Marketplace can support the co-sell and commercial motion and structure the private offers early in the deal cycle. Days 61–90: Measure Track conversion at each stage, split by partner-led versus inbound origin: co-sell ready to opportunity created or received, to active pipeline, to Marketplace transaction, to closed-won. Refine private offer workflows based on identified bottlenecks. Run a postmortem on one deal that closed cleanly and one that required several interventions. Measuring co-sell performance Five indicators provide a practical view of whether the co-sell motion is producing pipeline and converting opportunities into revenue: Inbound referral volume and value from Microsoft: Track referral volume, potential value, and progression to active pipeline and closed-won. Response time to first customer conversation: Track time from opportunity creation or receipt to the first substantive customer interaction. Co-sell opportunity-to-closed-won conversion: Measure conversion by stage and separately for partner-led and inbound opportunities. Share of enterprise deals closing through Microsoft Marketplace: Track the percentage and value of co-sell deals transacted through Marketplace when it aligns with customers’ purchasing needs. Private offer creation and approval cycle time: Track request-to-acceptance time to assess whether private offer operations are keeping pace with co-sell volume. Supporting metric: Partner Center data completeness and consistency. Bringing it together Microsoft co-sell gives software companies opportunities to expand their reach and work jointly with Microsoft sellers on relevant customer opportunities, with Microsoft Marketplace supporting the commercial path when it aligns to the customer’s purchasing needs. Making that motion work consistently comes down to practical disciplines: keeping Partner Center data current, responding promptly to inbound referrals, and preparing private offer workflows early. The value builds when those practices work together consistently across opportunities.How to deliver unified cloud firewall policy as a service with Check Point in Microsoft Marketplace
In this guest blog post, Paul Ardoin, Manager, Cloud Security Partner Marketing at Check Point Software Technologies, details how Check Point’s Cloud Firewall as a Service in Microsoft Marketplace can eliminate policy bottlenecks in multi-tenant, multi-vendor cloud environments while enabling central security teams to control firewall policy.Empowering human and virtual agents with CallMiner in Microsoft Marketplace and Dynamics 365
In this guest blog post, Scott Kendrick, SVP Strategy and Alliances, CallMiner, discusses the challenges hybrid contact centers face and how CallMiner in Microsoft Marketplace bridges the gap between human agent and AI agent to provide consistent, exceptional customer experiences at scale.
