Azure Local | HomeLab – Updating Images

Img 0380.png
Reading Time: 3 minutes

In a previous post, https://www.gettothe.cloud/azure-local-bicep-marketplace-images/, I explained how to retrieve images from the Azure Marketplace when working in an Azure Local environment. In that example, I used Azure Bicep to automate the process; however, the same actions can also be performed directly through the Azure portal. This gives users the flexibility to choose whichever method best fits their workflow, whether they prefer infrastructure-as-code or a graphical interface.

As you can see, two of the images—Windows Server 2022 and Windows Server 2025—have an update available. This notification is generated by the Azure portal. The image version (as defined in the earlier Bicep example) has become outdated, and a newer build is now available.

These updated images typically include the latest Windows patches, security updates, and general improvements. To ensure that your deployments remain secure, compliant, and up to date, it is recommended to update the referenced image version accordingly. This can be done either by adjusting the image version in your Bicep configuration or by selecting the updated version directly through the Azure portal.

Update via portal

When you click the “New update available” link in the Azure Portal, you are taken directly to the section where you can review and update the image version. Updating the image through the portal is straightforward:

  1. In the Azure Portal, navigate to your VM Image overview.
  2. Locate the image that shows the “New update available” notification.
  3. Click the “New update available” link.
  4. Save the changes. New deployments will automatically use the updated image version.

This method is especially useful if you prefer working through the portal rather than managing versions manually through infrastructure-as-code.

Update via code

In our current Bicep parameter file, we have a hardcoded image version defined for the selected SKU. This means that each time Microsoft releases a new image update, such as the ones indicated by the “New update available” banner in the Azure portal, the deployment continues to reference the old version unless we manually change it.

To make the deployment automatically use the newest image published in the Azure Marketplace, we need to modify this parameter and replace the fixed version number with the value 'latest'. Azure will then always resolve the most recent version available at deployment time.

Example before (hardcoded)
  {
    parImageName: 'win11-24h2-avd-m365-01' // e.g. name of the marketplace image as you want to identify it
    parResourceGroupName: '' // e.g. resource group of cluster
    parSubscriptionId: subscriptionId
    parExtendedLocationName: '' // e.g. extended location of cluster
    parOsType: 'Windows' // e.g. 'Windows' or 'Linux'
    parPublisherId: 'microsoftwindowsdesktop' // e.g. 'microsoftwindowsdesktop' for Windows 11 AVD images
    parOfferId: 'office-365' // e.g. 'office-365' for Windows 11 AVD images
    parSku: 'win11-24h2-avd-m365' // e.g. 'win11-24h2-avd-m365' for Windows 11 AVD images
    parSkuVersion: '26100.7462.251209' // e.g. specific version of the image
    parHyperVGeneration: 'V2' // e.g. 'V1' or 'V2'
    parTags: {} // e.g. {
      //   environment: 'demo'
      //   project: 'get-to-the-cloud'
      // }
  }
Example after (Automatic latest version)
  {
    parImageName: 'win11-24h2-avd-m365-01' // e.g. name of the marketplace image as you want to identify it
    parResourceGroupName: '' // e.g. resource group of cluster
    parSubscriptionId: subscriptionId
    parExtendedLocationName: '' // e.g. extended location of cluster
    parOsType: 'Windows' // e.g. 'Windows' or 'Linux'
    parPublisherId: 'microsoftwindowsdesktop' // e.g. 'microsoftwindowsdesktop' for Windows 11 AVD images
    parOfferId: 'office-365' // e.g. 'office-365' for Windows 11 AVD images
    parSku: 'win11-24h2-avd-m365' // e.g. 'win11-24h2-avd-m365' for Windows 11 AVD images
    parSkuVersion: 'latest' // e.g. specific version of the image
    parHyperVGeneration: 'V2' // e.g. 'V1' or 'V2'
    parTags: {} // e.g. {
      //   environment: 'demo'
      //   project: 'get-to-the-cloud'
      // }
  }

Share and Enjoy !

Shares
Designer (23)

Stay close to the action—follow GetToThe.Cloud across social!
Deep dives and hands‑on how‑tos on Azure Local, hybrid cloud, automation, PowerShell/Bicep, AVD + FSLogix, image pipelines, monitoring, networking, and resilient design when the internet/Azure is down.

🔗 Our channels
▶️ YouTube: https://www.youtube.com/channel/UCa33PgGdXt-Dr4w3Ub9hrdQ
💼 LinkedIn Group: https://www.linkedin.com/groups/9181126/
✖️ X (Twitter): https://x.com/Gettothecloud
🎵 TikTok: https://www.tiktok.com/@gettothecloud
🐙 GitHub: https://github.com/GetToThe-Cloud/Website
💬 Slack: DM us for an invite
📲 WhatsApp: DM for the community link

WP Twitter Auto Publish Powered By : XYZScripts.com
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Privacy & Cookie policy
Privacy & Cookies policy
Cookie name Active

Who we are

Our website address is: https://www.gettothe.cloud

Comments

When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection. An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Cookies

If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year. If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser. When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select "Remember Me", your login will persist for two weeks. If you log out of your account, the login cookies will be removed. If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website. These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

If you request a password reset, your IP address will be included in the reset email.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue. For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.
Save settings
Cookies settings