Episode 363 – Hibernation is for more than bears

December 07, 2023

Episode Transcript

In Episode 363, Ben and Scott talk through some new hibernation capabilities coming to an Azure VM near you and the announced retirement of SharePoint Add-Ins.

It’s also the season of giving and we’re raising money for Girls Who Code. Donate today at https://give.girlswhocode.com/msclouditpro!

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,415 - Welcome to episode 363 2 00:00:06,435 --> 00:00:08,775 of the Microsoft Cloud IT Pro Podcast 3 00:00:09,375 --> 00:00:12,095 recorded live on November 30th, 2023. 4 00:00:12,525 --> 00:00:14,935 This is a show about Microsoft 365 5 00:00:14,935 --> 00:00:17,015 and Azure from the perspective of it pros 6 00:00:17,015 --> 00:00:20,295 and end users where we discuss a topic or recent news 7 00:00:20,315 --> 00:00:21,575 and how it relates to you. 8 00:00:22,005 --> 00:00:23,335 It's wintertime in the us. 9 00:00:23,475 --> 00:00:26,815 So this week we figured we'd talk about hibernation only 10 00:00:26,815 --> 00:00:27,895 instead of animals. 11 00:00:28,085 --> 00:00:31,095 It's a new feature coming to virtual machines. That's right. 12 00:00:31,195 --> 00:00:34,895 You can now hibernate some VMs to save a few bucks instead 13 00:00:34,895 --> 00:00:35,975 of deprovisioning them. 14 00:00:36,395 --> 00:00:38,655 We also discuss a feature going away 15 00:00:38,835 --> 00:00:41,375 as Microsoft has officially announced the end 16 00:00:41,375 --> 00:00:42,535 of SharePoint atoms. 17 00:00:42,765 --> 00:00:44,935 Finally, as we're in this holiday season, 18 00:00:45,025 --> 00:00:47,495 we're once again raising money for girls who code. 19 00:00:47,625 --> 00:00:49,135 Check out the link in the show notes 20 00:00:49,195 --> 00:00:51,375 to join us in our second annual campaign 21 00:00:51,395 --> 00:00:52,695 to support the organization. 22 00:00:55,095 --> 00:00:56,375 I know you don't watch football, 23 00:00:56,635 --> 00:01:00,535 but I watched Michigan beat Ohio State over the Thanksgiving 24 00:01:00,535 --> 00:01:02,935 weekend here in the US and thoroughly enjoyed it. 25 00:01:02,935 --> 00:01:05,015 So I'm sorry to any Ohio State fans that listen 26 00:01:05,015 --> 00:01:06,535 to the podcast , but 27 00:01:06,995 --> 00:01:07,995 - Should let me know. 28 00:01:07,995 --> 00:01:09,455 I would've worn my sports ball shirt today. 29 00:01:09,595 --> 00:01:11,815 But uh, yeah, no sports ball shirt, 30 00:01:11,955 --> 00:01:12,955 - No sports ball. 31 00:01:12,955 --> 00:01:14,295 Well we don't need to talk about sports ball. 32 00:01:14,555 --> 00:01:17,175 We can talk about other stuff today. 33 00:01:17,595 --> 00:01:18,775 Do you have one you wanna start with? 34 00:01:18,795 --> 00:01:20,815 You highlighted some things. I've got some things. 35 00:01:20,875 --> 00:01:22,855 We have some ignite to e stuff. 36 00:01:23,435 --> 00:01:25,935 We have some AI stuff that 37 00:01:26,495 --> 00:01:27,975 apparently is blown up on LinkedIn 38 00:01:27,975 --> 00:01:29,015 and everybody's been playing with. 39 00:01:29,015 --> 00:01:32,655 Now. Where should we start , Mr. Scott? Yeah, 40 00:01:32,945 --> 00:01:35,295 - Let's do some uh, newsy stuff. 41 00:01:35,535 --> 00:01:36,775 I think. I think I have a couple. Okay. 42 00:01:37,075 --> 00:01:41,415 One of these is a pre-post during Ignite announcement. 43 00:01:41,535 --> 00:01:43,535 I, I don't even know when these things fall 44 00:01:43,555 --> 00:01:44,575 at this point anymore. 45 00:01:44,965 --> 00:01:46,495 It's all over the place for me. 46 00:01:47,005 --> 00:01:51,175 That being said, VM hibernation, did you see this one? I 47 00:01:51,175 --> 00:01:53,135 - Did have seen it in Azure portal. 48 00:01:53,255 --> 00:01:55,015 I haven't used it. I think this was ignite 49 00:01:55,015 --> 00:01:56,775 because I think we like mentioned, 50 00:01:57,195 --> 00:01:59,535 hey this is out there on the Ignite episode. 51 00:01:59,555 --> 00:02:02,415 We just did but we spent no time talking about it 52 00:02:02,575 --> 00:02:04,295 'cause I don't really remember much about it. 53 00:02:04,325 --> 00:02:08,015 Yeah, but hibernating virtual machines, this is not like 54 00:02:08,015 --> 00:02:09,055 before you could shut down 55 00:02:09,075 --> 00:02:10,135 and not deprovisioned, 56 00:02:10,435 --> 00:02:12,455 you could deprovision a virtual machine 57 00:02:12,455 --> 00:02:13,655 whether you got built or not. 58 00:02:13,955 --> 00:02:16,655 Now we have a hibernating, a virtual machine. Yeah, 59 00:02:16,975 --> 00:02:20,415 - I think this is a good capability 60 00:02:20,755 --> 00:02:22,215 to bring forward. 61 00:02:22,485 --> 00:02:23,895 There's a couple dimensions here. 62 00:02:24,595 --> 00:02:28,735 One is you just need to save money on your compute always. 63 00:02:28,855 --> 00:02:30,935 I think all of us are in this mode 64 00:02:31,395 --> 00:02:33,375 and I've certainly got to the model 65 00:02:33,555 --> 00:02:36,495 of more ephemeral compute in everything I do. 66 00:02:36,495 --> 00:02:40,615 Like I find myself constantly these days like spinning up 67 00:02:40,615 --> 00:02:44,215 and deleting Databricks clusters, Kubernetes clusters, like 68 00:02:44,835 --> 00:02:47,455 all the things, it's all become very ephemeral to me. 69 00:02:47,725 --> 00:02:50,495 Even potentially things that should be living 70 00:02:50,995 --> 00:02:52,455 and be online more than they should be. 71 00:02:52,635 --> 00:02:55,655 So I'm fully on board with the servers, this cattle thing 72 00:02:55,955 --> 00:03:00,005 and the ephemeral nature of compute to save money. 73 00:03:00,065 --> 00:03:01,285 And then like you said in the past, 74 00:03:01,475 --> 00:03:04,005 it's been shut down your virtual machines to save money 75 00:03:04,465 --> 00:03:06,325 or delete your virtual machine, 76 00:03:06,585 --> 00:03:09,925 delete your VM profile which effectively shuts it down, 77 00:03:10,185 --> 00:03:13,165 but then maybe do something like retain the disks to keep it 78 00:03:13,165 --> 00:03:14,965 around so you still have the OSS 79 00:03:14,965 --> 00:03:16,365 and data diss and things like that. 80 00:03:16,625 --> 00:03:18,045 So that's all well and good, 81 00:03:18,425 --> 00:03:21,885 but that is not the same as hibernation, which lets you 82 00:03:22,585 --> 00:03:25,125 not only shut the VM down to save money 83 00:03:25,705 --> 00:03:30,045 but also suspend the memory for that virtual machine to disc 84 00:03:30,465 --> 00:03:33,125 so that when you come back from a hibernation event just 85 00:03:33,125 --> 00:03:35,325 like you would in VMware or HyperV 86 00:03:35,345 --> 00:03:37,325 or any other hypervisor that's out there, 87 00:03:38,115 --> 00:03:42,005 effectively your full kit comes back online just as was. 88 00:03:42,425 --> 00:03:44,085 And that's really what this capability is. 89 00:03:44,515 --> 00:03:48,605 This is fully deallocate your compute so 90 00:03:48,605 --> 00:03:51,645 that you're shutting down your VM to save money effectively. 91 00:03:51,645 --> 00:03:52,805 Like it's a location 92 00:03:53,505 --> 00:03:57,325 but it's an extra mode to de location that allows you to 93 00:03:58,075 --> 00:04:00,165 persist that virtual machine's memory 94 00:04:00,465 --> 00:04:02,725 and suspend it fully down to disc 95 00:04:03,185 --> 00:04:06,605 so you retain not only the discs for your virtual machines. 96 00:04:06,605 --> 00:04:09,325 So things like your data discs and your OSS disc, all that. 97 00:04:09,665 --> 00:04:14,485 You also retain the memory for the state that you were in. 98 00:04:14,505 --> 00:04:16,005 But again, this is just like, 99 00:04:16,235 --> 00:04:17,965 it's not some nifty new capability. 100 00:04:17,995 --> 00:04:20,565 This is in, I don't know, every hypervisor 101 00:04:20,945 --> 00:04:22,405 that's out there today. 102 00:04:23,275 --> 00:04:27,685 It's just this is now a native Azure capability. 103 00:04:28,115 --> 00:04:32,645 It's a little wonky I think at least in this first 104 00:04:32,915 --> 00:04:36,405 iteration when it comes to things like support for 105 00:04:36,435 --> 00:04:38,645 what can be hibernated and what can't be hibernated. 106 00:04:38,945 --> 00:04:40,565 So that's in a couple dimensions. 107 00:04:40,905 --> 00:04:43,325 One is things like operating systems. 108 00:04:43,905 --> 00:04:45,285 So if you go and look and, 109 00:04:45,285 --> 00:04:46,685 and this is all in preview is not 110 00:04:46,685 --> 00:04:48,045 production, blah blah blah. 111 00:04:48,355 --> 00:04:50,485 That whole disc that that whole disclaimer. 112 00:04:50,865 --> 00:04:54,405 But if you go and look at the operating systems 113 00:04:54,435 --> 00:04:56,765 that are supported, it's everything on the Windows side, 114 00:04:56,765 --> 00:05:00,525 windows 10, windows 11, server 2019, 115 00:05:00,585 --> 00:05:03,725 server 20, 20 22, all that kind of stuff is there. 116 00:05:03,825 --> 00:05:06,925 That's all good. Linux is a little hairier. 117 00:05:07,045 --> 00:05:10,205 I think it's a little spottier. So there's Ubuntu and Dian. 118 00:05:10,715 --> 00:05:13,445 There's no support for RL today. 119 00:05:13,925 --> 00:05:17,045 I imagine that's gotta be on the roadmap someplace is 120 00:05:17,205 --> 00:05:20,245 bringing things like Red Hat Enterprise Linux over to 121 00:05:20,875 --> 00:05:21,885 that list of things. 122 00:05:22,265 --> 00:05:25,925 And I imagine, hey it's preview that all comes into time 123 00:05:26,105 --> 00:05:27,485 as they iterate on the preview 124 00:05:27,665 --> 00:05:28,965 and uh, get ready 125 00:05:28,965 --> 00:05:31,445 to hit general availability, all that good kind of stuff. 126 00:05:31,705 --> 00:05:35,045 So the first one is hey go to go check the docs 127 00:05:35,105 --> 00:05:36,685 and see what's going on there. 128 00:05:37,075 --> 00:05:38,845 Does this work for what you needed to do 129 00:05:38,845 --> 00:05:40,725 with the operating systems that you have? 130 00:05:41,105 --> 00:05:43,005 And then the other piece of it is 131 00:05:43,555 --> 00:05:45,245 it's only supported on a couple 132 00:05:45,265 --> 00:05:48,005 of different virtual machine sizes 133 00:05:48,705 --> 00:05:53,565 and only up to it has a a ceiling for the amount of RAM 134 00:05:53,565 --> 00:05:55,725 that's allocated to that VM size 135 00:05:56,275 --> 00:05:57,965 that it's gonna let you actually go 136 00:05:57,965 --> 00:05:59,005 ahead and hibernate through. 137 00:05:59,145 --> 00:06:03,565 So it's DASV fives, D-A-D-V-S, 138 00:06:03,725 --> 00:06:07,565 V fives, DS V fives and DDSV fives. 139 00:06:08,085 --> 00:06:11,485 Anything up to 32 gigs of RAM can be hibernated today. 140 00:06:11,705 --> 00:06:13,485 So if you happen to be running on something that says, 141 00:06:14,025 --> 00:06:17,565 say goes to 64 gigs of ram, well sorry 142 00:06:17,995 --> 00:06:20,165 that one can't be hibernated today. 143 00:06:20,165 --> 00:06:23,365 Again, I imagine that gets fixed over time 144 00:06:24,265 --> 00:06:27,445 as they get closer to ga. 145 00:06:27,835 --> 00:06:29,885 Okay, that's all all ready to go there. 146 00:06:29,955 --> 00:06:31,045 - Well and I imagine 147 00:06:31,075 --> 00:06:33,565 that there's maybe some technical limitations there 148 00:06:33,845 --> 00:06:37,245 because it does say when you're looking through this too, 149 00:06:37,315 --> 00:06:39,725 that when you hibernate a vm 150 00:06:40,305 --> 00:06:44,045 it signals the VMs operating system to perform a suspend 151 00:06:44,045 --> 00:06:47,085 to disc action in the memory contents 152 00:06:47,085 --> 00:06:49,885 of the VM are stored in the OSS disc 153 00:06:50,265 --> 00:06:53,445 and what these OSS disks are only 128 gigs. 154 00:06:53,925 --> 00:06:57,365 I imagine once you start getting up into 64 gigs of RAM 155 00:06:57,665 --> 00:06:59,805 and 128 gigs of ram, some of those, 156 00:07:00,395 --> 00:07:04,805 what if there's not enough room on the OSS disc for your 157 00:07:05,385 --> 00:07:08,685 amount of memory or even I'm curiously it 158 00:07:08,685 --> 00:07:10,845 - Is a consideration if 159 00:07:10,845 --> 00:07:14,045 - You install apps like some people, let's face it, 160 00:07:14,065 --> 00:07:15,245 you should add data disks 161 00:07:15,245 --> 00:07:16,645 and install your apps on the data dis. 162 00:07:16,745 --> 00:07:18,445 But if you're doing things like IIS 163 00:07:18,545 --> 00:07:21,125 and you have it sitting on the OSS disk 164 00:07:21,265 --> 00:07:25,045 and your IS logs start ramping up, like I would be curious 165 00:07:25,145 --> 00:07:26,685 to try to fill up an OSS disk 166 00:07:26,785 --> 00:07:29,605 and then try to hibernate one with 32 gigs of RAM 167 00:07:29,755 --> 00:07:32,725 with 10 gigs free on the OSS DIS and see what happens. 168 00:07:32,725 --> 00:07:34,805 Because I like to try to break stuff. 169 00:07:35,325 --> 00:07:37,805 - the other fun thing that happens here, 170 00:07:38,105 --> 00:07:40,445 and this is always, it's always fun to read 171 00:07:40,445 --> 00:07:42,045 between the lines to see like why 172 00:07:42,045 --> 00:07:43,085 they do these kinds of things. 173 00:07:43,505 --> 00:07:47,885 So why bring VM hibernation this late in the game? 174 00:07:47,945 --> 00:07:50,525 You would think hey it's been hyper V under the hood 175 00:07:50,635 --> 00:07:52,365 effectively for a long time. 176 00:07:52,385 --> 00:07:54,085 Now that's a native capability. 177 00:07:54,115 --> 00:07:57,165 Like why hold it back , you 178 00:07:57,165 --> 00:07:59,885 and I with our little virtual machines, like just going 179 00:07:59,885 --> 00:08:01,565 around one Z, two Z um, 180 00:08:01,745 --> 00:08:05,165 or even a customer that has a fleet of 10,000 VMs 181 00:08:05,975 --> 00:08:08,765 might not be the largest of the large 182 00:08:08,795 --> 00:08:12,485 that move the needle when it comes to how much it costs to 183 00:08:13,045 --> 00:08:14,725 actually run your service and put things forward. 184 00:08:15,425 --> 00:08:16,925 So if you look at this announcement 185 00:08:16,945 --> 00:08:18,645 and when it came out, you go 186 00:08:18,705 --> 00:08:20,445 and Google binging DuckDuckGo 187 00:08:20,905 --> 00:08:24,365 for all the other compute services that rely 188 00:08:24,985 --> 00:08:28,765 on Azure compute and deliver compute as a service to you. 189 00:08:29,225 --> 00:08:30,685 For example, dev box, 190 00:08:31,055 --> 00:08:32,685 we've talked about dev box in the past, 191 00:08:33,255 --> 00:08:34,565 Azure Virtual Desktop. 192 00:08:34,695 --> 00:08:36,565 We've talked about A VD in the past. 193 00:08:37,265 --> 00:08:39,125 At the same time that this announcement came out, 194 00:08:39,525 --> 00:08:41,205 a VD dev box 195 00:08:41,305 --> 00:08:42,525 and a bunch of these other ones, 196 00:08:42,825 --> 00:08:46,045 Citrix has a big deployment on top of Azure VMs. 197 00:08:46,475 --> 00:08:48,845 They all came out and said, Hey guess what? 198 00:08:49,065 --> 00:08:52,045 Our virtual desktop services all now support hibernation 199 00:08:52,645 --> 00:08:53,645 - . 200 00:08:53,665 --> 00:08:56,125 - Oh, oh, okay. I see why that's really there. 201 00:08:56,125 --> 00:08:58,005 It's maybe not there for us as mere mortals. 202 00:08:58,145 --> 00:08:59,445 Hey it's a nice to have 203 00:08:59,465 --> 00:09:01,925 and it's a good consideration for us now that it is there. 204 00:09:02,465 --> 00:09:04,365 But I think for the most part it's really there 205 00:09:04,545 --> 00:09:08,245 to support the desktop as a service provider kind 206 00:09:08,245 --> 00:09:09,565 of stuff that's out there. 207 00:09:09,625 --> 00:09:11,805 And that could certainly help you in your environments. 208 00:09:11,835 --> 00:09:14,925 Like I know you do a VD deployments with your customers. 209 00:09:14,985 --> 00:09:16,805 Yep. And potentially that's something 210 00:09:16,805 --> 00:09:19,005 that they're interested in along the way. Yeah, 211 00:09:19,185 --> 00:09:20,565 - I'm absolutely gonna look at this. 212 00:09:20,975 --> 00:09:24,245 Again, one of our deployments, we would run into one 213 00:09:24,245 --> 00:09:25,245 of those VM sizes 214 00:09:25,445 --> 00:09:28,325 'cause we're doing a VM with 128 gigs of ram. 215 00:09:28,335 --> 00:09:29,845 We're trying to cram a bunch 216 00:09:29,845 --> 00:09:32,285 of people on one rather than a bunch of small ones 217 00:09:32,355 --> 00:09:33,805 with a few people on it. 218 00:09:33,985 --> 00:09:36,285 But some of those smaller deployments, 219 00:09:36,285 --> 00:09:38,045 this is absolutely interesting. 220 00:09:38,045 --> 00:09:40,685 There's some times too, I even use VMs 221 00:09:40,685 --> 00:09:43,845 for different client stuff where it would be nice to deposit 222 00:09:44,145 --> 00:09:47,365 and be able to come back with that memory state versus 223 00:09:48,035 --> 00:09:50,165 shut it down, lose everything 224 00:09:51,065 --> 00:09:53,045 and like stuff I'm working on, 225 00:09:53,125 --> 00:09:54,965 I have just stuff up in visual studio code. 226 00:09:55,035 --> 00:09:58,565 Yeah I save it, I can close it all down, reopen it all. 227 00:09:58,665 --> 00:10:00,645 But sometimes it's like just suspend it. 228 00:10:00,885 --> 00:10:05,405 - I very much want this for the EVD instances 229 00:10:05,635 --> 00:10:07,725 that I get access to through my employer. 230 00:10:08,285 --> 00:10:09,925 'cause I, so one of the things 231 00:10:09,925 --> 00:10:13,605 that happens in the environment I work in is I can either do 232 00:10:13,605 --> 00:10:15,085 my work from employer 233 00:10:15,485 --> 00:10:17,845 provided device where it's all MD MD and ready to go. 234 00:10:18,265 --> 00:10:21,245 Or in the cases where I'm not, I, 235 00:10:21,325 --> 00:10:22,965 I don't have access to an MDM device. 236 00:10:23,235 --> 00:10:24,965 Last week here in the US was Thanksgiving, 237 00:10:25,675 --> 00:10:26,885 most of us were on vacation. 238 00:10:27,075 --> 00:10:29,925 Like I was up in the mountains completely disconnected. 239 00:10:29,995 --> 00:10:32,805 Like I didn't take anything other than my personal laptop 240 00:10:32,805 --> 00:10:35,845 and an iPad with me, neither of which are md md. 241 00:10:35,985 --> 00:10:38,805 So if I had wanted or had a need to do anything at work 242 00:10:38,805 --> 00:10:40,205 that way I claimed there was an escalation 243 00:10:40,205 --> 00:10:41,965 and I got called in, I wouldn't have been able 244 00:10:42,025 --> 00:10:45,565 to do anything unless I could do it through a VD. 245 00:10:45,865 --> 00:10:48,805 And in those instances I would very much want like my A VD 246 00:10:48,805 --> 00:10:50,485 instances to be suspendable as well. 247 00:10:50,765 --> 00:10:52,085 'cause once I'm in one of those sessions 248 00:10:52,185 --> 00:10:53,325 and I think it's one 249 00:10:53,325 --> 00:10:55,165 of the things like once I've started debugging a thing, 250 00:10:55,165 --> 00:10:57,725 like I've got Outlook open, I've got VS code open, 251 00:10:58,475 --> 00:10:59,685 I've got Edge open 252 00:11:00,185 --> 00:11:03,205 and I've got a bunch of very specifically CUSTO queries 253 00:11:03,205 --> 00:11:05,045 or something like that up and running 254 00:11:05,705 --> 00:11:07,085 or I'm in like one of the internal 255 00:11:07,085 --> 00:11:08,325 telemetry portals or something. 256 00:11:08,405 --> 00:11:09,565 I just want all that stuff back. 257 00:11:09,975 --> 00:11:12,565 Especially when I get back to work mode and 258 00:11:12,565 --> 00:11:13,645 and can log in again. 259 00:11:14,025 --> 00:11:15,365 I'm hoping they light it up for us. 260 00:11:15,475 --> 00:11:16,685 - Yeah. I'm curious too, 261 00:11:16,685 --> 00:11:18,765 you mentioned why not have it right away since it's all on 262 00:11:18,765 --> 00:11:21,605 Hyper V but another aspect of this too 263 00:11:21,995 --> 00:11:26,405 that I'm curious about is I don't believe, 264 00:11:26,875 --> 00:11:29,125 does HyperV suspend to the OSS disc 265 00:11:29,185 --> 00:11:31,525 or does it still keep stuff in memory? 266 00:11:32,005 --> 00:11:34,525 I feel like when I've used it before 267 00:11:34,745 --> 00:11:35,805 and it's been a long time 268 00:11:36,145 --> 00:11:38,885 to be fair since I've done HyperV on a physical VM 269 00:11:38,905 --> 00:11:39,965 or a physical machine, 270 00:11:40,405 --> 00:11:42,605 I feel like even though when I suspend it 271 00:11:42,755 --> 00:11:45,125 that machine is still taking up the same amount of memory 272 00:11:45,185 --> 00:11:47,485 and it's actually storing the suspended memory 273 00:11:47,505 --> 00:11:50,765 and memory versus suspended memory copied 274 00:11:50,905 --> 00:11:52,485 and retrieved from the OS disc. 275 00:11:52,845 --> 00:11:56,165 I wonder if there's some additional technology updates 276 00:11:56,165 --> 00:11:58,245 that kind of went out on the backend to support that. 277 00:11:58,375 --> 00:12:00,085 - There might be. I think it's an interesting 278 00:12:00,625 --> 00:12:03,925 choice design choice to go with hibernating the 279 00:12:04,185 --> 00:12:05,205 by compressing that memory 280 00:12:05,225 --> 00:12:08,645 and putting it into the OSS disc versus just side curing it 281 00:12:08,865 --> 00:12:10,445 and having it off to the side. 282 00:12:10,905 --> 00:12:13,565 And I don't know why that choice was made. 283 00:12:13,795 --> 00:12:17,685 Like maybe there's some underlying limitation in, it'd have 284 00:12:17,685 --> 00:12:19,245 to be both Windows and Linux, right? 285 00:12:19,405 --> 00:12:20,805 'cause it's supported across the board. 286 00:12:21,125 --> 00:12:23,685 I don't know what drives those. Like who knows? 287 00:12:23,685 --> 00:12:25,645 There's maybe some weird technical limitation. 288 00:12:25,815 --> 00:12:29,805 Maybe it's an a cost saving measure for customers like it, 289 00:12:29,825 --> 00:12:31,925 it certainly takes away the variability and cost. 290 00:12:32,485 --> 00:12:34,445 'cause in many cases you're already paying a fixed 291 00:12:34,475 --> 00:12:35,525 size for your discs. 292 00:12:35,525 --> 00:12:37,805 Like you're paying for what your provision not what you use. 293 00:12:38,185 --> 00:12:41,325 So if you're already paying for 128 gigs then it's a 294 00:12:41,495 --> 00:12:43,045 solid cost for you. 295 00:12:43,275 --> 00:12:44,925 It's easier for you to project and manage 296 00:12:45,465 --> 00:12:46,885 and for you as a customer 297 00:12:46,905 --> 00:12:49,045 to control your kind of cogs, right? 298 00:12:49,315 --> 00:12:51,285 Your costs of services and what that looks like. 299 00:12:51,885 --> 00:12:55,365 I think that all potentially makes sense there and it 300 00:12:55,365 --> 00:12:58,045 and is a good like forcing function 301 00:12:58,265 --> 00:12:59,525 to, to get it over that way. 302 00:12:59,585 --> 00:13:01,565 But yeah, interesting design choice. I 303 00:13:01,565 --> 00:13:03,325 - Wonder if it has to do too with, you don't know where 304 00:13:03,325 --> 00:13:04,885 that's gonna spin back up, right? 305 00:13:04,885 --> 00:13:06,605 Because if you hibernate it 306 00:13:06,665 --> 00:13:08,445 and you're deprovisioning it from 307 00:13:08,665 --> 00:13:12,085 or locating resources, when you go to un hibernate it, 308 00:13:12,155 --> 00:13:15,005 wake it back up, it could spin up in an entirely different 309 00:13:15,405 --> 00:13:18,525 rack, an entirely different data center within the region. 310 00:13:18,945 --> 00:13:21,525 And if it's in a separate sidecar storage, you'd have 311 00:13:21,525 --> 00:13:23,605 to keep track of all that together. You would, 312 00:13:23,605 --> 00:13:24,965 - There could be latency there. 313 00:13:25,205 --> 00:13:26,845 I imagine there's a way to pull it off, right? 314 00:13:26,845 --> 00:13:30,565 Especially in the world of managed disks where Microsoft 315 00:13:31,225 --> 00:13:34,325 is hosting the storage account and the VHD for you. 316 00:13:34,915 --> 00:13:36,685 They know where all that stuff lives and 317 00:13:36,705 --> 00:13:38,405 and they've already got that mapping in place. 318 00:13:38,835 --> 00:13:42,925 There's probably some weird trade off in there between cost 319 00:13:43,695 --> 00:13:46,085 complexity, friction for customers, friction 320 00:13:46,145 --> 00:13:50,125 as a service provider on the Azure side just to light up 321 00:13:50,125 --> 00:13:51,685 that capability and keep it going 322 00:13:52,345 --> 00:13:53,525 and make sure that it's robust 323 00:13:53,545 --> 00:13:55,005 and it works the way you want it to. 324 00:13:55,305 --> 00:13:56,645 All that kind of stuff. 325 00:13:56,745 --> 00:13:59,165 - So it's not taking a bunch of, I can see cost too. 326 00:13:59,565 --> 00:14:01,445 'cause you talk about like 32 gigs of ram. 327 00:14:01,455 --> 00:14:04,445 Let's say you suspend a hundred thousand virtual machines. 328 00:14:05,025 --> 00:14:07,605 If you're spinning that up in some sidecar blob storage 329 00:14:07,665 --> 00:14:09,525 that's going into your storage Scott. 330 00:14:09,705 --> 00:14:13,845 And yes I imagine it, I, we don't think of it as much 331 00:14:14,065 --> 00:14:16,685 but at that type of scale that could be a lot 332 00:14:16,685 --> 00:14:19,245 of extra storage versus to your point, 333 00:14:19,315 --> 00:14:21,805 just putting it in OSS disk that's already been 334 00:14:22,435 --> 00:14:23,845 planned on provisioned. 335 00:14:23,845 --> 00:14:24,885 You're paying for it. 336 00:14:25,155 --> 00:14:27,285 There's not extra storage 337 00:14:27,385 --> 00:14:30,125 that's being consumed on the side because of it. 338 00:14:30,155 --> 00:14:31,765 Yeah it is. It's interesting. And 339 00:14:31,765 --> 00:14:33,405 - That's a consideration for you as a customer 340 00:14:33,465 --> 00:14:35,565 and I think Microsoft as a service provider, right? 341 00:14:35,565 --> 00:14:38,925 Like how do you plan for capacity in that world and 342 00:14:38,925 --> 00:14:40,205 and that level of variability. 343 00:14:40,445 --> 00:14:42,325 I don't know that you can in the current 344 00:14:42,325 --> 00:14:43,565 landscape and how things go. 345 00:14:44,105 --> 00:14:46,605 So yeah it makes sense if you peel back the curtain 346 00:14:46,825 --> 00:14:48,765 but I don't know, it's like you're a customer. 347 00:14:48,925 --> 00:14:50,325 I think you just need to know the way it works 348 00:14:51,105 --> 00:14:52,525 and understand that behavior 349 00:14:53,065 --> 00:14:56,285 versus understanding like hey here's like the underlying 350 00:14:56,285 --> 00:14:57,445 design decision behind it. 351 00:14:57,465 --> 00:14:59,685 - Design decisions are just fascinating to me. 352 00:15:00,005 --> 00:15:02,005 , that's stuff that interests me. 353 00:15:02,185 --> 00:15:03,725 You should, I need to go get a job at 354 00:15:04,005 --> 00:15:05,165 Microsoft just so I can. 355 00:15:05,395 --> 00:15:07,165 Yeah. See some design decisions 356 00:15:07,505 --> 00:15:11,165 - We make them every day trade offs abound. 357 00:15:11,915 --> 00:15:13,565 Yeah, I wish everybody could go 358 00:15:13,565 --> 00:15:15,645 and uh, I imagine especially like the folks 359 00:15:15,645 --> 00:15:17,845 who listen to this podcast like going 360 00:15:17,905 --> 00:15:20,605 and working for a hyperscaler in one 361 00:15:20,605 --> 00:15:22,285 of the hyperscale services. 362 00:15:22,885 --> 00:15:24,645 'cause not every service is a hyperscale 363 00:15:24,645 --> 00:15:25,685 service either, right? 364 00:15:25,685 --> 00:15:27,645 Like there, there's some that are small, there's some 365 00:15:27,645 --> 00:15:29,045 that are medium and there's some 366 00:15:29,045 --> 00:15:30,765 that are just like absolutely massive. 367 00:15:31,555 --> 00:15:33,685 Like I work in storage in Azure 368 00:15:33,705 --> 00:15:35,885 and that's a massive part of it. 369 00:15:36,035 --> 00:15:38,365 Compute ISS a big part. Networking's a big part. 370 00:15:38,755 --> 00:15:40,645 There's other smaller stuff out there. 371 00:15:40,665 --> 00:15:42,765 But like if you can go and work for a big one, whew. 372 00:15:43,325 --> 00:15:46,165 I lemme tell you, I've seen some stuff. I 373 00:15:46,625 --> 00:15:47,765 - Am sure I would. 374 00:15:47,765 --> 00:15:48,965 Again, I would love stories. 375 00:15:49,205 --> 00:15:51,365 I don't know that I want stories bad enough to come work 376 00:15:51,385 --> 00:15:52,525 for Microsoft yet . 377 00:15:52,625 --> 00:15:57,605 But we'll see. Do you feel 378 00:15:57,605 --> 00:16:00,805 overwhelmed by trying to manage your Office 365 environment? 379 00:16:00,905 --> 00:16:02,605 Are you facing unexpected issues 380 00:16:02,605 --> 00:16:04,645 that disrupt your company's productivity? 381 00:16:04,715 --> 00:16:07,565 Intelligent is here to help much like you take your car 382 00:16:07,565 --> 00:16:10,245 to the mechanic that has specialized knowledge on how 383 00:16:10,245 --> 00:16:13,005 to best keep your car running Intelligent helps you 384 00:16:13,005 --> 00:16:14,725 with your Microsoft Cloud environment 385 00:16:14,725 --> 00:16:16,325 because that's their expertise. 386 00:16:16,475 --> 00:16:17,765 Intelligent keeps up 387 00:16:17,765 --> 00:16:19,645 with the latest updates in the Microsoft cloud 388 00:16:19,665 --> 00:16:21,205 to help keep your business running 389 00:16:21,525 --> 00:16:22,605 smoothly and ahead of the curve. 390 00:16:22,715 --> 00:16:24,765 Whether you are a small organization 391 00:16:24,765 --> 00:16:27,245 with just a few users up to an organization 392 00:16:27,245 --> 00:16:30,525 of several thousand employees they want to partner with you 393 00:16:30,545 --> 00:16:33,965 to implement and administer your Microsoft Cloud technology, 394 00:16:34,535 --> 00:16:37,845 visit them at intelligent.com/podcast. 395 00:16:38,185 --> 00:16:42,845 That's I-N-T-E-L-L-I-G-I-N 396 00:16:42,965 --> 00:16:46,525 k.com/podcast For more information 397 00:16:46,585 --> 00:16:48,205 or to schedule a 30 minute call 398 00:16:48,205 --> 00:16:49,525 to get started with them today. 399 00:16:50,365 --> 00:16:53,005 Remember intelligent focuses on the Microsoft cloud 400 00:16:53,105 --> 00:16:54,965 so you can focus on your business. 401 00:16:57,345 --> 00:16:59,685 - So VM hibernation was mine. What do you got? What 402 00:16:59,685 --> 00:17:00,685 - Do I got man? 403 00:17:00,685 --> 00:17:01,685 I dunno which one to talk about. 404 00:17:01,695 --> 00:17:03,525 Let's talk about a small one first just 405 00:17:03,645 --> 00:17:05,565 'cause this one's kind of interesting. 406 00:17:05,755 --> 00:17:09,205 It's not the new tab. Remember when we talked a while back 407 00:17:09,205 --> 00:17:11,765 about Microsoft is gonna start transitioning everything 408 00:17:11,825 --> 00:17:15,245 to their own TD under cloud Microsoft? 409 00:17:15,245 --> 00:17:17,165 MM-Hmm the first one that I'm aware 410 00:17:17,165 --> 00:17:21,605 of is now out there your email if you want to go look for 411 00:17:22,385 --> 00:17:25,765 organizational email, this is not personal accounts yet. 412 00:17:26,165 --> 00:17:29,725 Personal accounts are still gonna be outlook.live.com But if 413 00:17:29,725 --> 00:17:32,845 you're using Microsoft 365, you wanna go check your email, 414 00:17:33,145 --> 00:17:37,845 you can now go to outlook.cloud.microsoft and it does work. 415 00:17:38,045 --> 00:17:41,605 I did try it. I don't think mail.office.com redirects 416 00:17:41,745 --> 00:17:43,285 to the cloud version yet. 417 00:17:43,505 --> 00:17:46,045 But if you were looking forward to using that cloud, 418 00:17:46,065 --> 00:17:48,285 do Microsoft go check out your outlook. 419 00:17:49,205 --> 00:17:53,285 - Interesting. I've been waiting to see when these are going 420 00:17:53,545 --> 00:17:56,245 to hit and this one's kind of funny 421 00:17:56,565 --> 00:17:58,805 'cause it's Outlook, all the things 422 00:17:59,025 --> 00:18:01,125 but the, IT does have a redirect in there 423 00:18:01,305 --> 00:18:03,245 for outlook.live.com 424 00:18:04,385 --> 00:18:08,805 and getting you over to your MSA kind of stuff. 425 00:18:09,315 --> 00:18:11,085 Yeah, I don't know, I don't have a ton 426 00:18:11,085 --> 00:18:16,005 of insight into the.microsoft TLD like I would 427 00:18:16,005 --> 00:18:20,125 expect you see that used in more places over time. 428 00:18:20,515 --> 00:18:23,485 Even outside like the M 365 stack. I 429 00:18:23,485 --> 00:18:25,445 - Would think so I think that's the plan. And 430 00:18:25,495 --> 00:18:29,485 - Azure land you see a lot of azure.net kinds of things 431 00:18:29,745 --> 00:18:31,885 or some variation of azure.net 432 00:18:32,265 --> 00:18:34,765 and I'll give you like azure star.net. 433 00:18:34,765 --> 00:18:38,525 So you've got like azure websites.net storage.azure.net, 434 00:18:39,025 --> 00:18:40,805 all those kinds of things exist out there 435 00:18:40,965 --> 00:18:42,245 'cause they have the Azure branding in there. 436 00:18:42,865 --> 00:18:45,765 So I don't know if someday you see a similar effort 437 00:18:45,765 --> 00:18:48,125 to come over to like do Microsoft for that stuff. 438 00:18:48,195 --> 00:18:49,965 It'd be interesting if that ever happened. 439 00:18:50,145 --> 00:18:52,325 - It would like if you'd have it Azure, 440 00:18:52,605 --> 00:18:53,685 I mean the root portal. 441 00:18:53,865 --> 00:18:56,085 If you had azure.cloud do Microsoft 442 00:18:56,345 --> 00:18:59,725 or I'm thinking it's gonna start the Microsoft 365 world. 443 00:18:59,725 --> 00:19:03,405 Like it wouldn't surprise me to start seeing onedrive.cloud, 444 00:19:03,425 --> 00:19:07,165 do Microsoft or onenote.cloud, do Microsoft. 445 00:19:07,435 --> 00:19:10,245 Some of those are probably also a little bit easier 446 00:19:11,015 --> 00:19:13,965 transition than maybe some of the other services. 447 00:19:14,325 --> 00:19:16,645 - I think M 360 five's a good place to start with it. 448 00:19:16,965 --> 00:19:20,645 'cause that's where I think people really need the, 449 00:19:21,435 --> 00:19:22,925 they don't need the cognitive load 450 00:19:22,945 --> 00:19:25,525 of remembering all the variations in URLs 451 00:19:25,525 --> 00:19:27,085 that maybe like we put up 452 00:19:27,085 --> 00:19:29,525 with on the admin side or the tooling side. Exactly. 453 00:19:29,525 --> 00:19:31,445 - And if you know the product, if they can keep doing it 454 00:19:31,445 --> 00:19:35,365 with Outlook, word, Excel, OneDrive, SharePoint, 455 00:19:35,835 --> 00:19:36,965 well not SharePoint 456 00:19:37,125 --> 00:19:38,485 'cause that gets into the tenant level stuff. 457 00:19:38,585 --> 00:19:40,925 But yeah, just have all the products.cloud 458 00:19:41,325 --> 00:19:42,605 Microsoft could be nice. 459 00:19:42,795 --> 00:19:44,805 - That was the plan. I'm, I'm trying to remember, 460 00:19:44,805 --> 00:19:46,725 they didn't link in the article that you had, 461 00:19:46,725 --> 00:19:48,605 they didn't link back to the original announcement 462 00:19:48,865 --> 00:19:50,965 but I believe the original announcement was like a bunch 463 00:19:50,965 --> 00:19:53,205 of those properties were come under the fold 464 00:19:53,265 --> 00:19:54,965 of the Microsoft T ld. 465 00:19:55,585 --> 00:19:57,085 The other interesting thing about that 466 00:19:57,705 --> 00:20:01,245 and I I think it's another good call out 467 00:20:01,245 --> 00:20:03,405 and driver for customers as they get ready for this 468 00:20:04,105 --> 00:20:07,245 is there's lots of customers that are looking to 469 00:20:07,765 --> 00:20:10,245 disambiguate between their resources 470 00:20:10,305 --> 00:20:11,725 and Microsoft's resources. 471 00:20:12,065 --> 00:20:14,525 Say you go to download an asset from someplace, a lot 472 00:20:14,525 --> 00:20:16,845 of it today like might exist in a storage account. 473 00:20:17,225 --> 00:20:19,045 How do you know a storage account is a 474 00:20:19,805 --> 00:20:21,365 Microsoft storage account like a Microsoft 475 00:20:21,365 --> 00:20:22,405 managed storage account? 476 00:20:22,595 --> 00:20:25,325 Like you bootstrap office office does a bunch of stuff 477 00:20:25,325 --> 00:20:27,165 where it downloads assets from blob storage 478 00:20:27,705 --> 00:20:29,405 and how do you disambiguate 479 00:20:29,405 --> 00:20:31,485 and know that the blob storage account for 480 00:20:31,485 --> 00:20:33,765 that office thing is different than the one 481 00:20:33,765 --> 00:20:35,605 that's maybe in your tenant and your environment. 482 00:20:36,195 --> 00:20:39,365 Very hard to do like when every storage account is blob dot 483 00:20:39,365 --> 00:20:40,805 core windows.net today. 484 00:20:41,105 --> 00:20:43,605 But potentially easier in the future if that's all massed 485 00:20:43,605 --> 00:20:45,365 between oh Microsoft assets are 486 00:20:45,365 --> 00:20:47,005 behind the dot, Microsoft T ld. 487 00:20:47,345 --> 00:20:48,805 Go ahead and allow list those 488 00:20:49,145 --> 00:20:50,325 and then maybe you do something 489 00:20:50,355 --> 00:20:52,165 with your own stuff on the side. Yeah, 490 00:20:52,345 --> 00:20:53,845 - So - For those customers who are looking 491 00:20:53,905 --> 00:20:58,285 for either data exfiltration controls, they're just looking 492 00:20:58,305 --> 00:20:59,845 for that additional click stop 493 00:20:59,845 --> 00:21:03,165 of control in their environment, having a lockdown TLD 494 00:21:03,165 --> 00:21:06,485 that's unique to the service provider opens up a world 495 00:21:06,505 --> 00:21:08,565 of possibilities for you there as well. 496 00:21:08,655 --> 00:21:11,005 Makes the network admins happy and the security folks. 497 00:21:11,075 --> 00:21:13,085 - Yeah, so we like keeping network admins 498 00:21:13,085 --> 00:21:14,085 and security folks happy. 499 00:21:14,235 --> 00:21:15,885 Some of us do. Some of us. Yeah. 500 00:21:15,995 --> 00:21:18,445 Another news one, we should talk about this one 501 00:21:18,445 --> 00:21:21,965 because SharePoint is near and dear to both of our hearts. 502 00:21:22,375 --> 00:21:25,565 Scott and I had another one along the lines of this too. 503 00:21:25,615 --> 00:21:27,405 There were two things that got retired. 504 00:21:27,625 --> 00:21:31,365 One of them being the SharePoint ADD-in retirement in 505 00:21:31,645 --> 00:21:32,885 Microsoft 365. 506 00:21:33,145 --> 00:21:36,805 To be clear, this is not anything with 507 00:21:37,535 --> 00:21:39,605 SharePoint on-prem, 508 00:21:39,655 --> 00:21:42,005 SharePoint server on-premises can still 509 00:21:42,105 --> 00:21:43,405 do SharePoint, add-ins. 510 00:21:43,405 --> 00:21:44,525 We'll still have all of that. 511 00:21:45,215 --> 00:21:48,245 There are gonna be some things that impact it in terms 512 00:21:48,245 --> 00:21:51,405 of SharePoint add-ins from the Mark public marketplace. 513 00:21:52,065 --> 00:21:56,045 But SharePoint online SharePoint admins are going away. 514 00:21:56,045 --> 00:21:57,805 SharePoint framework is the way forward 515 00:21:58,305 --> 00:22:01,325 as I'm sure AC would've told you long ago, 516 00:22:01,735 --> 00:22:03,805 - Years and years ago. 517 00:22:04,425 --> 00:22:07,445 But now you're gonna be potentially, depending on 518 00:22:07,445 --> 00:22:08,765 how your deployments look like and 519 00:22:08,785 --> 00:22:10,645 and what things look like in your environment, 520 00:22:11,105 --> 00:22:13,365 you are gonna be forced into the framework path. 521 00:22:13,665 --> 00:22:15,925 And I think that's fine for some folks. 522 00:22:16,475 --> 00:22:18,725 Like when I see announcements like this, like one 523 00:22:18,725 --> 00:22:21,925 of the fun things to do is go out on like public forums like 524 00:22:21,935 --> 00:22:24,285 Stack Overflow, Reddit, all that kind of stuff 525 00:22:24,705 --> 00:22:27,725 and just see what people are latching 526 00:22:27,725 --> 00:22:28,965 onto and complaining about. 527 00:22:29,625 --> 00:22:32,405 And I saw a couple interesting ones on Redmond, 528 00:22:32,745 --> 00:22:36,845 on Redmond on Reddit rather where folks we're, oh 529 00:22:37,515 --> 00:22:40,885 crap, we've developed solutions in-house years ago 530 00:22:41,225 --> 00:22:43,365 and they've just been running and we 531 00:22:43,365 --> 00:22:44,525 don't have access to the code. 532 00:22:44,665 --> 00:22:45,765 We don't know what's going on 533 00:22:45,865 --> 00:22:48,805 and now that's all potentially going to break 534 00:22:48,865 --> 00:22:49,885 and have to go away from them. 535 00:22:50,265 --> 00:22:51,885 Or another one that I saw, it was somebody 536 00:22:51,885 --> 00:22:56,005 who like whatever add-in they had built was it was helping 537 00:22:56,345 --> 00:22:59,405 admins function in the environment like administrators 538 00:22:59,585 --> 00:23:01,765 of their SharePoint tenancy 539 00:23:02,265 --> 00:23:04,205 and whatever they were doing in that thing, 540 00:23:04,205 --> 00:23:05,685 they were all freaked out 'cause they're like, 541 00:23:05,685 --> 00:23:07,085 well we're all admins, we don't know. 542 00:23:07,085 --> 00:23:09,325 We don't even remember who built this thing years 543 00:23:09,345 --> 00:23:10,445 and years ago 544 00:23:10,465 --> 00:23:12,285 but like we depend on it every single day 545 00:23:12,825 --> 00:23:15,045 for our jobs and now what do we do? 546 00:23:15,385 --> 00:23:16,485 - It was, this is one of those 547 00:23:16,595 --> 00:23:19,645 that the writing has been on the wall of this for a while 548 00:23:19,665 --> 00:23:21,245 and they haven't been investing in the 549 00:23:21,245 --> 00:23:22,525 add-in framework for a while. 550 00:23:22,665 --> 00:23:24,285 But to your point, I'm in the same boat. 551 00:23:24,365 --> 00:23:27,205 I still go into clients and they're using old add-ins 552 00:23:27,585 --> 00:23:29,645 or old development things. 553 00:23:29,785 --> 00:23:34,725 And even this could go down another path to like even people 554 00:23:34,725 --> 00:23:36,565 that have built stuff for the SharePoint framework 555 00:23:37,035 --> 00:23:38,325 that never go back 556 00:23:38,425 --> 00:23:40,925 and bother updating their solutions 557 00:23:41,065 --> 00:23:43,885 to the more recent version of the SharePoint framework. 558 00:23:44,545 --> 00:23:48,245 And in the meantime Microsoft's making continual updates, 559 00:23:48,315 --> 00:23:50,365 continual improvements to SharePoint and 560 00:23:50,365 --> 00:23:52,925 before they know what they're running customizations built 561 00:23:52,925 --> 00:23:55,005 on the SharePoint framework that are three years old 562 00:23:55,225 --> 00:23:56,245 and stuff starts breaking 563 00:23:56,465 --> 00:23:57,965 and then you have to go in and fix it. 564 00:23:58,225 --> 00:24:01,925 And there's not always a straightforward path from 565 00:24:02,555 --> 00:24:03,965 what I've seen with some of these clients 566 00:24:03,965 --> 00:24:06,445 that I've come into where it's let's just go 567 00:24:06,505 --> 00:24:07,885 update this to the latest version 568 00:24:08,325 --> 00:24:09,525 - . Uh, so I think 569 00:24:09,595 --> 00:24:12,045 - It's still some of that caution. There's 570 00:24:12,045 --> 00:24:15,725 - No easy button for a migration here if you don't have an 571 00:24:15,735 --> 00:24:17,565 equivalent in the SharePoint framework. 572 00:24:17,905 --> 00:24:20,885 And let's be honest, it might not be possible for you 573 00:24:20,885 --> 00:24:23,205 to a straight one-to-one equivalent in the SharePoint 574 00:24:23,205 --> 00:24:25,245 framework without a heavy lift. 575 00:24:25,985 --> 00:24:28,245 So if you don't have that one-to-one option, 576 00:24:28,615 --> 00:24:31,005 there is no one-click migration, anything like that, 577 00:24:31,075 --> 00:24:34,285 like you really do have to start rationalizing 578 00:24:34,585 --> 00:24:35,765 and thinking through what 579 00:24:35,765 --> 00:24:37,325 that looks like for you along the way. 580 00:24:37,905 --> 00:24:40,765 So I feel really bad for the customers 581 00:24:40,785 --> 00:24:42,925 who are relying on add-ins in the marketplace 582 00:24:43,465 --> 00:24:45,525 and the marketplace is going away as well. 583 00:24:45,585 --> 00:24:46,645 And potentially those vendors 584 00:24:46,645 --> 00:24:48,285 that have been in the marketplace don't have 585 00:24:48,285 --> 00:24:49,725 equivalence in the SharePoint framework. 586 00:24:50,065 --> 00:24:51,445 If they do have equivalence, 587 00:24:51,795 --> 00:24:54,045 there's often not like a data migration path 588 00:24:54,045 --> 00:24:55,245 for you depending on how 589 00:24:55,245 --> 00:24:56,725 that solution was originally built. 590 00:24:57,065 --> 00:25:01,045 So there's all sorts of kind of wonkiness 591 00:25:01,115 --> 00:25:02,485 that comes along the way with this. 592 00:25:02,785 --> 00:25:07,165 And then there's another impact add-ins in the uh, 593 00:25:07,165 --> 00:25:09,845 SharePoint to add-ins also relied on 594 00:25:10,225 --> 00:25:11,405 access control services. 595 00:25:11,735 --> 00:25:13,845 Azure, Azure access control services. 596 00:25:14,005 --> 00:25:18,765 A-C-S-A-C-S is also being retired at the same time 597 00:25:19,305 --> 00:25:21,605 and basically on the same timeline. 598 00:25:22,025 --> 00:25:24,765 So even if you weren't using SharePoint ADD-ins, 599 00:25:24,785 --> 00:25:26,685 but for some reason you were using a CS 600 00:25:26,685 --> 00:25:29,365 for something else in your environment, that's another thing 601 00:25:29,365 --> 00:25:30,645 that now you gotta go figure out. 602 00:25:30,905 --> 00:25:34,365 And the replacement is enter id, which is not a 603 00:25:34,925 --> 00:25:37,525 straight one-to-one replacement either. 604 00:25:38,055 --> 00:25:41,485 Again, there's work here for you to do. 605 00:25:42,385 --> 00:25:44,925 I'm sympathetic to customers 606 00:25:45,105 --> 00:25:46,805 who can't come along for the ride. 607 00:25:47,185 --> 00:25:49,525 But at the same time, like this is part of the deal 608 00:25:49,545 --> 00:25:51,805 of cloud is that it is ever changing. 609 00:25:52,665 --> 00:25:54,405 I'm always telling my customers this, Hey, 610 00:25:54,425 --> 00:25:57,005 for all the time you're not spending managing servers 611 00:25:57,745 --> 00:25:59,405 now you're spending time managing the service 612 00:25:59,545 --> 00:26:00,725 and managing to the service 613 00:26:00,905 --> 00:26:03,245 and you should like, it's not like you're spending less time 614 00:26:03,245 --> 00:26:05,565 on it, you're just spending time in different places. 615 00:26:06,305 --> 00:26:08,765 And I see a lot of customers that don't treat it that way. 616 00:26:08,765 --> 00:26:09,845 They go, oh it's sas, 617 00:26:09,845 --> 00:26:11,405 it's evergreen, it's just gonna work forever. 618 00:26:11,945 --> 00:26:14,205 I'm like, yeah, that works until you customize it. 619 00:26:14,205 --> 00:26:17,805 But as soon as you go off the beaten path, you need to plan 620 00:26:18,065 --> 00:26:19,845 for your own success there. 621 00:26:19,875 --> 00:26:21,365 Like your own success is tied 622 00:26:21,365 --> 00:26:22,845 to the provider's success at that point. 623 00:26:23,265 --> 00:26:25,165 And you've gotta rationalize that 624 00:26:25,305 --> 00:26:26,965 and figure out what it looks like for you. 625 00:26:27,465 --> 00:26:30,005 So I'm hoping after years and years and 626 00:26:30,065 --> 00:26:32,805 and maybe this'll be another good example of it, 627 00:26:33,135 --> 00:26:35,325 those customers that haven't been planning for the future, 628 00:26:35,865 --> 00:26:37,085 you really do need to. 629 00:26:37,305 --> 00:26:40,565 - And one of the things, I get it, customers do need addeds. 630 00:26:40,565 --> 00:26:41,725 There's some benefit to add-ins. 631 00:26:41,725 --> 00:26:42,725 There's some good ones out there. 632 00:26:43,325 --> 00:26:45,325 I think this also speaks a little bit too, 633 00:26:45,385 --> 00:26:48,405 and not to tell you not to do development on SharePoint, 634 00:26:48,865 --> 00:26:53,005 but I think there's a lot of people sometimes developers, 635 00:26:53,005 --> 00:26:54,765 can I make fun of developers? Scott, your 636 00:26:54,765 --> 00:26:56,925 - Show have fun - Every okay good 637 00:26:57,075 --> 00:27:00,285 that treat every challenge they run into is SharePoint 638 00:27:00,625 --> 00:27:02,565 as a we need to fix it 639 00:27:02,565 --> 00:27:06,245 with development versus first looking to, 640 00:27:06,875 --> 00:27:08,605 there's stuff you can do outta the box. 641 00:27:09,035 --> 00:27:10,445 What can we do out of the box? 642 00:27:10,825 --> 00:27:13,725 And I think at one particular client that we helped 643 00:27:13,755 --> 00:27:15,525 with this, it was probably a year 644 00:27:15,525 --> 00:27:18,725 or two ago now, they had 25 different 645 00:27:19,305 --> 00:27:22,405 custom solutions built for their SharePoint intranet. 646 00:27:22,625 --> 00:27:25,765 And they were ones where it wasn't an add-in 647 00:27:26,105 --> 00:27:28,685 but they were on an old version of the SharePoint framework 648 00:27:28,705 --> 00:27:29,885 and stuff just kept breaking. 649 00:27:30,065 --> 00:27:31,685 So it was let's go in 650 00:27:31,685 --> 00:27:32,965 and update everything to the SharePoint 651 00:27:32,965 --> 00:27:34,165 framework or a new version. 652 00:27:34,425 --> 00:27:35,525 We started looking at it 653 00:27:35,585 --> 00:27:39,965 and we were able to cut down their, the number of SharePoint 654 00:27:40,825 --> 00:27:42,925 web parts, it's not add-ins 655 00:27:42,925 --> 00:27:45,285 but SharePoint framework customizations. 656 00:27:45,625 --> 00:27:48,485 We cut it down from whatever I said, 25, 26, 657 00:27:48,495 --> 00:27:50,565 maybe even 30 down to two 658 00:27:50,865 --> 00:27:52,765 and did everything else with the other 20 just 659 00:27:52,765 --> 00:27:53,885 doing out of the box stuff. 660 00:27:54,175 --> 00:27:57,605 Maybe it wasn't quite as pretty, it wasn't quite 661 00:27:58,235 --> 00:28:01,445 what they had before but it was pretty close 662 00:28:01,905 --> 00:28:06,525 and close enough that it wasn't worth trying to maintain all 663 00:28:06,525 --> 00:28:09,405 of this custom development work over the course of time. 664 00:28:09,465 --> 00:28:11,445 And I think that's the other thing that jumps out 665 00:28:11,445 --> 00:28:15,085 to me at this is when you're looking at SharePoint, 666 00:28:15,425 --> 00:28:17,885 you don't have to develop solutions for everything. 667 00:28:18,345 --> 00:28:21,765 Go look at some of the what can you do outta the box first 668 00:28:22,305 --> 00:28:26,325 and only would you absolutely have to go build web parts, 669 00:28:26,385 --> 00:28:28,165 go do custom development, that type of stuff. 670 00:28:28,425 --> 00:28:30,405 - That's been the case all along, right? 671 00:28:30,405 --> 00:28:32,565 You're paying Microsoft for SharePoint, 672 00:28:32,625 --> 00:28:35,925 you're not paying Microsoft to then go pay a bunch 673 00:28:35,925 --> 00:28:40,245 of developers or consultancy service providers. 674 00:28:40,805 --> 00:28:42,005 Anything would anything out there 675 00:28:42,385 --> 00:28:44,165 to then go ahead and give you what you need. 676 00:28:44,165 --> 00:28:46,445 Like you decided to invest in the platform in the first 677 00:28:46,445 --> 00:28:47,485 place for a certain reason. 678 00:28:47,755 --> 00:28:49,245 Make sure you maximize that benefit 679 00:28:49,785 --> 00:28:54,685 before you go down the not so beaten path. 680 00:28:54,835 --> 00:28:57,245 - Yeah and I don't think we said this was going away. 681 00:28:57,365 --> 00:28:58,925 I don't think we announced any timelines. 682 00:28:59,345 --> 00:29:02,205 We should probably let people know. So SharePoint add-ins. 683 00:29:02,425 --> 00:29:04,845 - I'm not the one who announces the timelines. Microsoft is. 684 00:29:05,115 --> 00:29:06,765 - Okay. So Microsoft announced the timelines. 685 00:29:06,785 --> 00:29:08,925 We did not inform our listeners of the timelines. 686 00:29:08,925 --> 00:29:10,005 We just said it's going away. 687 00:29:10,315 --> 00:29:12,885 They are uninformed unless they read the article. 688 00:29:13,245 --> 00:29:16,365 November 21st or November 21st. 689 00:29:16,725 --> 00:29:19,085 November 1st, 2024. 690 00:29:19,465 --> 00:29:22,685 So a year from when we're recording this, 691 00:29:23,225 --> 00:29:26,045 ADDINS will stop working in new tenants. 692 00:29:26,105 --> 00:29:27,645 So if you go spin up a brand new tenant 693 00:29:27,975 --> 00:29:31,285 after November 1st of next year, 2024 694 00:29:31,965 --> 00:29:33,325 a CS will no longer work 695 00:29:33,465 --> 00:29:36,205 and SharePoint add-ins will no longer work SharePoint 696 00:29:36,435 --> 00:29:40,765 ADD-ins and a CS will stop working in 697 00:29:41,195 --> 00:29:43,205 current tenants as 698 00:29:43,225 --> 00:29:46,485 of April 2nd, 2026. 699 00:29:47,025 --> 00:29:50,565 So roughly two and a half years from now. 700 00:29:50,725 --> 00:29:53,445 I think that works out too. Mm-Hmm right ish. 701 00:29:54,185 --> 00:29:58,085 And then as of I'm losing my timelines. So 702 00:29:58,085 --> 00:30:01,845 - I think your next important one is July 1st, 2024. 703 00:30:02,025 --> 00:30:03,685 - Yes, that's what I missed. Which 704 00:30:03,705 --> 00:30:08,565 - Is when you will no longer be able to get new add-ins 705 00:30:09,105 --> 00:30:11,525 or, or you will not be no longer be able 706 00:30:11,525 --> 00:30:14,525 to purchase add-ins from the public marketplace. 707 00:30:14,795 --> 00:30:16,405 Well actually it's not very clear in the way they worded it. 708 00:30:16,465 --> 00:30:20,445 Uh, so ven vendors can't add new add-ins to the marketplace. 709 00:30:20,805 --> 00:30:22,965 I don't know. I don't understand. Basically if you're doing 710 00:30:22,965 --> 00:30:25,445 add-ins today, don't go buy any new ones 711 00:30:25,845 --> 00:30:26,965 like after today. 712 00:30:27,425 --> 00:30:28,445 That's good advice. Yes. 713 00:30:28,445 --> 00:30:30,165 Yeah, please don't go buy any new ones 714 00:30:30,545 --> 00:30:33,405 and then start coming up with your ramp-down plan. 715 00:30:33,905 --> 00:30:35,325 And I imagine for some of this, 716 00:30:35,325 --> 00:30:38,565 especially if you're on marketplace add-ins, you are going 717 00:30:38,565 --> 00:30:41,685 to have to wait for those vendors to announce their plans 718 00:30:42,505 --> 00:30:45,925 and hopefully their plans can line up with the 719 00:30:46,565 --> 00:30:48,085 Microsoft timelines for all this stuff. 720 00:30:48,225 --> 00:30:51,325 - Yep. And then that April 2nd, it was nice 721 00:30:51,325 --> 00:30:52,725 of them not to do this on April 1st. 722 00:30:53,045 --> 00:30:55,845 I wonder if that was intentional April 2nd, 723 00:30:55,915 --> 00:30:57,165 it's all going to go away. 724 00:30:57,305 --> 00:30:59,085 And they do say in here there's not gonna be 725 00:30:59,085 --> 00:31:00,165 an option to extend it. 726 00:31:00,305 --> 00:31:03,365 So unless Microsoft makes additional announcements like 727 00:31:03,375 --> 00:31:04,965 April 2nd, it all shuts down 728 00:31:05,065 --> 00:31:08,965 and you're hosed if you haven't made that transition off. 729 00:31:09,105 --> 00:31:10,485 But you have two and a half years to do it. 730 00:31:10,545 --> 00:31:13,365 So all kinds of time right Scott? 731 00:31:13,625 --> 00:31:16,045 - All kinds of time. I always love things like this 732 00:31:16,285 --> 00:31:19,045 'cause again there's all the knock-on effects that come in. 733 00:31:19,185 --> 00:31:21,925 So add-ins going away, a CS going away. 734 00:31:22,535 --> 00:31:25,885 There were multiple flavors of ADD-ins, like basically 735 00:31:26,585 --> 00:31:28,885 UI add-ins that you added that manipulated D UI 736 00:31:29,545 --> 00:31:32,925 and then there were hosted add-ins, which 737 00:31:33,755 --> 00:31:37,045 were the ones that used a CS in the middle 738 00:31:37,105 --> 00:31:40,005 as an auth framework provider hosted add-ins 739 00:31:40,025 --> 00:31:41,605 and I think officially is what they were called. 740 00:31:42,225 --> 00:31:44,525 But then those were hosted on their own units of compute 741 00:31:44,545 --> 00:31:45,765 and all that stuff that's out there. 742 00:31:46,225 --> 00:31:47,805 You gotta go figure all that out as well. 743 00:31:48,285 --> 00:31:50,325 like what's all the other stuff running in my 744 00:31:50,445 --> 00:31:53,485 environment that was actually potentially tied to 745 00:31:53,995 --> 00:31:56,045 this Add-in along the way, 746 00:31:56,115 --> 00:31:59,165 whether it came from the marketplace custom developed in 747 00:31:59,165 --> 00:32:01,525 your own tenant catalog, like whatever it happened to be. 748 00:32:01,535 --> 00:32:03,805 - Right? And this is another interesting call out. 749 00:32:03,805 --> 00:32:05,125 They call it out towards the bottom 750 00:32:05,185 --> 00:32:07,245 of the a CS documentation. 751 00:32:07,565 --> 00:32:09,485 I don't know that it's in Okay. 752 00:32:09,485 --> 00:32:12,045 They do have it in the SharePoint documentation too 753 00:32:12,745 --> 00:32:14,285 for people that forget. 754 00:32:14,595 --> 00:32:17,965 Project Online is built on top of SharePoint. 755 00:32:18,185 --> 00:32:22,765 So this also applies to anything project online related 756 00:32:22,915 --> 00:32:25,365 because SharePoint A are going away 757 00:32:26,065 --> 00:32:28,285 and could affect project online 758 00:32:28,825 --> 00:32:33,405 and a CS going away could also affect project online for any 759 00:32:33,405 --> 00:32:36,405 of those extensions that you built on top 760 00:32:36,405 --> 00:32:40,445 of SharePoint online slash project deadline. 761 00:32:40,645 --> 00:32:42,525 - I wonder what that means in context of 762 00:32:42,675 --> 00:32:44,965 what we talked about last week or the week 763 00:32:44,965 --> 00:32:47,285 before with the collapse, the unification 764 00:32:47,305 --> 00:32:48,405 of and all the things. 765 00:32:48,465 --> 00:32:50,045 So project coming over to play in 766 00:32:50,345 --> 00:32:53,645 and wasn't very clear what that looked like at the time. 767 00:32:53,765 --> 00:32:56,765 I wonder if some of that's driven by this too. It wouldn't 768 00:32:57,325 --> 00:33:01,085 - Surprise me if there's yeah, if project in 769 00:33:01,085 --> 00:33:03,925 and of itself, like not even custom stuff on top of project, 770 00:33:04,105 --> 00:33:08,405 but to your point like did Microsoft have some add-ins 771 00:33:09,075 --> 00:33:11,925 some stuff that they're using in Project online 772 00:33:12,075 --> 00:33:16,485 that is using the A CS and SharePoint ADD model 773 00:33:16,545 --> 00:33:18,925 and they were forced into this. 774 00:33:19,285 --> 00:33:20,805 - wouldn't surprise me or 775 00:33:20,865 --> 00:33:22,845 - In agreement with Microsoft on it. 776 00:33:22,925 --> 00:33:25,285 I don't know if they were forced or arms twisted 777 00:33:25,285 --> 00:33:27,845 or if this was a mutual decision, 778 00:33:28,105 --> 00:33:30,085 but I can see some stuff being there too. 779 00:33:30,115 --> 00:33:32,805 Yeah. Oh good times Scott. 780 00:33:33,385 --> 00:33:35,205 The ever-changing Cloud . 781 00:33:35,525 --> 00:33:36,525 Anything else you wanna talk about 782 00:33:36,665 --> 00:33:39,445 before we wrap up our Thursday recording? 783 00:33:39,545 --> 00:33:40,685 No, we have tomorrow too. 784 00:33:40,685 --> 00:33:42,005 Yeah, we're gonna record again tomorrow. 785 00:33:42,305 --> 00:33:44,405 Our, these holidays mess us up. Sometimes 786 00:33:44,615 --> 00:33:47,645 - We're gonna chat again in like less than 24 hours. 787 00:33:47,865 --> 00:33:49,205 So we'll talk more then. 788 00:33:49,205 --> 00:33:52,805 - Yeah, we save some stuff for that episode. All right. 789 00:33:53,365 --> 00:33:57,645 Go enjoy the rest of your nice cool Florida weather. 790 00:33:57,815 --> 00:34:00,045 There was frost on the roof the other morning, Scott. 791 00:34:00,145 --> 00:34:01,485 It felt so good outside. I 792 00:34:01,485 --> 00:34:04,405 - Know I've broken out all my fluffy sweatshirts 793 00:34:04,545 --> 00:34:05,925 and so it was 794 00:34:06,535 --> 00:34:10,325 47 Fahrenheit two days ago and so that was the day. 795 00:34:10,325 --> 00:34:12,565 There was like frost outside in the morning. 796 00:34:13,125 --> 00:34:14,125 I was freezing that day. 797 00:34:14,125 --> 00:34:15,485 I haven't turned the heat on in my house yet. 798 00:34:15,505 --> 00:34:17,205 I'm one of those people who like, I wait 799 00:34:17,205 --> 00:34:18,365 until the very last minute. 800 00:34:18,365 --> 00:34:21,045 Good for you. We all just, we bundle up around here. 801 00:34:21,545 --> 00:34:23,685 So I broke out all my fluffy sweatshirts and did all that 802 00:34:23,685 --> 00:34:25,165 and I was like, it was so cold. 803 00:34:25,205 --> 00:34:27,685 I had to go find like my little thin bird gloves, , 804 00:34:28,115 --> 00:34:29,845 like my little underlayment gloves 805 00:34:29,945 --> 00:34:31,565 so I could take the dogs on a walk. 806 00:34:31,665 --> 00:34:36,285 And I, I did all that and then the next day I woke up 807 00:34:36,285 --> 00:34:38,005 and it was still cold, slept 808 00:34:38,005 --> 00:34:39,445 with the window open, all that kind of stuff. 809 00:34:39,465 --> 00:34:42,725 We broke out the extra big quilt and comforter. 810 00:34:42,905 --> 00:34:44,845 That's wonderful. And we did all that. And so I woke up 811 00:34:44,845 --> 00:34:47,725 and it was still cold so I went over to the closet, 812 00:34:48,145 --> 00:34:51,005 got dressed in the morning, put on my big fluffy sweatshirt 813 00:34:51,105 --> 00:34:53,005 and I walked around the house most of the day freezing. 814 00:34:53,365 --> 00:34:55,085 'cause once it gets cold, I don't turn the heat on 815 00:34:55,085 --> 00:34:57,205 so it stays cold inside the house too. 816 00:34:57,665 --> 00:34:59,965 And then I had to go to the grocery store and go shopping 817 00:35:00,145 --> 00:35:02,605 and I walked outside and it was like 65 Fahrenheit. 818 00:35:02,685 --> 00:35:04,125 I was like, oh no, what happened? 819 00:35:04,385 --> 00:35:05,525 And I had already walked out the door. 820 00:35:05,605 --> 00:35:07,645 I wasn't gonna turn around and change my whole outfit 821 00:35:07,645 --> 00:35:08,765 for the day, but I went 822 00:35:08,765 --> 00:35:13,325 to the grocery store dressed up like I've got thick boots on 823 00:35:13,905 --> 00:35:15,645 and a big fluffy sweatshirt. 824 00:35:15,905 --> 00:35:17,285 And I showed up at the grocery store 825 00:35:17,285 --> 00:35:19,565 and everybody's there in like shorts and a T-shirt. 826 00:35:19,565 --> 00:35:21,605 And I'm like, Hmm. Either they're tourists 827 00:35:22,265 --> 00:35:24,565 or yeah, they gotta be tourists. I, they're not, 828 00:35:24,565 --> 00:35:26,005 - I was gonna say tourists, like they're 829 00:35:26,095 --> 00:35:27,445 - Their blood's not thin enough yet. 830 00:35:27,585 --> 00:35:28,685 - No. Anybody in Florida, 831 00:35:29,065 --> 00:35:31,485 if it's under 70 Florida's bundle up. 832 00:35:31,485 --> 00:35:33,685 Like it's the middle of winter one. 833 00:35:33,845 --> 00:35:36,125 I don't know if it's 'cause everybody in Florida's cold 834 00:35:36,345 --> 00:35:38,965 or if it's because everybody in Florida wants an excuse 835 00:35:39,025 --> 00:35:40,405 to wear all their warm clothes 836 00:35:40,745 --> 00:35:43,965 and like 70 is that threshold where you can put up 837 00:35:43,965 --> 00:35:45,885 with it once it drops under 70. Part 838 00:35:45,885 --> 00:35:47,845 - Of it was I did need the excuse to wear the clothes. 839 00:35:48,145 --> 00:35:50,645 So like my wife bought me a bunch of new flannel shirts 840 00:35:50,645 --> 00:35:52,805 and things before we went on vacation for Thanksgiving. 841 00:35:52,815 --> 00:35:54,365 She's like, we're going to the mountains, 842 00:35:54,365 --> 00:35:55,525 we're gonna be in front of a fire. 843 00:35:55,665 --> 00:35:57,405 You need plaid and and flannel. 844 00:35:57,405 --> 00:35:58,605 And I was like, sure, whatever. 845 00:35:58,605 --> 00:36:00,365 Like it's cold up there, legitimately cold. 846 00:36:00,545 --> 00:36:02,365 So I came back and I washed everything. 847 00:36:02,385 --> 00:36:04,205 Now I've got all these flannel shirts. 848 00:36:04,265 --> 00:36:07,085 I'm like what am I gonna wear these down here? know. 849 00:36:07,465 --> 00:36:10,725 But yeah, we are officially into hopefully cold season. 850 00:36:11,015 --> 00:36:12,485 We'll see how long it sticks. I 851 00:36:12,485 --> 00:36:14,245 - Don't think it's supposed to stay too long. 852 00:36:14,255 --> 00:36:17,205 We're actually headed down to Disney this weekend 853 00:36:17,545 --> 00:36:19,645 and one of my kids was bummed out 854 00:36:19,805 --> 00:36:21,725 'cause it's supposed to be like 80 down in Disney. 855 00:36:21,835 --> 00:36:24,325 Yeah, it's a little south. I don't know about here. 856 00:36:24,715 --> 00:36:26,765 It's supposed to be up to 78 Friday. 857 00:36:27,065 --> 00:36:29,525 - Fun thing about living in Florida, we have two seasons. 858 00:36:29,545 --> 00:36:31,405 We have summer and we have summer light 859 00:36:31,705 --> 00:36:34,285 and we're like, so when I say we're making the transition 860 00:36:34,285 --> 00:36:35,965 to the cold season, we're making the transition 861 00:36:35,965 --> 00:36:38,205 to summer light maybe kind of sorta Yes 862 00:36:38,465 --> 00:36:40,125 and really not even now. 863 00:36:40,125 --> 00:36:43,005 Like it still gets into Yeah, the eighties and December. 864 00:36:43,595 --> 00:36:46,485 Yeah, we'll see. Usually like January, February you start 865 00:36:46,485 --> 00:36:48,045 to hit like that cold snap 866 00:36:48,185 --> 00:36:49,885 and when I say cold snap it's, ooh, 867 00:36:49,885 --> 00:36:51,925 it's 60 degrees every day. Rough. 868 00:36:52,065 --> 00:36:53,965 - And that's the high it does get down. 869 00:36:54,235 --> 00:36:56,525 I've woken up and had to scrape my windshield in Florida. 870 00:36:56,615 --> 00:36:58,525 Every once in a while you get a thin layer of ice. 871 00:36:58,905 --> 00:37:01,765 But yeah, Friday, tomorrow's Scott high of 78. 872 00:37:01,945 --> 00:37:04,405 So don't put on all your warm clothes tomorrow 873 00:37:04,405 --> 00:37:07,605 because it's gonna be a warm one-ish. Alright, 874 00:37:08,135 --> 00:37:09,135 - Noted. 875 00:37:09,135 --> 00:37:09,525 - Alright, well thanks. 876 00:37:09,865 --> 00:37:13,485 Now go enjoy your nice fluffy warm clothes for one more day 877 00:37:13,485 --> 00:37:15,685 before you have to go pack the ball away for a couple days 878 00:37:15,785 --> 00:37:18,445 and then you can get 'em out again by a week from now. 879 00:37:18,545 --> 00:37:19,765 - All right, sounds good. Thanks Ben. 880 00:37:19,795 --> 00:37:24,005 - Talk to you later. Scott, if you enjoyed the podcast, 881 00:37:24,505 --> 00:37:26,485 go leave us a five star rating in iTunes. 882 00:37:26,665 --> 00:37:28,205 It helps to get the word out 883 00:37:28,265 --> 00:37:31,765 so more it pros can learn about Office 365 and Azure. 884 00:37:32,505 --> 00:37:35,045 If you have any questions you want us to address on the show 885 00:37:35,185 --> 00:37:37,645 or feedback about the show, feel free 886 00:37:37,665 --> 00:37:40,725 to reach out via our website, Twitter, or Facebook. 887 00:37:40,945 --> 00:37:42,885 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