An open drawer in a grey card-index cabinet, packed with filed cards, among rows of closed drawers.

Direct award to Microsoft: what a Swiss authority must prove

Luzern renewed its Microsoft Enterprise Agreement by freihändige Vergabe on 11 November 2026. What BGE 150 II 105 asks an authority to document first.

In short

  • On 11 November 2026, Stadt Luzern awarded its Microsoft Enterprise Agreement for 1 February 2027 to 31 January 2030 to Microsoft Ireland Operations Limited by direct award, for CHF 6,257,909 including VAT.
  • The other Microsoft licence notices on simap from 25 October to 19 November 2026 were reseller competitions, tenders or a direct award to a reseller: each named Microsoft licences as the object.
  • Since BGE 150 II 105 of 6 November 2023, an authority that awards a contract directly because no adequate alternative exists must prove it, not the company that challenges the award.
  • An authority planning a Microsoft renewal in 2029 or 2030 can start now: inventory its proprietary interfaces, write a complete requirements list, record a market analysis and run one function on a second source.
On this page (8)

On 11 November 2026, the City of Lucerne (Stadt Luzern) renewed its Microsoft Enterprise Agreement by freihändige Vergabe (direct award, without a tender). It awarded CHF 6,257,909 including VAT to Microsoft Ireland Operations Limited for 1 February 2027 to 31 January 2030, published on simap on 13 November under Article 21(2)(c) of the intercantonal procurement agreement (IVöB). The other Microsoft licence notices on simap between 25 October and 19 November 2026 concerned the choice of reseller, not a choice between Microsoft and another product. Since a Federal Supreme Court ruling of 6 November 2023, an authority that awards directly because no adequate alternative exists carries the burden of proving it, so an authority facing a renewal in 2029 or 2030 has to build that file before it.

This post covers the notices, what the courts require, the other side and what to do before the next renewal. Translations from German and French are ours, and facts are as of 19 November 2026. It does not assess any individual award: a notice gives the reasons in a few lines, and the file behind it is not public.

What did Luzern’s freihändige Vergabe for Microsoft licences say?

The notice, “Freihändige Vergabe Microsoft-Lizenzen”, from the city’s central IT services (Zentrale Informatikdienste), covers “die Verlängerung des Microsoft Enterprise Agreements (EA)” for three years, for all the Microsoft products and services the city needs.

The Luzern notice in numbers

  • CHF 6,257,909 including VAT, to Microsoft Ireland Operations Limited
  • 3 years from 1 February 2027 to 31 January 2030
  • 1,000+ specialist and group applications on proprietary interfaces, in the city’s words
Source: simap.ch, publication 47462-01

The legal ground it cites is “Art. 21 Abs. 2 lit. c IVöB”, followed by a summary of that exception: “technische Besonderheiten bzw. Schutz geistigen Eigentums, sofern nur ein Anbieter infrage kommt und keine angemessene Alternative besteht” (technical particularities or protection of intellectual property, where only one supplier comes into question and there is no adequate alternative). The city’s own reasoning follows:

“Die ICT-Grundversorgung der Stadtverwaltung, ihrer Kunden sowie der Volksschule basiert seit Jahrzehnten auf Microsoft-Produkten. Proprietäre Schnittstellen verbinden diese mit über tausend Fach- und Konzernapplikationen. Konkurrenzprodukte könnten diese Schnittstellen nicht durchgehend bereitstellen. Ein Wechsel würde erhebliche Betriebsrisiken mit sich bringen und eine umfassende Erneuerung der Verwaltungs-ICT voraussetzen.”

In English: the basic ICT provision of the city administration, its customers and the public schools has rested on Microsoft products for decades; proprietary interfaces connect them with more than a thousand specialist and group applications; competing products could not provide those interfaces throughout; and a switch would bring considerable operational risks and require a comprehensive renewal of the administration’s ICT.

The canton of Luzern has applied the IVöB 2019 since 1 January 2023.

Microsoft licences on simap: competition between resellers

The notices below, published between 25 October and 19 November 2026, each name Microsoft licences as the object, so the competition, where there was one, decided who supplies them and at what price, not whether to buy them.

Buyer Published Procedure Result
City of Bern 25 October Open, 3 offers Swisscom, CHF 7,246,850.10
Mendrisio 28 October Open, 2 offers Swisscom, CHF 987,456.53, EA for 2026 to 2029
Canton of Valais 5 November Direct award, “Renouvellement de licences” SoftwareONE, CHF 3,949,615.95
Geneva, EPI 14 November Open tender (corrected notice) Offers due 7 December, contract 1 March 2027 to 28 February 2030
Basel-Landschaft, schools 18 November Open, 1 offer Bechtle Schweiz, price not published
Canton of Jura 19 November Open, 2 offers Bechtle Suisse, CHF 2,249,743

All prices include VAT. Valais’s direct award gives “Renouvellement de licences” (renewal of licences) as its justification. The same office also has an open tender for Microsoft licences with offers due on 2 December 2026. Jura weighted price at 80% of the evaluation.

