[Autogenerated] now that we know the why.
Let's learn how to lock and unlock
SharePoint Sykes Locking and unlocking
SharePoint Sykes is done again with the
SharePoint online PowerShell module. And,
as always, make sure you have the latest
version available. There are three lakh
options for SharePoint sites. First one
is, of course, unlocked, which is the
normal state with normal collaboration.
The second option is read only where, as
the name says, the content can be read.
But you're preventing users from adding,
updating or deleting content. The last
option is no access. In no access. Users
would not be able to access the site at
all, and they would get a 403 error. You
could optionally set up a red direct. You
are well for all of the sites locked in no
access mode so you could create a support
page, for example, telling them that the
site cannot be accessed and the way to
contact i t. If they need it unlocked.
There are some limitations you need to
know. First of all, you cannot set the log
state on the route site of your tenant or
a Microsoft 365 group connected site for
sites that are Microsoft 365 group
connected and also have a Microsoft Eames
team. You could look at the are high
functionality provided from Microsoft
teams, but that's outside of the scope of
this course to lock a sight. More
specifically in read only, we will use the
set. Spock IT partial cmdlet provide the
identity of the site, which is the You are
well, and the parameter we will use is
Block State and to make it read only we
will pass read only in there to make the
site inaccessible. It's very similar, but
we will use no access inside the Log state
parameter to configure the tenant wide
redirect for no exercise. We actually need
to specify the site or page at the tenant
level, so we will use the set Spoto Tenant
PowerShell cmdlet and specify the no
access redirect. You are real parameter
and pointed to where we want people to be read, erected