Novell, Inc. v. Microsoft Corp. (2002): what Delaware LLC founders should know

Case at a glance

• Case name: Novell, Inc. v. Microsoft Corp.
• Year: 2002
• Court: Federal Court
• Citation: (D.D.C.)
• Category: Member Disputes

The facts

Novell antitrust claims against Microsoft.

The holding

Antitrust framework applied.

Why this case matters

Not directly LLC law; included for context.

What this means for Delaware LLC founders

Not directly applicable.

How Novell v. Microsoft applies to your LLC

For solo single-member Delaware LLC founders, most fiduciary-duty cases have limited direct application: there is no co-member to owe duties to, and creditor-fiduciary-duty exposure arises only after actual insolvency. The cases become more relevant as the LLC grows:

• Adding co-founders or investors: multi-member LLCs face the full range of fiduciary-duty analysis, though Operating Agreements can modify duties under § 18-1101.
• Manager-managed structures: when non-member managers run the LLC, they owe fiduciary duties to members by default (§ 18-1104).
• Sale or merger transactions: Revlon and Unocal duties translate to LLC change-of-control transactions.
• Member disputes: Court of Chancery jurisdiction over Operating Agreement disputes applies the body of Delaware case law as guidance.

Primary source

The full text of Novell, Inc. v. Microsoft Corp. is available through Westlaw, LexisNexis, and Google Scholar. The Delaware Court of Chancery publishes opinions at courts.delaware.gov/chancery. The Delaware Supreme Court publishes opinions at courts.delaware.gov/supreme.

Related cases and concepts

For broader Delaware corporate and LLC case law context, see our coverage of the business judgment rule, fiduciary duties, Delaware Court of Chancery, and the Delaware LLC Act. The Delaware Limited Liability Company Act sections (6 Del. C. § 18-101 et seq.) interact with the body of Delaware case law to define LLC governance.

See all cases in the Delaware Case Law Library →

What kind of dispute was Novell v. Microsoft, and why does it sit in a Delaware case library?

Novell, Inc. v. Microsoft Corp. is an antitrust matter between two technology companies, litigated in federal court rather than in the Delaware Court of Chancery. The record we summarize describes Novell's antitrust claims against Microsoft and the application of an antitrust framework to those claims. That places this dispute in a different legal universe from the corporate-governance and fiduciary-duty cases that usually define Delaware business-entity law. Antitrust law asks whether a firm used market power to harm competition. Corporate law asks whether managers and members honored duties owed inside a company. Those are separate questions, decided by different courts under different statutes.

Because the case is not a Delaware corporate decision, it does not set or restate a rule of Delaware LLC law. The honest framing is that this matter appears in a Delaware case library for context, not as governing doctrine for a limited liability company. We treat it that way throughout this page. Rather than stretch an antitrust ruling into LLC governance principles it never addressed, the sections below explain what the dispute was about in plain language, what general business lessons a non-resident founder can reasonably draw from it, and how a Delaware LLC's own governance documents and the Delaware Limited Liability Company Act handle the very different set of questions that actually shape day-to-day ownership and management.

What were the underlying facts as the record describes them?

The record characterizes the matter as Novell's antitrust claims against Microsoft. At a high level, antitrust disputes of this type involve allegations that a company with substantial market power acted in ways that suppressed competition, harmed rival products, or foreclosed competitors from reaching customers. Novell, as the claimant, advanced theories that Microsoft's conduct injured its business in a relevant market. Microsoft, as the defendant, contested those theories. Because our record states the facts qualitatively rather than reproducing the full procedural history, we do not attribute specific findings, dollar figures, or product details that the record does not supply.

For a non-resident founder, the useful point is structural rather than granular. A dispute like this turns on market definition, market power, the nature of the challenged conduct, and proof of competitive harm. Those elements are the building blocks of any antitrust theory. None of them depend on whether the parties were corporations, limited liability companies, or partnerships. Antitrust exposure attaches to conduct in a market, not to a particular choice of entity. A Delaware LLC is no more and no less subject to antitrust scrutiny than a Delaware corporation carrying on the same business. The lesson to carry forward is that entity choice shapes governance and liability among owners, while competition law reaches the firm's external conduct regardless of that choice.

What was the central legal question?

