Apple opened its Worldwide Developers Conference 2026 this morning with a keynote that delivered the most consequential Siri overhaul in the assistant’s history, alongside platform-wide changes that will reshape how enterprises manage Apple devices and govern AI-generated data across their fleets.

The headline announcement is a rebuilt Siri powered by Google Gemini models, processed through Apple’s own Private Cloud Compute infrastructure rather than Google’s servers. Developer betas for iOS 27, iPadOS 27, macOS 27, watchOS 27, tvOS 27, and visionOS 27 are available today.

What Changed with Siri

The new Siri moves into the Dynamic Island on supported iPhones and behaves as a full conversational assistant rather than a command executor. Users swipe down from the top centre of the display to open a persistent chat interface that maintains context across a session.

The Gemini model processes more complex queries, including multi-step reasoning and cross-app tasks, while simpler commands continue to run on-device. Apple routes cloud-processed queries through Private Cloud Compute, which means they pass through Apple’s inference infrastructure rather than reaching Google’s standard cloud endpoints. Apple has published verifiable attestations of the processing environment, giving security teams a technical claim to audit rather than a contractual promise to accept.

iOS 27 also introduces configurable Siri conversation history retention, allowing users to choose between automatic deletion after 30 days, one year, or indefinite storage. Organisations with managed device policies can enforce specific retention settings through MDM profiles.

Third-Party AI as System Default

A second significant change: iOS 27 allows users to designate third-party AI services as the default for Apple Intelligence features including Writing Tools and Image Playground. Supported services will appear as system-level defaults rather than requiring manual copy-paste between apps.

For enterprises, this creates a new category of data governance concern. When a user invokes a system-level AI feature on a managed device, the query now potentially routes to a third-party AI provider chosen by the user, not necessarily one approved by IT. Organisations without explicit MDM policies covering third-party AI defaults will find that their managed fleets behave differently from June’s developer beta onward, with full public release expected in autumn.

Liquid Glass and macOS 27

iOS 27 refines the Liquid Glass visual language introduced in iOS 26, adding an intensity slider that lets users reduce transparency effects. This directly responds to accessibility feedback about high-contrast needs, and it removes a blocker that had prevented some organisations from certifying iOS 26 for deployment in accessibility-sensitive contexts.

macOS 27 brings a redesigned interface alongside the same Siri and Apple Intelligence changes. Enterprises running Mac fleets in sectors where the EU AI Act’s transparency requirements for high-risk AI systems apply will need to assess whether the new Siri capabilities fall within scope once the AI Act’s high-risk provisions reach full enforcement in August 2026.

What the EU AI Act Means for Managed Apple Devices

The timing matters. The EU AI Act’s compliance deadline for high-risk AI systems is August 2026, six weeks after iOS 27’s developer beta. Organisations in regulated sectors, including financial services, healthcare, and critical infrastructure, need to determine whether the new Siri capabilities constitute AI system deployment within the Act’s definitions and whether Private Cloud Compute’s verifiable attestation model satisfies their transparency documentation obligations.

Apple’s approach differs architecturally from most enterprise AI tools: the Private Cloud Compute model provides cryptographic verification of the processing environment, which is a stronger technical guarantee than the contractual assurances typical in cloud AI service agreements. Whether regulators and compliance teams treat that difference as substantive is not yet settled.

MDM Action Items Before Autumn

For IT and security teams managing Apple device estates, the developer beta landing today is the starting point, not something to monitor from a distance:

• Review third-party AI default policies. MDM profiles will need to address whether users can set non-approved AI services as system defaults. Apple has not yet confirmed which MDM configuration keys govern this setting, but beta documentation will clarify this within days.
• Audit Siri conversation retention settings. Decide whether your organisation’s data retention policies require a specific retention window and configure accordingly in device management profiles.
• Assess EU AI Act applicability. If your organisation operates in sectors covered by the Act’s high-risk provisions, Siri’s cloud capabilities need to be evaluated before August.
• Test existing applications against iOS 27 betas. API deprecation timelines published today will govern what needs to change before autumn. Applications that integrate with Siri via App Intents may require updates if the underlying architecture has changed.

The window between today’s developer beta and the public autumn release compresses quickly once regression testing, App Store review, and internal QA are factored in.

If you need help reviewing your organisation’s Apple MDM policies in light of today’s announcements, assessing EU AI Act applicability for managed devices, or planning application updates for iOS 27, contact Excello Digital. We work with European organisations to keep device management policies current and compliance postures defensible as Apple’s platform evolves.