Revise Windows Server 2019 deprecation dates #14339
Conversation
Updated the deprecation schedule for Windows Server 2019 hosted image. ## Summary This PR updates the documentation for Microsoft-hosted Azure Pipelines agents (`docs/pipelines/agents/hosted.md`): - The brownout period for the Windows Server 2019 hosted agent image is now clearly specified as: - **3rd June 2025 to 24th June 2025** - **2nd December 2025 to 9th December 2025** This change reflects the updated timeline announced in our blog post: [Upcoming Updates for Azure Pipelines Agents Images - Windows](https://devblogs.microsoft.com/devops/upcoming-updates-for-azure-pipelines-agents-images/#windows) - Removed the redundant section link that previously linked to "Windows Server 2019 hosted image deprecation schedule." The information is now directly presented in the schedule section. ## Reason for change These updates follow the new brownout schedule and address a navigation improvement to prevent user confusion. **Reference:** - [Microsoft DevOps blog post on agent updates](https://devblogs.microsoft.com/devops/upcoming-updates-for-azure-pipelines-agents-images/#windows) --- Please let me know if any further edits or details are required!
|
@SahithKesireddy9 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull request overview
This PR updates the deprecation schedule documentation for the Windows Server 2019 hosted agent image in Azure Pipelines to reflect the latest timeline announced by Microsoft DevOps.
Key Changes:
- Updated brownout period to include two separate time windows: June 3-24, 2025 and December 2-9, 2025
- Removed redundant internal navigation link to improve documentation clarity
| The Windows Server 2019 image is scheduled to be deprecated: | ||
| * Deprecation start date: June 1, 2025 | ||
| * Brownout period: June 3, 2025 to June 24, 2025 | ||
| * Brownout period: 3rd June 2025 to 24th June 2025, 2nd December 2025 to 9th December 2025 |
There was a problem hiding this comment.
Date format inconsistency detected. Line 50 uses "June 1, 2025" format, while line 51 uses "3rd June 2025" format. Line 52 uses "December 31, 2025" format. For consistency within the same section, all dates should follow the same format. Consider using either:
- "June 1, 2025" and "June 3, 2025 to June 24, 2025, December 2, 2025 to December 9, 2025", or
- "1st June 2025" and "3rd June 2025 to 24th June 2025, 2nd December 2025 to 9th December 2025"
| * Brownout period: 3rd June 2025 to 24th June 2025, 2nd December 2025 to 9th December 2025 | |
| * Brownout period: June 3, 2025 to June 24, 2025, December 2, 2025 to December 9, 2025 |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
3 participants
Updated the deprecation schedule for Windows Server 2019 hosted image.
Summary
This PR updates the documentation for Microsoft-hosted Azure Pipelines agents (
docs/pipelines/agents/hosted.md):The brownout period for the Windows Server 2019 hosted agent image is now clearly specified as:
This change reflects the updated timeline announced in our blog post:
Upcoming Updates for Azure Pipelines Agents Images - Windows
Removed the redundant section link that previously linked to "Windows Server 2019 hosted image deprecation schedule." The information is now directly presented in the schedule section.
Reason for change
These updates follow the new brownout schedule and address a navigation improvement to prevent user confusion.
Reference:
Please let me know if any further edits or details are required!