Italy Microsoft 365 Probe: Opt-Out Is Not Attach

On 26 June 2026 Italy’s Competition Authority, the AGCM, opened case PS13129 against Microsoft Ireland Operations Ltd. and Microsoft S.r.l. Copilot and Designer had been added to Microsoft 365. Consumers were placed, by default, on a costlier plan unless they exercised their right of withdrawal. The watchdog says the information was fragmented, may not have been enough for an informed renewal decision, and may have been an aggressive practice. The probe is open. There is no finding.

That’s the problem.

This is not an AI-adoption story, and it is not a verdict. AGCM is not asking whether Copilot is useful. It is asking whether consumers were told clearly enough that the product had changed and the bill had gone up, and whether an auto-move that requires an opt-out restricted their freedom of choice. Your job is not to predict the Italian outcome. Your job is to know whether any of those consumer plans sit in your estate, and whether a SKU on your commercial paper can change without a buying decision.

What AGCM actually opened

The English press release is short and specific. The named parties are Microsoft Ireland Operations and Microsoft Italy. The concern is an unfair commercial practice around information given to consumers about a Microsoft 365 subscription price increase. That information “appears to have been provided in a fragmented manner, without making it sufficiently clear that the subscription service had been integrated with the ‘Copilot’ and ‘Designer’ artificial intelligence services.” Consumers “were placed, by default, on a new subscription plan at a higher price, unless they exercised their right of withdrawal.”

Then the two legal theories. “In the Authority’s view, this conduct may be contrary to consumer rules, since Microsoft appears to have failed to provide consumers with sufficient information to assess the changes made to the service offered and, as a consequence, make an informed decision as to whether or not to renew their subscription.” And: “The way in which the information was communicated may also constitute an aggressive practice, as it appears to have unduly restricted consumers’ freedom of choice.”

Rome, 26 June 2026. Preliminary. No euro delta in the notice. No Personal, Family, Classic, or Premium SKU named. None will be invented here.

The case lands weeks after the UK CMA opened a strategic market status investigation into Microsoft’s business software: bundling, licensing, interoperability, defaults. Do not collapse those files. CMA SMS is market structure. PS13129 is consumer practice. One is a designation clock. The other is an information-and-opt-out file. Microsoft has spent the past year weaving Copilot into Microsoft 365. That is context. AGCM has not decided whether consumer rules were broken.

An auto-move is a default SKU, not attach

Microsoft put Copilot and Designer into the Microsoft 365 subscription. Subscribers who did nothing were shifted onto the costlier plan. Subscribers who did not want the extra cost had to opt out.

That is an auto-move. It is not attach.

Attach is a person choosing a SKU, a quantity, and a price. An auto-move is a catalog change that lands on the people who do nothing. AGCM does not publish a euro delta for the Italian plans. Neither will this post. The mechanism is the story: inaction was treated as consent to a richer, costlier tier.

If that pattern feels familiar, the problem is not your team’s maturity. Enterprise defaulting looks different on paper and works the same way in a meeting. Copilot attach gets framed as “do you want AI.” Designer arrives inside the bundle, not as a line item anyone signed. Add-ons auto-renew on the anniversary. The vendor has a number. You are asked whether you want to keep up.

Do not let Microsoft frame this headline as “Italy is looking at consumer plans, so nothing changes on the EA.” The right question is whether a SKU in your estate can move to a richer, costlier tier without someone in procurement signing for it.

Fragmented information is the charge in Rome. It is also how most Microsoft 365 estates look from the inside. Consumer plans on one export. Commercial seats on another. Copilot as an add-on in a third view. Designer nowhere, because nobody tagged it as a license event. Legal reads the AGCM notice. SAM reads a seat count. Nobody has the same object. Traditional SAM tools collect seats and answer slowly. The gap is interpretation work.

PS13129 is consumer paper, not your EA

AGCM is reading consumer Microsoft 365: Copilot, Designer, the automatic shift, the opt-out. Your EA, CSP, or MCA is a different commercial object. Some estates run both, including in Italy: a consumer plan on a corporate card, a contractor seat that never migrated, a Microsoft Italy-billed line next to an Ireland-billed enterprise agreement, and the commercial tenant you actually negotiate.

The named parties matter. The case is against Microsoft Ireland Operations and Microsoft Italy. Consumer comms and local billing can sit on one surface. The group EA can sit on the other. If you cannot say which seats belong to which, you will brief the AGCM headline as if it were the renewal.

Picture the European CIO after legal forwards the Rome notice. Finance wants to know whether any Microsoft 365 in the group was auto-moved. Someone asks if Designer is even a SKU you pay for. If SAM needs three weeks to recast consumer versus commercial, auto-moved versus opted-out, assigned versus paid, the headline becomes the file.

Map the paper. Separate consumer SKUs from commercial SKUs. Know which seats can shift at renewal without a buying decision.

What to check on the M365 plan mix

Do this in the next thirty days, as a decision pack rather than a project.

Then say, in one page, whether the next conversation is a cleanup of consumer paper, a refusal to treat an auto-move as demand, or a commercial renewal on the SKUs you actually chose. If a non-specialist cannot walk the CIO through that pack today, you do not have an AGCM Microsoft 365 position. You have a seat export and a press cutting.

The decision layer, not another inventory

You already have admin-center exports and a seat count. The gap is not another inventory. The gap is turning that estate into a decision: which catalog each plan sits on, which seats can auto-move at renewal without a buying decision, and what should happen next. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer. Microsoft Deployment Manager is the pack that splits consumer versus commercial catalogs. A live Microsoft 365 position from the Graph data you already have is the point.

If you are heading into a Microsoft conversation this year and your current tools still need three weeks to turn “we have Microsoft 365” into consumer versus commercial, auto-moved versus opted-out, assigned versus paid, book a Software Intelligence Review. You can also start on the free plan and run the analysis on your own data.

The question to walk in with

AGCM may find that consumers were not given enough information, or that the auto-move was an aggressive practice. It may not. It has reached no conclusion. PS13129 is open.

Your renewal will not wait for that ruling. Do not let the next meeting open as “do you want Copilot.” The right question is what you are actually running, which catalog each plan sits on, which seats can change without a buying decision, and what you would still buy if the default had never moved. That is a data question, not a sales question.

The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.