Module client 

PurviewClient: calls the Microsoft Graph processContent endpoint.

Scope

Python’s PurviewClient exposes three Graph calls (get_protection_scopes, process_content, send_content_activities), orchestrated by a separate ScopedContentProcessor that: computes applicable protection scopes first (cached, with ETag-based invalidation), only calls process_content when a scope actually applies (inline) or queues it in the background (offline execution mode), and logs a contentActivities entry in the background when no scope applies at all. This work package’s brief scopes this crate down to just processContent — “POST the processContent route Python uses … parse verdict” — so only that one endpoint is called here: no protection- scopes precheck, no response caching, no background content-activity logging. This is a deliberate, brief-directed scope cut, not an oversight; see crate::processor for where the request-building logic that is ported lives, and the crate docs for the full list of what’s out of scope.

Structs

PurviewClient

Calls the Microsoft Graph dataSecurityAndGovernance/processContent endpoint. See the module docs for how this differs in scope from Python’s PurviewClient.