I have my backoffice running on a different server than my website. For the backoffice I use a sql user that has read/write permission to the db. For the public facing website I had been using a sql user that only has read permission on the db.

Today I upgraded from one umbraco version to the next and maybe my unattended upgrade was kicked off by the public site instead of the backoffice instance and I got an error on the public site complaining that my sql user didn't have write access to the "umbracoLock" table.

Maybe my solution should be to disable unattended upgrades on the public website so that the backoffice is the only server that can kick those off. Does that sound like the correct approach?