Two days after Apple staged the WWDC 2026 procurement story — Gemini as the new Siri default, Extensions as a system-level vendor toggle — the European footnote landed. On June 9, 2026, Apple confirmed in its newsroom post titled Due to DMA, Siri AI delayed in EU for iOS 27 and iPadOS 27 that the entire Siri AI surface — the dedicated Siri app, the expanded Visual Intelligence, the integrated Writing Tools, the Siri mode in Camera, the whole on-device chatbot story — will not ship on iPhone or iPad in the European Union when iOS 27 and iPadOS 27 launch this autumn.

macOS 27, visionOS 27, and watchOS 27 will get Siri AI in the EU on schedule. Only iPhone and iPad are blocked. Same model, same data boundary, same Private Cloud Compute architecture. Different regulatory regime. Different ship date — and right now, no ship date at all for the EU mobile fleet.

The consumer angle reads as a feature delay. For enterprise IT teams running European fleets, it’s something more structural. The procurement decision Apple handed every IT team on Monday — pick Gemini, ChatGPT, or Claude for Siri Extensions — doesn’t exist in the EU for two of the most important device classes you manage. Your German sales team’s iPhone and your French marketing team’s iPad are now on a different software baseline than the rest of your global fleet.

Quick Summary: What Changed on June 9, 2026

Detail	Info
Date	June 9, 2026 (Apple newsroom announcement)
Blocked surfaces	iOS 27 and iPadOS 27 — Siri AI and all related WWDC 2026 features
Unblocked surfaces	macOS 27, visionOS 27, watchOS 27
Users affected	~450 million EU iPhone and iPad users (per TechTimes)
Cause	DMA interoperability requirements — EU rejected every Apple proposal
Apple’s proposed fixes	Trusted System Agent intermediary + 18-month phased rollout — both rejected
EU position	Per the Commission’s response, exemption “not an option” because it would favor Apple’s assistant over competitors
Extensions framework in EU	Not shipping on iPhone or iPad — no Gemini, no ChatGPT, no Claude through Siri
Timeline to resolution	None announced

Bottom line: EU iPhone and iPad fleets diverge from the rest of the world on Apple’s AI roadmap, and the divergence has no posted end date.

---

What Apple’s Newsroom Post Actually Says

The post is short and unusually direct for an Apple statement. Three things are worth pulling out verbatim before we get into the analysis.

First, Apple positioned the delay as a regulatory outcome, not a product choice. The headline phrasing — “Due to DMA” — frames the EU regulators as the agent. Craig Federighi, Apple’s senior vice president of Software Engineering, said in the post that Apple is “deeply disappointed that our EU users won’t have Siri AI on iPhone or iPad when we share our new software releases later this year.” That’s an unusual public posture for Apple, which typically avoids this kind of direct sub-tweet of a regulator.

Second, Apple documented two specific proposals it made and the EU rejected. The first was something Apple called a Trusted System Agent — an intermediary layer that would have given third-party virtual assistants access to the same iPhone capabilities Siri AI uses, while maintaining what Apple described as additional privacy and security safeguards. The second was a phased rollout: launch Siri AI in the EU now and deploy the full interoperability framework over 18 months. Per MacRumors’ reporting on the announcement, the European Commission did not accept either.

Third, the cross-platform asymmetry is on the record. macOS 27, visionOS 27, and watchOS 27 ship Siri AI in the EU. The DMA’s interoperability mandates land hardest on iPhone and iPad because those are the gatekeeper platforms designated under the DMA. Apple’s Mac and watch platforms aren’t subject to the same interoperability obligations, and the Vision Pro install base is below DMA thresholds. The result is that the same Apple ID can log into Siri AI on a MacBook in Berlin but not on the iPhone in the same person’s pocket.

What the EU Actually Said Back

The Commission’s response, delivered the same day, was sharper than Apple’s framing. Per RTÉ’s reporting on the EU rebuttal, Thomas Regnier, the European Commission’s digital affairs spokesman, said the decision to withhold Siri AI from the EU “is Apple’s and Apple’s only, because absolutely nothing in the DMA prohibits Apple from introducing new products in the EU.” Regnier’s position, on the record: “Apple was simply unable to develop interoperability solutions that meet essential EU privacy and security standards.”

That’s a meaningful framing fight. Apple’s narrative is regulatory blockage. The EU’s narrative is engineering inability. Both are partially true, and both are doing political work for their authors.

The substantive point the Commission keeps making is that an exemption “was not an option.” Per BusinessWorld’s coverage of the EU statement, the regulators’ position is that giving Apple a carve-out from interoperability requirements would let Apple’s own assistant access iPhone features that competing virtual assistants couldn’t — which is exactly the structural dynamic the DMA was written to prevent. Approving the carve-out would have functionally repealed the DMA’s gatekeeper rules for the largest consumer AI surface launching in 2026.

