Security | Data security and compliance: 3 API change passages
What Microsoft published
Month-dated announcementAdded the contentFiltering member to the userActivityTypes enumeration used by the compute protection scopes for a user and compute protection scopes for a tenant APIs, enabling applications to determine whether data loss prevention policies govern content filtering before evaluating content. Updated the contentActivity resource to support reporting Secure by Default policy evaluations that couldn't be completed. Enforcement planes can submit structured incomplete-inspection reasons through the existing content activity ingestion API. Added the policyConfiguration property to the policyScopeBase resource type. Enforcement planes can use the effective Secure by Default configuration returned by the protection scope APIs to determine whether to audit or block content when policy evaluation can't be completed.
3 individual passage citations
5 API documentation links
Related public evidence
- Official documentation · 20 Oct 2026Graph changes
Observed announcement history and complete recorded revisions
What changed
First observed 21 Oct 2026No field changes in the recorded history.
Cite this recorded revision to keep the same title, summary, facts and links when the page changes.
A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.