The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Informatica adds governed enterprise data to Copilot, Foundry and Fabric (opens in a new tab)

You will learn what Informatica's Microsoft integrations now provide: Copilot access to business context, MCP-based governance for Foundry agents, and broader Fabric lineage scanning.

Why read this

You will also see the new U.S. East Coast Azure deployment option and what is generally available.

  1. Informatica governance and lineage data
  2. Headless MCP servers and scanners
  3. Microsoft Copilot, Foundry and Fabric
  4. Governed AI agents and analytics
How Informatica trusted data reaches Copilot, Foundry and Fabric agents

Informatica from Salesforce has expanded its collaboration with Microsoft, announced at Microsoft Ignite 2026. The integration brings Informatica’s enterprise data intelligence into Microsoft Copilot and Teams, giving business users access to business definitions, data quality, governance and lineage through natural-language experiences. The article presents this as a response to the gap between agents that can access data and agents that understand it and operate within access policies.

For AI developers, the integration with Microsoft Foundry extends Informatica Headless MCP servers, which reached general availability earlier, with new governance, identity and administrative capabilities. These let developers ground agents in authoritative definitions, quality indicators and lineage, apply access controls, and trace agent interactions with data management services. Informatica’s MCP services are also being expanded across Azure-based IDMC points of delivery worldwide.

For data engineers and analysts on Fabric, Informatica’s scanners now cover notebooks and data pipelines as well as data at rest. The enhanced scanners provide lineage across multistep pipeline orchestrations, support impact analysis, and are administered through a consolidated interface. The article also announces a new U.S. East Coast Azure point of delivery for customers with data residency or procurement requirements, and notes that Informatica purchases through Microsoft Marketplace can count toward a Microsoft Azure Consumption Commitment.

Availability is staggered: the Copilot integration is generally available, the Foundry MCP server integration is generally available with its expanded capabilities, the Fabric scanners are generally available for notebooks and pipelines, and the Azure U.S. East IDMC point of delivery is generally available. The piece is largely promotional, with customer and executive quotes, so the technical detail on the MCP governance features is thin.

Read the original at Salesforce News (opens in a new tab)

Also told by Salesforce Time (opens in a new tab)

Worth reading?

Recommended

Salesforce Agent Fabric adds cross-platform evals, due January 2027 (opens in a new tab)

You will learn what Salesforce's planned Agent Evals and API Evals do, how the availability timeline looks, and how they compare with evaluation tools already on the market.

Why read this

You will also see where the promised features are still only roadmap.

  1. Define what the agent should and should not do
  2. Generate a test set from requirements
  3. Grade results with an LLM judge and data checks
  4. Quarantine the agent if quality thresholds fail
Agent Evals workflow as described for the January 2027 general availability

Vernon Keenan, writing for SalesforceDevops.net, reviews Salesforce’s Agent Fabric update, which adds Agent Evals and API Evals to its agent control plane. Agent Evals is pitched as working across any platform: it generates tests before deployment, scores production agents against quality thresholds, and can trigger a kill switch. API Evals generates functional and performance tests from API specifications so breaking changes are caught early. Salesforce’s earlier Agentforce Testing Center, generally available in February 2025, covered only Agentforce agents.

The availability timeline matters. Agent Evals and API Evals target beta in November 2026 and general availability in January 2027, and the triggered kill switch also targets January 2027. What is generally available today is the defensive layer: a manual kill switch, a FinOps dashboard, Model Wallet budget limits, cost optimization policies, and federated gateway policies. Salesforce says the policies cut token usage by up to 75% in test scenarios, which Keenan treats as a best case. Cross-platform LLM and MCP server evals are still labeled “coming soon,” and Salesforce has not confirmed live-traffic scoring. Keenan argues that enterprises are buying the control plane mainly to manage sprawl, while orchestration features wait on customers’ workflows.

Keenan compares the offering with tools already on the market, including Arize Phoenix, LangSmith, Langfuse and Braintrust, which offer evals and tracing, some with online scoring. He also cites AWS AgentCore Evaluations, Google Cloud agent evaluation, IBM watsonx Orchestrate and ServiceNow AI Control Tower, which has a kill switch that revokes credentials. Developer tools instrument the agent’s own build, while Agent Fabric governs agents its customers did not build and can pause them. A key unanswered question is whether Agent Evals will show step-level traces for third-party agents, since a failing score without a trace explains little.

In his closing section, Keenan urges Salesforce to make evals the centerpiece. His recommendations include shipping a versioned test suite with each context pack, making eval libraries exportable in open formats, grading live traffic with linked traces, and bringing Testing Center customers into Agent Evals. He also asks Salesforce to publish a reproducible benchmark before the January general availability, comparing a frontier model alone, the same model with equivalent data access, and the model using the Enterprise AI Harness.

Read the original at SalesforceDevOps.net (opens in a new tab)

Worth reading?

Salesforce announces Agentic Identity and flex credit adjustments for Model Context Protocol servers (opens in a new tab)

Readers will understand how Model Context Protocol servers connect Salesforce to external systems through natural language prompts.

Why read this

They will also learn about the upcoming November changes to the flex credits model and the new Agentic Identity framework for agent permissions.

The article introduces Model Context Protocol servers as a standardized interface for linking artificial intelligence hosts to enterprise systems like Salesforce. It outlines a three-part architecture comprising a host application, a client, and a server that securely exposes tools and resources. This design aims to replace custom integrations by allowing large language models to automatically discover and execute connected capabilities.

Practical examples demonstrate how sales and support teams can retrieve pipeline data or automate cross-platform workflows using simple natural language commands. These scenarios eliminate the need to manually switch between separate applications and navigate multiple forms to complete routine tasks.

Financial and governance impacts are also addressed, noting that agent-driven calls will begin consuming standard flex credits in November. The piece explains the introduction of Agentic Identity to distinguish between standard user operations and scoped agent permissions. Testing environments including Sandboxes and Scratch Orgs remain exempt from these billing changes, allowing teams to evaluate the technology safely before production deployment.

Read the original at Nebula Consulting (opens in a new tab)

Worth reading?