DA best practice_offload instructions.md#98
Merged
Lauragra merged 5 commits intoMicrosoftDocs:mainfrom Apr 27, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the declarative agent instruction authoring guidance to discourage “offloading” maker instructions into SharePoint (or other knowledge sources) as a workaround for the 8,000-character limit, highlighting reliability and security implications (XPIA / governance).
Changes:
- Adds an Important callout warning against storing declarative agent instructions in knowledge sources to bypass the instruction length limit.
- Explains why this pattern can lead to blocked/sanitized directives and increases the attack surface via editable content.
Comment on lines
+60
to
+61
| > [!IMPORTANT] | ||
| > Do not store or offload declarative agent instructions in SharePoint documents (or any other knowledge source) to work around the 8,000-character instruction limit. Knowledge source content is not a trusted maker instructions, and is subject to Cross-Prompt Injection Attack (XPIA) classifiers — directive-like language can be blocked, truncated, or sanitized at runtime, causing unpredictable agent behavior. This pattern also expands the attack surface: anyone with edit access to the referenced document can alter agent behavior at runtime, bypassing the manifest's authoring, versioning, and governance controls. Knowledge sources are designed to ground factual responses, not to serve as system-level instructions, and the platform makes no guarantee they will be honored as agent instructions |
There was a problem hiding this comment.
Since this change updates the article’s guidance/best practices, please update the ms.date in the YAML front matter to reflect the date of this revision (per repo guidance for content updates).
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Lauragra
approved these changes
Apr 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Basis learning from customer persistent (Sev2), we need to update this note to ensure other customer are not designing the agent instructions.