The legal question in an antitrust case of this kind is whether the defendant's conduct violated the competition rules that govern dominant firms. That inquiry is fundamentally different from the questions a Delaware governance court asks. A federal antitrust court examines the relevant market, the defendant's power within it, the specific acts complained of, and whether those acts produced anticompetitive effects that outweighed any legitimate business justification. The framing is economic and market-facing.

By contrast, the questions that animate Delaware LLC law are internal and relational. They ask who owes duties to whom, what an operating agreement permits or forbids, and how members and managers must behave toward one another. Recognizing that the central question here was an antitrust question, and not a governance question, is the single most important interpretive move for a founder reading this case. It prevents the common error of importing a market-competition holding into the ownership-and-management context where it has no work to do. Keeping the two domains distinct lets a founder use the case for what it genuinely teaches about external conduct, while looking elsewhere for the rules that govern the inside of an LLC.

What did the court hold, and what doctrine did it apply?

Our record states that an antitrust framework was applied to the dispute. In keeping with the instruction to ground everything strictly in the record, we describe the holding qualitatively rather than asserting a precise outcome, damages figure, or appellate disposition that the record does not contain. The doctrine at work was the body of competition law that governs how firms with market power may behave. That framework is federal and statutory in origin, and it is enforced through federal courts and federal agencies rather than through Delaware's entity statutes.

Crucially, an antitrust framework is not a corporate or LLC governance framework. It does not address fiduciary duties among members, the enforceability of operating agreement terms, or the standards of review a Delaware court uses to evaluate management decisions. So while the case applied a recognized legal doctrine, that doctrine sits outside the Delaware LLC Act and outside the line of Court of Chancery decisions that founders usually consult. A founder should read the holding as an example of how competition law constrains a firm's outward conduct, and should not read it as a statement about how to allocate control, profits, or duties inside a Delaware limited liability company.

Did this case shape Delaware corporate or LLC law?

It is more accurate to say this case did not shape Delaware corporate or LLC law in any direct way. The decisions that built Delaware governance law come overwhelmingly from the Delaware Court of Chancery and the Delaware Supreme Court, applying the Delaware General Corporation Law and the Delaware Limited Liability Company Act. An antitrust matter decided in federal court operates on a separate track. Its reasoning does not become precedent for how Delaware judges analyze member disputes, manager conduct, or operating agreement interpretation.

That separation is itself a worthwhile takeaway. Founders sometimes assume that any high-profile case involving a large company must carry lessons for their own entity governance. In reality, the relevance of a decision depends on its subject matter and the court that issued it. This case is included for context so a reader can see the full landscape of business litigation that companies face, which includes competition law alongside governance law. But its presence in the library should not be mistaken for doctrinal influence on Delaware LLC rules. The genuine Delaware governance principles a founder needs come from a different family of cases entirely, and those cases are cataloged separately.

How does the principle carry over to a Delaware LLC and its operating agreement?

Because the case is an antitrust matter, it does not supply a governance principle that maps onto an operating agreement. What it does is highlight, by contrast, what an operating agreement is actually for. An operating agreement is the internal contract among the members of a Delaware LLC. It allocates ownership percentages, voting power, profit and loss distributions, management authority, and the procedures for admitting or removing members. None of those subjects are touched by an antitrust ruling about market conduct.

A few distinctions help a founder keep the two domains apart:

• Internal versus external: an operating agreement governs relationships inside the LLC, while antitrust law governs the LLC's conduct toward competitors and customers outside it.
• Contract versus statute: the operating agreement is a private contract enforced under the Delaware LLC Act, while antitrust obligations arise from public competition statutes that apply regardless of any contract.
• Drafting reach: careful drafting can shape duties and dispute procedures among members, but no operating agreement clause can waive the firm's obligations under competition law.

What should a non-resident founder take from this case in practical terms?

For a founder outside the United States forming a Delaware LLC, the practical message is to separate two categories of risk that are easy to blur. The first category is governance risk, meaning disputes among owners and managers about control, money, and duties. That risk is managed through the operating agreement and through the Delaware LLC Act. The second category is market-conduct risk, meaning exposure to competition law and other external regulation that depends on how the business behaves in its market. This case sits in the second category.

