Microsoft makes UI-driving agents generally available in Copilot Studio

What changed: Microsoft said computer-using agents in Copilot Studio are now generally available, so teams can build agents that operate websites and desktop apps through the screen when older systems do not have APIs. Microsoft also added a redesigned workflow builder, Work IQ API and command-line options, support for remote MCP servers — a standard way for agents to connect to outside tools — and generally available agent-to-agent communication.

Why it matters: This is useful for operators with messy back-office work: vendor portals, legacy desktop tools, email intake, approvals, and exception handling. Instead of waiting for a full systems integration project, a business can test whether an agent can handle the repetitive clicking while workflows keep approvals and escalation paths in place.

Try/watch: Start with a low-risk queue such as order intake or case triage, require secure credential handling, and log every agent action before expanding to financial or customer-impacting work.

GitHub adds memory and model controls for Copilot-heavy teams

What changed: GitHub Copilot Memory now has clearer deletion guidance, a repository-level off switch, a /memory command in the Copilot CLI, and clearer prompts showing whether a memory is personal or shared at the repository level. GitHub also introduced targeted model rules in public preview so enterprise owners can allow specific Copilot models for specific organizations instead of using one setting across the whole company.

Why it matters: Coding agents get more useful when they remember project conventions, but memory can also create governance headaches. These controls help engineering leaders let Copilot adapt to a codebase while keeping sensitive repositories, regulated teams, or costlier models under tighter rules.

Try/watch: Decide which repositories should allow shared memory, document what should never be stored, and use model rules to separate experimental teams from production engineering groups.

SAP sharpens its pitch around agents that understand business processes

What changed: SAP framed its next Business AI push around the “Autonomous Enterprise,” saying its Business AI Platform brings together enterprise data, processes, and governance, while Joule Assistants work with users and Joule Agents execute business workflows end to end. SAP also said it is introducing new AI-led RISE with SAP and SAP GROW offerings.

Why it matters: For SAP customers, the practical opportunity is not a generic chatbot; it is an agent that knows finance, procurement, HR, supply chain rules, approvals, and permissions. Consultants and operators should think in terms of process redesign, not just prompt design.

Try/watch: Pick one workflow that crosses departments, map the data and approvals needed, and define where the agent can act versus where a human must approve.

Salesforce packages more of Agentforce around everyday CRM work

What changed: Salesforce’s quarterly highlights positioned its platform as an “Agentic Enterprise” stack and pointed to Agentforce Communications with five prebuilt AI agents for billing resolution, service-level-objective insights, quoting, site grouping, and guided selling. Salesforce also said teams can update opportunities, research accounts, route cases, trigger workflows, and activate Agentforce agents directly through conversation.

Why it matters: If your company already lives in Salesforce, the most realistic agent wins may come from reducing CRM busywork and service handoffs rather than building a standalone AI app. Buyers should still verify the workflow in their own sandbox, because CRM data quality and permissions will decide whether the agent is helpful or risky.

Try/watch: Test one role-specific use case, measure time saved and error rates, and require clear fallback to a human when the agent is uncertain.