1 00:00:02,240 --> 00:00:03,870 [Autogenerated] we have now covered the 2 00:00:03,870 --> 00:00:07,310 site rename. So let's move on to swapping 3 00:00:07,310 --> 00:00:10,710 SharePoint sites. When would you swap a 4 00:00:10,710 --> 00:00:14,320 SharePoint site? Some common use cases are 5 00:00:14,320 --> 00:00:17,170 replacing the root side of your tenant and 6 00:00:17,170 --> 00:00:20,430 you internet Go live or replacing the 7 00:00:20,430 --> 00:00:22,920 enterprise search center of your 8 00:00:22,920 --> 00:00:26,570 organization. But before we get into the 9 00:00:26,570 --> 00:00:30,540 details, how is the site swap different? 10 00:00:30,540 --> 00:00:34,210 First of all, a site swap can only be used 11 00:00:34,210 --> 00:00:38,150 for the root site or the search center. It 12 00:00:38,150 --> 00:00:42,560 cannot be used on any other site. Also, 13 00:00:42,560 --> 00:00:46,070 while the word swap makes it seem super 14 00:00:46,070 --> 00:00:49,320 simple, it's actually a bit more 15 00:00:49,320 --> 00:00:52,860 complicated than that. Let's take a look 16 00:00:52,860 --> 00:00:56,270 at an example. Let's say I am building a 17 00:00:56,270 --> 00:00:59,860 new internet, which is currently hosted at 18 00:00:59,860 --> 00:01:03,670 the tenant. URL slash sykes slash new 19 00:01:03,670 --> 00:01:07,460 internet. My current internet is hosted 20 00:01:07,460 --> 00:01:11,130 directly in the tenant route. What I want 21 00:01:11,130 --> 00:01:14,630 to do is I want to do a site swap in order 22 00:01:14,630 --> 00:01:17,770 to get the new intranet at the tenant 23 00:01:17,770 --> 00:01:21,510 route. The first thing that will happen in 24 00:01:21,510 --> 00:01:25,440 the swap is that the new internet will be 25 00:01:25,440 --> 00:01:28,470 moved to the tenant route, while the 26 00:01:28,470 --> 00:01:31,860 current internet will actually be moved to 27 00:01:31,860 --> 00:01:36,000 what we call an R hive. You are real, so 28 00:01:36,000 --> 00:01:39,840 it will be moved to a new location. And in 29 00:01:39,840 --> 00:01:43,560 this example, it will be hosted at slash 30 00:01:43,560 --> 00:01:47,590 ___ slash internet. Our hive. There is 31 00:01:47,590 --> 00:01:51,490 another step which is a ready rex. IT will 32 00:01:51,490 --> 00:01:55,090 automatically be created at the original. 33 00:01:55,090 --> 00:01:58,120 You are real of our new internet. Was that 34 00:01:58,120 --> 00:02:01,750 so? At tenant URL real slash ___ slash new 35 00:02:01,750 --> 00:02:05,510 internet and this will be used to redirect 36 00:02:05,510 --> 00:02:08,870 any queries to that site to x new 37 00:02:08,870 --> 00:02:13,340 location, which is now the tenant route. 38 00:02:13,340 --> 00:02:16,850 The site swap can be done via the user 39 00:02:16,850 --> 00:02:20,340 interface and if you select an eligible 40 00:02:20,340 --> 00:02:23,220 site which remember are either the root 41 00:02:23,220 --> 00:02:26,760 site or the search center, you will see a 42 00:02:26,760 --> 00:02:31,160 replace site option appear in the toolbar. 43 00:02:31,160 --> 00:02:34,070 Really important. You will only sit on 44 00:02:34,070 --> 00:02:37,080 eligible sites. You will not see it on any 45 00:02:37,080 --> 00:02:40,140 other ones. So most of the time you will 46 00:02:40,140 --> 00:02:43,070 not see that in the menu As you work with 47 00:02:43,070 --> 00:02:47,400 the admin center To do this site swap with 48 00:02:47,400 --> 00:02:51,570 PowerShell, we will use the invoke Spock. 49 00:02:51,570 --> 00:02:54,800 IT swap PowerShell cmdlet specify the 50 00:02:54,800 --> 00:02:58,390 source. You are real. So our new internet, 51 00:02:58,390 --> 00:03:01,710 the target you are real. So roots IT in 52 00:03:01,710 --> 00:03:05,390 this example and our hive URL real, which 53 00:03:05,390 --> 00:03:08,940 is where the current route site should go, 54 00:03:08,940 --> 00:03:12,090 Dex. It The red direct site is all done 55 00:03:12,090 --> 00:03:19,000 automatically in the back end, so you do not need to manage that.