After connecting a Microsoft Foundry agent to Copilot Studio, it may fail with a 400 error even though the connection itself looks correct. In my case, Copilot Studio returned this message: Error Message: The connector 'Azure AI Foundry Agent Service' returned an HTTP error with code 400. Inner Error: Agent imageanalyser endpoint does not support activity. Please update the agent endpoint to support this protocol. [Request ID: 2b48657361bf53a06e37ae96a2dcf789] Error Code: ConnectorRequestFailure Conversation Id: ad73179d-ccce-47b7-bd95-0054ff7c3cd7 Time (UTC): 2026-09-06T19:38:39.

Summary If you want to build agents that can call Microsoft Graph actions through the Model Context Protocol (MCP), the setup needs a few moving parts: Entra ID permissions, an OAuth client registration, and the MCP server configuration in Agents Toolkit. Get started with the Microsoft MCP Server for Enterprise provides instructions how to set it up and this post will look into using it within Agents toolkit. What we are configuring We will:

This post explains how to map a SharePoint site URL back to the corresponding Microsoft Teams team and channel using PnP PowerShell. It also retrieves the Hub Site Url information. The script reads site URLs from a CSV file, connects to each site, and determines whether the site is a teams site or a channel site. Why this is useful Validate which Teams or channels are behind your SharePoint site collection URLs.