The Commission’s read of the situation, in other words, is that Apple knew the rule and built a product that doesn’t comply with it. Apple’s read is that the rule is technically impossible to comply with at the privacy and security bar Apple is willing to ship behind. Both readings can be defended. Only one of them gets you Siri AI on a European iPhone.

What This Means for Your Fleet — The Concrete Picture

For an enterprise IT team running iPhones and iPads in Europe, the practical picture splits into two cases.

EU-headquartered companies with a primarily European fleet. Your fleet just lost the Siri AI surface entirely on phones and tablets. The whole WWDC 2026 Extensions framework story — the procurement decision about whether your Siri runs on Gemini, ChatGPT, or Claude — doesn’t apply to your iPhones and iPads. The on-screen awareness, the cross-app actions, the file analysis, the dedicated Siri app: none of it lands in iOS 27 on your fleet. Your AI usage policy doesn’t need a “Siri row” the way US fleets do, because the surface isn’t there to govern. The vendor risk question simplifies. The capability gap widens.

Multinational companies with mixed fleets. This is where the operational headache lives. Your US, UK, and APAC iPhones get Siri AI with the full Extensions framework. Your EU iPhones don’t. Same hardware, same iOS version, materially different feature set. The MDM rules you write for the global fleet now need region-aware logic. The user training you push for the new Siri capabilities applies to most of your employees but not all. The corporate AI usage policy needs an EU annex. The data processing agreements you renegotiate around Siri-routed queries cover the non-EU portion of your fleet but not the EU portion — because EU queries aren’t routed.

For both cases, the Mac and Vision Pro side is worth a separate beat. EU-based employees still get Siri AI on their MacBooks and on Vision Pro headsets. Same Private Cloud Compute architecture. Same Extensions choice. The cross-platform inconsistency means a single employee can have Siri AI on three of their Apple devices and not the fourth and fifth. The user experience of that gap is uncharted. The compliance experience of it — when a query types into MacBook Siri triggers a different data flow than the same query spoken to iPhone Siri — is going to need a policy answer.

The Cross-Platform Asymmetry Is the Strange Part

Apple’s decision to ship Siri AI to macOS, visionOS, and watchOS in the EU while withholding it from iOS and iPadOS is the technically interesting choice in the whole announcement.

The reason the iPhone and iPad are different is the DMA’s gatekeeper classification. iOS is explicitly designated. iPadOS is explicitly designated. macOS is not — Mac sells too small a share of the European desktop market to meet the DMA gatekeeper threshold. visionOS isn’t designated because Vision Pro hasn’t shipped enough units. watchOS isn’t designated because it isn’t a primary computing platform under DMA definitions.

The interoperability mandates that triggered the rejection apply specifically to gatekeeper platforms. So the same Siri AI capability, running through the same Private Cloud Compute envelope, hitting the same model providers, with the same on-device architecture, ships on Mac and watch but not on phone and tablet — because the regulatory ceiling on what Apple can build varies by platform.

For consumer users, that’s annoying. For enterprise IT teams, it’s a fleet management problem with no clean answer. You probably manage all of those device classes under a single MDM and a single AI usage policy. The DMA just split your policy boundary along a hardware line your security architecture wasn’t designed around.

This is the kind of inconsistency the previous Apple-DMA fights produced too — the App Store sideloading rules and Core Technology Fee saga of 2024 created similar phone-versus-mac asymmetries. The pattern is becoming the new normal for European Apple device management.

How This Changes the WWDC 2026 Procurement Picture

Two days ago, every enterprise running iPhones had a fresh procurement decision to make: which model — Gemini, ChatGPT, or Claude — should be the upstream behind Siri 2.0 through the Extensions framework, and how should MDM enforce the choice across the fleet. The decision matrix was the centerpiece of the WWDC 2026 enterprise story.

In the EU, that decision is moot for iPhone and iPad. The Extensions framework isn’t shipping there on those device classes, so the model choice doesn’t exist as a configuration. The Gemini-versus-ChatGPT-versus-Claude question becomes a Mac and Vision Pro question only — significantly lower stakes given the install base distribution most enterprises have.

What that means for the labs is asymmetric. The Gemini-as-default position Apple negotiated with Google is worth materially less in the EU because the default surface is missing on the highest-volume device classes. OpenAI’s loss of the privileged Siri slot is also less painful in the EU because no third-party model is shipping in Siri on iPhone there anyway. Anthropic’s distribution upside through Extensions evaporates in the EU iPhone segment for the same reason.

