A site outside city limits can look easier to develop because it faces fewer municipal land-use controls. That does not make its development path predictable. A campus still needs power, water, roads, permits, capital, and a community prepared to live with the consequences. A dispute over any one of those can consume the schedule even when the developer ultimately has the stronger legal position.
For selected Texas projects, voluntary annexation can offer a more defensible path: bring the campus into a municipality through a coordinated package of land-use approvals, service commitments, infrastructure funding, and enforceable operating conditions. The additional obligations may be worth accepting if they replace open-ended disputes with requirements the project can meet.
But annexation is not an exemption from Texas law. A city boundary does not protect a campus from statewide restrictions, create electric capacity, transfer another provider’s water rights, or guarantee support from future elected officials.
The investment question is therefore not simply whether to enter a city. It is which uncertainties the complete municipal package actually resolves, at what cost, and with what evidence.
The campus problem
Illustrative scenario, not a claimed client result.
A campus outside city limits has one tenant approaching a commitment. The city is open to annexation, but the serving water provider is a separate entity. A new main would serve both the campus and adjacent growth. The second phase has no fixed opening date. The owner must compare annexation with remaining outside the city under an otherwise lawful development and service route. Neither choice can be evaluated from tax rates alone.
The owner also faces genuine political uncertainty. The purpose of the comparison is to identify which route can make the first phase more dependable, while retaining viable later phases. It is not to assume that either route is immune from future law.
Loudoun is a warning about political durability, not a Texas legal precedent
On July 23, 2026, Loudoun Supervisor Juli Briskman’s office announced a motion directing staff to return on September 15 with a proposed pause on data center and substation applications and legal analysis. That is a scheduled consideration, not an adopted September moratorium.[1]
Separately, Loudoun County’s published land-use guidance says Virginia law does not allow a blanket moratorium on new applications without individual consideration. The same guidance describes the county’s March 2025 change requiring special-exception approval for new data centers. The distinction matters: a disputed pause and a lawfully adopted change to development rules are not the same action.[2]
For Texas investors, the useful lesson is commercial rather than jurisdictional. A location’s history of welcoming data centers does not remove the possibility of political change. Equally, an objectionable or legally vulnerable restriction can still create delay, litigation expense, and uncertainty over a tenant’s opening date. Texas authority must be analyzed under Texas law, not inferred from Virginia’s position.
Distinguish political risk from enacted restrictions
The prospect of tighter Texas controls is not imaginary. The Texas Tribune reported that Governor Greg Abbott called in June for prohibiting AI data centers in rural Texas neighborhoods. Those remarks are a political signal, not an enacted statewide siting rule. Nor should “rural neighborhoods” be treated as a legal synonym for every unincorporated parcel.[3]
The Governor’s July announcement concerning a withdrawn Henderson County project also called for legislation addressing data center resource reporting and incentives. Its account connected development expectations to infrastructure costs, water use, and neighborhood impacts.[4] None of that establishes a general annexation exemption.
State-level scrutiny is already operational. ERCOT’s September 9 notice describes verification requests for many conditionally eligible Batch Zero large-load projects. Recipients generally have ten business days after issuance to supply complete responses; a limited extension can be requested. Successful verification is a condition of Batch Zero inclusion, not permission to energize. The notice also anticipates a separate request addressing state and community impacts.[5]
This process concerns the affected ERCOT projects, not every Texas site or every grid in the state. Its practical significance is nevertheless direct: a developer cannot solve an ERCOT documentation or eligibility problem by annexing its land.
Keep two schedules: one for local development approvals and one for utility and state requirements. A favorable city vote does not close the second schedule.
Fewer county powers do not mean an uncontested project
Texas counties generally do not possess the broad zoning powers of municipalities. Chapter 231 provides geographically specific county zoning authorities rather than a universal county zoning system. County platting authority under Chapter 232 is also statutory, with requirements and limits that must be checked against the actual project.[6][7]
Those limits matter when evaluating a county demand, but they are not a reason to omit drainage, access, flood exposure, emergency response, or downstream infrastructure from the development plan. Separate agencies and providers may control essential approvals or assets.
Hill County illustrates the difference between a legal argument and a dependable schedule. According to the Texas Tribune, commissioners rescinded a data center moratorium in June after litigation began and replaced it with a checklist. That sequence is not a judicial ruling settling every county’s authority.[8] The Attorney General’s website also lists a request concerning county moratorium authority for energy facilities, including data centers, as pending.[9] The Attorney General has not yet answered that request, and no statute clearly lets a Texas county pause a data center; a county’s leverage comes from approvals a site needs from it, such as road closures, plats and abatements.
The developer’s choice is not limited to “accept every county demand” or “sue and build.” It can compare a supported unincorporated development path, a lawful extraterritorial-jurisdiction agreement where available, annexation into a suitable city, and an alternative site. The appropriate route depends on the approval sequence and infrastructure, not simply the least restrictive zoning map.
What annexation can buy: an accountable local arrangement
Temple offers a useful example of the mechanism. In its August 2026 development statement, the city explained that annexation provides a basis for enforceable zoning, development conditions, and utility agreements. Its stated measures include water limits and metering, noise studies and compliance requirements, and developer-funded road improvements. The city also explicitly distinguishes its authority from that of ERCOT, Oncor, and the state.[10]
That is a city-specific approach, not proof that every municipal package will work. Its value is the connection between a concern and an enforceable response.
For a proposed campus, the negotiation should answer questions such as:
- Water: What annual and peak-day demand is permitted, under which cooling scenario, and what happens during drought? Who funds an alternative if the assumed source cannot serve the phase?
- Noise: Which equipment and operating conditions are tested? Does the assessment include simultaneous generator testing, cooling systems at peak duty, and nearby homes outside the annexation boundary?
- Roads: Who funds construction damage, permanent improvements, and maintenance? What happens when the heavy-haul route crosses another jurisdiction?
- Emergency response: What staffing, equipment, access, training, and operating information are required, and when must they be available?
- Public cost: Which improvements are paid for by the developer, which depend on future tax collections, and who bears the shortfall if later halls never arrive?
These are proposed diligence and negotiating questions, not representations that every city may impose every condition. Counsel must confirm authority and applicable approval procedures.
The political benefit is not that opposition disappears. It is that residents, officials, and investors can test the same commitments: the limit, the measurement, the responsible party, and the consequence of failure. An unfunded community-benefit promise does not provide that protection.
A city can also be the more restrictive choice
San Marcos is an important counterexample. Its official June 16, 2026 council recap records adoption of a development-code amendment prohibiting data centers in all zoning districts. That establishes the city’s adopted policy, not an independent judicial determination of its validity.[11]
A developer cannot assume that entering a municipality makes approval more likely. Annexation can add municipal taxes, more demanding design standards, discretionary land-use decisions, and operating restrictions. A city facing a water shortage or strong neighborhood opposition may be a worse fit than a well-supported unincorporated route.
Evaluate the receiving jurisdiction before negotiating the boundary. Does its adopted code accommodate the intended use? Are the power plant, substation, battery system, cooling infrastructure, and future halls covered by the proposed approvals? Is there an established public process for the project, or merely an encouraging introductory meeting?
The latter is not an entitlement.
Solutions and their tradeoffs
Owner-requested annexation with a coordinated service package
The municipality has a useful role and the service obligations can be made specific.
Conditions to resolve: Confirm the lawful route, required approvals, provider participation, taxes, fees and the executable delivery schedule.
Remain unincorporated with authorized provider agreements
Existing jurisdiction and service arrangements can support the campus without annexation.
Conditions to resolve: Verify applicable land-use, drainage, fire, environmental and utility requirements. Absence of city zoning is not absence of regulation.
Change the initial phase or select a different service route
Neither original option supports the required date or cost.
Conditions to resolve: Compare resizing, alternative providers where lawful, or another site against carrying costs and tenant consequences.
An eligible ETJ development agreement can also be evaluated where it supplies a useful intermediate framework. Its availability and effect require the separate legal review described below.
Four different decisions must become one executable package
Annexation, zoning, services, and utility delivery solve different problems. Treating one document as a substitute for the others creates false confidence.
Swipe or scroll to compare all columns.
| Decision | Evidence the developer needs | What it does not establish |
|---|---|---|
| Annexation | Valid route, ownership and boundary review, required process, adopted ordinance | Permission for every intended use or protection against state law |
| Land use and development | Applicable zoning and permits; any lawful development agreement; phase and operating assumptions | Funded utility capacity or freedom from every later requirement |
| Municipal services | Written responsibilities, scope, timing, costs, dependencies, and remedies | Automatic delivery by an independent provider |
| Utility and enabling infrastructure | Provider commitments, required approvals, capacity basis, funded works, access rights, and milestones | An unconditional tenant opening date |
Under the owner-requested route in Chapter 43, Subchapter C-3, each landowner in the area requests annexation and the municipality may elect to proceed. Section 43.0672 requires a written service agreement before annexation under that route, identifying services supplied on the effective date and a schedule for later services. Services omitted from that agreement are not automatically required under that provision.[12]
This is a reason to negotiate the substance early. “The city will serve the campus” is not enough. Specify the scope, delivery assumptions, funding, third-party dependencies, and consequences of delay.
Coordinate the four decisions through a counsel-led closing and approval plan. Do not assume a city can contract away a required hearing or predetermine a discretionary vote. Equally, do not accept annexation and its costs first while leaving the essential land-use decision to an undefined later process.
Negotiate the service schedule against the first useful phase
A list of municipal services is not a construction schedule. For each service, identify the provider, agreed demand, capital works, funding, delivery trigger, acceptance evidence, and consequence of delay. Separate a commitment to consider an upgrade from an obligation that can support the tenant’s opening date.
The master plan belongs in that negotiation. A first-building service package may leave later halls unsupported, while an immediate commitment to ultimate buildout can create unaffordable payments. Define phase-demand assumptions, reserved corridors, capacity-allocation rules, expansion triggers, and who funds a change. Test the case where the second tenant is delayed or never arrives.
Existing residents, campus demand, and optional regional growth should have distinguishable cost responsibilities. Do not count prospective reimbursement as secured funding. Verify actual emergency-response arrangements and any insurer requirements rather than assuming annexation creates coverage or an insurance discount.
A service boundary is not a city boundary
Water is a particularly expensive place to confuse jurisdiction with delivery. Water Code Chapter 13 protects existing certificated service arrangements and provides conditional procedures for changes. Annexation does not automatically displace another water or sewer provider. The municipal single-certification route in Section 13.255 has substantive requirements and provider-specific limits, including subsection (j).[13]
If another provider controls the critical service, it must be part of the delivery solution. A promise from the wrong counterparty is not capacity. The technical companion, Annexation, ETJs and CCNs: who controls each campus dependency?, sets out the authority map, connection interfaces, evidence requirements, and release sequence.
Vesting deserves its own analysis
A developer facing political change may ask whether annexation or an early filing locks in the rules. That requires a project-specific answer.
Chapter 245 provides protections tied to qualifying permit applications or plans giving fair notice of a project. It contains significant exemptions, including utility-connection regulations, permit fees, and certain annexation, safety, and public-works requirements. Its definition of a regulatory agency concerns political subdivisions, not a blanket freeze on future action by the Texas Legislature or state agencies.[14]
Buying land, obtaining annexation, filing an incomplete description, and establishing protected rights for the whole planned campus are therefore not interchangeable events. Have counsel document the qualifying project, applications, protected requirements, exceptions, deadlines, and treatment of later phases.
An eligible ETJ development agreement can also deserve consideration before annexation. Section 212.172 authorizes specified agreements, including arrangements addressing development and future annexation. Its formalities include written terms, property identification, approvals, disclosure, and recording. A compliant agreement binds specified successors, survives annexation, and constitutes a permit under Chapter 245, subject to the statutes’ limits.[15]
Neither instrument should be sold internally as “grandfathering everything.” The practical output is a rights-and-dependencies schedule that identifies what is protected, what remains discretionary, and what could still change.
Underwrite 2027 by the wording of a law, not a rumor
No enacted blanket Texas data center siting ban, or specific 2027 bill creating an annexation safe harbor, was identified in the materials Sitebraid reviewed. That is a research limit as of September 11, 2026, not a prediction that legislation will not emerge.
Texas’s Constitution expressly prevents home-rule charters and ordinances from conflicting with general state law.[16] A local agreement may have enforceable rights worth preserving, but its treatment under a future statute cannot be assumed in advance.
The following are underwriting scenarios, not descriptions of filed legislation:
Swipe or scroll to compare all columns.
| Hypothetical restriction | Would annexation help? | Required diligence |
|---|---|---|
| Restrictions expressly limited to unincorporated land | Potentially, if the enacted definitions and timing recognize the annexation | Effective date, boundary rules, grandfathering, and any anti-avoidance provisions |
| Restrictions based on proximity to rural homes or sensitive resources | Not necessarily; the physical relationship may remain unchanged | Definitions, setbacks, covered facilities, and mitigation exceptions |
| Statewide power, water, reporting, or eligibility requirements | No automatic exemption | Whether the campus and its supporting infrastructure satisfy those requirements |
| Protection only for projects reaching specified permit or construction milestones | Annexation alone may be insufficient | Exact qualifying milestone, project scope, documentation, and deadlines |
| Changes to tax incentives or infrastructure cost allocation | City status may not protect the economics | Revised operating costs, development budget, and tenant pricing |
Do not pay an annexation premium solely for an assumed exemption from a law that does not yet exist. Pay for identifiable local value, then separately test the remaining state-level exposure.
Follow the campus beyond the annexed parcel
A boundary review limited to the data halls can miss the infrastructure that determines whether they open.
The water main may cross unincorporated land. A generation site may have a different owner and permitting route. An access improvement may require county cooperation. A substation, transmission route, or drainage outfall may sit outside the area covered by the city’s commitments.
Prepare a dependency map for each phase showing the asset, jurisdiction, rights holder, approval, funding source, delivery date, and alternative. Then test three changes: the first tenant arrives late, the next tenant requires a different cooling system, and an off-site approval takes a year longer than assumed. Ask which local commitments, infrastructure sizes, and commercial obligations must be reopened.
This is also where legal protection and operational flexibility can conflict. A tightly defined approved scheme may support certainty while leaving too little room for a new tenant. Preserve lawful change procedures and realistic phase envelopes; do not rely on a vague promise of future administrative flexibility.
Does the added cost purchase enough certainty?
Consider an illustrative comparison, not a Sitebraid client result or market estimate. Assume the annexation package has $9 million of incremental present-value cost compared with a viable unincorporated route. That amount includes modeled additional taxes, compliance measures, and infrastructure obligations, net of substantiated benefits.
Assume a local delay costs the project $1.5 million per month at the decision date, using a consistently discounted measure of incremental cash impact. The model excludes double counting between carrying costs, lost margin, and contractual damages.
Swipe or scroll to compare all columns.
| Local delay genuinely avoided by the municipal package | Modeled avoided impact | Net benefit after $9 million incremental cost |
|---|---|---|
| Three months | $4.5 million | Negative $4.5 million |
| Six months | $9 million | Break-even |
| Nine months | $13.5 million | Positive $4.5 million |
The arithmetic does not prove that annexation saves time. It exposes the evidence needed to justify the choice. Why would the municipal route avoid six months? Are its approvals achievable? Are promised services funded? Does it introduce its own delay?
If both routes are stopped by the same state-level restriction or unavailable power, that shared delay does not count as an annexation benefit. A probabilistic model should use defensible scenario weights, not an invented probability of a 2027 ban.
The full comparison should also capture approved capacity, operating limits, expansion flexibility, remedies, and tenant acceptability. A slightly cheaper route that cannot support the required phase is not a real alternative.
Putting the analysis to work
Sitebraid’s development role is to connect the legal review to infrastructure, phasing, funding, and the tenant commitment. Counsel determines legal authority and enforceability; engineers and providers establish the technical and service basis. The developer needs those conclusions in one executable plan.
The assessment should deliver:
- A jurisdiction and dependency map: the campus and off-site assets, decision makers, service territories, rights, and unresolved interfaces.
- A route comparison: unincorporated development, eligible ETJ agreement, annexation, and relocation where justified, using consistent assumptions.
- A coordinated approval and agreement plan: what must be approved, contracted, funded, or evidenced before the next commitment.
- A phase-level financial model: taxes, infrastructure contributions, minimum commitments, delay exposure, downside cases, and obligations if expansion stops.
- A measurable community-commitment schedule: water, noise, traffic, emergency response, reporting, responsible parties, and legally available remedies.
- A release recommendation: proceed, proceed subject to specified evidence, redesign, defer, or reject, with unresolved assumptions visible.
The result the owner should require
Annexation is a credible risk-reduction strategy when it secures approvals the project can use, services the providers can deliver, obligations the investment can support, and conditions the community can verify.
It is not credible when its principal justification is that a new line on the map will protect the campus from Austin.
Choose a municipality because it offers a workable development framework, not because it appears to be a hiding place from the next law.
Connect the decision to the work
- Resolve the technical dependencies: Annexation, ETJs and CCNs: who controls each campus dependency? explains the authority, provider, connection, and off-site interface record.
- Advance the approval and development scope: Entitlements & community explains how Sitebraid connects the work; Entitlements stalled describes the problem when approvals cannot advance.
- Commission the site-specific decision package: Site selection & assessment tests jurisdiction options alongside mapped constraints, infrastructure alternatives, capacity scenarios, and phased costs.
Sources and status
Research reviewed September 11, 2026. This is development-strategy analysis, not legal advice. Applicability depends on the parcel, municipality, provider, project scope, and current law. Have project counsel confirm authority, vesting, procedures, agreements, and remedies before reliance.
- Supervisor Briskman’s office, July 23, 2026: proposal for September 15 consideration. Official sponsor statement; not an adopted pause or final legal opinion.
- Loudoun County: Land Use Considerations. Published county guidance on moratoria and the March 2025 rules; not a Texas authority.
- Texas Tribune, June 30, 2026: Abbott’s rural data center remarks. Original reporting of a political position, not legislation.
- Office of the Governor, July 23, 2026: East Texas project withdrawal and development standards. Executive statement; its account is not a judicial finding or enacted statewide ban.
- ERCOT, September 9, 2026: M-A090926-01. Operational notice concerning large-load verification and Batch Zero.
- Texas Local Government Code, Chapter 231. County zoning authorities with specific geographic applicability.
- Texas Local Government Code, Chapter 232. County subdivision regulation; actual applicability and limits require project review.
- Texas Tribune, June 5, 2026: Hill County rescinds moratorium. Reporting of withdrawal and litigation, not a merits judgment.
- Texas Attorney General, RQ-0634-KP. February 24, 2026 request; website lists pending status, not an issued opinion.
- City of Temple, August 13, 2026: Data Center Development Considerations. Municipal statement describing local controls and limits of city authority.
- City of San Marcos, June 16, 2026 Council Recap. Official record of adopted code changes, including the data center prohibition.
- Texas Local Government Code, Chapter 43, §§43.0671–43.0673. Owner-requested annexation route and written services agreement.
- Texas Water Code, Chapter 13, §§13.247 and 13.255. Certificated service rights and conditional municipal single-certification procedures.
- Texas Local Government Code, Chapter 245. Project and permit protections, definitions, exemptions, and expiration provisions.
- Texas Local Government Code, Chapter 212, §§212.171–212.172. Applicability and requirements for specified ETJ development agreements.
- Texas Constitution, Article XI, §5. Limits on home-rule charters and ordinances inconsistent with general state law.