In plain English
Who it covers: Anyone proposing a data center in Phoenix. The 26 June 2025 draft limits data centers to the C-2, C-3, CP/GCP, A-1 and A-2 zoning districts, with a special permit, which the City Council may grant after a Planning Commission recommendation. The final minutes say a waiver process was also part of the adoption.
What it provides: Phoenix's zoning rules had not defined data centers or listed them as a permitted use, and they were handled by informal interpretation. This ordinance adds a definition, design standards and special permit conditions. The Council approved it per a 1 July 2025 memo from the Planning and Development Director.
About these figures: These figures are not confirmed as the adopted numbers. They come from a draft the city marked as not the official copy, and the Council acted on a later 1 July 2025 memo that is not among the attachments posted with this item. The minutes also say a waiver process was part of the adoption, and this draft has none.
- Distance from transit (26 June 2025 draft): No closer than 2,640 feet from an approved high-capacity transit station (Section 647.A.2.KK(1))
- Power supply (26 June 2025 draft): No preliminary site plan approval until a local utility provides a contractual agreement affirming its capacity and commitment to serve the data center's energy demand (Section 647.A.2.KK(2))
- Noise near homes (26 June 2025 draft): On sites within 300 feet of a residential zoning district: no more than 5% above the existing ambient noise level for the site, or a specific noise standard set as a special permit condition (Section 647.A.2.KK(3))
- Equipment setback (26 June 2025 draft): Mechanical equipment at least 150 feet from abutting right-of-way or residentially zoned property, and fully screened (Section 507 Tab A.II.D, item 5.1)
- Not counted as a data center (26 June 2025 draft): A facility of no more than 10% of the gross floor area of all on-site buildings that serves the on-site owner's enterprise functions and does not lease data services to third parties (Section 202)
- Not covered (26 June 2025 draft): Data centers with final site plan approval, or a data center use specifically listed or discussed in a Council adopted planned unit development narrative, before the effective date (Section 647.A.2.KK(4))
Written from Draft ordinance text, Exhibit B to the 26 June 2025 Planning and Development memo, read on 3 November 2026. A reading aid, not legal advice. The document controls.
Summary
The Phoenix City Council adopted Ordinance G-7396 (Z-TA-2-25-Y) on 2 July 2025. It adds a zoning definition for data centers, design standards, and a requirement that data centers in the C-2, C-3, CP/GCP, A-1 and A-2 districts obtain a Special Permit and meet performance standards such as noise limits and spacing from high-capacity transit. The city's legislative record shows the ordinance as adopted; the adopted exhibit and a legal effective day were not opened.
Scope
Phoenix Ordinance G-7396 (text amendment Z-TA-2-25-Y), adopted by the City Council on 2 July 2025, amends the Phoenix Zoning Ordinance to add a definition for data centers, add design standards for data centers to the city-wide design review guidelines, and add data centers as a Special Permit use in the C-2, C-3, CP/GCP, A-1 and A-2 zoning districts with performance standards. It applies only in Phoenix.
- Geographic scope
- Phoenix, Arizona
- Jurisdiction
- Local
- Authority type
- Local government
- Issuing authority
- Phoenix City Council
Dates
- Adopted
- 2 July 2025
- Effective
- Effective status not verified
- Scheduled expiration
- See completion condition
- Ended
- Not recorded as ended
- Completion condition
- The legislative record states no expiration and no separate effective day.
- Source document
- 2 July 2025
- Last checked
- 3 November 2026
About this date
This record was last checked before the tracker date, 16 November 2026. An earlier check date does not by itself mean the record's status has changed.
What this does not establish
- The primary source is the City Clerk's Legistar record (status Adopted, final action 2 July 2025), not the adopted ordinance exhibit.
- No effective day is stored because the record does not state one; the ordinance was adopted more than a year before this review.
- The final minutes say the Council approved the ordinance, 9 yes and 0 no, per a 1 July 2025 memo from the Planning and Development Director, and that a waiver process was part of the adoption. That memo and the adopted text could not be read. The 26 June 2025 draft has no waiver section, so the adopted figures may differ from it.
Unresolved questions
- When the ordinance took effect was not established: the legislative record states no effective day, and the adopted text could not be read.
Relationships
Supersession means a later instrument replaces the earlier legal effect. Repeal links identify the repeal instrument and the measure it ends. A later implementation or related letter is not treated as a replacement unless the record says so.
- No related action is recorded.
Sources
Primary source: Phoenix City Council page on phoenix.legistar.com
- Draft ordinance text, Exhibit B to the 26 June 2025 memo — draft, not the adopted text; read on 3 November 2026 · 26 June 2025
- Phoenix City Council final minutes, 2 July 2025 — records the vote and the 1 July 2025 memo; read on 3 November 2026 · 2 July 2025