Skip to content

Windows Server 2022 will retire on June 30, 2028. Removal on June 30, 2029.Β #4168

Closed

Description

@allyford

Windows Server 2022 retirement has been extended. Please note the following updates:

Windows Server 2022 retires on June 30, 2028. After that date, AKS will no longer produce new node images or provide security patches. After that date, you will not be able to create new node pools with Windows Server 2022 on any Kubernetes version. All existing node pools with Windows Server 2022 will be unsupported. Windows Server 2022 is not supported in Kubernetes version 1.37 and above. Starting on June 30, 2029, AKS will remove all existing node images for Windows Server 2022, meaning that scaling operations will fail.

We encourage you to upgrade before 30 June 2028 to gain the richer benefits of Windows Server 2025. For more updates, see our AKS public roadmap. See AKS documentation for migration guidance.

If you have questions feel free to leave them below or get answers from community experts in Microsoft Q&A. If you have a support plan and you need technical help, create a support request using the following steps:

Under Issue type, select Technical.
Under Subscription, select your subscription.
Under Service, select Kubernetes Service (AKS).
Select your Kubernetes resource, then select Problem type Deprecation and Retirement.
Under Problem subtype select Guidance regarding Windows Server retirement.

Activity

  1. microsoft-github-policy-service commented on May 29, 2024

    @microsoft-github-policy-service
    Contributor

    This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

  2. microsoft-github-policy-service commented on Jun 19, 2024

    @microsoft-github-policy-service
    Contributor

    This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

  3. microsoft-github-policy-service commented on Jul 16, 2024

    @microsoft-github-policy-service
    Contributor

    This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

  4. 10 remaining items

  5. microsoft-github-policy-service commented on Nov 4, 2024

    @microsoft-github-policy-service
    Contributor

    This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

  6. microsoft-github-policy-service commented on Nov 11, 2024

    @microsoft-github-policy-service
    Contributor

    This issue will now be closed because it hasn't had any activity for 7 days after stale. allyford feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.

  7. allyford commented on May 8, 2026

    @allyford
    ContributorAuthor

    Update: Windows Server 2022 will be supported in k8s 1.36 since Windows Server 2025 is not yet GA. Our current estimate is that Windows Server 2022 will not be supported in k8s 1.37+.

  8. allyford commented on Jun 9, 2026

    @allyford
    ContributorAuthor

    Windows Server 2022 retirement has been extended. Please note the following updates:

    Windows Server 2022 retires on June 30, 2028. After that date, AKS will no longer produce new node images or provide security patches. After that date, you will not be able to create new node pools with Windows Server 2022 on any Kubernetes version. All existing node pools with Windows Server 2022 will be unsupported. Windows Server 2022 is not supported in Kubernetes version 1.37 and above. Starting on June 30, 2029, AKS will remove all existing node images for Windows Server 2022, meaning that scaling operations will fail.

    We encourage you to upgrade before 30 June 2028 to gain the richer benefits of Windows Server 2025. For more updates, see our AKS public roadmap. See AKS documentation for migration guidance.

  9. changed the title [-]Windows Server 2022 will be retired on 15 March 2027 [/-] [+]Windows Server 2022 will be retired on 30 June 2028[/+] on Jun 9, 2026
  10. changed the title [-]Windows Server 2022 will be retired on 30 June 2028[/-] [+]Windows Server 2022 will retire on June 30, 2028. Removal on June 30, 2029.[/+] on Aug 11, 2026
  11. microsoft-github-policy-service commented on Nov 9, 2026

    @microsoft-github-policy-service
    Contributor

    This announcement has been automatically marked as stale because it has not had any activity for 90 days. It will be closed if no further activity occurs within 7 days of this comment.

  12. microsoft-github-policy-service commented on Nov 17, 2026

    @microsoft-github-policy-service
    Contributor

    This issue will now be closed because it hasn't had any activity for 7 days after stale. Ally Ford (@allyford) feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions