# Rocky Linux Images on Azure(Old Publisher Account)

**URL:** <https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [May 29, 2024, 9:45am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313 "2024-05-29T09:45:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![KenichiTanaka](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@KenichiTanaka](https://forums.rockylinux.org/u/KenichiTanaka)\
**Post date:** [May 29, 2024, 9:45am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/1 "2024-05-29T09:45:38Z")

</div>

Hi Team,

Could you please let me check some points about the following URL:

> [@Rocky Linux Images on Azure: Important Update](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-important-update/13721):
>
> Hello Rocky Linux Community, I wanted to share some important updates and guidance regarding Rocky Linux images on Azure. Our work aims to improve access and usability for our users and to ensure a seamless transition between our old and new offerings. These changes affect both the Community Galleries and the Marketplace images. Community Galleries The Cloud Special Interest Group (SIG) has been collaborating closely with the Azure Community Galleries team to enhance the availability and conve…

**Question**  
1.Specific impact after October 2024 for VMs created with old images → Please provide specific impacts if any.  
2.Until when can VMs created with old images be continued to be used? → Please provide information if there is no expiration.  
3.Until when will support be provided for VMs created with old images?  
4.What is the specific reason for Rocky Enterprise Software Foundation to switch the Azure publisher account?  
・Old publisher account: erockyenterprisesoftwarefoundationinc1653071250513  
・New publisher account: resf

**Application deadline**  
May 31, 2024

Best Regards,  
Kenichi

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [May 29, 2024, 10:25am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/2 "2024-05-29T10:25:08Z")

</div>

From what I read in the link:

1. Impact that you cannot create new VM’s with the old image after October 2024, nor can you scale out your existing VM’s.

> [@](#):
>
> Virtual Machines that were deployed using these old images will continue to operate as normal

> [@](#):
>
> **After the EOL date:**
> 
> - **Deployment Restrictions** : New deployments using the deprecated images will not be possible. This includes creating new VM instances or scaling out existing virtual machine scale sets.
> - **Active Instances Unaffected** : VMs deployed with the deprecated images before the EOL date will continue to function. However, scaling out existing virtual machine scale sets will not be permitted.
> - **Scale Sets** : For any deprecated plans or offers, all images within those plans or offers will no longer be available, affecting the ability to scale out existing virtual machine scale sets that utilize these images.

1. Existing VM’s on the old images can still be used, you just cannot scale them anymore therefore limiting them to their current capabilities/resources.

2. Since the images are deprecated, no support will be provided after that date. You are encouraged to move to the new images under the new account.

3. I expect for clearness and clarity of who the publisher is.

@neil will be able to correct any of the above or add more info where necessary.

---

<div class="post-metadata">

**Author:** ![KenichiTanaka](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@KenichiTanaka](https://forums.rockylinux.org/u/KenichiTanaka)\
**Post date:** [May 31, 2024, 9:14am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/3 "2024-05-31T09:14:44Z")

</div>

Hi, Thank you for reply!!

Impacted by this are about 100 VMs, so the impact is significant. We are in trouble. We would like to verify if the existing VMs can continue to be safely used. Please confirm if the following understanding is correct:

- Support for the old image has ended, and image updates will not be performed.
- Security updates through commands are possible for RockyLinux running on the old image VMs.

Best Regards,  
Kenichi

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [May 31, 2024, 1:15pm UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/4 "2024-05-31T13:15:31Z")

</div>

> [@KenichiTanaka](#):
>
> Security updates through commands are possible for RockyLinux running on the old image VMs.

A simple `dnf update` on any system will bring it up to date.

---

<div class="post-metadata">

**Author:** ![ramblingkenji](https://avatars.discourse-cdn.com/v4/letter/r/94ad74/32.png) [@ramblingkenji](https://forums.rockylinux.org/u/ramblingkenji)\
**Post date:** [June 5, 2024, 3:03am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/5 "2024-06-05T03:03:31Z")

</div>

Hi @KenichiTanaka,

I’ve also done something similar where I could still use the older rocky image and it can update as expected (including security patches). This is because the updates are pulled from the repos located in the `/etc/yum.repos.d/` path.

Personally, I used ansible for maintaining my VMs at scale. Just a simple playbook like the following (assuming they are reachable with your architecture/setup).

```yaml
- name: Updating my rocky VMs
  hosts: rocky_hosts
  remote_user: <your_ssh_username>
  become: yes

  tasks:
    - name: Upgrade all packages using DNF
      dnf:
        name: "*"
        state: latest

```

The main reason is that it helps give me a single area to manage it. But plenty of options exist. Otherwise, if you spin it up and destroy them often then a `cloud-init` file could also be useful 🙂

---

<div class="post-metadata">

**Author:** ![KenichiTanaka](https://avatars.discourse-cdn.com/v4/letter/k/f9ae1b/32.png) [@KenichiTanaka](https://forums.rockylinux.org/u/KenichiTanaka)\
**Post date:** [June 7, 2024, 5:34am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/6 "2024-06-07T05:34:12Z")

</div>

Hi @label @ramblingkenji ,  
Unknown points were resolved. Thank you very much!  
Best Regards,  
Kenichi

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [August 6, 2024, 5:34am UTC](https://forums.rockylinux.org/t/rocky-linux-images-on-azure-old-publisher-account/14313/7 "2024-08-06T05:34:29Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.