Microsoft Copilot (Microsoft 365): [Copilot Extensibility] Users can create agents scoped on Custom connector containers

Why it matters: Retirement / removal — plan migration

From Microsoft's description: “<ol> <li>Makers can now scope their data in their agent created on custom connector data at a particular container.</li> <li>These containers will be defined during creation/updating of the custom connector.</li> </ol…”

<ol> <li>Makers can now scope their data in their agent created on custom connector data at a particular container.</li> <li>These containers will be defined during creation/updating of the custom connector.</li> </ol> <p>Note: This roadmap item is no longer accurate and will be removed from the roadmap. We apologize for any inconvenience.</p>

Affected: Microsoft Copilot (Microsoft 365)

Related changes

• Microsoft Copilot (Microsoft 365): [Copilot Extensibility] Users in GCC-H will be able to use custom engine agents · Extensibility
• Microsoft Copilot (Microsoft 365): [Copilot Extensibility] Users will be able to upload files stored locally or in one drive to custom engine agents · Extensibility
• Microsoft Copilot (Microsoft 365): [Copilot Extensibility] User can create agents scoped on specific item/ container using URL · Extensibility
• Microsoft Copilot (Microsoft 365): [Copilot Extensibility] Improve discovery of Champion connector prompts for Users · Extensibility
• Microsoft Copilot (Microsoft 365): [Copilot Extensibility] Users can explore third-party content in Copilot chat with deep citations and side-by-side previews · Extensibility
• Microsoft Copilot (Microsoft 365): Copilot Chat in OneNote can create, edit, and refine content · Create

Change history

View at Microsoft → Copy summary