Competition between resellers is real competition on price and service. It is a different question from the one Article 21(2)(c) asks, which is whether anything other than the product could meet the need.

Who has to prove there is no adequate alternative?

The authority. That has been the rule since BGE 150 II 105 (2C_50/2022), decided on 6 November 2023. Its headnote reads: “Demgegenüber ist es Sache der Vergabebehörde, das Fehlen einer angemessenen Alternative nachzuweisen, wenn die freihändige Vergabe darauf beruht (Änderung der Rechtsprechung; E. 5.5-5.10)” (by contrast, it is for the contracting authority to prove the absence of an adequate alternative where the direct award rests on it; change of case law).

The case concerned the canton of Vaud’s vehicle registration office, which had run the same application since 2005. In 2021 the canton decided to buy its new version and extend the contract to 2034 by direct award, for CHF 45,891,000. A competing supplier challenged it; the cantonal court overturned the award, and the Federal Supreme Court confirmed that result.

  • A partial reversal. The court “partially” abandoned its “Microsoft” judgment of 11 March 2011 (BGE 137 II 313), which had put the burden on the challenger, and applied the new rule to Article 21(2)(c) of both the federal procurement act and the IVöB 2019 (E. 5.10). A challenger still has to show credibly that it is a potential supplier.
  • What the file lacked. On the cantonal court’s findings, which bound the Federal Supreme Court, the authority had not listed its expected technical characteristics exhaustively, nor shown that it had “concretely and seriously” considered other software; it had not approached the two other providers in that market (E. 6.2). There was no “analyse concrète” of other solutions, “tant sous l’angle fonctionnel qu’économique” (functionally and economically) (E. 6.3).
  • What did not save it. The incumbent argued that a switch meant taking the work back in house, redeveloping interfaces and migration costs of CHF 24.5 million, more than half the award’s value. The court held this was argued “en vain”: whether the rival’s product is worse is for a tender to decide (E. 6.4).

The IVöB also requires a record. For every contract awarded under one of the exceptions, Article 21(3) asks the authority to document the buyer and supplier, the type and value of the purchase, and an “Erklärung der Umstände und Bedingungen, welche die Anwendung des freihändigen Verfahrens rechtfertigen” (an explanation of the circumstances and conditions that justify the direct procedure) (text of the IVöB 2019, in the canton of Glarus’s synopsis).

The other side: the authority defines what it buys

The burden of proof does not settle what counts as an alternative. In 2C_285/2025 of 24 March 2026, the Federal Supreme Court turned down a challenge to the canton of Thurgau’s direct award of six modules for its tax return software eFisc, for CHF 416,000. The authority has “ein weiter Ermessensspielraum” (wide discretion) in defining its needs, within the principles of procurement law, the court said (E. 1.1.3.2), and it won although it had made no market inquiries and drawn up no specification, because what it bought was narrowly defined. The source code belonged to the supplier, so only the supplier could build the modules, and a new application, which the challenger offered as the alternative, “steht vorliegend aber nicht zur Diskussion” (is not at issue here) (E. 5.3.2). The court noted that it had not yet dealt in depth with vendor lock-in.

Practitioners also defend dependency awards. Thomas M. Fischer, deputy head of the canton of Bern’s Office for Informatics and Organisation (KAIO), presented his view at the Vergabetagung of 19 June 2026, speaking in a personal capacity. He estimates that dependency awards make up “70 % der Anzahl / 80 % des Werts aller IT-Freihandvergaben” (70% of the number and 80% of the value of all IT direct awards), a figure he labels as his own “potenziell fehleranfällige KI-Analyse” (potentially error-prone AI analysis) of simap data. He gives Microsoft licence purchases as an example where functionality, migration cost and staff availability combine, and argues that a dependency award is admissible at least where the authority shows it avoids a pro-forma tender that only one supplier could win.

His slides set out the same duty, though. The evidence is “dokumentierte Marktanalyse” (a documented market analysis), a complete requirements list is needed after BGE 150 II 105, and intellectual property is no automatic ground for a direct award. He describes the analysis in four steps, with a request for information on simap often helpful and a duty to document the result.

The burden of proof and one renewal cycle

  1. 11 March 2011: The “Microsoft” judgment puts the burden on the challenger.
  2. 1 January 2023: The canton of Luzern applies the IVöB 2019.
  3. 6 November 2023: BGE 150 II 105 moves the burden to the authority.
  4. 24 March 2026: 2C_285/2025 turns down a challenge to Thurgau’s eFisc award.
  5. 11 November 2026: Luzern decides its Enterprise Agreement renewal.
  6. 13 November 2026: The award is published on simap.
  7. 1 February 2027: The three-year term starts.
  8. 31 January 2030: The term ends.
Court dates from the judgments; the 2023 date from the canton; Luzern’s dates from its notice.

Microsoft lock-in sits in the interfaces, not in Word

