Wednesday, 25 February 2026

Day in brief

Collection, residency, sharing, and user rights shape Intune's expanded privacy guidance

25 February was primarily an Intune privacy-content expansion and path reorganization. New or newly surfaced Learn pages cover what Intune collects, where Customer Data is stored and processed, what it shares with Apple, Google, Jamf, and Zebra, and how admins handle personal-data requests. An added compliance overview and removed older compliance page appear to be a documentation move, not a product certification or feature retirement. The supplied diffs identify no Intune feature launch, preview, GA transition, deadline, or tenant-behavior change; many remaining edits are link, path, wording, and formatting corrections.

Intune · General
Privacy overview defines Intune's data-processing scope and user rights
The new Privacy and personal data in Intune overview states that Intune operates as a data processor under the Microsoft Online Services Terms. It covers collection, storage, retention, processing, security, sharing, auditing, export, review, correction, and deletion; says Intune does not use service-collected personal data for profiling, advertising, or marketing; and points to Company Portal terms and conditions for displaying an organization's privacy statement before enrollment. This is newly organized guidance
Intune · General
Storage guidance sets geography at Entra provisioning and preserves existing locations
The storage and processing reference says Intune operates in North America, Europe, and Asia Pacific, with local geographies in Australia, India, and Switzerland. A tenant's geography is selected from the country or region in its Microsoft Entra directory at first provisioning and cannot be changed later; later deployments do not move existing tenants. The page also notes that preview, beta, or other prerelease services typically store Customer Data in the United States but might store it globally. Existing-tenants
Intune · General
Personal-data procedures document two-year audit retention and three handling routes
The audit, export, or delete article documents two-year retention for user and device audit logs, automatic deletion after two years, and that admins cannot delete logs; admins can request them through the support form. Export is available from the All devices node or through Export-IntuneData.ps1. For deletion, it lists deleting the user from Microsoft Entra ID, resetting the device, or user self-removal. These are documented procedures, not evidence that a new deletion control shipped.
Intune · Apple
Apple integration reference lists account prerequisites and exchanged fields
For Apple DEP, APNs, ASM, and VPP, the reference says Intune establishes a connection with Apple when the service is enabled and requires an Apple account for each service. Its tables identify exchanged values including APNs message type, topic, device UDID, OS and build version, product name, and ASM/DEP server, organization, device, and profile-status fields. It documents the data flow; the diff does not say that Apple integrations changed.
Intune · App management
Zero Trust Layer 4 now emphasizes healthy, compliant devices
The deployment guide changes the section from Conditional Access enforcement to Require healthy and compliant devices. It frames Layer 4 as requiring healthy and compliant devices before access and directs admins to work with the identity team to create Conditional Access policies in Microsoft Entra ID. This is a terminology and workflow clarification, not a new Conditional Access capability.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.

Wednesday, 25 February 2026

Collection, residency, sharing, and user rights shape Intune's expanded privacy guidance

84 updates