[westey (westey-m)]

Motivation & Context

Improve documentation to explain how binary content is classified.

Description & Review Guide

Improve documentation to explain how binary content is classified.

Related Issue

Fixes #

AI Assistance

• No material AI assistance was used.
• This is an AI-assisted contribution. I reviewed, understood, and verified all submitted content and accept responsibility for it.

AI assistance details:

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR links to an agreed issue with no competing open PR, or the Related Issue section documents a trivial-change or repository-automation exception.
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

🟢 Approval recommended

No active review issues were identified in the documentation updates clarifying Purview binary-content classification and DLP policy behavior.

No open issues 🎉

What changed in this PR

This documentation-only PR clarifies how the Python and .NET Purview integrations classify binary content, aligning package documentation with consumer integration guidance.

Changes:

• Explains that binary prompts use UploadText and binary responses use DownloadText, rather than file activities.
• Warns that DLP policies targeting only UploadFile or DownloadFile do not block binary content through these integrations.

File	Description
skills/​agent-framework-builder-python/​references/​integrations.md	Adds Python Purview activity and DLP policy guidance.
skills/​agent-framework-builder-dotnet/​references/​integrations.md	Adds equivalent .NET Purview guidance.
python/​packages/​purview/​README.md	Documents binary-content activity mapping for both Python middleware classes.
dotnet/​src/​Microsoft.Agents.AI.Purview/​README.md	Documents binary-content activity mapping for agent and chat middleware.

_{Review effort: Balanced}

[github-actions]

MAF Automated Review — Iteration 1

Result: No findings
Scope: full PR (1 commit(s)): 4bd1f3ddf42e
Model: gpt-5.6-sol

Overview

This documentation-only change accurately clarifies that both Purview middleware implementations retain UploadText and DownloadText activities when submitting binary content. The .NET and Python conversion paths preserve non-empty binary payloads as Purview binary content without changing the middleware-selected activity, and existing tests pin both aspects of that contract. No publishable risk remains in the authoritative diff.

Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.