Luzern’s reasoning is not about office documents but about applications connected through proprietary interfaces. On 21 May 2026, the City of Zurich reported that an open-source suite met the basic needs of office work, but that replacing Microsoft 365 was not yet possible “da zahlreiche Abhängigkeiten zur vorhandenen IT-Infrastruktur und zu Fach-Anwendungen bestehen” (because there are numerous dependencies on existing IT infrastructure and specialist applications). The licences also cover device management, telephony and security services, it added.

The study for Digitale Verwaltung Schweiz reached a similar finding: migration is easier where applications use generic file operations, WebDAV or REST, and harder with SharePoint metadata, workflows or connectors (our reading of the study).

Where the notices give a term, it is three years. Every specialist application bought on a proprietary interface between two renewals adds to the count. That is the variable an authority controls, application by application, long before the next renewal.

Open standards make the alternative something you can show

BGE 150 II 105 asks whether another product meets the authority’s needs, functionally and economically; Fischer reads it as requiring a complete, documented requirements list. Two things make that comparison possible: interfaces that other products can implement, and evidence from production rather than a vendor’s datasheet.

Open source and open standards help with both, within limits. An open-source workplace has interfaces too: the DVS study expects much of the integration work to stay with the organisation’s own IT even when a hoster runs the platform, and Fischer calls dependency-reduction measures, open source and open standards among them, not required and partly risky in themselves, but worth examining. What open software changes is that the interface is documented and public, the code can be inspected, and the operator can be replaced without replacing the software. A function that already runs on it, with its data exported in open formats, gives the market analysis something real to compare. For federal bodies the EMBAG adds its own rules on source code; it does not bind cantons and communes directly.

The federal government plans its open-source workplace for about 3,000 staff the same way, in parallel with Microsoft 365.

A market analysis in four steps

  1. Requirements: Draw up a complete, justified list of requirements.
  2. Market: Identify potential suppliers and products.
  3. Adequacy: Assess whether each one is an adequate alternative.
  4. Decision: Decide the procedure, and keep the record.
The KAIO model as presented by Thomas M. Fischer; he calls a request for information on simap often helpful and the record a duty. Source: Thomas M. Fischer, Vergabetagung 2026

What to do before a 2029 or 2030 Microsoft renewal

The duties to prove and to document come from BGE 150 II 105 and Article 21(3) IVöB. The dates are our suggestion for an agreement that ends in early 2030.

  1. By 31 December 2027: inventory the proprietary interfaces. For each specialist application, record the Microsoft service it depends on (directory, mail, SharePoint, Graph API), its owner and whether an open protocol could serve.
  2. From your next tender: require open standards. Require documented, open interfaces for identity, files and calendars, so the list in step 1 stops growing.
  3. By 30 June 2028: run one function on a second source. Pick one with few interfaces, such as file sharing for one department, run it in production on open-source software and measure cost, integration hours and tickets.
  4. By 30 September 2028: write the complete requirements list. Functional and economic, justified line by line: the yardstick any alternative is measured against.
  5. By 31 December 2028: record the market analysis. Publish a request for information on simap, approach the providers, assess adequacy and keep the record, whatever it finds.
  6. About 12 months before the term ends: choose the procedure. If the analysis finds no adequate alternative, the file shows why. If it finds one, there is still time for a tender.

How Pilae fits

A market analysis is stronger when one alternative already runs and its gaps are written down. Pilae operates open-source apps on your premises or on dedicated machines in Pilae Cloud, and it can operate one function on open-source software while the rest stays where it is.

  • A fallback with a test record. For a critical service we name an open-source or source-available fallback, with its gaps written down, export your data on a schedule in open formats and write the switch-over runbook. Each plan is exercised on a schedule you set and leaves a dated record (exit plan). An exit plan does not oblige you to leave the provider.
  • One function first. Files on Nextcloud with Collabora Online, chat on Mattermost or Element, meetings on Jitsi Meet: you can start with one app and keep Microsoft 365 for the rest, and from the Business plan Keycloak can federate with Entra ID so staff keep one login (sovereign workplace).
  • The integrations found before anything moves. A migration starts with an inventory that includes the automations and integrations nobody wrote down, then a written plan at a fixed price, a parallel run and a cutover with a rollback (migration).
  • Your servers, and nothing locked in. We install on the machines you choose, VMware, Proxmox and Hyper-V included. Every app is open source or source-available with its licence named, and your data, configuration and runbooks come back in open formats on request (on your premises, public sector).

Operation on your premises starts on the Business plan; our plans and prices are on the pricing page. If your next renewal falls in 2029 or 2030, talk to an engineer: we go through the interfaces your specialist applications depend on and which function could move to open-source software first.

This post is general information, not legal advice. For the official texts, read BGE 150 II 105, judgment 2C_285/2025 and the Luzern notice on simap.

Cover: photo by Maksym Kaharlytskyi on Unsplash, redrawn in pixels.

Talk to an engineer about a gradual way off Microsoft 365

Thirty minutes with an engineer, a written plan and a fixed price for the first workload.

Book 30 minutes

Tell us what you need to run.