Hi Kevin,
We’ve received requests to allow PowerShell with MFA-enabled accounts, but for automated scripts this usually doesn’t help, as the script can’t complete MFA on its own. The same applies to REST API queries.
We may also consider a future “maintenance mode” to help ensure no backup jobs are running when you start your server updates (Windows patching?). Would that help in your case?
For now, the most practical approach is to use a service account with a strong password stored securely in encrypted form on the machine. I found this external blog (not from Veeam) with some ideas and pros/cons:
https://www.secureideas.com/blog/secure ... -practices
Best,
Fabian
We’ve received requests to allow PowerShell with MFA-enabled accounts, but for automated scripts this usually doesn’t help, as the script can’t complete MFA on its own. The same applies to REST API queries.
We may also consider a future “maintenance mode” to help ensure no backup jobs are running when you start your server updates (Windows patching?). Would that help in your case?
For now, the most practical approach is to use a service account with a strong password stored securely in encrypted form on the machine. I found this external blog (not from Veeam) with some ideas and pros/cons:
https://www.secureideas.com/blog/secure ... -practices
Best,
Fabian
Statistics: Posted by Mildur — May 19, 2026 7:13 am
