If you are following an automated Build and Release process for your SharePoint Framework then you will have come across the need to store your tenant SharePoint admin username and password as variables in the pipeline.
Whle this works and I believe the credentials are encrypted, this is not going to fly with enterprise corporate security. They are going to insist that the credentials are kept centrally in a secure KeyVault. Conveniently for us, a KeyVault is available for us to use in Azure.
Using the process described by the Azure DevOps Labs team you can set up a KeyVault and integrate it into your pipeline.
I am adding the KeyVault pipeline into an older version of an SPFx release (for the most up to date doc check this post out).
Once that is run the new password is successfully utilized instead of the variable I had stored within Azure DevOps.