Azure Local OS Upgrade process.

rajneesh kumar 0 Reputation points
2025-12-18T16:40:22.0166667+00:00

Hi All,

Currently our Cluster is running Solution version-10.2503.0.13 and nodes are running with Operating system as 23H2 and OS Build:-25398.1965.

Just wanted to check till what date this OS version is supported.

Kindly suggest the right path and step by step document to upgrade the Operating system to the latest version.

I can see URL https://learn.microsoft.com/en-us/azure/azure-local/upgrade/install-solution-upgrade?view=azloc-2509 for Solution upgrade and URL https://learn.microsoft.com/en-us/azure/azure-local/upgrade/upgrade-22h2-to-23h2-powershell?view=azloc-2509&pivots=os-24h2 for OS upgrade.

But i have few doubt like rollback plan and downtime of the node.

I can see update status is showing failed in azure portal as it was waiting for Nodes to reboot complete which i have done now, but i am reluctant to start the update again as i am not sure if this will reboot the nodes in proper manner like put MM then drain mode install patch and reboot and put back load on it and than go to next Node.

So need your suggestion for the same.

Azure Local
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Q&A Assist
    2025-12-18T16:40:38.67+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The OS version 23H2 (OS build 25398.xxxx) is supported until April 2026. After this date, you will no longer receive monthly security and quality updates for this version, and support requests will only be available for patching to a supported release.

    For upgrading your operating system to the latest version, you can follow these high-level steps:

    1. Upgrade the old OS to the new OS via PowerShell.
    2. Perform post-OS upgrade tasks.
    3. Validate the solution upgrade readiness.
    4. Apply the solution upgrade.

    Regarding your concerns about the rollback plan and downtime, it's essential to have a strategy in place before proceeding with the upgrade. Ensure that you have backups and a clear rollback plan should the upgrade fail. The update process typically involves rebooting nodes, and you should monitor the update status closely to ensure that it completes successfully. If you encounter issues, it may be necessary to consult the documentation or seek assistance from Microsoft Support.

    For detailed instructions on the upgrade process, you can refer to the following documents:

    Make sure to review the specific requirements and steps outlined in these documents before proceeding with the upgrade.


    References:

    0 comments No comments

  2. Jilakara Hemalatha 6,610 Reputation points Microsoft External Staff Moderator
    2025-12-18T18:51:42.05+00:00

    Hey rajneesh kumar

    It sounds like you're looking to upgrade your Azure Local OS and want to ensure everything goes smoothly while addressing some concerns about downtime and rollback plans. Firstly, it's important to know that Microsoft generally supports Windows operating systems according to their release cadence, but the specific support dates for your current version can often be found in the official Microsoft lifecycle documentation.

    Here’s a general guide to help you with the OS upgrade:

    1. Check for Support Dates: For end-of-life dates regarding your current OS version (23H2), refer to Microsoft's Windows lifecycle fact sheet for specific timelines.
    2. Upgrade Process:
      • Pre-Upgrade Backup: Before initiating the upgrade, make sure to create a backup or snapshot of your current VM. This is crucial for your rollback plan.
      • Upgrade Instructions: Follow the detailed steps outlined in the Upgrade to 23H2 OS via PowerShell documentation.
    3. Handling Downtime:
      • Ideally, perform the upgrade in a maintenance window to minimize impact on users.
      • Ensure you are putting the node into maintenance mode and draining it before beginning updates or reboots.
    4. Rebooting Nodes:
      • If the update status is showing as failed due to waiting on a reboot, confirm the nodes are fully operational and then consider attempting the process again, but follow these steps to mitigate risk:
      • Put the node in maintenance mode.
      • Drain the node to stop traffic.
      • Install the patch.
      • Reboot, then bring the node back online.
      • Repeat for remaining nodes in a rolling upgrade fashion.
    5. Rollback Plan: If something goes wrong after the upgrade:
      • You can use the backups or snapshots you created before the upgrade to restore the VMs to their previous state.
      • Alternatively, if the upgrade fails and you cannot recover, you might need to rebuild the VM using the latest images and restore data.
      Please refer below documentations:

    Hope this helps! Please let me know if you have any queries in comments.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.