replace azure bastion virtual machines with current gen
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Migrate retiring Azure Virtual Machines (VMs) to latest-generation VMs before 15 November 2028
You're receiving this notification because you're associated with one or more Azure subscriptions that use, or have used, VM types that are retiring.
On 15 November 2028, we'll be retiring F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B-series Azure VMs. You won't be able to use or purchase these VMs, or any constrained core sizes that are part of the retiring VM series, after that date.
We are currently using Standard B1 for bastions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Azure configuration that provisions the bastions and confirm where Standard B1 is used. Review the linked Azure VM retirement notice and identify a current-generation replacement, then verify that the bastions still provision successfully and no retiring VM series remains.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100