Jenkins azure plugin is being retired on 29 Feb 2024 - switch to CLI?

[sxa]

We have been having problems with the jenkins plugin for Azure not working properly (failed provisions).

When raising this with Azure we got the following response indicating that we should change our approach sine the Azure plugin is being officially retired at the end of February:

Because the Azure command-line interface (Azure CLI) provides a more up-to-date and robust experience when accessing Azure services, we will retire Jenkins plug-ins for Azure on 29 February 2024. For more details, refer to this list of affected Jenkins plug-ins.
Required action
To avoid disruption to your current workloads, review the steps required to transition your pipeline scripts to Azure CLI.
More information
If you have any feedback or you need technical help, please contact us

[sxa]

Noting that in today's jenkins upgrade cycle we left the Azure VM Agents plugin at version 825.v470cb_9e7361a_ due to the following warning:
Warning: The new version of this plugin is marked as incompatible with the installed version. This is usually the case because its behavior changed, or because it uses a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details.
The Releases page for the plugin lists a number of breaking changes which would need potentially need to be addressed

[sxa]

As agreed at the PMC meeting earlier this month, in order to reduce the number of warnings in the log I have removed the adopt_azdo cloud from our jenkins instance. The configuration was as follows:

• Cloud name: adopt_azdo
• Azure credentials: azdo-jenkins-service-princile
• Max jenkins agents limit: 20
• Deployment timeout (seconds): 2000
• Custom tag: None
• Resource group name: Use existing -> adoptopenjdk