What the cancelled item promised
The item was titled "[Copilot Extensibility] User can create agents scoped on specific item/container using URL." An archived copy of the entry is no help on this point. The copy I'm drawing on instead comes from the Microsoft 365 Message Center Archive, which preserved the earlier snapshot. It records a "Maker can create agents by providing 3p URL" description and says the maker could supply either an item URL or a container-level URL. The examples were an Azure DevOps (ADO) ticket and an ADO area path.
Roadmap metadata for the item:
- Product: Microsoft Copilot (Microsoft 365)
- Platform: Web
- Release ring: General Availability
- Cloud instance: Worldwide (Standard Multi-Tenant)
- Estimated GA: December 2025
- Status in the archive snapshot (first published October 27, 2025): In development
- Current status: Cancelled
The December 2025 date was only an estimate. Nothing in the evidence suggests the feature ever shipped.
What the cancellation does and doesn't tell us
Microsoft's notice doesn't say why the item was cancelled. It doesn't say whether a replacement exists. I won't guess. It isn't evidence of a security problem or a product defect. It also isn't evidence that Microsoft has abandoned agents grounded in third-party data.
Microsoft's roadmap page says its dates and descriptions are subject to change. It also says entries are removed when a feature reaches general availability, is cancelled, or is postponed. Because of that, an entry that quietly vanishes is ambiguous. This one explicitly says "cancelled", so there's no guesswork.
What makers can do today for the same use case
The cancelled idea was a paste-a-URL shortcut. Microsoft's documentation describes a related route that already exists, and it works through connectors rather than URLs. This is a separate, documented capability, not a successor to item 502547. Microsoft hasn't linked the two.
According to Microsoft Learn's Agent Builder documentation, you can expand an added connector and select the attribute you want to scope the knowledge to, such as project, space or folder. The same page gives an Azure DevOps example: with the Azure DevOps Work Items connector, you can scope the agent to a particular area path so it focuses on the most pertinent work items. The documented scoping attributes include area path for Azure DevOps Work Items and project for Azure DevOps Wiki.
The workflow differs from the cancelled idea in a few ways:
- An admin deploys the connector first. In the Microsoft 365 admin center, you choose Copilot > Connectors. You then provide your Azure DevOps organization name, which is the segment after dev.azure.com.
- The data is indexed. The Work Items connector indexes user stories, tasks, bugs and features into Microsoft 365. Indexed properties include AreaPath, TeamProject, and a URL for direct access to each work item.
- Makers scope inside the agent. Developers can use the connector as a knowledge source in declarative agents built with Copilot Studio, Agent Builder, or the Microsoft 365 Agents Toolkit.
The practical difference is that a maker can't just paste a ticket link and go. Someone has to stand up the connector, and scoping happens at the attribute level, such as area path. A single-ticket URL scope isn't part of what that documentation describes.
One more point from third-party commentary. An Office 365 Clinic walkthrough argues that a connector-based approach is grounded, cited, permission-aware and read-only. That is a practitioner's view of the connector route, not Microsoft's description. The point matters because the cancelled URL approach never had its permission model described, so there's nothing to compare it against.
Guidance for admins and makers
- Take it off the plan. Don't schedule work that assumes URL-pasted item or container scoping for agents.
- Check the connector route. If your content lives in Azure DevOps work items or wikis, see whether the scoping attributes above meet your needs.
- Mind the limits. Microsoft support answers note that Copilot Studio supports Azure DevOps Wikis only via the official Wiki connector, which covers classic wikis hosted in Azure DevOps itself, not OneDrive. Repos are a separate matter. A Microsoft Q&A answer says Copilot Studio doesn't natively support Azure DevOps repositories as a built-in knowledge source. That answer is nearly a year old, so verify it before you rely on it.
- Don't count on remote MCP either. A June 2026 Microsoft Q&A answer states that the Remote Azure DevOps MCP Server cannot currently be connected to agents in Copilot Studio. Since it dates from June, recheck current docs.
The bottom line
This is a small roadmap cleanup with a real planning consequence. A pasted-URL scoping feature slated for December 2025 will not arrive as described. Microsoft hasn't said why or named a replacement. The documented alternative today is the connector-based scoping route, which is more work to set up but has actual documentation behind it. Roadmap estimates are a forecast, not a contract, so build on what has shipped.