MicrosoftDocs
docs: Generalize Ubuntu Pro guidance beyond EOL scenarios
The previous guidance focused primarily on Ubuntu Pro as a solution for End-of-Life (EOL) systems. This update expands the scope to also cover another key benefit: security patching for the Universe repository (esm-apps), which applies to all supported LTS versions.
To reflect this, the document is updated to clarify the Main vs. Universe distinction and show that Azure Update Manager’s recommendations cover both use cases. Redundant lifecycle details are also removed in favor of a link to the primary guidance document.
@jcastros : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 2850e26:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/update-manager/security-awareness-ubuntu-support.md | :warning:Warning | Details |
articles/update-manager/security-awareness-ubuntu-support.md
- Line 35, Column 116: [Warning: hard-coded-locale - See documentation]
Link 'https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/canonical/ubuntu-els-guidance' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. - Line 35, Column 116: [Suggestion: docs-link-absolute - See documentation]
Absolute link 'https://learn.microsoft.com/en-us/azure/virtual-machines/workloads/canonical/ubuntu-els-guidance' will be broken in isolated environments. Replace with a relative link.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
@habibaum - Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@kjohn-msft PRMerger will only accept sign off from the article's listed author. However, if you are a Microsoft employee authorized to update this content, you can send a request to [email protected] for this PR to be merged. Include your role and an explanation of why the PR should be merged without approval from the listed author.
@kjohn-msft PRMerger will only accept sign off from the article's listed author. However, if you are a Microsoft employee authorized to update this content, you can send a request to [email protected] for this PR to be merged. Include your role and an explanation of why the PR should be merged without approval from the listed author.
My sign off is to notionally support the changes proposed as-is. As designed, I'd want the listed author to be the final sign off and use my sign off as a supporting signal of SME support.
We should remove the final line as 20.04 is also now EOL, and it would be better to keep the content general. "- Ubuntu offers 20.04 LTS and 22.04 LTS as a migration from 18.04 LTS. Learn more."
We should remove the final line as 20.04 is also now EOL, and it would be better to keep the content general. "- Ubuntu offers 20.04 LTS and 22.04 LTS as a migration from 18.04 LTS. Learn more."
@jcastros Can you respond to the requested changes or let us know if you would like us to commit them?
@habibaum @bmcder - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
Learn Build status updates of commit eb4b41e:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/update-manager/security-awareness-ubuntu-support.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
@v-dirichards I acepted the change, something went wrong there: :::image type="content" source="./media/security-awareness-ubuntu-support/ubuntu-pro-subscription-inline.png" alt-text="Screenshot of recommendation to subscribe to Ubuntu Pro in Azure Update Manager." lightbox="./media/security-awareness-ubuntu-support/ubuntu-pro-subscription-expanded.png":::
It was an image and it should still go, I did not changed it, could you pls check?
Thanks!
@v-dirichards I acepted the change, something went wrong there: :::image type="content" source="./media/security-awareness-ubuntu-support/ubuntu-pro-subscription-inline.png" alt-text="Screenshot of recommendation to subscribe to Ubuntu Pro in Azure Update Manager." lightbox="./media/security-awareness-ubuntu-support/ubuntu-pro-subscription-expanded.png":::
It was an image and it should still go, I did not changed it, could you pls check?
Thanks!
@jcastros Where should the image go (as in, between which two line numbers should it be added)? I don't see it in your initial commit: https://github.com/MicrosoftDocs/azure-docs/pull/127167/commits/2850e2663b04bdf40a281013a84277cc9366b50e
@v-dirichards Before "You can continue to use the Azure Update Manager capabilities" as it was on the original one: https://learn.microsoft.com/en-us/azure/update-manager/security-awareness-ubuntu-support Thanks
@habibaum @bmcder - When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
@MicrosoftDocs/public-repo-pr-review-team
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @habibaum
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @habibaum