MC1122154 – Scoped Knowledge in Declarative Agents (archived)

cloudscout.one Icon

check before: 2025-08-15

Product:

Copilot, Entra, Project

Platform:

Online, World tenant

Status:

Change type:

New feature, User impact, Admin impact

Links:

Details:

Summary:
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 with organizational policies.

Details:
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.

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:

Created:
2025-07-26

updated:
2025-07-26

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Limited Data Access
Without proper preparation, users may experience restricted access to necessary data, leading to delays in project completion and decision-making.
   - roles: Project Managers, Developers
   - references: https://www.microsoft.com/en-us/microsoft-365/blog/2023/08/01/introducing-microsoft-copilot-in-azure-devops/, https://www.microsoft.com/en-us/security/blog/2023/09/15/understanding-data-governance-in-the-cloud/

User Experience Degradation
If scoped knowledge is implemented without prior configuration, users may receive irrelevant or incomplete responses from agents, negatively impacting their productivity.
   - roles: End Users, Support Staff
   - references: https://www.forbes.com/sites/bernardmarr/2023/07/10/how-ai-is-transforming-the-user-experience-in-business/?sh=5c1e4c1e4b8d, https://www.gartner.com/en/information-technology/insights/ai-in-the-enterprise

Compliance Risks
Inadequate preparation for scoped knowledge may lead to unintentional exposure of sensitive data, resulting in compliance violations and potential legal issues.
   - roles: Compliance Officers, IT Security Managers
   - references: https://www.dataprotectionreport.com/2023/06/ai-and-data-protection-compliance-in-the-age-of-ai/, https://www.csoonline.com/article/3641230/the-importance-of-compliance-in-ai-implementation.html

Configutation Options**

XXXXXXX ... paid membership only

Opportunities**

XXXXXXX ... free basic plan only

Potentional Risks**

XXXXXXX ... paid membership only

Data Protection**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

Hypothetical Work Council Statement**

XXXXXXX ... paid membership only

DPIA Draft**

XXXXXXX ... paid membership only

explanation for non-techies**

Scoped knowledge support for Declarative Agents is like giving your team of assistants specific folders to work from, rather than letting them roam freely through all the filing cabinets in the office. Imagine you have a team of paralegals, and each one is assigned to work on different cases. Instead of giving them access to every document in the office, you provide them with only the files relevant to their specific cases. This ensures they focus on the right information, improving their efficiency and the quality of their work.

With this new feature, organizations can limit the access of Declarative Agents to specific data containers across various platforms like Azure DevOps, GitHub, Jira, and ServiceNow. Think of these platforms as different departments in your company, each with its own set of filing cabinets. By restricting access to certain cabinets, or in this case, data containers, the agents can provide more relevant and personalized responses. This is similar to how a lawyer might specialize in a particular area of law, ensuring they provide the most accurate and informed advice.

This change not only improves the relevance of the responses but also helps in maintaining control over data exposure. It aligns with compliance and governance policies, much like how a company might ensure that only certain employees have access to sensitive client information. Admins can configure these access levels using tools like Entra ID, similar to how HR might manage employee access to different levels of company resources.

As organizations prepare for this change, they should review their current agent configurations and consider where scoped knowledge could be beneficial. It's like reassessing which employees need access to which resources to perform their jobs effectively. By defining these boundaries, companies can enhance their data control and ensure that their agents, much like their employees, are working with the most relevant and necessary information.

** AI generated content. This information must be reviewed before use.

a free basic plan is required to see more details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.



Last updated 4 months ago ago

Leave a Reply

Share to MS Teams

Login to your account

Welcome Back, We Missed You!