What Adobe actually announced
On November 4, 2026, Adobe said CX Enterprise Coworker is available within several AI platforms. Adobe lists them as ChatGPT (as a plugin), Claude, Databricks Genie, Gemini for business and Microsoft Copilot. Amazon Quick, IBM and Snowflake are listed as "expected soon", so they are planned and not shipping. Adobe gave no date or rollout schedule for those three.
Adobe describes the product as an end-to-end agentic system for the customer lifecycle. That runs from acquiring prospects to conversion and customer lifetime value. The listed capabilities are:
- campaign-performance and trend analysis
- audience forecasting
- journey optimization
- conflict resolution
- planning and work management
Adobe says it runs customer experience orchestration workflows "with human oversight". It says the product is built on Model Context Protocol (MCP) and Agent2Agent (A2A). These are Adobe's own claims. The release offers no performance data, and the "industry's leading" label is self-assigned.
Only the ChatGPT integration is explicitly called a plugin. Adobe doesn't say how the Copilot, Claude, Gemini or Genie integrations are built, so don't assume they are interchangeable.
Where this fits in Adobe's timeline
Adobe first unveiled CX Enterprise Coworker on April 20, 2026, at Adobe Summit. At that point it said the product "will be generally available in the coming months". It also said the product could operate across Adobe applications and AI platforms from AWS, Anthropic, Google Cloud, Microsoft, OpenAI and others. The November release is the follow-through. It names which platforms are live now and which are still to come.
The connectors, and the Microsoft Work IQ piece
Adobe also launched connectors that it describes as pre-built MCP server integrations with partner technologies. The named ones are:
- Amazon Ads
- Databricks Genie
- Demandbase
- an ads MCP server for Meta campaigns
- Microsoft Work IQ
- RainFocus
- Snowflake Cortex AI
The list ends with "and more". Adobe says marketers can connect systems they already use "without custom integration work". It also says one request can pull data and take actions across several systems.
For Windows and Microsoft 365 administrators, Work IQ is the notable entry. Microsoft Learn describes the Work IQ MCP server as exposing Microsoft 365 capabilities to AI agents through MCP. Its tools include fetch, fetch_blob, create_entity, update_entity, delete_entity, do_action and call_function. Microsoft's docs also describe tools for invoking Microsoft 365 Copilot and retrieving grounding content.
Adobe doesn't say which of those capabilities its connector uses. Everything below describes Work IQ in general and is not a verified description of Adobe's connector.
What Microsoft's documentation says about Work IQ controls
Microsoft documents several guardrails for Work IQ MCP in general:
- Identity: Work IQ MCP uses Microsoft Entra authentication and the signed-in user's Microsoft 365 permissions when its tools access Microsoft Graph resource paths.
- Writes are off by default: A separate tenant policy layer evaluates each tool request and blocks mutation operations by default. Administrators can enable supported create, update, delete and action requests through that policy.
- Admin center control: In the Microsoft 365 admin center, tenant administrators can turn Work IQ MCP policy on or off for the tenant.
- Granularity: OAuth permissions provide broad access boundaries, while policy can apply more specific controls based on the requested path and operation.
Third-party documentation matches this behavior. One vendor's setup guide says a tool call can be refused even when the token is valid, because the tenant policy sits on top of user permissions. If an Adobe workflow tries to send mail or update an item through Work IQ, a policy-denied error is a plausible result. That is an inference from Microsoft's general design and not a reported fault in Adobe's product.
Questions to answer before you enable it
The announcement is not an implementation guide. It gives no configuration steps, supported Copilot versions, licensing requirements, regional availability or pricing. It also doesn't describe the connector's authentication flow, logging or admin controls. Reasonable due-diligence questions for your Adobe and Microsoft contacts are:
- Which Copilot surfaces and licenses are supported? Adobe says "Microsoft Copilot" and nothing more specific.
- Which Work IQ tools does the Adobe connector call? Read-only access carries a very different risk from mail-sending or deletion.
- Does it use delegated user permissions or a separate app identity? Microsoft's general Work IQ model is delegated, but Adobe hasn't confirmed its flow.
- Will your tenant policy need changes? Writes are blocked by default in Work IQ, so any action beyond reading may need explicit admin approval.
- Where are actions logged, and who approves them? "Human oversight" is asserted but not specified.
- How does "without custom integration work" hold up in your environment? Adobe doesn't say whether this applies to every enterprise deployment.
The partner ecosystem
Adobe says it is working with Accenture, Capgemini, Cognizant, Deloitte Digital, EY, IBM, Infosys, PwC and TCS to build industry-specific agentic solutions. Agencies dentsu, Havas, Omnicom, Publicis, Stagwell and WPP are adding their own IP, agents and tools for joint clients. The release gives no customer case studies, deployment counts, prices or delivery dates for any of this.
Analysis
The strategic logic is easy to see. Rather than make marketers open yet another console, Adobe is meeting them inside the assistants they already use. MCP is what makes that practical, since one connector standard can reach many hosts. Microsoft's Rob Howard and Google's Rao Surapaneni are quoted in the release backing the approach. Vendor quotes in a joint press release are endorsements and not evidence of results.
The trade-off is that each new connector widens the set of systems an AI agent can touch. Marketing teams may move faster, but identity, consent and audit now matter in tools that used to be purely conversational. For IT admins, the sensible posture is the one Microsoft already builds into Work IQ. Start read-only, allow writes deliberately, and verify what a vendor's connector actually does before it sees production data.