Microsoft Files 910,000-Sq-Ft ATL50 Data Center Plan

Microsoft is named as the developer of ATL50, a proposed 910,000-square-foot data center campus at 5235 Stonewall Tell Road in Union City, Georgia. The initial state filing describes two three-story buildings on 88.01 acres, west of Stonewall Tell Road and north of Koweta Road. Union City submitted the proposal on September 15, 2026, under Development of Regional Impact number 4843. The filing gives contractors a specific project and address to research before the delivery team and trade packages become public.

The source is the initial DRI information form. At LVN's September 23 review, the application history still showed an initial submission. Construction authorization, a field start, electrical capacity, project cost and contractor awards remain unverified. The proposal identifies data-center use; it does not disclose an AI tenant, accelerator deployment or specific computing workload.

What Microsoft has proposed in Union City

Item	Filed detail	Qualification
Project	ATL50	DRI 4843
Location	5235 Stonewall Tell Road	Union City, Georgia
Buildings	Two, three stories each	Proposed configuration
Total floor area	910,000 square feet	Both buildings combined
Site	88.01 acres	Filed site acreage
Completion	2032	Planning estimate
Power and budget	Undisclosed	No verified MW or cost

The scale matters for early business development, but square footage alone cannot establish the value of a cabling package. Equipment layouts, building services, room classifications, phasing and responsibility boundaries determine what a specialty contractor could actually price. Applying a generic percentage to an undisclosed construction budget would create false precision. LVN is leaving both project investment and low-voltage contract value open until a defensible basis appears.

The 2032 figure is the form's overall completion estimate. It should be treated as a planning year rather than a committed opening or energization date. The separate phase-completion field contains the value “1,” which supplies no usable schedule. A contractor needs later design and procurement milestones to understand when estimating, qualification, purchasing and mobilization might become practical.

The review record is still at the beginning

The application summary names the Atlanta Regional Commission and indicates Georgia Regional Transportation Authority jurisdiction. It records no additional-form submission, completeness certification, request for comments, regional finding or GRTA finding. These are observations about the public record reviewed on September 23. They do not resolve every separate municipal action that could exist outside that record.

The initial form marks a permit action and includes masterplan-review wording. Neither establishes that a permit has been issued. For firms deciding whether to spend estimating time, the useful next documents are the actual review materials, local decisions, approved drawings and procurement notices. Those documents can turn a broad development proposal into a scope with a buyer, a deadline and a contractual boundary.

The additional-information page is especially relevant to that transition. Its build-out value, employment, water, wastewater, energy-provider and peak electrical-load fields were unfilled at review. Blank fields leave the questions unanswered. They provide no basis for a zero-impact claim, an assumed utility agreement, a cooling strategy or a numerical estimate of eventual IT load.

Who is named, and where the delivery team is still unknown

Organization	Documented role	Evidence boundary
Microsoft	Named developer	Initial DRI filing
Union City	Submitting government	Local filing role
Atlanta Regional Commission	Regional review body	No finding recorded
GRTA	Jurisdiction indicated	No finding recorded
GC and design firms	Unverified	No sourced appointments
Installation contractors	Unverified	No sourced awards

Microsoft's developer role is explicit. The legal property-owning entity, eventual operating arrangements and tenant commitments need separate confirmation. A contact listed on a planning form is insufficient evidence of corporate land ownership. A title record or a project-specific company statement would provide a stronger basis for describing those relationships.

No reviewed source identifies an ATL50 general contractor, architect, civil engineer, MEP engineer, electrical contractor or low-voltage integrator. That gap also covers fiber, security, fire alarm, controls and commissioning appointments. Firms already working elsewhere in Microsoft's Georgia portfolio cannot be assumed to hold ATL50 work. A supplier interested in this campus should request a project-specific qualification route and verify the organization receiving that information.

Microsoft's Georgia community page describes its wider regional activity, including Douglasville, Palmetto and East Point. It is useful company context. Its regional commitments and other site updates do not establish ATL50's construction schedule, labor demand, utility performance or contractor roster.

Keep the neighboring campus and older warehouse plan separate

Stonewall Tell Road appears in more than one development story. Data Center Dynamics' September 17 report distinguishes ATL50 at 5235 from a separately reported Microsoft and EdgeConneX development at 4810 Stonewall Tell Road. The report associates 324 MW and approximately 2.1 million square feet with that other campus. Those figures do not establish ATL50's power capacity or area, and the report does not establish an EdgeConneX role at ATL50.

