Gong announced on July 1 that its Revenue AI OS is now available in Microsoft Marketplace, with Model Context Protocol support live for Microsoft 365 Copilot workflows. The move lets enterprises buy Gong through existing Microsoft procurement paths and connect Gong context into Microsoft tools.
The announcement has two parts. First, Microsoft Marketplace availability can let customers apply Azure Consumption Commitments to Gong purchases. Second, Gong says teams can connect Microsoft 365 Copilot to Gong’s MCP Server so Copilot can access revenue AI and agents grounded in customer interactions.
For B2B RevOps teams, the real story is not another sales AI integration. When we covered ZoomInfo’s Amazon Quick Suite integration, the question was how verified GTM data behaves inside an AI workspace. Gong brings the same question to conversation intelligence: who can retrieve customer context, what can the agent change, and how does RevOps audit it?
Key takeaways:
- Gong became available in Microsoft Marketplace on July 1, 2026.
- Customers can use existing Microsoft buying paths, including Azure Consumption Commitments where eligible.
- Gong says MCP support is now live for Microsoft 365 Copilot access to Gong revenue AI and agents.
- Gong insights integrate across Copilot, Teams, Outlook, Dynamics 365, and Copilot Studio.
- The RevOps test is permissioned context: which conversations, fields, and agent actions can be used inside Microsoft workflows.
What Gong Actually Added
The Microsoft Marketplace piece removes a buying barrier. Gong’s own blog post frames the change around procurement friction: customers can buy through Microsoft relationships and align spending with Azure commitments rather than open a separate vendor path.
The technical piece is MCP. The Model Context Protocol gives AI clients a standard way to call tools and data sources. Gong says Microsoft 365 Copilot can connect to Gong’s MCP Server and return answers, summaries, and recommended next steps based on real customer data.
The Microsoft surface matters because sellers already live in Teams, Outlook, Copilot, and Dynamics 365. Gong’s claim is that customer context can move into those workflows rather than forcing users back into a separate revenue-intelligence window.
Why Marketplace Access Matters
Most coverage will treat this as a Microsoft integration. That is incomplete. Marketplace access changes the adoption path. Enterprise AI tools are often stalled less by demos than by security reviews, procurement routes, budget ownership, and cloud-commitment accounting.
If a revenue leader can buy Gong through Microsoft Marketplace, the evaluation shifts from “Can we add another AI vendor?” to “Does this fit the Microsoft environment we already fund?” That is a meaningful difference for RevOps leaders trying to get AI out of pilot mode and into daily seller workflow.
Our read: the marketplace move is the ranking wedge. The SERP is full of Gong and newswire pages saying the product is available. The B2B question is whether procurement through Microsoft accelerates adoption without weakening the governance work RevOps still needs to do.
The MCP Governance Question
Gong says its Revenue Graph is a continuously updated context layer built from customer interactions. That context is valuable because it includes call, email, meeting, account, and deal signals. It is also sensitive. The moment Copilot can query that context, RevOps needs clear rules.
Start with access. Should every seller see every call summary? Should managers see competitor mentions across their segment but not pricing exceptions outside their region? Should Copilot be allowed to update Dynamics 365 records, or only summarize the last meeting and suggest a next step?
This is the same authority problem showing up across sales and agreement workflows. Outreach’s Omni and Agent Studio put custom agents inside the revenue workflow. DocuSign Iris put agents into agreements. Gong is putting customer-conversation context into Microsoft work surfaces. Different surfaces, same control question.
What RevOps Teams Should Test First
Start read-only. Let Copilot summarize recent account activity, deal risk, customer objections, and next steps before giving any workflow permission to write back into the CRM.
Map role access before connecting users. SDRs, account executives, managers, enablement, and executives should not receive the same Gong context through Copilot. Copying broad admin access into an agent surface is the fastest way to create a trust problem.
Preserve source lineage. If a Copilot answer comes from Gong, the user should know which call, email, meeting, or deal record informed it. The Microsoft Marketplace listing says Gong captures customer interactions and turns them into insights; the audit trail needs to remain visible when those insights leave Gong.
Measure seller time and forecast quality separately. A workflow can save seller time without improving forecast accuracy. Track both. RevOps best practice still starts with data governance, and AI does not remove that order.
The useful Gong pilot is not “ask Copilot anything about revenue.” It is narrower: let Copilot answer a defined deal, account, or forecast question using Gong context, then verify whether the answer changed the next action and whether the data trail is clear.
Frequently Asked Questions
Gong announced that its Revenue AI OS is available in Microsoft Marketplace and that MCP support is live. The integration connects Gong’s revenue context to Microsoft 365 Copilot and related Microsoft workflows.
Marketplace access can simplify enterprise procurement and may let eligible customers apply Azure Consumption Commitments. For RevOps leaders, that can shorten the path from AI pilot to funded deployment inside an existing Microsoft buying motion.
MCP lets Microsoft 365 Copilot connect to Gong’s MCP Server and use Gong revenue context for summaries, answers, and recommended next steps. The business value depends on role-based access, source lineage, and limits on what the agent can change.
Start with read-only account and deal summaries, then test role access, source attribution, CRM write permissions, and audit logs. Do not allow agentic updates until RevOps can prove who requested the action, which Gong source informed it, and where the change landed.