In practice, that means a founder should not expect an operating agreement to address antitrust exposure, and should not expect competition law to resolve a fight between members. The two require different tools. A founder building a product that might one day hold meaningful market share would be wise to treat competition compliance as its own workstream, separate from internal governance. None of this is legal advice, and the specifics of antitrust risk depend heavily on industry, market position, and conduct. The general point is one of mental categorization: this case teaches about the firm's outward behavior, while the founder's entity documents teach about the owners' inward relationships.

How does it relate to fiduciary duties under the LLC Act?

Fiduciary duties under the Delaware LLC Act concern the obligations members and managers owe to one another and to the entity. By default, managers in a manager-managed LLC owe duties of care and loyalty to the members, and those defaults can be modified by agreement within the limits the statute allows. An antitrust matter does not engage any of this. Novell and Microsoft were adversaries in a market, not co-owners of a single enterprise, so no fiduciary relationship of the kind the LLC Act addresses was in play.

The contrast is instructive precisely because it shows where fiduciary analysis does and does not belong. Fiduciary duties arise from a relationship of trust inside a business organization. They do not arise between competitors in a marketplace. So when a founder evaluates fiduciary-duty questions for a Delaware LLC, the relevant authorities are the governance cases and the LLC Act provisions on duties, not a competition decision like this one. Reading this case helps a founder draw the boundary line clearly: fiduciary obligations track ownership and management relationships, and the absence of such a relationship between the parties here is exactly why fiduciary doctrine had no role to play.

How does it relate to contractual freedom in the LLC Act?

One of the defining features of Delaware LLC law is the principle, expressed in the Delaware LLC Act, that effect should be given to the freedom of contract and to the enforceability of operating agreements. That principle lets members tailor their internal arrangements with substantial flexibility. It is a powerful tool for structuring ownership and management. It is also, importantly, a tool with limits.

This case illustrates one of those limits by analogy. Contractual freedom under the LLC Act governs the relationships the members choose to create among themselves. It does not extend to contracting out of public obligations that apply to the firm's external conduct, such as competition law. A founder cannot draft an operating agreement that immunizes the business from antitrust scrutiny, because that body of law operates independently of any private agreement. So while founders should make full, deliberate use of contractual freedom to design their internal governance, they should also recognize that this freedom stops at the entity's boundary. Beyond that boundary, externally imposed rules like the ones at issue in this matter continue to apply regardless of what the members have agreed.

How should a founder use a case like this in a Delaware research library?

A practical way to use this entry is as a marker of scope. When a founder scans a library of Delaware business cases, most entries will be governance decisions that bear directly on operating agreements, fiduciary duties, and member disputes. A few entries, like this one, are included to show the wider field of litigation that companies encounter. Used that way, the case helps a reader build an accurate map of the legal terrain without confusing competition law for corporate governance.

The healthy habit is to ask, for any case, two questions: which court decided it, and what subject did it address. For this matter, the answers are a federal court and an antitrust framework. Those answers immediately signal that the relevant takeaways concern market conduct rather than internal LLC governance. A founder who internalizes that sorting discipline will read every case more accurately, spending governance research time on the Court of Chancery decisions that actually drive Delaware entity law, while noting matters like this one for the broader context they provide. That disciplined reading is itself a meaningful skill for anyone building a company under Delaware law.

What are the key points to remember about this case?

Pulling the threads together, the following points capture what this entry does and does not establish for a Delaware LLC founder. They are framed as general information about how to categorize and interpret the case, not as advice about any particular situation.

• Subject matter: this is an antitrust dispute between two technology companies, decided under a competition-law framework in federal court.
• Not Delaware governance doctrine: it does not set or restate any rule of Delaware corporate or LLC law, and it is included for context.
• Internal versus external: operating agreements and the LLC Act govern relationships among owners, while competition law governs the firm's conduct in the market.
• No fiduciary relationship: the parties were market adversaries, so the fiduciary-duty analysis central to many Delaware governance cases had no role.
• Limits of contractual freedom: the LLC Act's freedom-of-contract principle shapes internal arrangements but cannot waive externally imposed obligations like competition law.
• Reading discipline: identify the court and the subject before drawing lessons, which keeps competition rulings from being mistaken for governance precedent.