Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Coverage ended on October 13, 2026. Microsoft identifies that day’s security update as the final ESU update.
- Azure Arc’s 2012 ESU licenses deactivate at 00:00 UTC on October 14, or 08:00 in Beijing. This three-year program does not include a fourth-year renewal.
- The stated 2012/R2 scope covers Standard and Datacenter, excludes Windows Server 2012 Storage, and does not make Arc ESUs available in Azure regions operated by 21Vianet.
- Purchase dates and availability of historical-year licenses are separate from update coverage. A transaction does not extend the support period.
- Installed final updates, eligibility to install missing historical updates and account rights need separate checks. Windows 10 and Windows Server 2016 follow different schedules.
Security update coverage has ended
ESUs—Extended Security Updates—provide a temporary bridge while organizations move away from older systems. Microsoft’s current Azure Arc guide says the three-year Windows Server 2012 and 2012 R2 ESU period ends on October 13, 2026. The security update dated October 13 is the final update provided through that program.
Azure Arc-enabled 2012 ESU licenses deactivate at 00:00 UTC on October 14, 2026, and stop providing update eligibility. That is 08:00 in Beijing; convert the UTC time for your own location. Connecting a server to Arc or buying historical-year coverage does not establish a fourth year.
Identify the servers that fall within this scope
Start with your server inventory or system information. Confirm the actual product, edition and workload, distinguishing 2012 from 2012 R2 and Standard from Datacenter. Microsoft excludes Windows Server 2012 Storage from the stated ESU eligibility. A product name containing 2012 is not enough to establish the same licensing scope.
Match each machine’s actual ESU arrangement to existing licensing and purchase records. An Arc connection requires an Azure account, but a connected server is not proof of ESU eligibility. Arc ESUs for Windows Server 2012/2016 are currently unavailable in Azure regions operated by 21Vianet; conditions in other Azure regions cannot be assumed to apply there.
Keep purchasing requirements separate from coverage dates
The Arc guide lists Software Assurance through volume licensing or Microsoft Open Value programs among ESU purchasing requirements. For 2012/R2 machines licensed through SPLA or a Server Subscription, Software Assurance is not required to purchase ESUs. These are licensing conditions, not a promise of new updates after coverage ends.
Partner Center distinguishes coverage dates from catalog availability and the billing dates shown after purchase. ESUs for expired coverage years can still be available as perpetual software. In a hypothetical example, a purchase recorded after a coverage end date must still be matched to the year it covers; the transaction date is not a new support period. No real account is involved in this example.
Check the final update’s installation result
In your existing update-management tools, check the installation record and outcome for the final applicable October 13, 2026 security update against each machine’s actual 2012 or 2012 R2 version. Record completed, failed and missing updates separately. Connected to Arc or downloaded is not the same as installed.
Microsoft’s Arc guide says update delivery still needs Microsoft Update, WSUS or another patching solution configured; Azure Update Manager can also deliver updates. It requires the applicable licensing preparation package and servicing stack update, or SSU—the update infrastructure needed to install patches. Match the KB and prerequisites to the actual system.
These two documents do not provide a complete post-expiry installation procedure for every historical patch or establish an individual account’s entitlement. For a missing update, confirm the exact KB, existing coverage year and available delivery route with Microsoft Support or your licensing channel before acting. Preparation steps from before expiry are not proof of eligibility afterward.
Windows 10 and Server 2016 have separate timelines
Partner Center lists Windows 10’s second ESU year as starting on October 14, 2026. That is another product’s coverage period, not a fourth year for Windows Server 2012/R2. A Windows 10 annual offer does not change the 2012/R2 end date.
Windows Server 2016 has its own support deadline and ESU schedule. The Arc guide says its support ends on January 12, 2027, with Arc ESU billing beginning January 13, 2027. Group your inventory by product so that 2016’s future arrangements are not mistaken for continuing 2012/R2 coverage.
Finish the update check alongside your migration inventory
For each remaining 2012/R2 machine, complete a migration record with the workload owner, application dependencies, target system, available backups, cutover arrangements and outcome checks. Identify which workloads can be upgraded, which need migration to a supported platform and who will complete the work.
The final update check addresses already released updates; upgrading or migrating addresses ongoing support. Advance both tasks. A successful final patch installation does not create future ESU coverage, and a migration plan is not a completed migration. Carry out changes under your own authorization and maintenance arrangements.
Sources
Frequently Asked Questions
Why is a later date on a purchase record not proof of renewal?
Partner Center separates purchase and billing dates, catalog availability and actual coverage. Check the product and year on the record. Windows Server 2012/R2 Year 3 still ends on October 13, 2026; a transaction date does not extend it.
Does deactivation mean a missing historical security update can never be installed?
These two documents do not establish a universal answer. Check the exact KB, system version, coverage year and account rights. Loss of update eligibility after expiry is not proof that every historical patch is impossible to install.
Does a healthy Arc connection mean the final update was installed automatically?
No. The Arc guide still requires Microsoft Update, WSUS or another patching solution to be configured. Check actual installation records and outcomes instead of treating connection status as update acceptance.
Will this automatically shut down my server?
Microsoft specifies ESU license deactivation and the end of update eligibility here, not server shutdown or workload deletion. A running machine is not proof of continuing support; proceed with the appropriate upgrade or migration.