DataOne Unpermitted Generators Put Microsoft’s AI Capacity Deal Under Scrutiny
DataOne operated at least 45 gas-powered generators without state air permits, according to thermal footage from its partly completed Vineland data center. New Jersey regulators confirmed that they had neither approved permits nor received applications covering the power equipment.
The DataOne unpermitted generators controversy reaches beyond one construction site. The facility is intended to supply dedicated AI computing capacity to Nebius, which has a multiyear infrastructure agreement with Microsoft. That arrangement places pressure on DataOne to finish quickly, even as regulators examine how the site generated electricity.
The unresolved question is whether Vineland represents a temporary permitting failure or a repeatable model for accelerating AI infrastructure. Data centers increasingly seek their own power because utility connections and grid upgrades cannot match their construction schedules.
That approach can reduce dependence on an overloaded grid. It can also move pollution, permitting disputes, and operational risks directly into nearby communities.
What Investigators Found at the DataOne Site
The central fact is straightforward: state regulators found power-generating equipment at DataOne, but they had not issued permits for it.
Thermal drone footage captured in August showed at least 45 of the site’s 62 generators operating simultaneously. The images came from a joint investigation by Floodlight and The Guardian into the Vineland project.
Thermal imaging detects heat emitted by operating equipment. It provided evidence that generators were active, rather than merely parked at the site for future deployment.
The thermal investigation described the units as gas-powered generators roughly comparable in size to tractor-trailers. The equipment was supporting a data center that remained partly under construction.
The New Jersey Department of Environmental Protection, or NJDEP, had already seen natural-gas power equipment during a July 29 inspection. The department subsequently asked DataOne for more information.
NJDEP told reporters that it had issued no permits for power generators at the facility. It also said no generator permit applications were under review when the investigation appeared.
That confirmation does not constitute a completed enforcement ruling. The department said it would determine compliance after reviewing the information requested from the facility.
This distinction matters. The evidence establishes that equipment was operating and permits were absent. It does not establish which penalties, operating restrictions, or corrective measures NJDEP will ultimately impose.
Bruce Buckheit, a former Environmental Protection Agency air-enforcement chief, offered a stronger assessment. He said federal and state rules required final authorization before the generators were brought onsite and operated.
Buckheit told Floodlight that the activity violated federal law and should trigger an immediate shutdown and financial penalty. That represents an expert legal interpretation, not a final agency judgment.
The EPA gave the investigation a narrower response. It said New Jersey regulators held responsibility for air permitting at the DataOne facility.
DataOne did not answer the detailed questions about the generators. It said that the company remained committed to applicable environmental and permitting requirements.
Nebius did not provide a response before the original investigation was published. Microsoft declined to comment.
The operating timeline remains incomplete. Maintenance records reviewed by Floodlight suggested that the first generator began running in October 2025. Separate thermal imagery appeared to show 25 units active in late June 2026.
Those observations indicate that the August footage was not necessarily an isolated test. However, publicly available evidence does not establish continuous operation throughout that entire period.
It also remains unclear how DataOne classified each generator. The difference between emergency backup, testing, construction support, and routine power generation affects the rules that apply.
Federal regulations permit emergency engines to run during genuine emergencies. They also allow limited operating hours for maintenance, testing, and certain non-emergency circumstances.
Regularly supplying a data center is a different use. If DataOne relied on the generators as its ordinary power source, emergency-use exemptions would not automatically cover that operation.
The site’s size makes collective emissions another significant issue. A single generator and a fleet of 62 units can face different permitting consequences when regulators calculate total potential emissions.
That is why NJDEP’s compliance review matters more than the label placed on each machine. The agency must evaluate the equipment, operating hours, fuel, emissions, and relationship among the units.
Why DataOne Needs So Much Power Before Construction Ends
Vineland exposes the schedule mismatch between AI computing contracts and the infrastructure required to power them.
DataOne is developing the facility for Nebius, an Amsterdam-based AI infrastructure provider. Nebius plans to use the campus to deliver dedicated graphics-processing capacity to Microsoft.
A graphics processing unit, or GPU, is a chip optimized for parallel calculations used in training and running AI models. Large GPU clusters require substantial electricity, cooling, networking, and backup capacity.
Nebius signed its Microsoft agreement in September 2025. Its regulatory filing states that capacity would arrive in several tranches during 2025 and 2026.
The five-year agreement carries a base contract value of approximately $17.4 billion through 2031. Optional additional services could increase its value to approximately $19.4 billion.
Those amounts depend on deployment and availability. The agreement allows Microsoft to terminate an undelivered service tranche after a grace period if Nebius cannot provide alternative capacity.
That provision turns construction delays into direct commercial risk. A late electrical connection does not simply postpone a building opening. It can threaten contracted revenue and a major customer relationship.
DataOne’s proposed Vineland campus has a planned capacity of 300 megawatts. One megawatt equals one million watts, although actual consumption changes with workload and operating conditions.
At that scale, a data center resembles a major industrial power user. It cannot begin meaningful AI operations using a routine commercial connection.
DataOne initially proposed more than 30 Bergen natural-gas engines. These large engines are also used in marine applications, including propulsion systems for ships.
NJDEP identified deficiencies in the air-permit application for that plan. DataOne withdrew the application in May 2026 and changed its primary generation strategy.
The replacement plan uses Bloom Energy fuel cells with a combined planned output of 300 megawatts. A fuel cell converts fuel into electricity through an electrochemical reaction rather than conventional combustion.
Fuel cells generally release less nitrogen oxide and sulfur oxide than large gas engines. However, gas-powered fuel cells still release carbon dioxide and do not represent carbon-free generation.
A Bloom representative testified that the proposed Vineland array could emit more than two billion pounds of carbon dioxide each year. That estimate applies to the completed fuel-cell plan, not the temporary generators.
DataOne also pursued a large liquefied natural gas storage system to support onsite generation. Vineland later issued stop-work notices concerning work associated with the fuel cells and gas-storage infrastructure.
The fuel cells were intended to replace temporary generation. Yet their own construction became part of the permitting dispute.
That sequence created a difficult operational loop. DataOne needed temporary power because its permanent system was not ready, while disputed work slowed the system intended to replace that temporary power.
The DataOne unpermitted generators therefore cannot be separated from the project’s delivery schedule. The generators appear to be the bridge between a contracted AI capacity deadline and incomplete permanent infrastructure.
DataOne has not publicly explained exactly which workloads the generators supported. It has also not specified whether the equipment powered construction, testing, initial computing operations, or several functions.
That missing operational detail is important. It determines how closely the activity connects to Nebius’s delivery obligations and Microsoft’s access to GPU capacity.
DataOne Unpermitted Generators Test the Bring-Your-Own-Power Model
AI developers are compressing computing schedules by moving electricity generation onsite, but power plants bring a different regulatory burden.
The strategy is often called bring your own power. Instead of waiting for a full utility connection, a data center installs generation behind its electrical meter.
Behind-the-meter power is produced and consumed within a customer’s site rather than delivered through the wider transmission system. It can include gas turbines, engines, fuel cells, solar equipment, batteries, or several technologies combined.
This approach addresses a genuine infrastructure constraint. New transmission lines, substations, transformers, and generating plants can take years to approve and build.
AI computing projects often move on much shorter schedules. A customer may want GPU capacity within months, while a utility cannot promise adequate grid service for several years.
Onsite generation closes part of that gap. It can also protect households from paying directly for network upgrades created by one unusually large customer.
The tradeoff is that the data-center developer begins acting like a power producer. It must handle fuel delivery, air rules, safety reviews, noise limits, equipment maintenance, and community exposure.
Those responsibilities do not disappear because electricity supports AI. They become more visible because generation occurs beside homes, farms, schools, and local roads.
DataOne is the first New Jersey data center seeking to construct its own power plant. Its regulatory path will influence how other developers judge the state’s tolerance for behind-the-meter generation.
The project is not an isolated national experiment. Energy research has identified dozens of proposed data centers pursuing dedicated gas generation.
A project review by Cleanview examined developers considering private power plants and mobile gas turbines. It estimated that behind-the-meter data-center capacity would reach three gigawatts by the end of 2026.
Some projects will never reach operation. Developers frequently announce generation plans before securing permits, fuel, equipment, financing, or final customers.
Still, the direction is clear. AI infrastructure developers increasingly treat electricity as a component they must procure directly, rather than a service automatically supplied by the grid.
The closest precedent is xAI’s data-center expansion around Memphis, Tennessee, and neighboring Mississippi. That project also used mobile natural-gas turbines while permanent power infrastructure developed.
Environmental groups accused xAI of operating numerous turbines without proper air authorization. The dispute became a national example of AI construction moving faster than conventional regulatory review.
Vineland differs in ownership, technology, local rules, and customer structure. Microsoft does not own or operate DataOne, while Nebius is contracting for capacity from the developer.
Yet the operational logic resembles the Memphis approach. Both projects used modular generation to place computing equipment into service before permanent electricity systems were complete.
Portable or modular generators can arrive much faster than a conventional power plant. A fleet also scales incrementally because developers can activate additional units as computing demand rises.
Regulators then face questions that permitting systems were not designed to answer quickly. Is each unit separate, or should authorities evaluate the entire fleet as one source?
A portable engine can also become legally stationary after remaining at one location for a defined period. Equipment mobility does not guarantee permanent exemption from stationary-source regulation.
The EPA’s engine rules distinguish stationary engines by age, ignition type, location, emissions, and intended use. Emergency classification also brings operational limits and recordkeeping requirements.
NJDEP separately reminds facilities that emergency generators above 37 kilowatts face testing and maintenance restrictions. Even equipment without a conventional air permit can remain subject to operating rules.
This complexity is not an excuse for missing permits. It does explain why the final compliance decision requires more than counting machines in drone footage.
NJDEP must determine whether the generators were portable, stationary, emergency, temporary, or part of a combined major source. It must then compare actual operation with the applicable limits.
The industry will watch that analysis closely. A strict collective interpretation would make generator fleets harder to deploy as temporary AI power.
A narrow unit-by-unit interpretation could preserve more flexibility. It could also intensify community concerns that developers are dividing one industrial power system into smaller regulatory pieces.
The Commercial Promise Now Collides With Local Reality
The primary conflict is no longer Microsoft versus another cloud company. It is rapid AI delivery versus the credibility of responsible infrastructure promises.
Microsoft announced a Community-First AI Infrastructure initiative in January 2026. The company said successful construction required communities to believe that local benefits outweighed local costs.
Its five commitments covered electricity costs, water use, jobs, tax revenue, and local investment. Microsoft also promised earlier engagement with utilities and greater transparency around infrastructure needs.
The wording creates an important limitation. Microsoft described the commitments as applying to data centers that it builds, owns, and operates.
DataOne owns and develops the Vineland facility. Nebius provides the infrastructure capacity, while Microsoft is the contracted customer.
That structure gives Microsoft a plausible legal and operational separation from the alleged violations. It does not necessarily remove the reputational connection.
The Vineland project exists to serve a large Microsoft capacity commitment. Delivery deadlines in Nebius’s agreement provide a commercial incentive for the project to become operational quickly.
Microsoft therefore benefits from accelerated delivery even if it does not select each generator or submit each permit. Residents and campaigners see the customer’s demand as part of the causal chain.
Microsoft declined to comment on the generator allegations. That response leaves unclear whether it has asked Nebius or DataOne for compliance records, operating data, or a corrective timeline.
The silence also complicates the community-first message. A promise about responsible AI infrastructure has limited force if it addresses only sites held directly on Microsoft’s balance sheet.
Cloud companies increasingly rent capacity from specialist providers. Those arrangements let them expand without owning every building, generator, cooling system, or parcel of land.
Responsible-infrastructure standards must therefore address contractors and capacity partners. Otherwise, environmental and community risks can sit outside the boundary used for public commitments.
Nebius faces a related test. Its filing emphasizes deployment dates, service availability, and Microsoft’s termination rights.
The filing does not describe environmental violations as a delivery method. However, its deadlines illustrate the pressure carried through the contracting chain.
DataOne absorbs that pressure at the construction site. Local residents absorb the noise, emissions, traffic, water concerns, and uncertainty created by the resulting work.
Vineland officials have also emphasized potential benefits. DataOne says the facility will create more than 200 permanent full-time jobs and become one of the city’s largest taxpayers.
The mayor and City Council president have supported the project. The city approved a partial tax exemption through a five-year arrangement.
Those benefits make the dispute more complicated than a simple contest between technology and environmental protection. Local governments want investment, employment, and a larger tax base.
Residents want enforceable limits and accurate information before industrial systems begin operating near their homes. The two positions are not inherently incompatible.
Trust becomes the scarce resource when approvals trail activity. Residents can reasonably question later assurances after generators operate without applications under review.
Vineland residents had already complained about a persistent humming or metallic sound. A class-action lawsuit alleges harmful nighttime noise, although the generators have not been conclusively identified as its sole source.
The Cumberland County health department cited DataOne for nighttime noise violations in March, according to court filings reviewed by reporters. The city later issued two stop-work orders involving other construction.
Each episode has its own legal facts. Together, they create a pattern that makes the generator explanation harder for the developer to contain.
DataOne’s broad statement about following applicable requirements does not answer the immediate questions. It does not identify the legal exemption claimed, operating hours, emissions, fuel consumption, or shutdown conditions.
A credible response would need more than reassurance. It would need records that regulators and residents can compare against the site’s actual activity.
What the Generator Count Does Not Prove
The evidence creates a serious permitting question, but it does not resolve every technical, legal, or health claim surrounding DataOne.
Thermal footage shows that numerous generators were hot and apparently operating. It does not directly measure nitrogen oxides, carbon monoxide, particulate matter, hazardous pollutants, or carbon dioxide.
No public stack-testing results have established the actual emissions from those units. Fuel type, engine model, load factor, pollution controls, and operating duration all affect the total.
The observation of 45 active generators also captures one period. It cannot prove that the same number operated continuously every day or night.
Maintenance logs and earlier thermal imagery suggest a longer history. Regulators still need complete operating records to establish duration and purpose.
The legal conclusion also remains open. NJDEP explicitly said that its compliance determination was pending.
The department may find that one or more permits were required before installation or operation. It may also identify distinctions among the units or activities that change the applicable requirements.
Steve Gold, an environmental lawyer and Rutgers University professor, explained that federal obligations depend partly on total potential pollution. His comments in the local reporting focused on whether the combined equipment qualifies as a major emissions source.
If the fleet crosses that threshold, a permit could require more stringent pollution controls. Regulators would also consider whether separate units should be aggregated as one facility.
Proximity increases the stakes without proving individual harm. The DataOne site sits approximately one mile from two schools and near homes and agricultural land.
Gas engines emit pollutants associated with respiratory and cardiovascular risks. However, a responsible assessment needs measured concentrations, dispersion modeling, exposure periods, and baseline local air data.
The same caution applies to resident noise complaints. People have described an ongoing hum that disrupted sleep and family routines.
Those reports deserve investigation. They do not independently establish which machines produced every reported sound or the precise contribution of the generators.
The permanent fuel-cell plan creates another area for careful comparison. Fuel cells avoid conventional combustion and usually emit less local air pollution than gas engines.
They still consume natural gas and release carbon dioxide. Calling them cleaner than reciprocating engines does not make them emissions-free.
The projected two billion pounds of annual carbon dioxide is a facility estimate for the proposed array. Actual emissions will depend on completed capacity, utilization, fuel characteristics, and equipment performance.
The LNG storage plan introduces separate safety and land-use questions. Those issues should not be treated as proof of a generator violation because they follow different approval processes.
Similarly, stormwater and groundwater concerns require their own engineering evidence. Combining every complaint into one allegation would weaken the strongest verified point.
That point remains significant on its own. NJDEP saw power equipment, confirmed the absence of generator permits, and requested additional information.
DataOne can narrow the controversy by publishing equipment inventories, permit analyses, fuel records, and hourly operating logs. It can also explain which systems supplied construction loads and which supported computing.
Nebius can disclose whether Vineland capacity has entered paid service and whether permit issues affect delivery milestones. Microsoft can explain how supplier compliance fits its infrastructure commitments.
Until those disclosures arrive, strong conclusions in either direction would be premature. The generators should not be declared lawful merely because a final violation has not been issued.
They should also not be described as definitively causing specific illnesses without exposure evidence. The accountable position is to demand the records needed for both judgments.
Three Signals Will Show Whether Vineland Changes AI Infrastructure
The next stage will be decided by regulatory action, the permanent power transition, and customer oversight.
The first signal is NJDEP’s compliance determination. The agency has the authority and site-specific information needed to decide which state and federal requirements apply.
An enforcement notice, permit order, fine, or operating restriction would strengthen the case that DataOne placed delivery speed ahead of authorization. It would also warn other developers against using large generator fleets before completing reviews.
A finding that no permit was required would weaken the central legal allegation. Such a decision would need a detailed explanation of equipment classification, operating purpose, and applicable exemptions.
A delayed or opaque decision would preserve uncertainty. It could also encourage other projects to treat enforcement timing as part of their construction strategy.
The second signal is the transition to Bloom fuel cells. DataOne must obtain the necessary local and environmental approvals before the permanent system can replace temporary generation.
A documented fuel-cell commissioning schedule would show that the generators served a limited bridge role. It would not erase earlier violations, but it would define their endpoint.
Further stop-work orders or permitting deficiencies would extend reliance on temporary power. They would also increase pressure on Nebius’s delivery obligations.
Watch the actual operating data rather than an announced completion date. The important indicators are fuel-cell output, generator hours, removed units, and permitted emissions.
The third signal is how Nebius and Microsoft manage contractor accountability. Neither company had provided a detailed public response when the investigation appeared.
Nebius can require DataOne to demonstrate compliance before counting the facility as available capacity. It can also disclose whether regulatory delays affect the service tranches promised to Microsoft.
Microsoft can clarify whether its community-first principles cover contracted facilities that primarily serve its workloads. A supplier standard with audits and public reporting would strengthen its responsible-infrastructure message.
Continued silence would produce the opposite effect. It would suggest that public commitments stop where formal ownership ends, even when Microsoft’s demand drives construction.
The DataOne unpermitted generators case matters because outsourced infrastructure is becoming central to AI expansion. Hyperscalers cannot evaluate responsibility only inside the sites they directly own.
Developers, customers, regulators, and communities need a shared record of how temporary generation operates. That record should include equipment, hours, emissions, permits, complaints, and transition dates.
For enterprise buyers, the lesson extends beyond electricity. AI capacity carries regulatory, operational, and reputational dependencies that standard performance specifications do not capture.
Teams should ask where computing runs, who supplies its power, and which party monitors compliance. Procurement deadlines should include environmental and community risks alongside availability targets.
The immediate action is simpler. Watch NJDEP’s decision first, then compare it with generator activity and the fuel-cell schedule.
If the generators stop and permanent power receives approval, Vineland may remain a contained permitting failure. If temporary operation continues without transparent authorization, it becomes a model other communities will confront.
The final question is whether AI infrastructure customers will treat lawful, locally accountable power as a delivery requirement. The DataOne generator controversy will show how much that requirement matters when capacity deadlines are already binding.



