Microsoft Corporation - East Coast Data Center
101 HERBERT DRIVE
Parcel boundary
Recorded as in service.
Status inferred from osm footprint+epa permit (Sun, 06 Se). No filing states it in as many words.
- Status
- Operating (inferred)
- Owner
- Microsoft
- Capacity
- 14 MW directory claim
- Location known to
- Parcel boundary
- County
- Mecklenburg County
- State
- Virginia
- Electric utility
- Not identified
- Grid operator
- PJM
Location and nearby
Microsoft Corporation - East Coast Data Center is on record as operating in Mecklenburg County, Virginia. A directory lists its capacity at 14 MW; no filing we hold states a figure. 14 other campuses are on record within 25 miles, 7 of them within 5 miles. The nearest is 0.50 mi away.
Nearest of each kind: Operating 0.50 mi Permitted 1.3 mi Proposed 1.7 mi
Nearest campuses on record
- 0.50 mi
Operating · Mecklenburg County, VA
- 1.0 mi approximate
Operating · Mecklenburg County, VA
- 1.2 mi
Microsoft Corporation - Timber Data Center (52903)
Operating · Mecklenburg County, VA
- 1.2 mi approximate
Operating · Mecklenburg County, VA
- 1.3 mi approximate
Microsoft Corp - LYH10 Datacenter
Permitted · Mecklenburg County, VA
- 1.6 mi approximate
Operating · Mecklenburg County, VA
What is on record
Owner
Microsoft Strong
The chain
-
permittee name as filed with EPA
MICROSOFT CORPORATION - EAST COAST DATA CENTER
EPA ECHO Exporter, all facilities (weekly refresh) · Sep 6, 2026
Filed by: MICROSOFT CORPORATION
- Address on file
- 101 HERBERT DRIVE
- Capacity
- 14 MW as reported by cleanview, not from a filing
- Diesel generators
- Air permit on record VA0000005111700071
- Water
- Not collected. State water withdrawal permits are not in this build.
- Electric utility
- More than one utility serves this county, and no filing we hold names which one
- Also recorded as
- EAST COAST DATA CENTER · MICROSOFT CORP - LVL DATA CENTER · MICROSOFT CORPORATION - EAST COAST DATA CENTER · Microsoft East Coast BN1 · Microsoft East Coast BN3 · Microsoft East Coast BN80 and 9 more
Buildings and phases
9 distinct buildings, parcels or permits make up this campus.
| Name or address | Status | Permit | Area | Date |
|---|---|---|---|---|
| Unnamed data center (way/1074588578) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588579) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588580) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588582) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588583) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588584) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588585) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1074588586) | Operating | not stated | not stated | Jul 9, 2026 |
| Unnamed data center (way/1307454847) | Operating | not stated | not stated | Jul 9, 2026 |
How the status changed
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
osm footprint
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Jul 9, 2026 inferred
OSM footprint plus EPA permit
Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Operating Sep 8, 2026 inferred
Cleanview status 'Operating'
Cleanview state pages: facility markers (id, name, coordinates, status, MW, county)
- Permitted Sep 6, 2026
epa air permit active
- Permitted Sep 6, 2026
epa air permit active
About this data
Evidence
Primary record
A government filing, a federal permit, an assessor parcel or the operator’s own page.
Location known to
Parcel boundary
Matched to an assessor parcel, so the boundary is the parcel.
Independent sources
4
assessor parcel, directory, federal permit, osm footprint. Directories count once between them, because they copy each other.
Spotted something wrong? Tell us and we will fix it.
Where this comes from
15 source records back this page. Each row is a document we retrieved and kept, so a claim can be checked against the original.
| Document | Role | Row | Date |
|---|---|---|---|
| EPA ECHO Exporter, all facilities (weekly refresh) US | Primary | REGISTRY_ID=110042150524 | Sep 6, 2026 last changed on the server |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588578 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588579 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588580 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588582 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588583 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588584 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588585 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1074588586 | Jul 9, 2026 stated in the file |
| Overpass data_center query, tile conus-e1 bbox 24.0,-85.0,50.0,-75.0 US | Primary | osm=way/1307454847 | Jul 9, 2026 stated in the file |
| Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US | Primary | id=2897 | Sep 8, 2026 retrieved by us |
| Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US | Primary | id=2899 | Sep 8, 2026 retrieved by us |
| Cleanview state pages: facility markers (id, name, coordinates, status, MW, county) US | Primary | id=2911 | Sep 8, 2026 retrieved by us |
| EPA ECHO Exporter, all facilities (weekly refresh) US | Primary | REGISTRY_ID=110071240991 | Sep 6, 2026 last changed on the server |
| Virginia statewide parcels (VGIN) (point queries) US-VA assessor parcel 3675, owner of record None, match pin_on_facility | Corroborating | query=36.67659,-78.37243 | Sep 9, 2026 retrieved by us |
Cleanview (cleanview.co)
Free email alerts
Know first when a data center is recorded in Mecklenburg County
Each time we refresh the public records and a new campus appears in Mecklenburg County, you get one short email naming it, with the document behind it.