MC1122154: Scoped Knowledge in Declarative Agents
Scoped knowledge support for Declarative Agents will roll out worldwide in mid-August 2025, allowing organizations to limit agent access to specific data containers across connectors like Azure DevOps, GitHub, Jira, and ServiceNow. This improves response relevance, data control, and compliance wi...
We’re introducing scoped knowledge support for Declarative Agents (DA) across key connectors such as Azure DevOps (ADO) Work Items, Confluence, GitHub, Jira, and ServiceNow. This enhancement allows organizations to define precise knowledge boundaries, improving agent grounding and response quality while aligning with organizational policies and permissions.
When this will happen
- General availability (Worldwide): We will be rolling out this change in mid-August 2025.
How this affects your organization
Scoped knowledge enables admins to configure Declarative Agents to access specific containers or data sources within supported connectors. This allows agents to deliver more relevant, personalized responses by limiting their knowledge base to defined areas such as:
- ADO Work Items – Area Path
- Confluence – Space
- GitHub PRs, Issues, Docs – Repository
- Jira – Project
- ServiceNow KB – Knowledge Base
- ServiceNow Catalog – Catalog
- ServiceNow Tickets – Entity Type
This update supports more targeted agent creation, reducing irrelevant results and improving user experience. It also enhances control over data exposure and aligns with enterprise governance needs.
What you can do to prepare
- Review your current Declarative Agent configurations and identify opportunities to scope knowledge sources.
- Use the
itemPathproperty to define the appropriate container level for each connector. - Refer to updated documentation for connector-specific guidance on configuring scoped knowledge.
Compliance considerations
| Introduces or modifies AI/ML capabilities that interact with customer data | Declarative Agents now support scoped knowledge, allowing more precise access to customer data within defined containers. |
| Provides end users a new way of interacting with generative AI | Users can now interact with Copilot agents that are scoped to specific repositories or containers, improving personalization and relevance. |
| Includes admin control and can be managed via Entra ID group membership | Admins can configure scoped knowledge access and manage agent permissions through Entra ID group membership. |