Skip to content

Changes

Planned and completed infrastructure changes for the eSHARS platform. For incident response, see Incident Response.

Lifecycle

proposed → approved → scheduled → executing → verifying → completed

The git PR review is the approval process — no separate board. Each change lives as a markdown file; the PR merging it means it’s approved.

Scheduled

DateTypeTitleEnvironmentRiskStatus
2026-03-31networkProd SSRS VNet IntegrationprodLOWScheduled

Completed

DateTypeTitleEnvironmentOutcome
2026-04-17securityNonprod Bastion DecommissionnonprodSuccess — bastion-eshars-nonprod deleted; AzureBastionSubnet retained; VPN is sole access path
2026-04-16migrationNonprod SSRS VM ProvisionnonprodSuccess — vm-eshars-ssrs-np-cus deployed; pipeline cutover + vm-sql16-np decommission pending
2026-03-26migrationAthenaPractice Datacenter MigrationprodSuccess — no code changes needed; DNS handled automatically

Maintenance Windows

WindowTime (CDT)Notes
Weekday after-hoursAfter 5:00 PMPreferred for low-risk changes
WeekendAnytimePreferred for high-impact changes
Avoid7:00 AM – 4:00 PM CDTSchool hours — users active
AvoidMonth-end (last 3 days)Medicaid billing cycle — TMHP submissions in flight
AvoidSemester transitionsHigh-volume visit activity

Change Types

TypeExamples
networkVNet integration, subnets, NSG rules, private endpoints, App Gateway
securityCredential rotation, firewall changes, Defender remediation, cert renewal
capacityVM resizing, DTU scaling, disk changes, App Service plan changes
migrationDatacenter moves, database migrations, EOL replacements, app upgrades
maintenancePatching, config updates, cleanup, runbook-driven automation