Lock Out Specific Tenant

@Fie 

Yes there is, you need to log into the Tenant that you want to lock out, go to “Apply Updates” click on “SCHEDULE LOCK OUT” and deselect “Lock Out All Sites” and then click on “OK”:

So I tried that, but users still can’t login to the other tenants. Will show “in maintenance mode” anyway when they do login (2024R2 build 209)

There isn’t a way to lockout a specific tenant. Only the single instance or all instances used by the database.

What’s the use case by the way?

My use case is that my client has a new owner, and they want a copy of the production tenant that is frozen as of the acquisition date. We created a snapshot as of the sale date and created a tenant from the snapshot. The new tenant must stay frozen at that point in time, so I want to lock out just that tenant.

​@mburns47 in that case you can just run a import scenario/script to reset all the passwords for users and suspend emails in that tenant except for one user (admin). So nobody will be able to access the tenant except by your one user.

Then what is the purpose of the “Lock Out All Sites” option?

​@ggraham96 it will stop schedules in all instances (sites) tied to the database and kick out users that are not administrator. Generally locking out is done so that maintenance operations by administrators can be done safely (publishing, taking snapshots, restorations, etc.) that can interrupt work or worse mess up the database if people are working at the same time.

Thanks for the response.  My apologies, however, I still do not understand the difference or effect on the lock out whether or not I select the box. Outcome seems the same regardless.