The agent gains a bounded working role

Microsoft described new agent capabilities in Copilot Studio and Microsoft 365 Copilot on 21 May. An agent could use organizational records, answer questions and perform actions through connectors and workflows. SharePoint was due to let teams create an agent from a site, while Copilot Studio provided more control over instructions, knowledge and actions. Some elements were previews or announced deliveries, so status needed assessment for each capability.

In sales, an agent can assemble customer context and prepare follow-up. In service it can find knowledge or start a process. In project management it can monitor a list and create a task. These carry different risks. A response can be reviewed before use; an action may change CRM, notify a customer or create work for others.

Marketing receives an actual May update

Customer Insights - Journeys version 1.1.41881.62 made selection of a contact's correct email address generally available. A marketer could choose a work or personal address in a journey. The update also corrected some segment counts and made recurring journeys behave consistently across daylight-saving changes.

This matters for data quality and customer experience. Multiple addresses provide flexibility but require rules for purpose, consent and maintenance. Sales and service need to see which address was used, or the next interaction may rely on an incorrect channel history.

Automation needs accountability before action

Choose one low-consequence agent task, such as proposing tasks from a project meeting. Document its knowledge, permitted actions, user role and stopping point. Have the owner inspect a sample and record errors, missing sources and unwanted actions.

Then extend to one customer process. An agent can prepare sales follow-up or a service case, but an employee approves before CRM changes or customer contact. The marketing journey uses the selected address and recorded consent. Measure time to approved output, edited suggestions and tasks without owners.

The May announcements point toward more independent AI, while the Customer Insights update shows how concrete governance must be. Collaboration and productivity improve only when an agent operates within a clear process, uses authoritative records and leaves a traceable action that a named employee can explain.

Maintain an agent register with purpose, owner, data sources, actions and latest review. The project manager tracks failures as improvement tasks, while the CRM owner determines whether the cause lies in source records or instructions. When an agent proposes customer contact, the log identifies the approver and channel. The register allows one workflow to be stopped without halting all AI use and gives management a factual view of its scope.

Sources

Microsoft 365 Blog, “New agent capabilities in Microsoft Copilot unlock business value,” 21 May 2024

Microsoft Power Automate Blog, “Revolutionize the way you work with automation and AI,” 21 May 2024

Microsoft Learn, “What's new archive for Dynamics 365 Customer Insights - Journeys,” May 2024 update

Join the discussion

Which experience from your own organisation is most relevant to this story? Share what you learned.