1
00:00:02,240 --> 00:00:04,060
[Autogenerated] now that we know the why.

2
00:00:04,060 --> 00:00:06,870
Let's learn how to lock and unlock

3
00:00:06,870 --> 00:00:10,380
SharePoint Sykes Locking and unlocking

4
00:00:10,380 --> 00:00:13,180
SharePoint Sykes is done again with the

5
00:00:13,180 --> 00:00:16,440
SharePoint online PowerShell module. And,

6
00:00:16,440 --> 00:00:19,340
as always, make sure you have the latest

7
00:00:19,340 --> 00:00:23,170
version available. There are three lakh

8
00:00:23,170 --> 00:00:26,540
options for SharePoint sites. First one

9
00:00:26,540 --> 00:00:29,380
is, of course, unlocked, which is the

10
00:00:29,380 --> 00:00:33,440
normal state with normal collaboration.

11
00:00:33,440 --> 00:00:37,790
The second option is read only where, as

12
00:00:37,790 --> 00:00:41,060
the name says, the content can be read.

13
00:00:41,060 --> 00:00:43,860
But you're preventing users from adding,

14
00:00:43,860 --> 00:00:47,980
updating or deleting content. The last

15
00:00:47,980 --> 00:00:53,320
option is no access. In no access. Users

16
00:00:53,320 --> 00:00:56,320
would not be able to access the site at

17
00:00:56,320 --> 00:01:00,660
all, and they would get a 403 error. You

18
00:01:00,660 --> 00:01:03,460
could optionally set up a red direct. You

19
00:01:03,460 --> 00:01:06,600
are well for all of the sites locked in no

20
00:01:06,600 --> 00:01:09,800
access mode so you could create a support

21
00:01:09,800 --> 00:01:12,130
page, for example, telling them that the

22
00:01:12,130 --> 00:01:14,900
site cannot be accessed and the way to

23
00:01:14,900 --> 00:01:18,840
contact i t. If they need it unlocked.

24
00:01:18,840 --> 00:01:21,330
There are some limitations you need to

25
00:01:21,330 --> 00:01:24,980
know. First of all, you cannot set the log

26
00:01:24,980 --> 00:01:28,510
state on the route site of your tenant or

27
00:01:28,510 --> 00:01:32,970
a Microsoft 365 group connected site for

28
00:01:32,970 --> 00:01:35,920
sites that are Microsoft 365 group

29
00:01:35,920 --> 00:01:39,360
connected and also have a Microsoft Eames

30
00:01:39,360 --> 00:01:42,130
team. You could look at the are high

31
00:01:42,130 --> 00:01:45,120
functionality provided from Microsoft

32
00:01:45,120 --> 00:01:48,330
teams, but that's outside of the scope of

33
00:01:48,330 --> 00:01:51,630
this course to lock a sight. More

34
00:01:51,630 --> 00:01:54,960
specifically in read only, we will use the

35
00:01:54,960 --> 00:01:59,200
set. Spock IT partial cmdlet provide the

36
00:01:59,200 --> 00:02:01,970
identity of the site, which is the You are

37
00:02:01,970 --> 00:02:05,550
well, and the parameter we will use is

38
00:02:05,550 --> 00:02:09,230
Block State and to make it read only we

39
00:02:09,230 --> 00:02:12,780
will pass read only in there to make the

40
00:02:12,780 --> 00:02:16,430
site inaccessible. It's very similar, but

41
00:02:16,430 --> 00:02:20,190
we will use no access inside the Log state

42
00:02:20,190 --> 00:02:23,940
parameter to configure the tenant wide

43
00:02:23,940 --> 00:02:27,560
redirect for no exercise. We actually need

44
00:02:27,560 --> 00:02:31,900
to specify the site or page at the tenant

45
00:02:31,900 --> 00:02:35,290
level, so we will use the set Spoto Tenant

46
00:02:35,290 --> 00:02:39,140
PowerShell cmdlet and specify the no

47
00:02:39,140 --> 00:02:42,540
access redirect. You are real parameter

48
00:02:42,540 --> 00:02:49,000
and pointed to where we want people to be read, erected