Whether the EU mobile market becomes a structural drag on Apple’s frontier-model partnership terms depends on whether and when the impasse breaks. Apple did not announce a timeline. The Commission did not propose one. None of the public reporting suggests active negotiations that would change the iOS 27 launch posture.

What to Do This Week if You Manage European iOS Fleets

If you’ve already started the WWDC 2026 procurement conversation we covered Monday, the EU disclosure means three concrete adjustments.

Split the AI usage policy by region. The “Siri row” in your vendor matrix needs a EU footnote that says the Extensions framework doesn’t ship on iPhone or iPad. The Mac and Vision Pro side of the policy still applies. The phone and tablet side simplifies — Siri is back to where it was before iOS 26.4 on those EU devices, with no system-level AI surface to govern. Document the asymmetry now, not when employees start asking why the iPhone Siri on their colleague’s US device does things their iPhone Siri doesn’t.

Revisit your MDM enrollment strategy for EU devices. The MDM controls Apple is shipping for the Extensions framework — pin to Gemini, pin to Claude, disable third-party entirely — don’t apply to your EU iPhones and iPads because the framework isn’t there. Your global MDM policy needs region-specific logic to avoid pushing settings that target a non-existent surface. Microsoft Intune and Jamf will likely ship region-aware Extensions controls by the September iOS 27 release, but the timing isn’t published.

Recheck your data processing agreements. The DPAs you started renegotiating to cover Siri-routed queries through Apple Private Cloud Compute apply to the device classes where Siri AI ships. In the EU, those DPAs only need to cover macOS and visionOS for the moment. The work isn’t wasted — those agreements still need to exist — but the urgency profile shifts. If your EU exposure was the main driver behind a Claude-over-Gemini selection, the urgency on that decision drops substantially for the iPhone/iPad slice of the fleet.

For non-EU multinational fleets, the decision picture is the WWDC 2026 picture unchanged. Pick your Siri model. Document the policy. Update your DPAs. The same checklist applies, with the EU region carved out and the rationale documented.

The Bigger Picture — Three Things This Tells Us

The Siri AI standoff is a single incident, but it points at three larger patterns in how AI products will land in Europe over the next 18 months.

The DMA is now the binding constraint on consumer AI surfaces, not the EU AI Act. Most of the European AI regulatory conversation in 2025 and early 2026 was about the AI Act’s high-risk obligations. That conversation is still live. But the DMA — written about platform competition, not about AI specifically — turned out to be the lever that actually blocked a major AI product launch in Europe. Apple’s lobbying and Brussels’ enforcement are operating in the DMA frame, not the AI Act frame. That has implications for every gatekeeper platform planning to ship integrated AI features. Google, Microsoft, and Meta should be reading this announcement very carefully.

Cross-platform feature parity in the EU is now an explicit casualty of platform regulation. The fact that Siri AI ships on Mac and not iPhone, in the same country, for the same user, with the same Apple ID, is the kind of inconsistency the industry has spent a decade smoothing over for consumer experience reasons. The DMA’s gatekeeper classification structure makes this kind of platform-by-platform divergence the default, not the exception. Expect more of it across more vendors as the AI feature wave continues.

The “two regulatory regimes” outcome for global enterprise IT is locked in for at least the iOS 27 cycle. If you’re running a multinational fleet, the Europe-versus-rest-of-world split on AI surface availability is now a documented fact. Even if Apple and the Commission reach an agreement later in the iOS 27 cycle, the launch posture is what it is. The expectations your security team set with executive stakeholders about a single global AI policy needs to be reset to the practical reality that the EU and rest-of-world AI fleets diverge structurally.

The Great American AI Act’s federal-versus-state preemption split plays differently here too. The US federal-state regulatory picture is converging toward “federal regulates development, states regulate deployment.” The EU picture is converging toward “platform competition rules constrain what AI surfaces can ship at all, separate from deployment regulation.” Multinational compliance teams now have two different conceptual frames to map their programs against. That work is heavier than the work either jurisdiction alone would impose.

Frequently Asked Questions

Is Siri AI permanently blocked in the EU, or is this a delay?

Apple’s newsroom post uses the word “delayed,” not “blocked permanently.” Neither Apple nor the European Commission posted a timeline for resolution. As of June 10, 2026, there is no announced path to bringing Siri AI to EU iPhones or iPads. The practical effect through the iOS 27 lifecycle is a block. Whether that becomes structural or is resolved during iOS 28 development is unknown.

What features specifically are blocked on EU iPhones and iPads?

Per Apple’s post and MacRumors’ coverage, the dedicated Siri app, the expanded Visual Intelligence experience, the integrated Writing Tools at the iOS level, the Siri mode in Camera, and the entire Siri 2.0 chatbot capability set are not shipping. The Extensions framework that lets users pick Gemini, ChatGPT, or Claude as the Siri upstream also is not shipping on EU iPhone and iPad.

