![EU’s 3-Front Push on Big Tech: Cloud, AI, DMA [2026]](https://shattered.io/wp-content/uploads/2026/11/eu-three-front-push-us-tech-giants-cloud-ai-dma-developers-2026-gen.webp)
The European Commission is pushing on three fronts at once to rein in U.S. tech giants as of November 01, 2026. It is weighing a cloud gatekeeper decision that would pull Amazon Web Services and Microsoft Azure under the Digital Markets Act, it has a draft AI Office rulebook open for feedback, and it just finished a Digital Markets Act review that left the law mostly intact. Bloomberg reported on October 2 that the Commission plans to name AWS and Azure as gatekeepers as soon as November, though the decision is still a draft and could slip.
We tracked the first signals of that cloud move in our earlier report on the AWS and Azure gatekeeper tag and the 10% fine ceiling. This piece widens the frame. The cloud case is only one of three live files, and the other two shape how AI features inside the biggest platforms get policed and how much the Digital Markets Act can still change.
For software engineers the stakes are practical. A gatekeeper label on a cloud platform would bring a six-month compliance window, rules on self-preferencing, and pressure to make switching providers easier. Every team with an AWS or Azure bill has a reason to read the details.
Don't miss new tech stories on Google
Add Shattered once in the Google app and our stories show up in your news suggestions.
The Short Version: Three Fronts on One Calendar #
The dates matter more than the headlines, because several clocks run in parallel. The cloud designation decision is due in November 2026. The AI Office feedback window closes on November 9. The cloud investigation that could add interoperability and data portability duties runs to May 2027. Here is the timeline as the sources we checked lay it out.
| Date | Event | Reported by | Status on Nov. 1 |
|---|---|---|---|
| Nov. 2025 | Commission opens three market investigations into cloud, covering Azure and AWS | Tech Policy Press, European Business Magazine | Ongoing |
| Apr. 30, 2026 | First Digital Markets Act review published | Tech Policy Press | Done |
| Jun. 25, 2026 | Preliminary position that AWS and Azure should be designated | European Commission | Preliminary |
| Oct. 2, 2026 | Bloomberg says designation is planned as soon as November | Bloomberg | Draft, could slip |
| Oct. 12, 2026 | Draft AI Office implementing rules open for feedback | PPC Land | Open |
| Nov. 9, 2026 | AI Office feedback window closes | PPC Land | Upcoming |
| Nov. 2026 | Cloud designation decisions due | Tech Policy Press | Pending |
| Q4 2026 | Planned adoption of the AI Office rules | PPC Land | Planned |
| May 2027 | Cloud investigation conclusions on interoperability and portability | Tech Policy Press | Future |
One caution on language. Several outlets ran headlines saying the Commission has designated AWS and Azure. The official Commission page we checked describes only a preliminary position dated June 25, and the Commission told reporters after the Bloomberg story that no final decision had been taken. We treat the designation as pending until the Commission publishes a formal decision.
Front One: Cloud Gatekeepers for AWS and Azure #
On June 25, 2026 the Commission told Amazon and Microsoft it had reached a preliminary view that their cloud services should be designated under the Digital Markets Act. It called AWS the largest and Azure the second largest cloud computing service in the EU. Its reasoning rested on lock-in effects, high switching costs, large ecosystems and entrenched positions that have lasted for years. It also said AI tools and partnerships have become a decisive factor when companies buy cloud services.
Bloomberg’s October 2 report, relayed by outlets including Blockonomi, said Brussels could announce its final call as early as November. The Commission’s own response was cautious. It said the assessments were ongoing and no final decision had been taken. It had already shared its preliminary assessments with both companies in June.
If the designation goes through, both companies get six months to bring the designated cloud services into line with the Digital Markets Act. The Register reported that the penalty ceiling for non-compliance is 10 percent of worldwide annual turnover. The obligations reporters described include interoperability, data access, rules against favoring a provider’s own services, and limits on lock-in tactics. Exact wording will matter once the formal decision lands, and none of the reporting we reviewed spells out the technical specifics.
Both companies pushed back, in different tones. Microsoft told reporters it was in a productive dialogue with regulators, while according to The Register it also argued that ignoring the growing power of Google Cloud and Gemini would tilt the market in a harmful way. AWS said European customers already enjoy an unusually wide choice of cloud options and, per The Register, argued the findings disregard the breadth of services on offer and could deter investment. Neither company confirmed the designation was coming.
Why the Cloud Case Skips the Usual Size Test #
The most unusual detail is that AWS and Azure do not meet the Digital Markets Act’s numeric thresholds. The law normally leans on size tests for revenue, market value and user counts. Cloud infrastructure does not map neatly onto those yardsticks, because the customers are businesses and the usage is metered rather than counted in monthly active users.
So the Commission took a qualitative route through market investigations. Cloud was already a listed core platform service under the law, yet Tech Policy Press noted in its review coverage that it had zero designations, even though three U.S. providers control more than 65 percent of the EU market. Other reports on the Commission’s findings put the top two providers together at roughly 60 percent. Where figures conflict, we use the lower one and say so.
This matters beyond AWS and Azure. A qualitative designation sets a template. If the Commission can label a service a gatekeeper based on lock-in, switching costs and ecosystem pull, then other infrastructure layers could face the same logic later. That is our reading of the legal mechanics, not a statement from the Commission, and the first formal decision will show how broadly the reasoning is written.
The AI angle deserves attention too. The Commission explicitly cited AI tools and partnerships as a factor in cloud purchasing. That ties the cloud case to the model race, since a provider that bundles its own models, accelerators and managed AI services can make an exit expensive.
What the Six-Month Clock Would Mean for Engineering Teams #
Nothing changes in your infrastructure on the day of a designation. The six-month window gives AWS and Azure time to redesign contracts, tooling and documentation. The first visible effects would arrive in product terms and procurement terms, not in your pipelines. What follows is analysis based on the obligations reporters described, and the formal decision may narrow or widen them.
Interoperability and switching
Reports say the interoperability rules aim to make it easier for customers to move between cloud providers. For a platform team that could mean better export formats, documented APIs for managed services and less friction when moving data. The reports do not say whether egress charges fall inside the rules, so any assumption about cheaper data transfer is premature.
Self-preferencing
The rule against favoring a provider’s own products over third-party alternatives could touch marketplaces, default integrations and bundled AI tooling. If a cloud console steers you toward the provider’s own database or model by default, a gatekeeper would have to justify it. Third-party vendors that sell through these marketplaces stand to gain the most.
Lock-in and commitments
Multi-year spend commitments are where lock-in becomes a budget line. A designation that lands mid-contract leaves buyers asking whether new rights apply to existing deals. That question will drive many conversations between customers and account managers in the first half of 2027. Teams that already compare secrets and key management across vendors, as in our AWS Secrets Manager pricing comparison with Vault, Key Vault, OpenBao and Infisical, will find portability easier to prove.
Front Two: The AI Office Draft and the Five-Year Fining Clock #
While the cloud decision gets the headlines, a quieter text may shape enforcement for years. PPC Land reported that the Commission published a draft implementing regulation, referenced as Ares(2026)9589403, on October 12, 2026. It sets the procedural rules for Articles 75c and 75d of the AI Act. Feedback runs until November 9, adoption is planned for the fourth quarter, and the rules would take effect 20 days after publication in the Official Journal.
The draft moves control of certain AI systems to Brussels. Instead of leaving enforcement to national authorities, it gives the Commission exclusive oversight of AI systems built into designated very large platforms and search engines, and of systems built on a general-purpose model by the same company that made the model. The practical effect is a single enforcer for the biggest players.
| Draft element | What PPC Land says the text provides |
|---|---|
| Legal reference | Ares(2026)9589403, procedural rules under AI Act Articles 75c and 75d |
| Feedback window | October 12 to November 9, 2026 |
| Planned adoption | Fourth quarter of 2026 |
| Entry into force | 20 days after Official Journal publication |
| Core limitation period | Five years to impose and enforce penalties |
| Clock reset triggers | Six investigative actions, including information requests, inspections and opening or reopening proceedings |
| Absolute ceiling | Ten years, plus time suspended during court proceedings |
| File access | None before preliminary findings, redacted documents afterward, full access only for named external advisers |
| Confidentiality objections | One week to object before disclosure |
The reset mechanics are the part to watch. Each investigative step restarts the five-year period, up to a ten-year cap. For continuing violations, the clock only starts when the non-compliance ends. A company that stays out of compliance therefore cannot run out the clock, and the headline on PPC Land frames it as a restart of the fining clock for Google and Meta AI.
Who the AI Rules Reach, and Who They Do Not #
The draft names two categories. The first covers AI systems built on general-purpose models where the model developer and the system operator are the same entity. The second covers AI systems integrated into designated very large online platforms or search engines. The services PPC Land listed include Facebook, Instagram, YouTube, Google Search, the Amazon Store, LinkedIn, TikTok and Bing.
Most developers sit outside this scope. These are procedural rules for how the Commission investigates and fines the largest providers, not new duties for the average app builder. If you ship software on top of one of those platforms, the rules still matter indirectly, because an enforcement action against a platform’s built-in AI could change how that platform exposes AI features through APIs.
PPC Land also flagged weaknesses in the draft. It sets no minimum reply period for preliminary findings, whereas the parallel text for general-purpose model providers gives 21 days. It sets no page limits for written observations, where model providers face a 50-page cap. The outlet also found numbering errors, including Article 6 paragraphs numbered 6 and 7 instead of 1 and 2. Those are the kind of drafting slips the feedback window exists to catch.
Industry self-governance moves on a separate track. We covered how four AI giants backed a single opt-out token for AI training, which shows companies shaping their own rules while Brussels writes its enforcement procedures.
Front Three: A Digital Markets Act Review That Changed Little #
The third front is the law itself. Tech Policy Press covered the Commission’s first Digital Markets Act review, published April 30, 2026. The Commission concluded that the law had contributed effectively to its goals of fairer and more contestable markets. It also found the regulation fit for purpose and not in need of substantial revision.
Three decisions stand out. The list of core platform services stays unchanged. Generative AI is not being added as a designated service for now. The interoperability duty will not extend to Facebook, Instagram or other social networks. The Commission’s stated reason was that it has only two-plus years of enforcement to judge, which makes it too early to assess the impact.
On AI, the Commission chose to enforce existing duties on designated gatekeepers rather than write new ones. Tech Policy Press said it opened a specification proceeding on Google’s compliance with interoperability rules for AI services on Android. The Commission also concluded that the Digital Markets Act cannot tackle every competition issue in the AI value chain, so competition law cases will handle some of them. Reporting points to investigations into Google’s use of online content for AI Overviews and YouTube, and interim measures against Meta’s policy on WhatsApp chatbots.
For developers, the review included a sobering finding. Alternative app stores and alternative payment methods are allowed in theory, yet the review described them as hard to pursue because of technical and contractual barriers. In other words, the law opened a door and the practical hurdles remain. The same gap between rule and result could appear in cloud, which is why the exact obligations in a designation decision matter so much.
Competitive Comparison: AWS, Azure and Google Cloud #
The cloud case also reshapes the three-way race. AWS and Azure face possible gatekeeper status, and Google Cloud does not. When asked whether the decision could lead to a similar move on Google’s cloud services, the Commission indicated that Google Cloud does not appear to hold a comparably dominant position. That gives the third provider a regulatory tailwind it did not ask for.
| Provider | EU position per the Commission | Regulatory status | Company stance |
|---|---|---|---|
| AWS | Largest cloud computing service in the EU | Preliminary view: should be designated | Says findings disregard the breadth of services and could deter investment |
| Microsoft Azure | Second largest cloud computing service in the EU | Preliminary view: should be designated | Calls dialogue productive, warns that ignoring Google Cloud and Gemini tilts the market |
| Google Cloud | Not described as dominant | Not on track for designation, per the Commission | No reported objection |
Microsoft’s argument is a competitive one. It wants regulators to weigh the strength of Google Cloud and Gemini before drawing a line around two rivals. That line of defense will likely appear in any appeal, since the Commission’s own reasoning leans heavily on AI tools as a factor. If AI bundling drives gatekeeper status, critics will ask why a provider with a flagship model family sits outside the net.
The security picture adds another layer. Large managed platforms concentrate risk as well as customers, and our report on the Azure Kubernetes configuration service flaw rated CVSS 10.0 shows how a single managed-service bug can reach many tenants. Regulators raising interoperability will have to weigh it against the security argument providers make for tightly integrated stacks.
How We Got Here: From the 2022 Deal to the 2026 Cloud Case #
EU negotiators reached agreement on the Digital Markets Act in March 2022, a deal Al Jazeera described as a landmark law to curb U.S. big tech giants. In September 2023 the Commission confirmed the first group of gatekeepers, which TechCrunch summarized as six mostly U.S. tech giants subject to the law.
Cloud sat on the list of regulated service types from the start but never produced a designation. The November 2025 market investigations changed that, and the June 2026 preliminary position gave the first sign that the Commission was willing to reach past the numeric thresholds. By the April 2026 review, the Commission was already saying cloud designation decisions were due in November.
Enforcement ran in parallel. European Business Magazine reported that Google took a €2.95 billion fine in September 2025 for distorting competition in advertising technology. That case belongs to competition law rather than the Digital Markets Act, yet it shaped the political climate in which the cloud and AI files now move.
The European tools are also spreading beyond the Commission. French lawmakers backed an internet traffic levy that we covered in our report on the France traffic tax proposal at €0.055 per gigabyte. National measures like that add pressure on large platforms from a second direction.
The Washington Factor: Retaliation Threats and Trade Risk #
Every EU move against U.S. platforms now runs into transatlantic politics. European Business Magazine reported, in a January 5, 2026 piece, that the Trump administration threatened immediate and substantial retaliation after the Google adtech fine, with Section 301 of the Trade Act of 1974 as the mechanism. It said the threatened measures could hit European automobiles, luxury goods and agricultural products worth up to $200 billion. Its headline cites 25 percent tariffs, though we could not find that figure in the article body, so we do not rely on it.
The same piece listed European companies it said could be exposed, among them Spotify, DHL, Accenture, Siemens, SAP, Amadeus IT Group, Capgemini, Publicis Groupe and Mistral AI. It also stated that the AI Act becomes fully enforceable in August 2026 and that the Digital Markets Act review was due by May 3, 2026. The review landed on April 30, ahead of that date.
Tech Policy Press flagged a rumor that U.S. trade pressure may explain parts of the enforcement timing. It labeled that point unclear, and we agree. Nothing in the sources we reviewed documents a link between a specific trade threat and a specific Commission delay. The honest summary is that Brussels keeps moving while the political risk stays in the background.
Washington has its own pending debates. Our summary of Congress tech bills, including data center fines up to $1M a day shows U.S. lawmakers weighing oversight ideas of their own, even as the administration pushes back on Europe’s.
Market Impact: What Cloud Buyers and Investors Should Watch #
We found no confirmed stock reaction tied specifically to the October 2 Bloomberg report, so we offer no price figures. The market question is structural. A designation would not threaten AWS or Azure revenue directly, but it would add compliance costs, constrain bundling and open room for competitors that sell portability as a feature.
Three groups have the most to watch. Enterprise buyers in the EU gain negotiating leverage if the rules limit lock-in. Smaller cloud and software vendors gain a regulatory argument for access to the big platforms’ marketplaces and interfaces. Investors in the large providers should track whether the final text is narrow and procedural or broad enough to change product design.
The AI Office draft matters to a different set of firms. Companies embedding AI into platforms with huge user bases face one EU enforcer with a long fining window. A five-year clock that resets with each investigative step, capped at ten years, makes it harder for a company to wait out an inquiry.
Cloud customers are also watching their own spend. Regulators who limit lock-in might loosen the grip of long commitments over time. Whether that translates into lower bills is unproven, and no source we reviewed makes such a claim.
What Developers Should Do Before the Decision Lands #
You cannot act on rules that do not exist yet, but you can measure your exposure. Start with an inventory of provider-specific dependencies. The goal is a map of where your code touches proprietary services, so you know what a portability right would help with. Browse the software coverage on our software and developer tools hub for the tools we review.
grep -RIlE "boto3|aws-sdk|@azure/|azure-(storage|identity|mgmt)" \
--include=*.py --include=*.ts --include=*.js --include=*.go .
grep -RIn -E 'provider "(aws|azurerm)"' --include=*.tf .
- Map the lock-in points. List managed databases, queues, identity services and AI endpoints that have no drop-in equivalent elsewhere.
- Read your contract dates. Note when commitments renew, since a designation could change your leverage before or after those dates.
- Keep infrastructure code portable. Prefer open formats and standard protocols where the cost is small.
- Watch the November 9 feedback deadline. If your company builds on platform AI features, consider whether to comment on the AI Office draft.
- Track the formal decision text. The obligations, not the headlines, will decide what changes for you.
This is not legal advice, and regulations in other regions may also apply. The checklist helps you see your exposure whatever the Commission decides.
Five Predictions for the Next Six Months #
These are our own judgments based on the sources above. They are not reported facts.
- The formal cloud decision arrives by early 2027. Bloomberg said November was the target but flagged slippage risk. We expect the Commission to publish a formal decision within a few months of that target.
- Both companies contest the outcome. Their public statements already lay out arguments about market breadth and Google’s strength. Expect those points to appear in any legal challenge.
- The AI Office text changes before adoption. The drafting errors and gaps PPC Land identified, such as missing reply periods, make edits likely after the November 9 feedback window closes.
- Google Cloud stays outside the gatekeeper net through the May 2027 conclusions. The Commission has said it does not see comparable dominance, and we see no sign of a change.
- Trade friction continues but does not stop enforcement. Threats of retaliation have followed past decisions, and Brussels has kept going.
What We Still Do Not Know #
Several gaps remain. The Commission has not published a final cloud designation, and Bloomberg’s account rests on a draft. We have no confirmed list of the technical interoperability requirements. We do not know whether data egress charges fall within scope, whether existing contracts get new rights, or how the Commission will treat AI services bundled into cloud offerings.
On the AI side, the draft is not final. PPC Land noted that the text refers to information shared in real time or near real time through application programming interfaces without saying what data would flow that way. It also left the mechanism for reopening proceedings under Article 75b unexplained. We also could not independently verify claims of a collective fine estimate above €100 billion that appeared in secondary coverage, so we left it out.
The takeaway: the European push is real, it has dates attached, and most of the consequential detail sits in documents that have not been finalized. Developers get the most value by tracking the November decision, the November 9 feedback deadline and the May 2027 cloud conclusions, and by mapping their own dependencies in the meantime.
FAQ: EU Rules for U.S. Tech Giants #
Has the EU officially named AWS and Azure as gatekeepers?
Not yet, based on the sources we could confirm. The Commission announced a preliminary position on June 25, 2026. Bloomberg reported on October 2 that a final designation could come as soon as November, and the Commission said no final decision had been taken. Check the Commission’s Digital Markets Act page for the formal decision.
What happens after a Digital Markets Act designation?
The designated companies would have six months to comply with the law’s obligations for the designated services. Reports describe duties on interoperability, data access, self-preferencing and lock-in. Non-compliance can bring fines of up to 10 percent of worldwide annual turnover.
Why are AWS and Azure targeted if they miss the numeric thresholds?
The Commission is using a qualitative assessment. It cited their roles as gateways between businesses and customers, large user bases, lock-in effects, high switching costs, big ecosystems and AI tools that influence cloud buying decisions.
Is Google Cloud also being designated?
Not according to the Commission. When asked, it indicated that Google Cloud does not appear to hold a comparably dominant position. Microsoft has argued that regulators should weigh the power of Google Cloud and Gemini.
What is the AI Office draft and when does feedback close?
It is a draft implementing regulation with procedural rules for AI Act Articles 75c and 75d, published October 12, 2026. Feedback closes on November 9, 2026. Adoption is planned for the fourth quarter, and the rules would apply 20 days after Official Journal publication.
Does this affect individual developers or only large companies?
The obligations fall on the gatekeepers and the large platforms, not on app builders. Developers feel the effects indirectly, through changes to contracts, tooling, marketplaces and platform AI features. Teams with heavy use of AWS or Azure managed services have the most to gain from better portability.
Did the Digital Markets Act review add generative AI as a regulated service?
No. The April 30, 2026 review kept the list of core platform services unchanged and did not add generative AI for now. The Commission said it will enforce existing obligations and use competition law for some AI issues.