Episode 369 – Microsoft 365 Backup and Archive

February 01, 2024

Episode Transcript

In Episode 369, Ben and Scott explore the new Backup and Archive options for Microsoft 365 and Office 365 workloads – Microsoft 365 Archive and Microsoft 365 Backup. These two features may sound similar, but they have different functionalities. Microsoft 365 Archive provides coverage for SharePoint, while Microsoft 365 Backup provides coverage across SharePoint, OneDrive, and Exchange. We will be discussing why you should use these features, how to set them up, and their options. Additionally, we’ll cover the differences between the two features, such as the fact that Microsoft 365 Backup does not require an Azure subscription, unlike Microsoft 365 Archive. We’ll also delve into the policies, frequency and retention, and recovery options for each service.

Like what you hear and want to support the show? Check out our membership options.

Show Notes

About the sponsors

Intelligink utilizes their skill and passion for the Microsoft cloud to empower their customers with the freedom to focus on their core business. They partner with them to implement and administer their cloud technology deployments and solutions. Visit Intelligink.com for more info.

See full episode transcriptTranscript is autogenerated by AI

1 00:00:03,405 --> 00:00:06,055 - Welcome to episode 369 2 00:00:06,055 --> 00:00:08,375 of the Microsoft Cloud IT Pro Podcast 3 00:00:08,975 --> 00:00:11,935 recorded live on January 29th, 2024. 4 00:00:12,445 --> 00:00:14,735 This is a show about Microsoft 365 5 00:00:14,735 --> 00:00:17,015 and Azure from the perspective of it pros 6 00:00:17,015 --> 00:00:20,215 and end users where we discuss a topic or recent news 7 00:00:20,315 --> 00:00:21,495 and how it relates to you. 8 00:00:22,215 --> 00:00:23,815 Microsoft 365 backup 9 00:00:24,155 --> 00:00:27,855 and Microsoft 365 archive have arrived in public preview. 10 00:00:28,315 --> 00:00:31,375 In this episode, we're going to explore these new backup 11 00:00:31,515 --> 00:00:34,335 and archive options for Microsoft 365 12 00:00:34,395 --> 00:00:37,735 and Office 365 workloads, SharePoint, OneDrive 13 00:00:37,735 --> 00:00:41,335 and Exchange in what they have to offer, how to get started 14 00:00:41,365 --> 00:00:43,415 with them and the cost associated 15 00:00:43,565 --> 00:00:45,215 with these new preview services. 16 00:00:47,365 --> 00:00:49,295 Another episode on a Monday morning 17 00:00:49,295 --> 00:00:51,095 because of a teams outage, , 18 00:00:52,875 --> 00:00:55,535 - You know those global teams outages. Little get you. 19 00:00:55,565 --> 00:00:57,855 - Yeah. It was an adventurous day in Florida 20 00:00:57,855 --> 00:00:59,655 because not only was there a teams outage, 21 00:00:59,975 --> 00:01:01,655 apparently it did not affect me, 22 00:01:02,075 --> 00:01:04,055 but I work with a bunch 23 00:01:04,115 --> 00:01:06,095 of clients down in like the Tampa area 24 00:01:06,155 --> 00:01:07,535 and apparently there was a big spectrum 25 00:01:07,875 --> 00:01:09,095 outage down there as well. 26 00:01:09,515 --> 00:01:11,815 So they were all kinds of confused on 27 00:01:12,375 --> 00:01:14,455 spectrum causing issues as teams causing issues 28 00:01:14,475 --> 00:01:15,695 or both causing issues. 29 00:01:15,915 --> 00:01:19,175 Is one causing issues due to the other one having issues 30 00:01:19,515 --> 00:01:22,255 and it was just a day to just stop working early. 31 00:01:22,445 --> 00:01:25,655 - Yeah, it happens but we're back. 32 00:01:25,865 --> 00:01:28,855 We're into Monday. I got my coffee, I'm ready to go 33 00:01:28,955 --> 00:01:33,935 and talk all about Microsoft 365 back up in archive. 34 00:01:34,285 --> 00:01:39,055 - Yeah, this was a new, well not a new service, a service 35 00:01:39,085 --> 00:01:43,015 that was announced Ignite right this fall like 36 00:01:43,225 --> 00:01:44,815 three, four months ago. 37 00:01:45,835 --> 00:01:50,175 And it is now in a state of public 38 00:01:50,725 --> 00:01:53,415 paid preview I guess would be the official state. 39 00:01:53,515 --> 00:01:55,655 It isn't public preview, it's not ga, 40 00:01:56,155 --> 00:01:57,175 all the things about preview 41 00:01:57,715 --> 00:01:59,895 and you are gonna have to pay for it if you want 42 00:01:59,915 --> 00:02:04,375 to start using this Microsoft 365 backup, which 43 00:02:04,965 --> 00:02:07,695 this service, I think it makes sense that it's paid 44 00:02:07,695 --> 00:02:11,775 because you're backing up data to storage. 45 00:02:11,795 --> 00:02:14,215 You're gonna have to pay for storage. It takes storage. 46 00:02:14,835 --> 00:02:16,335 I'm okay with this one. How's that? 47 00:02:16,435 --> 00:02:18,855 I'm okay with this one being a paid preview. I think 48 00:02:19,115 --> 00:02:20,535 - You know, consumption's consumption 49 00:02:20,995 --> 00:02:24,015 so if if you're gonna hit it, sorry, like you, you, 50 00:02:24,035 --> 00:02:26,575 you are gonna have to pay for that at some point. 51 00:02:27,405 --> 00:02:31,215 Hopefully this ends up being kind of the the max rate 52 00:02:31,275 --> 00:02:34,415 for things we, I'm, I'm sure we'll kind of get into it 53 00:02:34,435 --> 00:02:36,215 and discuss pricing a little bit. 54 00:02:36,835 --> 00:02:39,575 But yeah, you are paying not only to be an early adopter 55 00:02:39,635 --> 00:02:43,735 but certainly paying to across these various things, 56 00:02:44,195 --> 00:02:46,215 be it paying on the backup side 57 00:02:46,475 --> 00:02:48,375 and then you've got the archive offering 58 00:02:48,395 --> 00:02:50,055 as well, which we'll get into. Yeah 59 00:02:50,275 --> 00:02:53,415 - And you get lightning fast ReSTOR ability from Microsoft 60 00:02:53,475 --> 00:02:55,575 to ensure your business continuity with this 61 00:02:56,215 --> 00:02:57,335 Microsoft 365 backup. 62 00:02:57,595 --> 00:03:01,235 So what is Microsoft 365 backup? Scott, 63 00:03:01,465 --> 00:03:04,475 - What is Microsoft 365 backup? 64 00:03:05,515 --> 00:03:10,195 Microsoft 365 backup is 65 00:03:11,035 --> 00:03:14,755 a service which provides you backup 66 00:03:14,855 --> 00:03:19,355 and recovery capabilities for SharePoint inclusive 67 00:03:19,935 --> 00:03:23,675 of OneDrive for Business and Exchange. 68 00:03:24,175 --> 00:03:25,915 And really that's about it. 69 00:03:25,935 --> 00:03:28,435 If you've been thinking about backing up those kinds 70 00:03:28,435 --> 00:03:32,115 of workloads, let's say in like SharePoint land, like I want 71 00:03:32,115 --> 00:03:36,395 to back up a a OneDrive for business site 72 00:03:36,495 --> 00:03:39,955 or I want to back up this team site just to have kind 73 00:03:39,955 --> 00:03:43,155 of a a point in time recovery option for it 74 00:03:43,155 --> 00:03:45,395 or a mailbox, you know, I wanna back up this mailbox 75 00:03:45,575 --> 00:03:46,795 and be able to restore it back 76 00:03:46,795 --> 00:03:48,835 to a certain amount in certain point in time. 77 00:03:49,575 --> 00:03:52,595 That's really what it's all about. 78 00:03:53,715 --> 00:03:58,075 Interesting thing about Microsoft 365 backup 79 00:03:58,725 --> 00:04:01,795 maybe versus some of the other 80 00:04:03,115 --> 00:04:06,515 existing in-market backup offerings for SharePoint 81 00:04:06,515 --> 00:04:09,715 and Exchange, be they Microsoft based third party, 82 00:04:10,195 --> 00:04:12,995 anything like that ISV whatever it is is 83 00:04:13,745 --> 00:04:17,875 that this one is just pego , yeah you kind 84 00:04:17,875 --> 00:04:19,635 of light it up and you pay for storage. 85 00:04:20,495 --> 00:04:24,315 You are not necessarily paying, well not necessarily. 86 00:04:24,775 --> 00:04:27,275 You are not paying per user licensing 87 00:04:27,775 --> 00:04:29,075 for backup capabilities. 88 00:04:29,175 --> 00:04:31,635 So it's basically like hey you're gonna light up this 89 00:04:31,635 --> 00:04:34,275 capability and just pay for storage for it. 90 00:04:34,375 --> 00:04:36,355 And I think that's in stark contrast to some 91 00:04:36,355 --> 00:04:37,835 of the other ISV and 92 00:04:37,855 --> 00:04:39,715 and vendor offerings that are out there today 93 00:04:40,245 --> 00:04:43,195 where you pay kind of per user 94 00:04:43,815 --> 00:04:47,275 and then get a subset of protected items behind that. Yeah, 95 00:04:47,295 --> 00:04:48,875 - It is and it's interesting 96 00:04:48,875 --> 00:04:52,275 because I think some of the ISVs are also starting 97 00:04:52,415 --> 00:04:55,195 to pivot sort of to this. Well 98 00:04:55,195 --> 00:04:57,475 - I think they have to because this is the new model, 99 00:04:57,585 --> 00:04:59,195 this is the new API surface. 100 00:04:59,425 --> 00:05:01,515 Like so if you're working with a vendor 101 00:05:01,575 --> 00:05:05,675 and they go we support Microsoft 365 backup, really 102 00:05:05,865 --> 00:05:07,955 what I would believe them to be saying is 103 00:05:08,925 --> 00:05:11,035 we've adopted the API surface 104 00:05:11,225 --> 00:05:13,635 that Microsoft themselves is using 105 00:05:13,895 --> 00:05:15,675 for their backup offerings. 106 00:05:16,095 --> 00:05:20,595 So ISVs and vendors can build upon the same API surface 107 00:05:21,135 --> 00:05:23,315 and offer not only the same capabilities 108 00:05:23,455 --> 00:05:25,755 but also a super set of capabilities depending on 109 00:05:25,755 --> 00:05:26,995 how they choose to approach it. 110 00:05:27,265 --> 00:05:31,115 - Yeah and even before that, so I have a ISV that I use 111 00:05:31,115 --> 00:05:32,635 for my backup because up 112 00:05:32,635 --> 00:05:34,355 until this point in time there wasn't one 113 00:05:34,695 --> 00:05:38,515 and I believe previously it was pay per user 114 00:05:38,815 --> 00:05:41,075 and it was essentially unlimited backup 115 00:05:41,175 --> 00:05:44,435 of exchange SharePoint OneDrive for that user for 116 00:05:44,435 --> 00:05:47,875 that set price in just this past, I don't know, 117 00:05:47,875 --> 00:05:49,035 it was only in the last like three 118 00:05:49,035 --> 00:05:50,795 or four months, they actually came to me 119 00:05:50,795 --> 00:05:53,795 and said you're exceeding your quota. 120 00:05:54,005 --> 00:05:55,435 Which I didn't know I had 121 00:05:55,435 --> 00:05:57,565 because I don't think I actually had one when I signed up 122 00:05:58,065 --> 00:06:00,645 and it was either, they didn't switch it to a PayGo 123 00:06:00,825 --> 00:06:04,405 but it was either go put in policies to trim off your backup 124 00:06:04,545 --> 00:06:07,845 so you don't keep so much more from a retention standpoint 125 00:06:08,265 --> 00:06:11,645 or start buying additional licenses to cover your storage. 126 00:06:12,025 --> 00:06:14,325 So it was, it was still like per user 127 00:06:14,665 --> 00:06:17,445 but it was you have to go buy extra licenses 128 00:06:17,665 --> 00:06:21,365 for non-existent users if you want to back up more data 129 00:06:21,365 --> 00:06:23,885 because you've exceeded what we give you for the amount 130 00:06:23,885 --> 00:06:24,925 of users you're licensing. 131 00:06:25,115 --> 00:06:28,645 - It's one of those weird sass you run into these edge 132 00:06:28,645 --> 00:06:30,405 cases, not even edge cases. 133 00:06:30,555 --> 00:06:32,685 Like somebody had to have think thought about them 134 00:06:32,705 --> 00:06:33,845 and that they were coming up. 135 00:06:33,915 --> 00:06:35,765 It's just like the way they've chosen 136 00:06:35,865 --> 00:06:36,885 to solve them is weird. 137 00:06:37,145 --> 00:06:40,165 It goes back to the old, you know when you needed more space 138 00:06:40,225 --> 00:06:41,325 for your SharePoint tenant 139 00:06:41,825 --> 00:06:44,045 and how did you allocate space for your SharePoint tenant? 140 00:06:44,045 --> 00:06:45,525 Well you just went and bought space 141 00:06:45,585 --> 00:06:47,285 but that was ultimately a license that needed 142 00:06:47,285 --> 00:06:48,645 to be allocated to a user , 143 00:06:48,745 --> 00:06:51,805 hey which user do I allocate that license to 144 00:06:51,805 --> 00:06:55,125 because it goes away then we're in trouble. Yeah 145 00:06:55,365 --> 00:06:56,365 - 'cause that was back 146 00:06:56,625 --> 00:06:58,525 and they have since changed it so it, 147 00:06:58,525 --> 00:06:59,805 this is not the case anymore 148 00:06:59,985 --> 00:07:01,765 but I absolutely had that where you, 149 00:07:01,985 --> 00:07:05,885 it was back when you actually bought add-ons under a 150 00:07:06,125 --> 00:07:09,125 specific user and you're right if that user went away, 151 00:07:09,265 --> 00:07:11,085 so did all the add-ons associated with it. 152 00:07:11,505 --> 00:07:13,965 So you either had to have like that global admin account 153 00:07:13,965 --> 00:07:15,885 that wasn't user based that never went away 154 00:07:16,345 --> 00:07:20,525 or if the user ever went away you had to cancel that 155 00:07:20,525 --> 00:07:22,965 and go buy the add-on all over again for another user. 156 00:07:23,025 --> 00:07:24,685 It was super bizarre. Fortunately 157 00:07:24,685 --> 00:07:26,485 that at least has since been fixed. It's 158 00:07:26,485 --> 00:07:28,405 - Those things that you don't think about 159 00:07:28,575 --> 00:07:30,165 until you run into them, right? 160 00:07:30,235 --> 00:07:32,965 Like and I think you see that a lot in this spaces. 161 00:07:33,295 --> 00:07:36,725 Folks are kind of sort of like testing the market 162 00:07:36,905 --> 00:07:39,285 and poking just as they go. Yeah. 163 00:07:39,465 --> 00:07:41,605 - So going back to Microsoft 365 backup, 164 00:07:41,715 --> 00:07:43,725 like you said OneDrive, SharePoint Exchange, 165 00:07:43,955 --> 00:07:46,885 they do have something on the website that says 166 00:07:47,405 --> 00:07:49,085 Microsoft Teams is coming soon 167 00:07:49,195 --> 00:07:51,605 because all your teams files are stored in SharePoint. 168 00:07:51,705 --> 00:07:53,485 I'm assuming this is more related 169 00:07:53,825 --> 00:07:57,325 to things like maybe chats, conversations. 170 00:07:58,335 --> 00:08:02,005 It'll be interesting to see what is included in teams. 171 00:08:02,465 --> 00:08:05,885 And I'm also curious to see as this continues, 172 00:08:06,235 --> 00:08:07,245 what else they add? 173 00:08:07,395 --> 00:08:11,165 Because last Friday I did a presentation 174 00:08:11,945 --> 00:08:13,765 on backup and restore 175 00:08:13,785 --> 00:08:17,525 and some of the challenges you run into with Microsoft 365 176 00:08:17,525 --> 00:08:18,525 and how to account for 'EM 177 00:08:18,525 --> 00:08:20,925 and OneDrive, SharePoint exchange teams are great 178 00:08:21,105 --> 00:08:23,085 but what a lot of people also don't think about is 179 00:08:23,235 --> 00:08:24,885 what am I doing for planner plans 180 00:08:24,905 --> 00:08:27,485 and what am I doing for power apps and power Automate 181 00:08:27,825 --> 00:08:30,325 and all of my files and emails are great 182 00:08:30,465 --> 00:08:32,925 but what if somebody goes in 183 00:08:32,945 --> 00:08:35,685 and deletes all my users in Azure AD 184 00:08:35,705 --> 00:08:38,645 and then deletes my deleted users in Azure AD 185 00:08:38,645 --> 00:08:40,685 and I no longer have user accounts there 186 00:08:40,705 --> 00:08:44,525 or I lose conditional access policies, Intune policies, 187 00:08:44,845 --> 00:08:46,605 configuration policies, compliance policies, 188 00:08:46,755 --> 00:08:49,365 like there's a lot of stuff in Microsoft 365 189 00:08:49,675 --> 00:08:53,685 that isn't backed up really by Microsoft 365 backup 190 00:08:53,945 --> 00:08:56,925 or for that matter any of the ISVs. 191 00:08:57,305 --> 00:09:01,005 So it will be interesting to see if this expands 192 00:09:01,465 --> 00:09:05,085 and if this truly becomes like a all-inclusive backup 193 00:09:05,465 --> 00:09:07,885 or where this goes over time 194 00:09:07,885 --> 00:09:11,925 because when I hear Microsoft 365 backup my mind goes to, 195 00:09:12,245 --> 00:09:15,685 I would love to see them back up a whole lot more than just 196 00:09:16,175 --> 00:09:18,605 these really three verticals, right? 197 00:09:18,605 --> 00:09:19,845 Because OneDrive is SharePoint. 198 00:09:19,945 --> 00:09:22,205 So really we're talking SharePoint exchange and teams. 199 00:09:22,385 --> 00:09:25,445 - That's part of the part of the things I look to Microsoft 200 00:09:25,465 --> 00:09:28,645 for as a, as a vendor, right? 201 00:09:28,715 --> 00:09:30,565 Like they're the creator of the stack. 202 00:09:30,755 --> 00:09:35,005 Like they're going to be able to do things along the way 203 00:09:35,395 --> 00:09:38,765 that other vendors in the ecosystem can't do 204 00:09:39,125 --> 00:09:40,885 'cause they're not the service owners. 205 00:09:41,465 --> 00:09:43,725 So I would hope that this becomes more 206 00:09:44,365 --> 00:09:45,845 holistic coverage over time. 207 00:09:46,245 --> 00:09:51,085 I don't know how that is going to necessarily 208 00:09:52,725 --> 00:09:55,365 manifest within the services themselves. 209 00:09:55,465 --> 00:09:57,085 So if you talk about things like planner, 210 00:09:57,515 --> 00:10:00,005 planner doesn't really have a backup mechanism 211 00:10:00,185 --> 00:10:01,845 nor a restore mechanism today. 212 00:10:01,985 --> 00:10:05,645 So you need this whole other surface to kind of exist first. 213 00:10:05,715 --> 00:10:09,525 Like what's important in planner plans to restore? 214 00:10:09,525 --> 00:10:12,685 Is it the entire plan? Is it individual items within a plan? 215 00:10:12,825 --> 00:10:14,485 Is it only individual items 216 00:10:14,485 --> 00:10:16,085 that are like tagged in a certain way? 217 00:10:16,475 --> 00:10:19,845 Like I can see how it's hard to rationalize some of that 218 00:10:19,945 --> 00:10:22,085 and put it together and figure out like hey what's the 219 00:10:22,285 --> 00:10:26,565 offering that customers actually need there? 220 00:10:27,035 --> 00:10:28,965 Like a lot of this stuff almost comes down 221 00:10:28,965 --> 00:10:31,765 to you almost want like a magic snapshot button 222 00:10:31,865 --> 00:10:35,205 for your tenant inclusive of all the data in it so 223 00:10:35,205 --> 00:10:36,405 that you could potentially go back 224 00:10:36,405 --> 00:10:38,085 and roll back to a point in time there 225 00:10:38,745 --> 00:10:40,485 or within granularity of 226 00:10:40,505 --> 00:10:42,725 of a given service be it something like planner 227 00:10:42,745 --> 00:10:43,925 or users OneDrive 228 00:10:43,925 --> 00:10:47,005 or whatever it happens, whatever it happens to be. 229 00:10:47,285 --> 00:10:49,205 I think the other thing you gotta figure out here is 230 00:10:50,155 --> 00:10:53,125 does backup make sense for you 231 00:10:53,545 --> 00:10:58,045 and your workload given the way your users use the service, 232 00:10:58,585 --> 00:11:00,125 the pricing for backup 233 00:11:00,945 --> 00:11:03,325 and the functionality that it brings along the way. 234 00:11:03,545 --> 00:11:06,645 So you might find that backup is 235 00:11:07,405 --> 00:11:09,645 a little inflexible. 236 00:11:09,905 --> 00:11:12,685 So like let's take like M 365 backup 237 00:11:13,345 --> 00:11:16,085 in the just retention model alone for it. 238 00:11:16,545 --> 00:11:20,285 So you can do 10 minutes, it's 10 minutes snapshots, 239 00:11:20,285 --> 00:11:22,765 basically like 10 minute backups is your frequency 240 00:11:22,765 --> 00:11:24,925 for backups and then you get a year of retention 241 00:11:25,105 --> 00:11:27,525 and none of that is currently modifiable there. 242 00:11:28,075 --> 00:11:29,405 Like do you actually need that? 243 00:11:29,405 --> 00:11:30,805 And if you don't actually need a year, 244 00:11:30,915 --> 00:11:32,205 like maybe you just need 245 00:11:32,205 --> 00:11:33,565 to get better about things like 246 00:11:33,965 --> 00:11:35,365 recycle bins within the service. 247 00:11:36,105 --> 00:11:38,085 You know that maybe doesn't help you on the exchange side 248 00:11:38,225 --> 00:11:40,845 but if SharePoint's your core concern 249 00:11:40,865 --> 00:11:44,645 and core workload, maybe that's where you're looking to go. 250 00:11:44,955 --> 00:11:47,525 There's a whole lot of kind of mental overhead 251 00:11:47,545 --> 00:11:50,405 and potentially like TCO math that folks need to do 252 00:11:50,945 --> 00:11:51,965 to sit down 253 00:11:52,025 --> 00:11:55,285 and figure out if M 365 backup versus 254 00:11:55,795 --> 00:11:59,405 another vendor's backup offering versus no backup 255 00:11:59,585 --> 00:12:01,005 and it's just a service that's 256 00:12:01,165 --> 00:12:03,205 provided to me is the way to go 257 00:12:03,305 --> 00:12:05,285 and kind of how they choose to live their lives. 258 00:12:05,685 --> 00:12:08,645 - I agree and this is another one I wanna see where it goes, 259 00:12:08,945 --> 00:12:11,885 but it is preview, like you said one your retention 260 00:12:11,945 --> 00:12:14,285 and I had this question during my presentation too. 261 00:12:14,285 --> 00:12:16,885 Someone asked, asked, they were like, well 262 00:12:16,885 --> 00:12:18,485 how much backup is enough? 263 00:12:18,545 --> 00:12:20,365 How often should I be backing stuff up? 264 00:12:20,675 --> 00:12:22,405 Like I don't really know. 265 00:12:22,475 --> 00:12:24,885 It's kind of like your corporate policies, right? 266 00:12:24,955 --> 00:12:26,765 Sometimes you have that 267 00:12:26,765 --> 00:12:29,445 - Is very situationally dependent. Yeah 268 00:12:29,665 --> 00:12:30,965 - You can have regulations 269 00:12:31,505 --> 00:12:34,765 or different compliance requirements of 270 00:12:35,465 --> 00:12:40,045 you need backup data for this long or even 271 00:12:41,055 --> 00:12:43,205 after so much time you don't want 272 00:12:43,205 --> 00:12:44,325 your backups around anymore. 273 00:12:44,325 --> 00:12:47,565 It gets into a little bit of that tension I would say 274 00:12:47,565 --> 00:12:50,165 between retention and retention policies 275 00:12:50,165 --> 00:12:53,365 and backup of you have retention policies in place 276 00:12:53,385 --> 00:12:55,965 for eDiscovery but we've talked about this 277 00:12:55,965 --> 00:12:57,885 before with certain retention policies. 278 00:12:58,185 --> 00:13:00,605 The goal is also to delete content 279 00:13:00,815 --> 00:13:02,005 after a certain amount of time 280 00:13:02,005 --> 00:13:05,645 because if you have it around you can still be liable 281 00:13:05,645 --> 00:13:09,485 for producing it in court cases, that type of stuff. 282 00:13:09,745 --> 00:13:13,125 And how do you balance that even with backup is 283 00:13:13,805 --> 00:13:16,685 Microsoft 365 backup one year retention can't change it. 284 00:13:16,705 --> 00:13:18,565 It is what it is. What if you want 285 00:13:18,565 --> 00:13:19,765 stuff deleted sooner than that? 286 00:13:19,785 --> 00:13:21,325 You only want backups for six months 287 00:13:21,385 --> 00:13:23,445 or you have to keep it longer Or even 288 00:13:23,465 --> 00:13:25,565 how does those retention policies 289 00:13:25,565 --> 00:13:26,725 and backup all play together? 290 00:13:26,915 --> 00:13:29,805 Because if you have retention policies 291 00:13:29,805 --> 00:13:31,245 to intentionally delete stuff 292 00:13:31,245 --> 00:13:34,325 after seven years, I'm thinking financial data in the US 293 00:13:34,675 --> 00:13:36,645 what if your backup is sticking around for 10 years? 294 00:13:36,995 --> 00:13:38,285 That was one question somebody asked me 295 00:13:38,285 --> 00:13:39,325 and I'm like I don't really know. 296 00:13:39,395 --> 00:13:41,445 It's like you said, it's very situational. 297 00:13:41,885 --> 00:13:44,165 I mean personally for me, 298 00:13:44,905 --> 00:13:47,925 unless one year seems like a good amount of time, 299 00:13:48,245 --> 00:13:52,605 I very rarely find myself in a situation whether it be 300 00:13:52,765 --> 00:13:53,765 Microsoft 365 301 00:13:54,105 --> 00:13:56,445 or my date on my devices 302 00:13:57,015 --> 00:14:00,005 where I don't realize I accidentally deleted something 303 00:14:00,305 --> 00:14:01,965 and it's like two years later 304 00:14:02,105 --> 00:14:04,965 and I'm gonna go back through my backups and try to find it. 305 00:14:05,765 --> 00:14:07,845 I think one year is a good place to start. 306 00:14:08,405 --> 00:14:11,445 I think it would be nice to see them expand on that. 307 00:14:11,455 --> 00:14:14,405 Especially given the model that we talked about 308 00:14:14,405 --> 00:14:16,405 where this is very much paper storage. 309 00:14:16,705 --> 00:14:20,645 If I choose to keep this data for 10 years, I'm gonna pay 310 00:14:20,745 --> 00:14:22,405 for this quantity of data 311 00:14:22,675 --> 00:14:24,725 because I'm keeping it around for longer. 312 00:14:25,105 --> 00:14:27,685 So it'll be interesting again, see if this is one 313 00:14:27,685 --> 00:14:29,245 of those just preview limitations. 314 00:14:29,245 --> 00:14:31,645 They wanna see how it goes, they're testing stuff out 315 00:14:31,865 --> 00:14:35,245 and they'll start opening up some of these retentions, 316 00:14:35,705 --> 00:14:36,925 the frequency and I, 317 00:14:36,925 --> 00:14:39,525 that one I can see being a little bit tougher to change 318 00:14:39,665 --> 00:14:42,565 but frankly every 10 minutes seems pretty quick to me. 319 00:14:42,865 --> 00:14:46,085 And then even some of the restore points and all of that 320 00:14:46,225 --> 00:14:49,365 or your RTO, the time to recover those options too. I 321 00:14:49,365 --> 00:14:53,445 - Think the RT o's interesting so Microsoft as a 322 00:14:54,425 --> 00:14:59,205 vendor here and kind of the purveyor of the APIs for this 323 00:14:59,725 --> 00:15:01,765 offering are kind of uniquely positioned 324 00:15:01,825 --> 00:15:03,245 to make some of that stuff happen. 325 00:15:03,905 --> 00:15:08,485 So I think when they talk about things like faster restores, 326 00:15:09,065 --> 00:15:11,645 you know part of it is it's like they can do it 327 00:15:11,645 --> 00:15:13,205 because they are the vendor and 328 00:15:13,205 --> 00:15:14,485 and they have that capability 329 00:15:14,625 --> 00:15:18,645 to say position the storage closer to the workload, 330 00:15:19,175 --> 00:15:21,165 those underlying APIs and 331 00:15:21,185 --> 00:15:24,165 and how they actually orchestrate restorations like 332 00:15:24,165 --> 00:15:26,525 that can all be orchestrated on the backend 333 00:15:26,865 --> 00:15:30,885 and push through to where it needs to be. 334 00:15:31,475 --> 00:15:34,165 It's a little bit of a different offering I think. 335 00:15:34,665 --> 00:15:37,885 You know another thing that folks might want to kind 336 00:15:37,885 --> 00:15:40,165 of think about and rationalize along the way is 337 00:15:40,975 --> 00:15:45,045 where your backups actually like live within this scenario 338 00:15:45,225 --> 00:15:47,525 and how that comes together as well. 339 00:15:48,225 --> 00:15:52,685 So in this case, like you're backing up to some storage 340 00:15:53,275 --> 00:15:56,885 that you don't really have insight into like backup up, 341 00:15:56,885 --> 00:16:00,285 the way it manifests today in M 365, like if you went 342 00:16:00,285 --> 00:16:04,005 and signed up for this preview is you're basically gonna go 343 00:16:04,665 --> 00:16:06,205 and turn it on. 344 00:16:06,435 --> 00:16:09,325 Like you say yep, I'm gonna do PayGo billing for this. 345 00:16:10,185 --> 00:16:11,445 You flip a switch 346 00:16:11,465 --> 00:16:14,045 and you say yep, I'm turning on M 365 backup. 347 00:16:14,505 --> 00:16:17,365 And then you start just creating policies kind 348 00:16:17,365 --> 00:16:18,525 of per service 349 00:16:19,065 --> 00:16:21,405 or I guess per offering, so be it OneDrive, 350 00:16:21,405 --> 00:16:23,765 SharePoint exchange, you're gonna go 351 00:16:23,765 --> 00:16:28,205 and configure policies for each of those, turn those on 352 00:16:28,225 --> 00:16:30,685 and then you are off to the races. 353 00:16:31,225 --> 00:16:33,805 So you know, so far Microsoft hasn't given the capability 354 00:16:34,625 --> 00:16:36,285 to be able to offload 355 00:16:36,345 --> 00:16:39,925 to say like your own storage be it like say like a storage 356 00:16:39,925 --> 00:16:41,645 account in your subscription 357 00:16:42,345 --> 00:16:44,445 in your Azure subscription, something like that. 358 00:16:45,105 --> 00:16:47,285 Or even to be able to like download those backups 359 00:16:47,285 --> 00:16:50,245 and take them off to another site or anything like that. 360 00:16:50,305 --> 00:16:52,365 So kind of the way it works today is you go turn it on, 361 00:16:52,515 --> 00:16:53,845 your data starts backing up, 362 00:16:54,025 --> 00:16:56,485 it does stay within geographic boundaries. 363 00:16:56,785 --> 00:17:01,085 So M 365 has all of its trust boundaries for 364 00:17:01,085 --> 00:17:02,685 where data stays. 365 00:17:02,705 --> 00:17:04,605 Say say you're like a European customer, 366 00:17:04,945 --> 00:17:07,605 you know you're gonna stay in the eu, that kind of thing. 367 00:17:08,155 --> 00:17:11,165 Data residency will be insured, all that good stuff. 368 00:17:11,355 --> 00:17:13,965 - Like you said, it really is easy to go turn it on. 369 00:17:14,145 --> 00:17:15,325 You can do all this in the gui. 370 00:17:15,405 --> 00:17:17,845 I know sometimes Microsoft rolls things out where you have 371 00:17:17,845 --> 00:17:18,965 to use PowerShell first 372 00:17:19,385 --> 00:17:22,045 and the policies, going back to 373 00:17:22,045 --> 00:17:23,965 what we said earlier are pretty straightforward. 374 00:17:24,305 --> 00:17:25,405 If you're a SharePoint admin 375 00:17:25,405 --> 00:17:27,725 or a global admin, you can set 'em up for SharePoint, 376 00:17:27,825 --> 00:17:31,205 global admins Exchange admins can set 'em up for exchange. 377 00:17:31,625 --> 00:17:32,845 But these policies, 378 00:17:33,275 --> 00:17:37,365 because you're kind of limited right now on frequency 379 00:17:37,705 --> 00:17:42,045 and on retention and all of that, it's you go pick OneDrive, 380 00:17:42,045 --> 00:17:43,845 you go pick SharePoint, you pick exchange, 381 00:17:43,955 --> 00:17:46,125 whoever you wanna set that policy up for. 382 00:17:46,585 --> 00:17:50,765 Go set the scope. So are we backing up certain sites, 383 00:17:50,875 --> 00:17:52,165 certain mailboxes 384 00:17:52,785 --> 00:17:56,045 or you can set up that scope to where it is 385 00:17:56,745 --> 00:17:57,925 set based on like, 386 00:17:58,265 --> 00:18:00,165 and I don't know how this works for SharePoint. 387 00:18:00,285 --> 00:18:01,285 I have not gone in 388 00:18:01,285 --> 00:18:03,805 and I, I bet you don't get these options for SharePoint, 389 00:18:03,805 --> 00:18:04,925 for OneDrive, for exchange. 390 00:18:04,925 --> 00:18:07,245 You can actually do it based on distribution lists 391 00:18:07,625 --> 00:18:08,685 or security groups. 392 00:18:09,145 --> 00:18:11,085 So all the users on this particular list, 393 00:18:11,115 --> 00:18:12,565 this particular security groups. 394 00:18:12,745 --> 00:18:15,205 If you do have some differences, maybe 395 00:18:15,305 --> 00:18:18,925 as more options become available based on the users, uh, 396 00:18:18,945 --> 00:18:22,245 you also do have an option to do like an import from A CSV 397 00:18:22,585 --> 00:18:26,885 and then once you select who it is you're going to back up. 398 00:18:27,225 --> 00:18:29,925 It really is just going and turning it on. 399 00:18:30,195 --> 00:18:33,685 There's no, how frequently is this gonna be backed up? 400 00:18:34,185 --> 00:18:35,765 How long is it gonna be retained for? 401 00:18:35,765 --> 00:18:39,525 Because those are just hard coded right now to 10 minutes 402 00:18:39,585 --> 00:18:43,085 for exchange, 15 minutes for OneDrive 403 00:18:43,085 --> 00:18:45,925 and SharePoint for that RPO as long 404 00:18:45,925 --> 00:18:48,285 as it's in the first 14 days. 405 00:18:48,385 --> 00:18:50,325 And this is another interesting thing right, 406 00:18:50,325 --> 00:18:53,445 is you'll be able to go back 15 minute increments up 407 00:18:53,445 --> 00:18:57,085 to the last two weeks after you hit those 14 days. 408 00:18:57,095 --> 00:19:00,325 Those two weeks exchange actually does stay 409 00:19:00,595 --> 00:19:02,165 with a 10 minute RPO 410 00:19:02,345 --> 00:19:05,605 for the entire year versus SharePoint 411 00:19:05,605 --> 00:19:08,405 where once you get past those initial two weeks, your 412 00:19:09,045 --> 00:19:13,405 recovery points for days 15 through 365 are gonna be a week. 413 00:19:13,585 --> 00:19:17,205 And all of this stuff is really just set in stone right now. 414 00:19:17,555 --> 00:19:19,925 This is what it is, you take it when you set up your 415 00:19:20,365 --> 00:19:25,285 policies and that's gonna be how it's going to be set up 416 00:19:25,305 --> 00:19:26,845 and backed up under these policies. 417 00:19:27,385 --> 00:19:29,725 So again, really straightforward 418 00:19:29,905 --> 00:19:31,365 to configure at this point in time. 419 00:19:31,545 --> 00:19:35,485 Really just a next, next select the users, the sites 420 00:19:36,025 --> 00:19:39,125 and turn it on and you're off to the races. 421 00:19:39,325 --> 00:19:44,165 - I guess beyond the recovery point kind of piece 422 00:19:44,165 --> 00:19:47,045 that you made, there's also recovery time 423 00:19:47,785 --> 00:19:49,565 and recovery time starts 424 00:19:49,625 --> 00:19:53,645 to vary a little bit too depending on what you're restoring. 425 00:19:53,825 --> 00:19:57,845 So kind of the general guidance today is a 30 gig mailbox 426 00:19:58,455 --> 00:20:02,565 would recover in less than one hour 427 00:20:02,905 --> 00:20:04,325 and you can kind of get from there 428 00:20:04,375 --> 00:20:08,645 after that it could take up to 12 hours, 429 00:20:08,985 --> 00:20:10,085 I'm gonna say up to 12 hours 430 00:20:10,325 --> 00:20:12,045 'cause the documentation says less than 12. 431 00:20:12,395 --> 00:20:15,125 Less than 12 feels a little bit different than up to 12. 432 00:20:15,485 --> 00:20:16,605 'cause it could be up to 12, 433 00:20:16,715 --> 00:20:18,325 - Less than 12 sounds shorter. 434 00:20:18,475 --> 00:20:20,165 It's kinda like labeling something 435 00:20:20,165 --> 00:20:22,285 with 99 cents instead of the even dollar. 436 00:20:22,525 --> 00:20:23,525 - A little bit of marketing there. 437 00:20:23,945 --> 00:20:28,005 But yeah, so mailboxes like the first restore is gonna be 438 00:20:28,035 --> 00:20:30,965 less than an hour, could be a little bit more 439 00:20:31,185 --> 00:20:33,565 for subsequent restores just as things come down. 440 00:20:34,095 --> 00:20:36,805 SharePoint sites are the same way. 441 00:20:37,025 --> 00:20:40,445 So general guidance they've got out now is 30 gigs less than 442 00:20:40,445 --> 00:20:43,765 an hour and then say you're restoring like a thousand 443 00:20:43,935 --> 00:20:45,325 sites in that same thing. 444 00:20:45,345 --> 00:20:49,005 So the first one less than an hour subsequent ones 445 00:20:49,735 --> 00:20:51,845 could take a little bit, uh, little bit more 446 00:20:52,425 --> 00:20:55,765 but hopefully the entire operation like they've targeted 447 00:20:55,835 --> 00:20:57,285 some pretty aggressive times for those. 448 00:20:57,345 --> 00:21:00,405 So like they're saying like a thousand sites in less 449 00:21:00,435 --> 00:21:01,725 than 12 hours. 450 00:21:01,955 --> 00:21:03,885 They're also saying a thousand mailboxes, 451 00:21:04,115 --> 00:21:07,365 like on average 30 gigs less than 12 hours 452 00:21:07,625 --> 00:21:09,085 to bring those back. 453 00:21:09,665 --> 00:21:11,045 So this was a little funny to me too. 454 00:21:11,045 --> 00:21:12,925 You mentioned like Gooeys to turn it all on, 455 00:21:13,435 --> 00:21:17,245 it's also gooeys to manage it all today at least as far 456 00:21:17,245 --> 00:21:19,325 as even doing restores and things like that. 457 00:21:19,705 --> 00:21:21,205 So you kind of just go into the gooey 458 00:21:21,205 --> 00:21:25,125 and you say, all right, here's my recovery point, you know, 459 00:21:25,185 --> 00:21:27,405 browse by datetime, get to the point you wanna be 460 00:21:27,705 --> 00:21:28,845 and then you just click the button 461 00:21:28,905 --> 00:21:30,525 and you say whether you're going back 462 00:21:30,525 --> 00:21:33,565 to the original location or a new destination 463 00:21:34,225 --> 00:21:35,845 and you're done. 464 00:21:35,955 --> 00:21:37,725 Like you're just off to the races. 465 00:21:37,785 --> 00:21:41,485 So very much like the simple, simple, simple view 466 00:21:41,485 --> 00:21:44,365 of backup today, I don't know that that's a bad thing, 467 00:21:44,745 --> 00:21:45,965 you know given the customer base 468 00:21:45,965 --> 00:21:49,645 and where things are at, like accessibility is probably 469 00:21:50,185 --> 00:21:53,005 way easier for this than lots of other admin tasks 470 00:21:53,035 --> 00:21:54,765 that you would have to do within the stack. 471 00:21:55,045 --> 00:21:58,045 - I like keeping it simple like that. I have no problems. 472 00:21:58,095 --> 00:22:01,085 Again, it would be nice to see at least retention maybe 473 00:22:01,505 --> 00:22:03,885 change down the road but I don't know 474 00:22:03,885 --> 00:22:07,085 that you need a whole lot more than 475 00:22:07,085 --> 00:22:08,485 what they have right now. 476 00:22:08,945 --> 00:22:10,885 So I'm with you. I like the simple, 477 00:22:11,325 --> 00:22:13,925 I like the way it's set up at least for now. 478 00:22:14,105 --> 00:22:16,445 I'm sure there will be more stuff that gets added, 479 00:22:16,755 --> 00:22:18,965 gets updated, gets changed in the future. 480 00:22:19,565 --> 00:22:21,325 I feel like there was something else I was gonna say 481 00:22:21,325 --> 00:22:23,525 and it's completely gone now. We should 482 00:22:23,685 --> 00:22:25,045 - Probably, before we move on to archive, 483 00:22:25,065 --> 00:22:27,005 we should probably talk pricing for this one real quick 484 00:22:27,205 --> 00:22:28,045 'cause it is a little bit of a 485 00:22:28,045 --> 00:22:29,085 different pricing model. Yeah 486 00:22:29,085 --> 00:22:31,165 - And one thing you did mention that I do like is they do 487 00:22:31,165 --> 00:22:33,405 give you that option too to restore to a different location. 488 00:22:33,505 --> 00:22:34,605 So if you do wanna restore 489 00:22:34,605 --> 00:22:37,325 to a different SharePoint site versus the original one, 490 00:22:37,675 --> 00:22:40,005 it's nice to see that built into this preview as well. 491 00:22:43,665 --> 00:22:45,245 Do you feel overwhelmed by trying 492 00:22:45,245 --> 00:22:47,525 to manage your Office 365 environment? 493 00:22:47,665 --> 00:22:49,405 Are you facing unexpected issues 494 00:22:49,435 --> 00:22:51,285 that disrupt your company's productivity? 495 00:22:51,285 --> 00:22:53,885 Intelligent is here to help much like you take your car 496 00:22:53,885 --> 00:22:56,725 to the mechanic that has specialized knowledge on how 497 00:22:56,725 --> 00:22:59,565 to best keep your car running Intelligent helps you 498 00:22:59,565 --> 00:23:01,285 with your Microsoft Cloud environment 499 00:23:01,285 --> 00:23:02,885 because that's their expertise. 500 00:23:03,035 --> 00:23:04,325 Intelligent keeps up 501 00:23:04,325 --> 00:23:06,405 with the latest updates in the Microsoft cloud 502 00:23:06,405 --> 00:23:07,845 to help keep your business running 503 00:23:08,205 --> 00:23:09,365 smoothly and ahead of the curve. 504 00:23:09,395 --> 00:23:11,125 Whether you are a small organization 505 00:23:11,125 --> 00:23:13,645 with just a few users up to an organization 506 00:23:13,645 --> 00:23:17,085 of several thousand employees, they want to partner with you 507 00:23:17,105 --> 00:23:20,525 to implement and administer your Microsoft Cloud technology, 508 00:23:21,095 --> 00:23:24,485 visit them at intelligent.com/podcast. 509 00:23:24,945 --> 00:23:29,365 That's I-N-T-E-L-L-I-G-I-N 510 00:23:29,445 --> 00:23:33,045 k.com/podcast for more information 511 00:23:33,045 --> 00:23:34,765 or to schedule a 30 minute call 512 00:23:34,765 --> 00:23:36,085 to get started with them today. 513 00:23:36,925 --> 00:23:39,565 Remember intelligent focuses on the Microsoft cloud 514 00:23:39,705 --> 00:23:44,285 so you can focus on your business Pricing. 515 00:23:45,035 --> 00:23:47,565 This one's interesting. We were talking about this a little 516 00:23:47,585 --> 00:23:49,445 bit before the show 517 00:23:50,065 --> 00:23:53,245 and like you mentioned it is pay 518 00:23:53,785 --> 00:23:56,965 per gigabyte in terms of backup storage 519 00:23:57,545 --> 00:23:59,965 and my article is not, 520 00:24:00,145 --> 00:24:02,645 it is 15 cents per gigabyte backed up 521 00:24:02,825 --> 00:24:04,845 and they have a pricing calculator for this. 522 00:24:05,165 --> 00:24:07,085 I should go over here, I do not have it, 523 00:24:07,295 --> 00:24:10,125 which actually just brings you to a shared Excel spreadsheet 524 00:24:10,225 --> 00:24:11,405 for the pricing calculator, 525 00:24:11,985 --> 00:24:15,485 but it is 15 cents bringing gigabyte backed up 526 00:24:15,865 --> 00:24:18,885 and then I believe there was pricing two on the restore 527 00:24:18,985 --> 00:24:23,405 and I am drawing a big blank here on terms of 528 00:24:23,455 --> 00:24:27,765 where I jotted that down or where I saw that. Where'd 529 00:24:27,765 --> 00:24:28,765 - It go? 530 00:24:28,765 --> 00:24:30,365 I know archive had a restore price. 531 00:24:30,725 --> 00:24:32,965 I don't remember it for backup off the top of my head. 532 00:24:32,965 --> 00:24:34,365 - Backup. It doesn't look like it. 533 00:24:34,385 --> 00:24:36,885 Backup is just 15 cents per gigabyte per month. 534 00:24:36,975 --> 00:24:39,525 We'll go with that. I think it was archive. 535 00:24:39,865 --> 00:24:41,725 So this is interesting to me Scott 536 00:24:42,145 --> 00:24:43,925 and we were talking about it 537 00:24:43,925 --> 00:24:47,885 because SharePoint storage not backup like hot storage, 538 00:24:47,995 --> 00:24:51,245 keep it in a SharePoint site is 20 cents 539 00:24:51,545 --> 00:24:52,725 per gigabyte per month. 540 00:24:53,185 --> 00:24:57,765 So backup, yes it is saving, saving you some 541 00:24:58,345 --> 00:25:00,285 but it is not saving you. 542 00:25:01,165 --> 00:25:03,245 I would say it's not saving you as much as I maybe 543 00:25:03,915 --> 00:25:05,205 anticipated it would. 544 00:25:05,875 --> 00:25:07,565 Also given the pricing, 545 00:25:07,825 --> 00:25:08,885 and this is 546 00:25:08,885 --> 00:25:11,125 where my head initially went when we first started talking 547 00:25:11,125 --> 00:25:14,205 about it, is you look at something like Azure blob storage 548 00:25:14,375 --> 00:25:17,765 where your Azure blob storage pricing is 549 00:25:18,435 --> 00:25:20,885 less than 10 cents per month 550 00:25:21,185 --> 00:25:23,725 for most types of storage. 551 00:25:24,135 --> 00:25:25,165 Again, you get into some 552 00:25:25,165 --> 00:25:27,645 of the premium versus hot versus cool versus cold. 553 00:25:28,225 --> 00:25:31,085 The what we were talking about the different redundancy 554 00:25:31,085 --> 00:25:34,405 options and blob storage and I think I looked at that 555 00:25:34,785 --> 00:25:37,245 and I looked at even things like a 556 00:25:37,755 --> 00:25:39,165 locally redundant storage, 557 00:25:39,175 --> 00:25:41,805 which we talked about probably not a good idea for backup, 558 00:25:42,345 --> 00:25:45,845 but that colder cool storage where I tend 559 00:25:45,845 --> 00:25:48,645 to like back up my files is 1 cent 560 00:25:48,825 --> 00:25:50,885 to less than a cent per gigabyte 561 00:25:50,905 --> 00:25:54,725 and I'm like man, 15 cents for SharePoint seems expensive. 562 00:25:54,985 --> 00:25:56,245 But then you pointed out some things 563 00:25:56,265 --> 00:26:00,205 and I'm curious your thoughts on this as well, 564 00:26:00,215 --> 00:26:05,085 especially given some of your storage experience in thinking 565 00:26:05,085 --> 00:26:08,165 through why it might be that pricing model 566 00:26:08,385 --> 00:26:11,405 or some of the reasons I still don't know that we came up 567 00:26:11,405 --> 00:26:13,805 with 15 cents, but it's, it's interesting. I 568 00:26:13,805 --> 00:26:15,805 - Think the first thing you have to keep in mind is, 569 00:26:16,225 --> 00:26:17,805 and it's easy to fall into this trap, 570 00:26:18,385 --> 00:26:20,445 is you're coming at it from the lens 571 00:26:20,945 --> 00:26:25,885 of oh they're charging me x cents per gigabyte for storage. 572 00:26:26,025 --> 00:26:27,365 Yep. You immediately go in your head 573 00:26:27,385 --> 00:26:30,085 to well what's the price that I can get for storage 574 00:26:30,145 --> 00:26:31,285 and other other places? 575 00:26:32,265 --> 00:26:36,085 The problem with that is it's not just X sense a gigabyte 576 00:26:36,085 --> 00:26:40,205 for storage, it's X sense a gigabyte plus hosting the API 577 00:26:40,205 --> 00:26:43,245 surface plus doing all the r and d and the the dev 578 00:26:43,265 --> 00:26:45,045 and all the other things that go on top of it, right? 579 00:26:45,425 --> 00:26:47,845 So there's some component in there that like, 580 00:26:48,235 --> 00:26:51,605 yeah you're paying for it because it's part of the service 581 00:26:51,705 --> 00:26:52,885 and it costs money to host 582 00:26:53,105 --> 00:26:55,325 and like what's that infrastructure look like? 583 00:26:55,385 --> 00:26:57,005 So like in this case for backup, 584 00:26:57,345 --> 00:27:00,365 you're not like giving it your own storage account 585 00:27:00,545 --> 00:27:02,005 or pointing it to a NAS 586 00:27:02,065 --> 00:27:03,725 or anything like that in your environment. 587 00:27:04,075 --> 00:27:06,805 Like it's just click a button, turn it on and it's there. 588 00:27:07,055 --> 00:27:10,965 Which means somebody else, Microsoft in this case with 589 00:27:10,965 --> 00:27:14,605 with their offering is in the background doing some things 590 00:27:14,635 --> 00:27:16,605 like they've probably gotta go provision more storage, 591 00:27:16,605 --> 00:27:19,125 they've gotta go light things up, they've gotta make sure 592 00:27:19,125 --> 00:27:24,045 that it meets the the promises of the service when it comes 593 00:27:24,105 --> 00:27:25,605 to things like durability 594 00:27:26,225 --> 00:27:29,085 and how that composes like you might be looking at just like 595 00:27:29,085 --> 00:27:33,805 an LRS storage account where if you look at like M 365, 596 00:27:33,905 --> 00:27:35,525 the way I think about M 365 597 00:27:35,625 --> 00:27:37,445 and like the way it manifests as a service, 598 00:27:37,855 --> 00:27:41,165 especially within like a geo again like let's take the EU 599 00:27:41,165 --> 00:27:43,925 or the U US or something like that is, 600 00:27:44,315 --> 00:27:46,485 it's not really like LRS at all. 601 00:27:46,555 --> 00:27:49,605 It's not really ZRS, it's something like plus , 602 00:27:49,865 --> 00:27:51,165 you know, where your data can kind 603 00:27:51,165 --> 00:27:52,965 of like live in a geo across a geo. 604 00:27:53,065 --> 00:27:56,165 So clearly there's other I think things 605 00:27:56,165 --> 00:27:58,725 that have been done there that just manifest in the service 606 00:27:58,865 --> 00:28:01,405 and then they kind of cost money along the way 607 00:28:01,785 --> 00:28:03,885 and then somebody needs to make money on it. 608 00:28:04,065 --> 00:28:06,085 That's the other stark reality 609 00:28:06,145 --> 00:28:08,445 and I don't know like what that looks like and, 610 00:28:08,545 --> 00:28:11,325 and you know what people's margins are 611 00:28:11,325 --> 00:28:13,005 and their targets and all those kinds of things. 612 00:28:13,225 --> 00:28:16,725 But at the end of the day like the price is the price 613 00:28:16,785 --> 00:28:17,805 and that's where they landed. 614 00:28:18,265 --> 00:28:21,405 So you know, you as a customer really do need to go out 615 00:28:21,405 --> 00:28:24,285 and kind of figure out like hey what's the TCO in 616 00:28:24,285 --> 00:28:25,485 this offering for me? 617 00:28:25,595 --> 00:28:29,245 Like is it worth it in its current form as it manifests 618 00:28:29,245 --> 00:28:30,245 with its set of capabilities? 619 00:28:30,315 --> 00:28:31,765 Like do you want to continue 620 00:28:31,765 --> 00:28:33,885 with like your third party backup provider 621 00:28:34,225 --> 00:28:35,285 or do you wanna go to this 622 00:28:35,385 --> 00:28:38,325 or do you wanna potentially do some mix of both? 623 00:28:38,335 --> 00:28:41,165 Right? Is there a subset where you can create a set 624 00:28:41,165 --> 00:28:42,605 of policies and 625 00:28:42,665 --> 00:28:44,325 and make those kinds of things work 626 00:28:44,345 --> 00:28:46,205 and come together? I don't know. Yeah, 627 00:28:46,485 --> 00:28:49,005 - I mean maybe that's part of it too is maybe you end up 628 00:28:49,005 --> 00:28:50,685 with a mix of this and a third party. 629 00:28:51,325 --> 00:28:55,405 I think the advantage of maybe a third party is some 630 00:28:55,405 --> 00:28:58,205 of these third parties do give you the option 631 00:28:58,205 --> 00:29:02,485 of I wanna back this up to AWS or I'm going to blob storage 632 00:29:02,785 --> 00:29:06,205 and I will say with those you're probably not going to get, 633 00:29:06,425 --> 00:29:08,445 or what I've seen and it'll be interesting 634 00:29:08,445 --> 00:29:11,445 to see is these third parties start using this new API 635 00:29:11,605 --> 00:29:13,445 that's a part of Microsoft 365 backup 636 00:29:13,445 --> 00:29:16,445 because they could also build their solutions on it is 637 00:29:16,825 --> 00:29:19,445 you're not able to get the speed the RTO 638 00:29:19,445 --> 00:29:21,965 and the RPO of in third parties 639 00:29:21,995 --> 00:29:23,805 that you can in Microsoft 365. 640 00:29:24,545 --> 00:29:28,405 So there could be that argument of there's certain sites 641 00:29:28,405 --> 00:29:30,885 where I don't need the frequency 642 00:29:31,065 --> 00:29:34,365 or the speed in my restore, so maybe I use a third party 643 00:29:34,585 --> 00:29:38,525 for some of my sites and I use the Microsoft 365 backup 644 00:29:38,525 --> 00:29:41,405 because like we said, you can't select them for more 645 00:29:41,405 --> 00:29:42,765 of those business critical sites 646 00:29:42,765 --> 00:29:44,925 where you do want a faster RPO and RTO. 647 00:29:45,195 --> 00:29:46,605 This one will be an interesting one 648 00:29:46,825 --> 00:29:49,085 to watch over time to see where it goes. 649 00:29:49,645 --> 00:29:51,925 I don't know that I'm gonna switch from a third party yet. 650 00:29:52,045 --> 00:29:55,005 I look at the cost of backup for me 651 00:29:55,265 --> 00:29:56,725 and what my requirements are 652 00:29:57,065 --> 00:29:59,125 and I start comparing like, 653 00:29:59,805 --> 00:30:02,085 I mean I have a fair amount of data in my tenant. 654 00:30:02,485 --> 00:30:06,685 I am several hundred gigabytes even for me backing up, 655 00:30:06,775 --> 00:30:10,365 let's say it's 500 gigabytes at 15 cents a month, 656 00:30:10,365 --> 00:30:12,965 that's $75 a month over the course of a year. 657 00:30:13,105 --> 00:30:14,845 That's $900 for my backup. 658 00:30:15,085 --> 00:30:19,245 I think right now I'm paying in the realm of like two 659 00:30:19,305 --> 00:30:20,565 to 300 a year. 660 00:30:20,705 --> 00:30:23,005 So this is like three times what I'm paying now, 661 00:30:23,665 --> 00:30:27,445 but I don't have the integration into the admin interface. 662 00:30:27,685 --> 00:30:29,565 I definitely don't have the backup speed. 663 00:30:29,985 --> 00:30:33,165 I'm lucky to get once a day backups I think is 664 00:30:33,165 --> 00:30:36,405 what I get now and included in that I think my, 665 00:30:37,045 --> 00:30:38,285 I think I have a terabyte of backup 666 00:30:38,385 --> 00:30:39,925 for like the four licenses I have. 667 00:30:40,065 --> 00:30:43,885 So this is definitely one of those that you really like. 668 00:30:43,885 --> 00:30:45,565 A lot of things should evaluate your requirements, 669 00:30:45,565 --> 00:30:48,645 what you need, what you don't need, the cost associated 670 00:30:48,645 --> 00:30:51,045 with it and is it worth it for you. I 671 00:30:51,045 --> 00:30:52,285 - Know nobody likes to sit down in front 672 00:30:52,285 --> 00:30:53,445 of a pricing calculator 673 00:30:53,545 --> 00:30:55,325 but somebody's gotta sit down in front 674 00:30:55,325 --> 00:30:57,405 of a pricing calculator for this one. Moving 675 00:30:57,505 --> 00:30:59,445 - On, that was backup archive. 676 00:30:59,795 --> 00:31:01,805 This is yeah, archive. 677 00:31:02,145 --> 00:31:05,805 So this is somewhere between archive, between archive 678 00:31:06,115 --> 00:31:08,125 between live storage and backup. 679 00:31:08,625 --> 00:31:10,285 Backup like we talked about. 680 00:31:10,315 --> 00:31:13,405 It's somebody deleted all my data, ransomware got in, 681 00:31:13,845 --> 00:31:16,485 synchronized all my content up, all my emails are gone, 682 00:31:16,845 --> 00:31:19,165 I need to restore from somewhere else. 683 00:31:19,755 --> 00:31:21,285 Archive on the other hand. 684 00:31:21,305 --> 00:31:25,685 And Microsoft 365 archive is going 685 00:31:26,235 --> 00:31:29,405 into more just SharePoint for this one. 686 00:31:29,465 --> 00:31:33,805 So this one is not going across exchange or other services. 687 00:31:34,475 --> 00:31:36,445 This is geared towards SharePoint 688 00:31:36,965 --> 00:31:38,765 archiving your content in place. 689 00:31:39,065 --> 00:31:42,365 So older data we talked about with backup, some 690 00:31:42,365 --> 00:31:44,205 of the retention stuff after a year, 691 00:31:44,665 --> 00:31:47,445 I'm no longer using this data or this is for an old client. 692 00:31:47,805 --> 00:31:50,005 I feel like me, I have teams 693 00:31:50,145 --> 00:31:52,245 or SharePoint sites for all the different clients. 694 00:31:52,635 --> 00:31:54,445 Some of those clients I haven't worked 695 00:31:54,445 --> 00:31:55,685 with in three or four years. 696 00:31:56,425 --> 00:31:57,725 I'm not in a backup scenario 697 00:31:58,105 --> 00:32:00,165 but I'm more in that inplace archive. 698 00:32:00,285 --> 00:32:03,525 I wanna maybe not pay the full price 699 00:32:03,705 --> 00:32:04,805 for my SharePoint storage 700 00:32:05,145 --> 00:32:07,045 and I just wanna go put this somewhere 701 00:32:07,045 --> 00:32:09,525 where it's a little bit cheaper to store it so 702 00:32:09,685 --> 00:32:11,805 that I can get to it, restore it, pull 703 00:32:11,805 --> 00:32:14,125 that data back at some point in time in 704 00:32:14,125 --> 00:32:15,205 the future if I want it. 705 00:32:15,905 --> 00:32:18,485 And again, this is only SharePoint 706 00:32:18,635 --> 00:32:21,965 because Exchange has a had archive for a while. 707 00:32:22,025 --> 00:32:23,765 Now the online archive that's included 708 00:32:23,835 --> 00:32:26,205 with your exchange mailboxes. 709 00:32:26,685 --> 00:32:28,765 I can be another topic of if that will remain 710 00:32:28,765 --> 00:32:30,925 or if that somehow gets rolled into this in the future. 711 00:32:31,505 --> 00:32:35,925 But today this is Microsoft 365 archive is SharePoint 712 00:32:36,315 --> 00:32:37,965 only for that purpose. 713 00:32:38,185 --> 00:32:40,285 - The way I like to think about these, like if you're trying 714 00:32:40,285 --> 00:32:41,405 to balance them in in your head 715 00:32:41,405 --> 00:32:43,845 and you're, you go okay there's backup over here, 716 00:32:43,845 --> 00:32:45,365 there's archive over here, like 717 00:32:45,395 --> 00:32:46,725 what the heck is the difference? 718 00:32:47,205 --> 00:32:48,885 I think one of the kind of things 719 00:32:48,905 --> 00:32:51,285 to key in on is you mentioned in place 720 00:32:51,785 --> 00:32:56,365 and archive is effectively an in place archive versus 721 00:32:56,365 --> 00:32:57,445 something like a backup, 722 00:32:57,775 --> 00:33:00,685 which even though it's abstracted away from you is kind 723 00:33:00,685 --> 00:33:02,445 of taking your data out of the surface. 724 00:33:02,665 --> 00:33:05,525 Uh, service. So those backups are stored 725 00:33:05,585 --> 00:33:06,685 in a, in a different place. 726 00:33:07,305 --> 00:33:09,365 Now there's some operational benefits 727 00:33:09,545 --> 00:33:11,845 to archive versus backup here. 728 00:33:11,865 --> 00:33:15,645 So one is gonna be even faster like it is, you know 729 00:33:15,645 --> 00:33:18,245 to the degree it can be even faster on things like 730 00:33:18,815 --> 00:33:21,445 being able to perform a restoration 731 00:33:21,545 --> 00:33:23,405 or rehydration from archive. 732 00:33:23,675 --> 00:33:26,285 There's no difference in the security 733 00:33:26,345 --> 00:33:27,765 domain, which I think is big. 734 00:33:27,795 --> 00:33:29,885 Like you never have to worry about crossing some 735 00:33:30,085 --> 00:33:31,565 external boundary or anything like that. 736 00:33:31,675 --> 00:33:35,005 Like it is all just in the service native. 737 00:33:35,545 --> 00:33:38,365 And then the other cool thing about archive versus something 738 00:33:38,365 --> 00:33:42,925 like backup is in archive land your, 739 00:33:43,705 --> 00:33:46,325 at least the way it works with SharePoint archive today 740 00:33:47,345 --> 00:33:48,885 or M 365 archive, 741 00:33:48,885 --> 00:33:52,565 which is four SharePoint sites today is your search indices 742 00:33:53,265 --> 00:33:54,485 remain in place. 743 00:33:55,145 --> 00:33:56,445 So if you go ahead 744 00:33:56,445 --> 00:33:58,045 and you archive content, 745 00:33:59,025 --> 00:34:01,565 end users will lose the ability to search. 746 00:34:01,985 --> 00:34:03,805 But admins retain the ability 747 00:34:03,865 --> 00:34:07,605 to search within those indices, which is kind of nifty 748 00:34:07,825 --> 00:34:10,685 and kind of powerful I think within this 749 00:34:10,945 --> 00:34:12,765 as a service offering. 750 00:34:13,345 --> 00:34:16,485 So if you're going out and say doing like a compliance 751 00:34:16,485 --> 00:34:17,765 search or something like that, 752 00:34:18,265 --> 00:34:20,285 you're still gonna be covered on the 753 00:34:20,715 --> 00:34:22,045 archive site to get that out. 754 00:34:22,465 --> 00:34:23,685 So it's really kind of nifty. 755 00:34:23,685 --> 00:34:27,045 It's, it's all a native construct within the service. 756 00:34:27,515 --> 00:34:28,645 Like if you go ahead 757 00:34:28,905 --> 00:34:33,045 and you archive a site, when you rehydrate 758 00:34:33,155 --> 00:34:34,925 that site it gets rehydrated. 759 00:34:34,925 --> 00:34:38,925 There's no loss of metadata, no loss of security versioning, 760 00:34:38,995 --> 00:34:40,725 like any of that stuff. 761 00:34:40,865 --> 00:34:43,085 It just comes back because it's SharePoint 762 00:34:43,085 --> 00:34:44,285 and SharePoint knows SharePoint. 763 00:34:44,665 --> 00:34:46,485 So I think they did kind of a, a really good job 764 00:34:47,005 --> 00:34:49,245 building out like that piece of the service 765 00:34:49,905 --> 00:34:53,885 and getting it to a point where it just, it makes sense. 766 00:34:54,625 --> 00:34:57,485 Now you could run into some weirdness along the way like you 767 00:34:57,485 --> 00:34:59,845 know, this is back archive for SharePoint sites. 768 00:35:00,225 --> 00:35:01,925 Not all sites are supported, 769 00:35:01,995 --> 00:35:04,805 like not all site templates are are out there supported 770 00:35:04,805 --> 00:35:07,405 today and yeah your, 771 00:35:07,405 --> 00:35:09,725 your mileage might vary a little bit along the way. 772 00:35:10,085 --> 00:35:12,605 I imagine they improve coverage coverage there. 773 00:35:13,035 --> 00:35:14,805 Another big difference between this 774 00:35:15,105 --> 00:35:18,125 and backup is we mentioned backup, like you just kind 775 00:35:18,125 --> 00:35:20,685 of just go turn it on and pay for it with archive 776 00:35:21,265 --> 00:35:26,005 before you can turn on Pego billing for archive you have 777 00:35:26,005 --> 00:35:28,925 to have an Azure subscription and an Azure resource group 778 00:35:29,585 --> 00:35:32,645 and those need to be provisioned prior 779 00:35:32,785 --> 00:35:36,525 to turning on the M 365 archive service. 780 00:35:36,865 --> 00:35:40,485 - And that was interesting to me as well. 781 00:35:40,515 --> 00:35:44,525 Also given like when we talked about backup, this indicates 782 00:35:44,525 --> 00:35:47,885 that almost archive is using some of 783 00:35:47,885 --> 00:35:49,805 that Azure storage on the backend 784 00:35:49,905 --> 00:35:52,205 for the archive like it versus backup 785 00:35:52,255 --> 00:35:54,685 where you're not using an Azure subscription. 786 00:35:54,685 --> 00:35:57,205 So it must be going someplace 787 00:35:57,755 --> 00:36:00,325 else would be maybe my assumption 788 00:36:00,385 --> 00:36:03,485 and maybe again some of those differences in prices 789 00:36:03,945 --> 00:36:06,205 and even when you start looking through some 790 00:36:06,205 --> 00:36:09,405 of the documentation, it references things like archive is 791 00:36:09,405 --> 00:36:12,405 going to a cooler storage, whether that's cool storage 792 00:36:12,465 --> 00:36:15,725 and Azure blob or not, I don't really know. 793 00:36:16,125 --> 00:36:18,965 I haven't gone in and turned this on yet. 794 00:36:19,405 --> 00:36:21,885 I would imagine that you're not actually able 795 00:36:21,945 --> 00:36:24,085 to see anything in that resource group 796 00:36:24,115 --> 00:36:26,845 that somehow this is tied to an Azure subscription. 797 00:36:27,185 --> 00:36:29,645 The fact that you need an Azure resource group means 798 00:36:29,645 --> 00:36:33,245 that I would assume something in here is going into 799 00:36:33,245 --> 00:36:36,085 that resource group, some resource is getting created, 800 00:36:36,435 --> 00:36:38,205 somehow the data's going in there 801 00:36:38,705 --> 00:36:40,685 and that you're then getting charged 802 00:36:41,695 --> 00:36:43,125 based on the data going in there. 803 00:36:43,155 --> 00:36:44,605 It's, it's interesting 804 00:36:44,605 --> 00:36:46,565 to see the differences in these building models, the 805 00:36:46,565 --> 00:36:48,645 - Joys of hosted on behalf of Yeah, 806 00:36:48,785 --> 00:36:52,045 you would be amazed at the amount of stuff that gets lit up 807 00:36:52,105 --> 00:36:55,925 inside like say your Azure subscriptions that you can't see 808 00:36:55,925 --> 00:36:57,565 that potentially come from like another 809 00:36:57,565 --> 00:36:59,405 service or something like that. , 810 00:36:59,925 --> 00:37:00,925 - I am sure. 811 00:37:01,105 --> 00:37:03,085 So this one as well, once you get 812 00:37:03,085 --> 00:37:06,245 that Azure subscription set up similar you need global admin 813 00:37:06,245 --> 00:37:07,845 or SharePoint admin for this one 814 00:37:08,785 --> 00:37:12,925 and you go turn this all on in the admin center, 815 00:37:13,075 --> 00:37:14,525 turn it off in the admin center. 816 00:37:14,945 --> 00:37:19,325 That's really all there is to it from a setup perspective. 817 00:37:19,465 --> 00:37:21,085 That's it. Yeah, it's look at basic, 818 00:37:21,265 --> 00:37:23,605 - You kind of turn it on, you start getting billed 819 00:37:23,865 --> 00:37:26,125 and then if you want to turn it off, 820 00:37:26,155 --> 00:37:28,525 just make sure you rehydrate everything first. 821 00:37:29,145 --> 00:37:30,165 So we should also mention 822 00:37:30,755 --> 00:37:33,445 that there's effectively a rehydration fee 823 00:37:33,935 --> 00:37:35,645 associated with this as well. 824 00:37:35,835 --> 00:37:38,565 Like when you're bringing items back from archive. 825 00:37:38,785 --> 00:37:40,005 So you know, 826 00:37:40,005 --> 00:37:42,885 you talked about like SharePoint storage being just 20 cents 827 00:37:42,925 --> 00:37:46,005 a gig and we talked about backup being 828 00:37:46,035 --> 00:37:47,645 15 cents a gig a month. 829 00:37:48,305 --> 00:37:52,165 Now archive is 5 cents a gig a month 830 00:37:52,785 --> 00:37:55,765 and that's in start contrast to like that 20 cents a gig. 831 00:37:55,765 --> 00:37:57,525 So you're getting some material savings there. Yep. 832 00:37:57,625 --> 00:37:59,885 But the reactivation of archive data, 833 00:37:59,905 --> 00:38:02,685 if it passes the seven day mark, 834 00:38:03,065 --> 00:38:07,685 you'll pay 60 cents a gigabyte effectively to rehydrate 835 00:38:07,835 --> 00:38:10,605 that archived item and get it up to where it needs to be. 836 00:38:10,625 --> 00:38:13,565 So another another thing that you'll need to account 837 00:38:13,565 --> 00:38:16,405 for in like your TCO calculations for something like archive 838 00:38:17,025 --> 00:38:21,525 is how often you actually rehydrate or intend to rehydrate. 839 00:38:21,925 --> 00:38:24,565 - I like this one more. So this one actually excites me more 840 00:38:24,565 --> 00:38:26,925 about than backup because I did have other options 841 00:38:26,925 --> 00:38:29,125 for backup and this might also be some 842 00:38:29,125 --> 00:38:32,525 of the pricing differences that we see here is, 843 00:38:32,985 --> 00:38:34,965 to your point, you do need to rehydrate, you pay 844 00:38:35,045 --> 00:38:39,925 to rehydrate but your rehydration here is not 845 00:38:40,025 --> 00:38:42,085 as fast as those backups are. 846 00:38:42,305 --> 00:38:44,925 So really your backups probably also have 847 00:38:44,925 --> 00:38:49,245 to be sitting on a higher tier storage with faster io, 848 00:38:49,425 --> 00:38:52,125 faster bandwidth, all of that when you're doing backup 849 00:38:52,785 --> 00:38:55,645 versus these archives, you can go into cheaper storage 850 00:38:55,875 --> 00:38:59,885 because it's not gonna come back as fast when you go choose 851 00:39:00,025 --> 00:39:01,725 to rehydrate this data. 852 00:39:02,325 --> 00:39:03,405 I can't remember what it was, 853 00:39:03,465 --> 00:39:06,325 but I wanna say it was, I was just looking 854 00:39:06,325 --> 00:39:09,005 through the documentation here on if it actually says 855 00:39:09,185 --> 00:39:11,645 how long it will take to come 856 00:39:11,645 --> 00:39:12,845 back don't but I wanna say it was 857 00:39:12,845 --> 00:39:13,565 - Like hours. I don't remember seeing 858 00:39:14,205 --> 00:39:14,965 - Anything. I don't either. 859 00:39:15,225 --> 00:39:17,125 - All I remember seeing is very fast. 860 00:39:17,765 --> 00:39:19,805 'cause you're effectively like in place. 861 00:39:19,995 --> 00:39:21,365 It's it's, it's more like a 862 00:39:22,285 --> 00:39:24,845 snapshot versus an offloaded backup is kind 863 00:39:24,845 --> 00:39:27,925 of the way I was thinking about it in my head as I was going 864 00:39:27,925 --> 00:39:30,165 through and looking at the way you light it up the way 865 00:39:30,725 --> 00:39:32,045 restores orchestrated. 866 00:39:32,325 --> 00:39:35,605 I guess rehydration are orchestrated across. 867 00:39:35,885 --> 00:39:38,325 - I don't see that in the documentation yet on 868 00:39:38,875 --> 00:39:41,525 when you do rehydrate, how long it will take. 869 00:39:41,965 --> 00:39:43,605 I was just looking through it all here. Yep. 870 00:39:43,735 --> 00:39:47,285 Legal hold can be archived, content admin, searchable. 871 00:39:47,755 --> 00:39:50,045 Yeah, there's nothing on how long it'll take to come back, 872 00:39:50,505 --> 00:39:53,445 but I think this is again two different use cases 873 00:39:53,585 --> 00:39:55,885 so you can't really compare and contrast these two. 874 00:39:56,025 --> 00:39:59,405 But I feel like there's a lot of clients that I've worked 875 00:39:59,405 --> 00:40:01,805 with that they actually care more about this. 876 00:40:02,115 --> 00:40:04,965 They have data, it's like a file server, right? 877 00:40:05,145 --> 00:40:07,525 You tend to, as you're using SharePoint more 878 00:40:07,785 --> 00:40:11,285 and as it's been around now for, well SharePoint online 879 00:40:11,545 --> 00:40:15,005 as it's been around now for know 12, 13 years, 880 00:40:15,005 --> 00:40:17,485 maybe even a few more, maybe even 14 or 15. 881 00:40:17,905 --> 00:40:20,085 Uh, clients are starting to get some of that. 882 00:40:20,185 --> 00:40:22,045 Or clients I work with are starting to get some of 883 00:40:22,045 --> 00:40:23,125 that older data out there. 884 00:40:23,155 --> 00:40:27,885 It's 10 years old, it's 12 years old, even five 885 00:40:27,885 --> 00:40:31,085 or six years old that they don't need it anymore. 886 00:40:31,505 --> 00:40:32,965 Uh, but they still wanna keep it 887 00:40:33,105 --> 00:40:36,085 and some of those people have started to pay 888 00:40:36,105 --> 00:40:40,005 for the 20 cents per gigabyte just to have some place 889 00:40:40,145 --> 00:40:41,605 to keep this data long term 890 00:40:41,695 --> 00:40:44,085 where they can still get it if they need it, moving it out 891 00:40:44,085 --> 00:40:45,405 to the 5 cents, having 892 00:40:45,425 --> 00:40:48,245 to pay 60 cents per gigabyte to restore it. 893 00:40:48,675 --> 00:40:50,525 This to me is also a good argument 894 00:40:50,585 --> 00:40:52,885 for making sure you do your taxonomy and SharePoint, right? 895 00:40:53,245 --> 00:40:56,725 , you don't wanna archive a one terabyte 896 00:40:56,725 --> 00:40:59,045 or 250 gigabyte SharePoint site 897 00:40:59,045 --> 00:41:03,365 because you decided to put everything in a single site 898 00:41:03,625 --> 00:41:04,685 or at a single location. 899 00:41:05,025 --> 00:41:09,085 If you bucket out your content properly, hopefully these 900 00:41:09,765 --> 00:41:11,965 restores or not the restores 901 00:41:11,965 --> 00:41:15,965 but the rehydration of data aren't going to cost you as much 902 00:41:15,965 --> 00:41:18,765 because you're able to rehydrate them in smaller batches. 903 00:41:19,085 --> 00:41:22,205 I didn't see, it looks like this is site based. 904 00:41:22,525 --> 00:41:23,965 I was just thinking as I was saying that, 905 00:41:23,965 --> 00:41:26,085 I'm like did we ever look at if this was folder 906 00:41:26,195 --> 00:41:27,285 file based, site based? 907 00:41:27,515 --> 00:41:29,045 - It's site based. - It is site based. 908 00:41:29,305 --> 00:41:31,645 So I have clients, we've talked about this Scott, 909 00:41:31,645 --> 00:41:33,245 we've done some of our storage episodes 910 00:41:33,365 --> 00:41:36,205 where it's like do not migrate a file share 911 00:41:36,425 --> 00:41:38,005 to a single SharePoint site. 912 00:41:38,075 --> 00:41:40,165 There's a multitude of reasons not to do that. 913 00:41:40,225 --> 00:41:42,325 Or don't put all your files in one SharePoint site, 914 00:41:42,325 --> 00:41:43,485 like really think through, 915 00:41:43,815 --> 00:41:46,045 break these out into different SharePoint sites, 916 00:41:46,495 --> 00:41:47,805 think through that taxonomy. 917 00:41:48,195 --> 00:41:51,645 This would be a another reason to really think through that. 918 00:41:51,865 --> 00:41:53,005 So if you do wanna archive 919 00:41:53,005 --> 00:41:55,565 and rehydrate you're rehydrating megabytes 920 00:41:55,585 --> 00:41:59,445 or maybe it's 10 20 gigabytes instead of, 921 00:41:59,995 --> 00:42:04,125 well now I can't archive because everything is in one site 922 00:42:04,425 --> 00:42:07,445 or when I do have to rehydrate, it's just a massive site. 923 00:42:07,445 --> 00:42:08,685 I'm rehydrating in 924 00:42:08,715 --> 00:42:12,165 that 60 cents per gigabyte can add up in a hurry 925 00:42:12,475 --> 00:42:14,645 - More to plan about in the future, right? 926 00:42:14,645 --> 00:42:17,165 Like I think folks are gonna kind of figure out as they go 927 00:42:17,505 --> 00:42:21,205 and over the next six months a year you'll start 928 00:42:21,205 --> 00:42:23,645 to see far more like tactical guidance come out 929 00:42:23,645 --> 00:42:25,885 around these things like hey, here's how to approach it. 930 00:42:25,885 --> 00:42:27,765 Here's how to maybe save money with this. 931 00:42:27,765 --> 00:42:31,005 Here's how to figure out like what is important to backup, 932 00:42:31,315 --> 00:42:34,165 what is important to archive, what's not important 933 00:42:34,185 --> 00:42:36,085 to back up, what's not important to archive? 934 00:42:36,345 --> 00:42:38,165 All those conversations are gonna kind 935 00:42:38,165 --> 00:42:41,565 of keep on coming over the course of the next, you know, 936 00:42:41,565 --> 00:42:42,925 six months to a year as folks 937 00:42:42,925 --> 00:42:44,085 get more and more hands-on with it. 938 00:42:44,305 --> 00:42:47,125 And as we start to see what type 939 00:42:47,205 --> 00:42:50,285 of vendor offerings are built out on top of this, right? 940 00:42:50,295 --> 00:42:51,805 We've still got SharePoint premium 941 00:42:52,065 --> 00:42:53,805 and all the things that come along with that 942 00:42:53,985 --> 00:42:55,885 and kind of the syntax rebrand. 943 00:42:56,235 --> 00:42:57,285 There's backup 944 00:42:57,385 --> 00:42:59,325 and archive kicking around out here right now. 945 00:42:59,325 --> 00:43:01,725 Like there's all these new API surfaces. 946 00:43:02,045 --> 00:43:04,645 I think it's gonna take folks a little bit of time just 947 00:43:04,645 --> 00:43:05,765 to wrap their heads around 948 00:43:06,105 --> 00:43:07,725 and figure out what the next steps are. 949 00:43:07,825 --> 00:43:09,405 - Yep. And if you do wanna track these, 950 00:43:09,495 --> 00:43:11,565 we'll put these links in the show notes as well. 951 00:43:11,615 --> 00:43:12,965 There is a roadmap, 952 00:43:13,525 --> 00:43:16,205 Microsoft 365 roadmap item for each of these. 953 00:43:16,755 --> 00:43:21,205 Archive is feature ID 1 7 1 1 0 0 954 00:43:21,825 --> 00:43:23,165 and again public preview. 955 00:43:23,305 --> 00:43:26,485 Now they do have a rollout date starting 956 00:43:26,545 --> 00:43:29,565 of March, 2024 for archive 957 00:43:29,785 --> 00:43:33,685 and then backup is 1 8, 8 7, 9, 9 public preview now 958 00:43:34,025 --> 00:43:37,045 and they have that rollout date starting in April of 2024. 959 00:43:37,185 --> 00:43:40,285 So archive should hit GA first in March, backup 960 00:43:40,845 --> 00:43:43,885 a month later in April of 2024. 961 00:43:43,955 --> 00:43:45,605 - They'll be here before you know it. 962 00:43:45,985 --> 00:43:47,645 - Yes. And I have not hit my 963 00:43:47,845 --> 00:43:49,045 provided storage yet, so I actually 964 00:43:49,045 --> 00:43:50,165 don't need to worry about archive. 965 00:43:50,665 --> 00:43:53,885 But for any of you that are paying for extra storage, 966 00:43:54,565 --> 00:43:56,445 I would keep an eye on archive especially 967 00:43:56,785 --> 00:43:58,485 and think through that data that you have out there 968 00:43:58,485 --> 00:43:59,485 and how it's architected 969 00:43:59,485 --> 00:44:02,725 because you may be able to stop paying the 20 cents per gig 970 00:44:02,785 --> 00:44:04,405 and start paying 5 cents per gig 971 00:44:04,405 --> 00:44:06,285 and archive off a bunch of that older data. 972 00:44:06,625 --> 00:44:08,725 It would, yeah. There is PowerShell too, 973 00:44:08,725 --> 00:44:10,245 so you can't set the archive status. 974 00:44:10,435 --> 00:44:12,005 There's a lot of things you could start doing 975 00:44:12,005 --> 00:44:14,885 with this Scott, with PowerShell, with Power Automate 976 00:44:15,025 --> 00:44:17,005 to run scripts to archive it. 977 00:44:17,305 --> 00:44:19,525 It would be nice to see some connectors built in. 978 00:44:19,925 --> 00:44:22,165 I am definitely more excited to play with archive than I am 979 00:44:22,165 --> 00:44:24,565 to put backup if I had to pick one of these too. Yeah, 980 00:44:24,565 --> 00:44:25,605 - Backup seems to be one 981 00:44:25,605 --> 00:44:28,125 of those fairly mature places already. 982 00:44:28,195 --> 00:44:31,565 Like you've already had options as a customer, so good, good 983 00:44:31,565 --> 00:44:34,045 that now you have more options, potentially easier 984 00:44:34,105 --> 00:44:37,005 to sit it out and wait and see how it forms out over time. 985 00:44:37,545 --> 00:44:39,605 But the archive thing, like you said, like there, 986 00:44:39,605 --> 00:44:42,525 there's meaningful savings to be had there depending on 987 00:44:42,525 --> 00:44:44,805 how you approach governance of your SharePoint sites today. 988 00:44:44,865 --> 00:44:46,605 - Oh well that Scott, we should probably wrap up. 989 00:44:46,715 --> 00:44:48,725 This one got a little longer with all the, 990 00:44:49,405 --> 00:44:50,445 - Probably it happens. 991 00:44:50,715 --> 00:44:54,285 - Details are on backup in archive. It does, but always fun. 992 00:44:54,285 --> 00:44:56,325 Always fun looking at these new features, trying 993 00:44:56,325 --> 00:44:59,405 to figure 'em out, use cases, all of those. Sounds 994 00:44:59,405 --> 00:44:59,965 - Good. Thanks 995 00:44:59,985 --> 00:45:00,985 - Ben. 996 00:45:00,985 --> 00:45:01,645 Alright, thank you. Enjoy your Monday 997 00:45:01,785 --> 00:45:02,885 and we will talk to you later. 998 00:45:05,225 --> 00:45:06,445 If you enjoyed the podcast, 999 00:45:06,985 --> 00:45:09,125 go leave us a five star rating in iTunes. 1000 00:45:09,345 --> 00:45:10,645 It helps to get the word out 1001 00:45:10,705 --> 00:45:14,205 so more IT pros can learn about Office 365 and Azure. 1002 00:45:14,945 --> 00:45:17,485 If you have any questions you want us to address on the show 1003 00:45:17,625 --> 00:45:20,085 or feedback about the show, feel free 1004 00:45:20,105 --> 00:45:23,045 to reach out via our website, Twitter or Facebook. 1005 00:45:23,265 --> 00:45:25,365 Thanks again for listening and have a great day.

Digital Dispatch Podcast Podcast Artwork Image

Microsoft Cloud IT Pro Podcast

Ben Stegink, Scott Hoag

On the MS Cloud IT Pro Podcast, Scott and Ben discuss the Microsoft Cloud with a focus on IT Pros. They'll discuss the latest in Microsoft 365 and Office 365 News, Azure news and talk about their experiences with managing the Microsoft Cloud as well as interview industry experts on various cloud technology. They'll cover things such as SharePoint, Exchange, Microsoft Teams, PowerShell, Azure, Azure AD, Security, Networking, Storage, and the many other technologies and products that have made their way into the Microsoft 365 suite and Azure. To stay up-to-date on the latest in Microsoft Cloud news and gain some valuable knowledge as you deploy it within your own organization, make sure to tune in every week! Find out more at msclouditpropodcast.com.

Contact Show