What about EU users on macOS, visionOS, and watchOS?

Siri AI ships in the EU on those platforms because they aren’t designated DMA gatekeeper platforms. The same Apple ID can use Siri AI on a MacBook or Vision Pro in the EU and not on the iPhone in the same person’s pocket. The cross-platform inconsistency is the strange operational reality of this regulatory split.

Can enterprise IT enable Siri AI on EU iPhones through MDM?

No. The MDM controls Apple is shipping for Siri Extensions configure a framework that isn’t present on EU iPhone or iPad. There is no documented path to enable Siri AI through enterprise enrollment on the blocked devices.

Does this affect China as well?

Yes. Per the MacRumors reporting, Siri AI is also not launching in China for separate regulatory reasons. The EU and China both miss the Siri AI launch on iPhone and iPad in iOS 27, though the underlying regulatory causes are different — DMA interoperability in the EU, content and data governance in China.

How does this affect the WWDC 2026 procurement decision for non-EU fleets?

It doesn’t. The Gemini-versus-ChatGPT-versus-Claude decision for Siri Extensions in the US, UK, and APAC enterprise fleets is unchanged. The change is at the regional boundary: your EU iPhone segment is exempt from the decision because the framework isn’t shipping there.

What’s Apple’s path back to shipping Siri AI in the EU?

Unclear. Apple’s Trusted System Agent proposal and the 18-month phased rollout were both rejected. Apple has not announced new proposals. The Commission’s position is that Apple needs to build genuine interoperability — let other virtual assistants do everything Siri AI can do, with the same data access — before Siri AI is permitted to ship. That’s a substantial engineering requirement, and Apple’s public posture suggests they don’t intend to meet it. The standoff has no posted resolution path.

Should our company change its iOS 27 deployment plan for EU fleets?

The iOS 27 rollout still happens. EU iPhones and iPads will get iOS 27 and iPadOS 27, including most of the non-Siri-AI improvements. What changes is the AI feature surface those devices receive. Your deployment plan needs a region-specific annex covering the Siri AI gap, the Extensions framework absence, and the cross-platform asymmetry with Mac and Vision Pro. The deployment itself isn’t blocked.

Our Take

Apple did not lose this one because the DMA is unreasonable or because the Commission is hostile to American tech companies. Apple lost it because the product they wanted to ship in Europe — Siri AI on iPhone with the option to swap in third-party models — was incompatible with the structural requirement the DMA was written to enforce. The Commission asked Apple to build a Siri that gives third-party assistants the same iPhone capabilities Siri itself uses. Apple proposed an intermediary layer that wouldn’t fully meet that bar. The Commission said no, and Apple chose to withhold the feature rather than ship something it considered insecure or commercially disadvantageous. Both parties acted rationally on their respective interests.

The deeper read for enterprise IT teams is that AI feature availability is now a structural variable in your European fleet management. The assumption that a global iPhone fleet has a single feature set, configurable through a single MDM, governed by a single policy, is no longer operationally accurate. That was already true for some niche features after the previous Apple-DMA fights. It’s now true for the most consequential consumer AI feature of 2026. The pattern is the new baseline.

For the frontier labs, the EU iPhone segment is going to underperform the global Extensions distribution opportunity for at least the iOS 27 cycle. That matters less for Anthropic than for Google or OpenAI, because Claude’s distribution story was always going to be heavier on direct enterprise than on consumer device defaults. It matters most for Google, which paid for default placement that doesn’t ship in the EU’s largest mobile market. Whether Google’s reported $1B-a-year Gemini license terms get renegotiated as the EU exposure becomes clearer is the kind of question that gets argued out in private and shows up in next quarter’s earnings call only as a footnote.

The procurement conversation we recommended Monday is still the right conversation — just with a region-specific annex now. Update the policy. Document the EU asymmetry. Tell your stakeholders that the global fleet picture diverged on June 9 and that the divergence has no posted end date. The work that comes after is the same work it was before: pick your model, document the boundary, ship the policy. Just with the map redrawn around the gap Brussels carved out this week.

---

Last updated: June 10, 2026. Sources: Apple newsroom — Due to DMA, Siri AI delayed in EU · RTÉ on the EU Commission rebuttal · BusinessWorld on the EU “no exemption” position · MacRumors on the EU and China Siri AI gap · TechTimes on the 450M-user impact.

Related reading: Apple WWDC 2026: Gemini Takes Over Siri · iOS 27 Turns AI Tools Into a System Setting · Siri iOS 26.4 Review: Apple’s Gemini-Powered AI Overhaul · Great American AI Act: What It Means for Tool Buyers · Enterprise AI Deployment 2026