If you were waiting for this control, stop counting on it. If you never heard of it, the short version is that a planned piece of agent data scoping won't arrive as described.
What Microsoft had promised
The original description was short. Microsoft said makers would be able to scope their data in their agent created on custom connector data at a particular container. These containers will be defined during creation/updating of the custom connector.
The item had been on the roadmap for about a year. The M365 Admin roadmap tracker lists it with a General Availability release phase, a December CY2025 release date, Web platform, Worldwide (Standard Multi-Tenant) cloud instance, and a created date of 2025-11-04. Planet Technologies included it in its Microsoft 365 Roadmap Updates for November 13, 2025, tagged December CY2025.
So a feature labelled for December 2025 general availability has now been formally cancelled, almost a year after that date. The old December 2025 estimate doesn't mean the feature ever shipped. Microsoft's roadmap page says its dates are estimates, all information is subject to change, and entries are removed once a feature becomes generally available, is cancelled or is postponed.
The sibling item
The cancelled item wasn't the only container-scoping entry from that period. M365 Admin also tracked roadmap ID 502547, "User can create agents scoped on specific item/container using URL." That item said a maker can create agents by providing 3p URL, and that a maker can provide either an item URL or a container level, for e.g. ADO ticket/ADO area path. It also had a December CY2025 target and was created 2025-10-27.
That Azure DevOps example gives a hint of what "container" meant for third-party data: a level of grouping above a single item. Two cautions apply, though:
- The cancelled entry, 502546, never defined "container." It didn't say how containers would map to the source system or whether scoping would enforce permissions or just narrow retrieval.
- Nothing available here confirms the current status of 502547. Don't read 502546's cancellation as a verdict on 502547, and don't treat 502547 as a replacement.
What the cancellation doesn't mean
Roadmap cancellations tend to get over-read, so here are the limits:
- Custom connectors aren't going away. Microsoft's Learn documentation, updated in October 2026, still describes custom federated connectors. These are built on a Model Context Protocol (MCP) server and created in the Microsoft 365 admin center under Copilot > Connectors.
- Microsoft gave no reason for the cancellation. It named no replacement and listed no migration steps.
- "Custom connector" means different things. Microsoft's "Ways to extend Microsoft 365 Copilot" overview separates Microsoft 365 Copilot connectors from the connectors used by Copilot Studio and Power Platform. It warns against assuming the same connector configuration works in both. Microsoft 365 Copilot connectors come in two kinds: synced connectors index content in Microsoft Graph, and federated connectors fetch it at query time. Copilot Studio's own documentation lists custom connectors, which you use to connect to any publicly available API for services not covered by existing connectors. That's a different path from the roadmap item.
Summary: One planned scoping control is gone. The wider connector and agent platform is still in place.
What admins can still control today
Below are the controls Microsoft documents for custom federated connectors right now. They don't replace container-level scoping. They decide who can use a connector, not which slice of the connector's data an agent can see.
According to Microsoft Learn's "Set up custom federated connectors" page:
- Tenant-wide gate: The "Allow agents and plugins built by your organization" setting under Agents > Settings > Agent and plugin access governs custom connectors.
- Population cap: Agents > Settings > User access sets the largest group of people who can use connectors.
- Staged rollout: For each connector, you can stage it to chosen users or groups before you pick "Deploy to all users."
- Lifecycle: Enable, disable, block (under Agents > Tools) or delete. Disabling keeps the configuration. Deleting can't be undone.
Microsoft says every one of these controls has to allow a user. If any of them is restrictive, the user can't use the connector. Changes can take up to 10 minutes to reach all Microsoft 365 experiences, and users may need to refresh Copilot or start a new conversation.
Microsoft Support adds a user-side rule: people only see connector content if an admin has enabled the connector, they can already access the content in the source system, and they have a Copilot license.
How to verify access without the cancelled feature
If you hoped container scoping would narrow what an agent can reach, you can at least check access at the connector level. Microsoft's own steps are:
- Confirm the connector's state in Your connections, Agents > Tools, Agent and plugin access, and User access.
- Sign in as a test user who isn't an admin.
- Open Copilot Chat > Settings > Sources and check whether the connector appears.
- Prompt Copilot and confirm it doesn't use a connector that should be off for that user.
That tests who can reach a connector. It doesn't scope one agent to part of a connector's data, which is the gap the cancelled item would have filled.
Analysis: why this matters more than one roadmap line
(This section is general industry analysis, not something Microsoft has said.)
Narrow scoping is one of the main ways to keep enterprise agents under control. A help-desk agent pointed at one project's tickets is easier to predict and audit than one that can search the whole ticketing system. One integration consultancy writing about Copilot extensibility notes that declarative agents can be scoped to specific connectors. The cancelled item would have taken that a step further, from scoping by connector to scoping by container. Without it, teams that want tight agent boundaries will probably have to:
- build several narrower connectors instead of one broad one, or
- limit what the connector or its MCP server exposes in the first place.
Both are design choices you can make today. Neither is a Microsoft-documented equivalent of the cancelled feature.
The process point is just as important. This item sat on the roadmap for roughly a year with a December 2025 general-availability label before it was cancelled. Treat the roadmap as a forecast, not a promise.
Bottom line for admins
- Take roadmap item 502546 out of your plans. Don't tell makers it's available or coming.
- Check any agent designs that assumed container-level scoping on custom-connector data.
- Use the connector governance controls Microsoft currently documents, and test them with users who aren't admins.
- Keep an eye on the roadmap for any replacement, but don't assume one exists until Microsoft documents it.