The ATL50 form also references historical DRI 2745, South Fulton Parkway at Stonewall Tell. That older filing describes a Majestic Realty warehouse and distribution proposal across 221.8 acres, with five buildings totaling 2,095,000 square feet. It is useful land-use history. Majestic's role and the older plan's dimensions should remain attached to that proposal.

For a salesperson, estimator or recruiter, these distinctions prevent a practical error: combining one site's developer, another site's capacity and a third announcement's schedule into a single opportunity. Use the ATL50 identifier, DRI number and filed address when checking later records. Ask which building, parcel and phase a new announcement actually covers before adding it to a pursuit.

Where low-voltage work could emerge

The following scope is LVN's analysis of prospective coordination needs for the proposed facility type. The filing does not provide installed quantities, an open solicitation or a confirmed subcontract. The value for contractors is a focused set of questions to ask when design and procurement information becomes available.

Prospective scope	Coordination question	Evidence to obtain
Fiber and outside plant	Entrances and service routes?	Route plans and boundaries
Structured cabling	Spaces and cable quantities?	Schedules and specifications
Security systems	Doors, cameras and networks?	Device plans and integrator
Fire interfaces	System responsibility?	Approved design and scope
BMS and controls	Points and handoffs?	Sequences and point lists
Commissioning	Tests and acceptance owners?	Test and turnover plans

For outside-plant firms, early questions include the boundary between carrier work, civil pathways and customer-owned fiber. For inside-plant teams, the questions shift to room readiness, riser pathways, cable management, bonding and documentation. None of those questions can be priced reliably from the total building area. A pursuit becomes more useful when it identifies who owns each interface and which document defines acceptance.

Security and controls teams should look for the eventual division between equipment vendors, electrical trades, network teams and integrators. A device schedule alone may leave programming, network configuration, testing and turnover responsibilities unresolved. Likewise, a fire-protection design appointment would not automatically identify the fire-alarm installation contractor. At this stage, these are qualification topics for later documents.

Prospective bidders can prepare examples of completed work without inventing an ATL50 scope: fiber test records, clear labeling, coordinated pathway drawings, as-built documentation and commissioning closeout. The eventual buyer's requirements should drive staffing and certification decisions. Project-specific prequalification, insurance, access, safety and manufacturer requirements remain unknown.

Jobs, trades and practical preparation

No source-backed ATL50 construction-job count, permanent-job count or hiring calendar is available in the reviewed material. Readers should avoid turning a proposed floor area into an employment forecast. A vacancy tied to a different Georgia facility also would not establish an ATL50 opening. The useful employment signals will identify the employer, work location, trade, phase and expected start.

There is a real regional training development to distinguish from those unknowns. Microsoft says two Datacenter Academy facilities opened on May 20, 2026, at Atlanta Technical College and West Georgia Technical College. Its Georgia workforce update describes training areas including datacenter operations, networking, cybersecurity and systems management. These are regional education pathways; the announcement does not designate either college as an ATL50 workforce partner or promise graduates a job at this campus.

For fiber-focused readers, the Fiber Optic Association's workforce resources provide background on installation, splicing, testing and training. BICSI's course catalog offers another place to research relevant education. Neither resource establishes an ATL50 certification requirement. Match training to the work you intend to perform, then confirm what the eventual project buyer actually specifies.

As a practical preparation exercise, a small contractor can assemble a concise capability package: relevant project examples, available supervision, testing equipment, document-control practices and the limits of self-performed work. Keep construction labor, equipment commissioning and ongoing facility operations distinct when presenting experience. That makes later conversations more specific without assuming a contract is available today.

What would make this opportunity actionable?

The next substantive evidence would address several separate questions: Does the additional DRI information establish utility requirements? Have regional and local review milestones advanced? Who controls the site? Which organizations hold design and construction responsibilities? Are bid packages, qualification windows or delivery dates available? Each answer changes how much time a contractor should invest and which team should engage.

Power deserves particular attention because a building plan does not demonstrate an energized service commitment. Future disclosures should identify the provider, the basis of any MW figure, infrastructure obligations and the relevant delivery milestone. Water and wastewater details need the same source-specific treatment. A general company pledge should not substitute for the documents describing this campus.

ATL50 offers an identifiable early-stage project to follow: a named developer, an address, two proposed buildings and a current planning record. Use LVN Signal to research construction projects and company relationships, then qualify the opportunity against current source documents. For this proposal, the immediate value is knowing which questions remain open before committing estimating effort, hiring assumptions or a bid.

Featured and social artwork are AI-generated concept illustrations. They do not depict an approved ATL50 design or document construction activity.