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.Four things leading partners teach their sellers to turn a Marketplace listing into co-sell growth
About the author: Reis Barrie is the Founder and CEO of Carve Partners, a growth advisory firm that helps software companies build and scale their Microsoft partnerships. Reis and his team have deep expertise in co-sell, Marketplace, Partner Center, and incentive programs helping software development companies handle both the strategy and the operational work underneath it, end to end. Carve works with some of the fastest-growing partners in the Microsoft ecosystem, and Reis is a regular voice in the broader partner community. ________________________________________________________________________________________________________________________________________________________________ Software companies are under pressure to reach more customers, accelerate sales cycles, and grow recurring revenue. Leading partners respond by creating repeatable buying experiences that help customers discover, purchase, and deploy solutions more efficiently through Microsoft Marketplace. Becoming transactable is an important milestone, but it is only the beginning. The next step is building Marketplace into the company’s go-to-market motion so sellers can connect customer needs with an efficient path to purchase. Microsoft Marketplace supports this motion by connecting customer interest, commerce, and opportunities to co-sell with Microsoft and its partner ecosystem. When sellers understand how to position Marketplace, qualify opportunities, and use available incentives, a live offer can become a foundation for repeatable growth. This post explores: Why the sales momentum is the actual work, not the listing itself The four things leading partners train their sellers to do Key indicators to evaluate and strengthen Marketplace performance across your pipeline What the partners who get there fastest do differently By the end, you should have a clearer view of where your sales motion is working and where it can be strengthened. Who this is for This advice is for you if you're already transactable and Azure IP co-sell eligible. If you're not there yet, go get that first; nothing below substitutes for it. If you're close, the fastest first transaction is usually a customer you already have moved onto Marketplace at their next renewal. The moment it lands, Microsoft sellers can see you. The opportunity Once an offer is established, the goal is to build sales momentum, improve forecasting, and give customers a buying experience aligned with how they prefer to purchase technology. Leading partners treat Marketplace as part of their go-to-market strategy, not simply as a publishing milestone. They prepare sellers to introduce Marketplace naturally in customer conversations and explain how an eligible purchase may apply toward a customer’s Azure commitment. That fluency can help customers move from interest to purchase more efficiently while creating opportunities for co-sell engagement and business growth. What leading partners train their sellers to do 1. Build Marketplace into the sales process Marketplace should be incorporated into discovery and qualification rather than treated as a separate sales motion. Two useful conversation starters are: Discovery: “Does your organization have a Microsoft Azure Consumption Commitment?” Positioning: “An eligible purchase through Microsoft Marketplace may count toward your Azure commitment, helping you maximize an investment you have already made.” Sellers do not need to manage every transaction detail. Establish a clear handoff so the seller identifies the opportunity, introduces the customer value, and connects the appropriate partnerships or operations team to support the transaction. Before publishing detailed eligibility or transaction guidance, confirm it against current Microsoft documentation. 2. Make account insights accessible to sellers Give sellers relevant Marketplace and account insights before customer conversations. Depending on the benefits and data available to your organization, useful CRM fields may include: Marketplace purchase indicators Azure commitment information Microsoft account alignment Relevant propensity or engagement signals These indicators should guide prioritization rather than serve as absolute qualification rules. Account context, customer needs, purchase readiness, and an active sales opportunity should remain part of the assessment. 3. Help sellers identify strong co-sell opportunities Train sellers to evaluate whether an opportunity has a clear customer need, an active buying motion, and a specific reason for Microsoft engagement. Useful considerations may include: Whether the customer has an Azure commitment Whether Microsoft is actively engaged with the account Whether the customer has experience purchasing through Marketplace Whether the opportunity aligns with shared customer and business outcomes These indicators can help sellers prioritize opportunities, but they should not be presented as a definitive co-sell eligibility test. When engaging a Microsoft seller, lead with customer context, demonstrated progress, and a specific request. Use partner-led visibility when no direct seller action is needed and request active engagement when there is a clear role for Microsoft. 4. Build repeatable programs around customer incentives Customer incentives can support qualified opportunities when they address a defined deployment, migration, or adoption need. They should complement the customer value proposition rather than replace it. Create a consistent program with: An owner: One person or team responsible for available funding and program guidance Clear criteria: Published guidance describing suitable use cases and approval requirements Tracked outcomes: Visibility into which opportunities received support and how that support contributed to the result Confirm current availability, eligibility, and terms before referring to specific funding or sponsorship programs. Indicators that can strengthen Marketplace performance Common opportunities for improvement include: Treating an offer as a source of demand without connecting it to a broader go-to-market motion Limiting Marketplace expertise to operations teams Requesting active co-sell engagement without a clear role for Microsoft Failing to incorporate available account insights into seller preparation Applying incentives before an opportunity is qualified Allowing outdated opportunities to remain in the pipeline Waiting for inbound interest rather than building momentum through existing customer relationships What leading partners do differently Fluency, account insights, qualification, and incentives work best as a connected system. Seller fluency makes account insights actionable. Better insights support stronger qualification. Strong qualification helps teams apply incentives more effectively. Leading partners tend to: Treat Marketplace as part of the sales process Give sellers useful account context before customer conversations Align co-sell requests to customer and Microsoft priorities Manage incentives through clear ownership and criteria Build early momentum through active customer relationships At Carve Partners, we help software companies makes these practices repeatable by improving seller readiness, integrating account insights into sales workflows, strengthening qualification, and establishing practical incentive programs. Join our How leading partners drive co-sell success with Marketplace session on September 10th at 8:30 AM PT. We will explore how these practices work in real scenarios and share practical considerations for strengthening your Marketplace sales motion. Resources Azure Consumption Commitment benefit: how Marketplace purchases count toward a customer’s commitment Co-sell requirements: what it takes to reach co-sell ready and Azure IP co-sell eligible status Marketplace Rewards: the benefits that unlock as your Marketplace business grows Private offers overview: custom pricing and terms for specific customers and partnersSecure traffic on Azure with Fortinet FortiGate in Microsoft Marketplace
In this guest blog post, Srija Reddy Allam, Cloud DevOps Architect at Fortinet, discusses the evolving requirements organizations face when extending their environments to the cloud and how FortiGate Next-Generation Firewall VM in Microsoft Marketplace delivers comprehensive security and flexible, high-performance networking.When cloud apps become a weak link: How FortiAppSec Cloud in Microsoft Marketplace bridges the gap
In this guest blog post, Srija Reddy Allam, Cloud Security/DevOps Architect, Fortinet, discusses the increase of attacks targeted at web applications and APIs and how FortiAppSec Cloud in Microsoft Marketplace provides a layer of adaptive security to address the challenge.3 key technical debt types before scaling with AI – CAST’s perspective via Microsoft Marketplace
In this guest blog post, Greg Rivera, VP of Product, CAST, details how CAST Highlight in Microsoft Marketplace identifies the three types of technical debt and prioritizes portfolio-level issues to effectively drive remediation and build a stable foundation for scaling with AI.Why MCAPS Start for Partners on July 22 matters for software development companies
Every new fiscal year begins with questions. Where is customer demand heading? Which technology investments matter most? How can software companies build solutions that stand out in an increasingly competitive Microsoft ecosystem? Software development companies, Marketplace publishers, architects, and developers across our partner community express a common theme: everyone is looking for clarity. Customers are moving quickly from AI experimentation toward operational AI adoption. New opportunities are emerging around agentic applications, modernization, and Microsoft Marketplace growth. At the same time, partners want to know where Microsoft is investing and how they can align their business for success. That is exactly why MCAPS Start for Partners on July 22 matters. This event is designed to help partners start FY27 with a clear understanding of Microsoft priorities, customer demand, and the opportunities ahead. More importantly, it is an opportunity to align early, before the year gains momentum and before critical decisions are made across solution development, go-to-market planning, and Marketplace strategy. The conversation we keep hearing from partners Over the last year, many software companies have invested heavily in AI. Teams have built proofs of concept, launched copilots, explored automation, and experimented with agents. Those efforts have created valuable learning, but customers are now asking a different set of questions. Instead of asking what AI can do, customers are asking how AI can create measurable business outcomes. They want solutions that can be governed, operationalized, and scaled across teams and business units. They want trusted platforms that protect data and intellectual property while helping them move faster. This shift represents something larger than a technology trend. It reflects what Microsoft describes as Frontier Transformation: the movement from isolated AI experimentation toward AI and agents becoming part of repeatable business operations. For software companies and Marketplace publishers, that creates a significant opportunity. The partners who can help customers operationalize AI, modernize applications, and deliver scalable outcomes will be positioned to lead customer conversations in FY27. MCPS for Partners provides an early look into how Microsoft is thinking about this transformation and where partners can create value. Why early alignment matters One lesson learned from working with software partners is that timing matters. The strongest partners rarely wait until priorities become widely understood. They start early. They align their product roadmap, Marketplace strategy, sales motions, and technical investments before demand peaks. MCAPS Start for Partners is designed to provide that early alignment. During the event, Microsoft leaders will share perspectives on FY27 priorities, innovation areas, investment focus, and growth opportunities. Partners will gain visibility into topics including AI innovation, agentic applications, Marketplace growth, co-sell opportunities, security, cloud platforms, and business applications. For developers and technical leaders, this means understanding where customers are investing and how emerging capabilities may influence future solution architectures. For Marketplace publishers, it means learning where discoverability, go-to-market alignment, and Marketplace motions can create growth opportunities. For business leaders, it means connecting Microsoft investments to practical execution plans that support long-term growth. The Marketplace opportunity is becoming more strategic Customers increasingly want streamlined procurement experiences and trusted solution sources. At the same time, partners are looking for scalable ways to expand reach and accelerate customer acquisition. That makes Marketplace more than a publishing destination. It becomes a strategic go-to-market channel. Organizations attending MCAPS Start for Partners will hear how Marketplace fits into broader partner growth strategies and how Marketplace motions can support customer demand generation and co-sell engagement. For software companies, this is an opportunity to think beyond listings and consider how Marketplace can support solution differentiation, visibility, and customer engagement throughout FY27. The most successful Marketplace publishers are not simply reacting to market changes. They are aligning their offerings to where customer demand is moving and where Microsoft is investing. Preparing for the conversations that will shape FY27 As July 22 approaches, partners can consider customer conversations happening today. Where are customers requesting guidance around AI transformation? Which application modernization projects are gaining momentum? How are security, governance, and scalability influencing solution requirements? These questions are increasingly connected. Customers are seeking partners that can help them connect AI, cloud, security, and business outcomes into a cohesive strategy. They are looking for expertise that goes beyond implementation and extends into long-term transformation. MCAPS Start for Partners was designed to help organizations think through those challenges and identify where Microsoft priorities intersect with customer demand. That alignment becomes even more valuable when technical leaders, sales teams, Marketplace owners, marketing teams, and delivery organizations participate together. When everyone hears the same guidance and leaves with shared priorities, execution becomes significantly easier. What attendees should listen for As you participate in the event, consider listening through three lenses: Pay attention to where customer demand is moving. Understanding demand signals can help guide product investments, roadmap decisions, and solution packaging. Look for insights into Microsoft investments and priorities. These insights can help partners determine where to focus skilling, innovation, and go-to-market efforts. Think about differentiation. Customers increasingly want partners who can move beyond experimentation and deliver repeatable outcomes. The organizations that combine technical excellence with operational execution will have a distinct advantage. The goal is not simply to collect information. The goal is to leave the event with clarity about what actions matter most for your organization. Turning insight into action Every fiscal year presents new opportunities, but not every partner starts with the same level of insight. MCAPS Start for Partners provides software companies, developers, architects, and Marketplace publishers with an early opportunity to understand Microsoft’s FY27 priorities, evaluate evolving customer demand, and identify where AI innovation, agentic applications, Marketplace growth, and co-sell opportunities are creating new possibilities. The partners that act early will be better positioned to build differentiated offerings, strengthen customer conversations, and execute with confidence throughout the year. Registration closes soon, and July 22 is quickly approaching. If you have not secured your place, now is the time to act. Register today, invite your cross-functional team, and ensure your organization is prepared for the Microsoft priorities, investments, and customer opportunities that will define FY27. Whether you are responsible for product strategy, solution architecture, Marketplace growth, sales execution, or customer success, MCAPS Start for Partners offers valuable insights that can help transform planning into action. 👉 Register for MCAPS Start for Partners Before July 22Microsoft Marketplace as a platform to support FinOps: Turning cloud spend into business value
FinOps conversations used to focus mostly on cost tracking and budget control. What we’re hearing now from customers is different. The question is no longer just “How do I monitor cloud spend?” It’s “How do I make every dollar count?” That shift is important. FinOps today is about connecting financial accountability to real business outcomes. It’s about understanding not just what you’re spending, but whether those investments are delivering value and how quickly you can optimize when they’re not. This is where Microsoft Marketplace starts to play a more strategic role. The evolving FinOps challenge FinOps is not just about understanding cloud costs; it’s about actively optimizing spend and ensuring every dollar delivers measurable value. At the same time, the role of FinOps teams is expanding. Organizations are managing not only infrastructure costs, but also growing SaaS portfolios, AI workloads, and increasingly complex vendor ecosystems with different pricing and billing models. That fragmentation creates operational friction across finance, procurement, and engineering teams. The rise of AI is accelerating this shift. As AI moves into mainstream use, financial accountability needs to start earlier; at the point where solutions are evaluated, purchased, and integrated into workflows. This requires a more unified approach to managing spend across environments that are only becoming more complex. In this context, Microsoft Marketplace is not a peripheral tool. It’s part of the solution providing a platform that helps organizations bring purchasing, governance, and cost optimization into a more connected, manageable model. Microsoft Marketplace as a platform to support FinOps Microsoft Marketplace is often thought of as a place to find and buy solutions. In practice, it operates as an extension of the Microsoft Cloud connecting discovery, purchasing, and management across Azure, Microsoft 365, and the broader partner ecosystem. It gives organizations flexibility in how they buy, while creating a more consistent way to manage how solutions are introduced into the environment. For FinOps teams, that combination matters. Bringing purchasing into a more centralized model improves visibility and governance. At the same time, flexible commercial options allow organizations to align procurement decisions with how they operate, whether that’s optimizing existing commitments, managing budgets, or scaling usage over time. The goal is straightforward: every dollar of technology spend should be visible, attributable, and easier to plan for. Microsoft Marketplace helps move organizations in that direction by connecting financial accountability more directly to how solutions are evaluated, purchased, and used. Enabling collaboration across teams Effective FinOps depends on tight coordination between finance, procurement, and engineering. Microsoft Marketplace helps make that coordination part of how teams already work, not an extra layer they have to manage. By aligning with existing Azure role-based access models, teams can operate within familiar governance structures while maintaining appropriate controls. A centralized, Microsoft‑vetted catalog reduces the risk of shadow IT and shadow AI, while consolidating purchases across vendors helps minimize duplication and unnecessary spend. The result is a shared operating model where teams have visibility into the same investments, follow consistent processes, and make decisions together, turning collaboration from a best practice into a built‑in capability. Driving ownership and accountability One of the biggest gaps in FinOps isn’t visibility, it’s ownership. When responsibility for usage, renewals, and lifecycle decisions is unclear, inefficiencies compound quickly. Microsoft Marketplace helps close that gap by extending familiar Azure-based tagging and SaaS management capabilities into third-party solution spend. Teams can take direct ownership of their subscriptions, with clear insight into renewal timelines, pricing terms, and lifecycle actions such as renewals or cancellations. Purchase order mapping reinforces that accountability by linking Marketplace transactions to internal budgets and cost centers, ensuring spend is attributed to the right teams instead of getting lost in aggregated billing. The result is a clearer line of sight between decisions, ownership, and financial impact. Reducing complexity through centralization Data fragmentation is one of the most persistent challenges in FinOps. With multiple vendors, invoices, and reporting tools, many organizations struggle to maintain a clear, unified view of their technology spend. Microsoft Marketplace helps address this by bringing third-party purchases into the Azure invoice and Microsoft Cost Management experience. Instead of reconciling across disconnected systems, teams can view both first-party and third-party spend in one place. The impact is practical: less time spent on reconciliation, more consistent reporting, and a scalable way to manage cloud financial operations as environments grow. Shifting the focus from cost to value Cost control still matters, but the conversation around technology investments is clearly shifting toward value. Organizations want to understand not just what they are spending, but how quickly those investments translate into impact. Microsoft Marketplace supports this shift by making it easier to evaluate solutions in the context of speed, flexibility, and alignment with business priorities, not just price. Capabilities like private offers and access to a broad catalog give teams more control over how they purchase and deploy solutions. The result is more informed, strategic decision-making, where financial oversight is directly connected to business outcomes and measurable value. Enhancing financial operations with purchase orders One of the most practical advancements highlighted in the session was the introduction of purchase order functionality for Microsoft Marketplace purchases. Traditional reconciliation of Marketplace spend often requires manual effort, particularly when aligning cloud charges with procurement systems. The purchase order capability simplifies this process by allowing organizations to define, manage, and map purchase orders directly within Azure billing. Teams can assign budgets, track utilization, and map purchases to specific vendors, products, or cost categories. Detailed charge information can be exported, and allocations can be updated within a defined post-invoicing period. This capability strengthens the alignment between financial systems and cloud consumption data, reducing operational overhead while improving accuracy and transparency. Adopting Microsoft Marketplace based on maturity Microsoft Marketplace adoption isn’t one‑size‑fits‑all; it evolves with an organization’s cloud and FinOps maturity. Teams early in their journey often start with low‑risk options like trials or pay‑as‑you‑go offers, helping them establish governance and visibility without adding complexity. As organizations mature, renewal cycles become a natural inflection point to consolidate existing contracts into Marketplace, improving visibility and reducing fragmentation across vendors. For those with established Azure consumption commitments, Microsoft Marketplace becomes a strategic lever, aligning purchases to consumption targets and helping maximize the value of existing investments. At the highest level of maturity, Microsoft Marketplace is built into long‑term planning, where procurement, FinOps, and engineering teams work together upfront to design more efficient, optimized cloud strategies. Key lessons for FinOps practitioners Several lessons stand out from how organizations are using Microsoft Marketplace in a FinOps context. First, Microsoft Marketplace works best when treated as part of your FinOps strategy, not just a purchasing layer. Early investment in visibility and attribution creates a stronger foundation for optimization over time. Second, governance tools, like curated catalogs and purchase order mapping, are most effective when used intentionally to guide how teams buy and manage solutions. These aren’t just controls; they shape behavior. Finally, aligning engineering decisions with financial accountability ensures that technology choices directly support measurable business outcomes, rather than operating in isolation. From spending to strategy Microsoft Marketplace gives organizations a practical way to rethink how technology investments are managed. As cloud, SaaS, and AI spending continue to converge, the need for a more unified approach to financial operations becomes harder to ignore. By bringing visibility, governance, and purchasing into a connected system, Microsoft Marketplace helps organizations move beyond tracking costs toward understanding value. The shift is subtle but important: from reacting to spend after the fact to making better decisions upfront at the point of evaluation and purchase. For teams looking to mature their FinOps practices or better manage Marketplace spend, the next step is to see how this works in practice. The full session offers deeper examples, customer perspectives, and actionable guidance on applying these principles in real environments. Watch and learn: Microsoft Marketplace as a FinOps platform - Microsoft Marketplace customer office hours
Open Data Infrastructure: How Fivetran in Microsoft Marketplace powers agentic AI on Azure
In this guest blog post, Natalie Waller, Lead Product Marketing Manager at Fivetran, examines why agentic AI is stalling in most enterprises — not because of the AI itself, but because today’s data infrastructure wasn’t built for autonomous agents.
