Episode 364 – Microsoft Designer, Azure Updates, and Enterprise IoT Security changes

December 14, 2023

Episode Transcript

In Episode 364, Ben and Scott discuss the recently announced Microsoft Designer, cover a handful of updates to Azure including Azure Automation and Azure Container Storage. Then they close out with some updates to the licensing model for Enterprise IoT Security.

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,175 - Welcome to episode 364 2 00:00:06,195 --> 00:00:08,535 of the Microsoft Cloud IT Pro Podcast 3 00:00:09,175 --> 00:00:11,735 recorded live on December 1st, 2023. 4 00:00:12,165 --> 00:00:14,655 This is a show about Microsoft 365 5 00:00:14,655 --> 00:00:16,855 and Azure from the perspective of it pros 6 00:00:16,855 --> 00:00:20,175 and end users where we discuss a topic or recent news 7 00:00:20,275 --> 00:00:21,535 and how it relates to you. 8 00:00:22,215 --> 00:00:23,975 Microsoft Designer has received a lot 9 00:00:23,975 --> 00:00:26,295 of attention creating images as of late. 10 00:00:26,595 --> 00:00:29,495 So we start out talking a bit about creating our own images. 11 00:00:29,995 --> 00:00:33,575 We also dive into some recent news around Azure automation, 12 00:00:33,945 --> 00:00:37,935 PowerShell container storage, and enterprise IOT security. 13 00:00:40,525 --> 00:00:43,055 Okay, let's go Scott. We have nothing. 14 00:00:43,275 --> 00:00:44,975 - We have nothing. It's your, it's, it's your show. 15 00:00:44,975 --> 00:00:46,295 You're supposed to plan all this out. 16 00:00:46,295 --> 00:00:48,015 Come on now. We have, we have, 17 00:00:48,415 --> 00:00:49,415 - I have planned out. 18 00:00:49,415 --> 00:00:50,655 I have planned out. I'm leaving for Disney 19 00:00:50,955 --> 00:00:53,015 and this podcast is standing in my way right now. 20 00:00:53,235 --> 00:00:54,775 - All right, well there, there you go. 21 00:00:54,875 --> 00:00:57,735 We, we will get through a nice, quick, concise 22 00:00:58,075 --> 00:00:59,815 and short one today. So 23 00:01:00,135 --> 00:01:02,655 - I have a question if this elevates my nerd status. 24 00:01:03,215 --> 00:01:05,255 I have a client that is moving offices. 25 00:01:05,955 --> 00:01:08,895 So this morning I took my truck and I went 26 00:01:09,275 --> 00:01:12,495 and he gave me his old server rack. 27 00:01:12,835 --> 00:01:14,775 So I now have, it's got, 28 00:01:14,775 --> 00:01:16,695 it's like a Threequarter height server rack. 29 00:01:16,695 --> 00:01:17,975 It's 65 inches tall, 30 00:01:18,235 --> 00:01:20,135 but I now have a 65 inch server rack 31 00:01:20,135 --> 00:01:22,415 that I'm putting in the closet in my bedroom 32 00:01:22,705 --> 00:01:24,215 slash it's my office bedroom. 33 00:01:24,495 --> 00:01:26,855 A bedroom in our house that serves as my office . 34 00:01:27,645 --> 00:01:29,455 - Well, I mean if you're gonna go 35 00:01:29,455 --> 00:01:30,975 ahead and do it, get it done. So 36 00:01:31,175 --> 00:01:32,615 - I already have a rack in here, 37 00:01:32,635 --> 00:01:35,775 but it's only, I think I made it like three feet tall 38 00:01:35,775 --> 00:01:37,135 and it's pretty much full. 39 00:01:37,555 --> 00:01:38,935 So now I have a bigger rack 40 00:01:39,315 --> 00:01:40,975 and I just have to pull it up the steps 41 00:01:41,035 --> 00:01:42,215 and swap everything out. 42 00:01:42,355 --> 00:01:45,375 So some weekend everything is getting disconnected, 43 00:01:45,375 --> 00:01:48,495 putting back in this rack I may add some shelves and drawers 44 00:01:48,495 --> 00:01:49,855 and stuff 'cause it also would serve 45 00:01:49,855 --> 00:01:51,015 some nice storage in the closet. 46 00:01:51,485 --> 00:01:55,815 - Yeah. So for a server room, what was that thing? 47 00:01:55,815 --> 00:01:57,495 It was like a six seven foot rack, right? 48 00:01:57,525 --> 00:01:58,855 Like it was, it was decent sized 49 00:01:59,025 --> 00:02:01,415 - 65 inches, not, what is that? 50 00:02:01,485 --> 00:02:02,575 Five and a half feet. 51 00:02:02,605 --> 00:02:04,575 Five and a half foot rack. Yeah, you get a 52 00:02:04,575 --> 00:02:05,615 - Little bit of street cred there. 53 00:02:05,615 --> 00:02:06,735 You get more street cred. 54 00:02:07,075 --> 00:02:09,735 So the, at least the picture you sent me was not a 55 00:02:10,545 --> 00:02:12,975 floor rack, like it wasn't floor mounted, 56 00:02:12,975 --> 00:02:14,175 it was still wall mounted. 57 00:02:14,595 --> 00:02:16,775 So you get, you get extra credit if you manage to get 58 00:02:16,775 --> 00:02:18,895 that thing a couple feet off the floor and mount it 59 00:02:18,895 --> 00:02:20,015 and get the fans plugged in. 60 00:02:20,015 --> 00:02:21,455 So it's actually circulating air. 61 00:02:21,455 --> 00:02:23,895 - Alright, so here's a question for listeners. 62 00:02:24,195 --> 00:02:27,415 Was I kind or not or should I have taken it? 63 00:02:27,535 --> 00:02:29,135 I left the wall rack there. , 64 00:02:29,635 --> 00:02:31,095 - You should have taken it. This is going to 65 00:02:31,445 --> 00:02:32,615 - Turn into a FLA rack. 66 00:02:33,085 --> 00:02:35,055 Okay, so here is why I left it there. 67 00:02:35,335 --> 00:02:38,455 I went there with every intention of taking the wall, 68 00:02:39,075 --> 00:02:40,615 the portion of it off, 69 00:02:41,195 --> 00:02:44,255 but the network cables all, I don't know 70 00:02:44,255 --> 00:02:47,335 how many there were, they had three full patch panels. 71 00:02:47,755 --> 00:02:50,335 So what is that? There's 16 ports 72 00:02:50,595 --> 00:02:55,295 and a panel about, so 32 ish cables? 73 00:02:55,715 --> 00:02:58,135 No, not 32. 16 times three. 74 00:02:58,315 --> 00:02:59,725 What's that? My math was failing me. 75 00:02:59,725 --> 00:03:02,525 - 48. 48. Yes, - 48 cables going into it. 76 00:03:02,525 --> 00:03:05,165 But they were strung through the top of the wall mount 77 00:03:05,545 --> 00:03:08,165 and then punched down onto the patch panels. 78 00:03:08,585 --> 00:03:12,885 In order to take the wall mount, I would've had to rip all 79 00:03:12,885 --> 00:03:14,885 of these cables off of the patch panels 80 00:03:15,265 --> 00:03:16,645 and leave them dangling there. 81 00:03:16,905 --> 00:03:19,085 And these were not, and the cables were not labeled 82 00:03:19,085 --> 00:03:20,045 - Well, I mean they weren't used in 83 00:03:20,045 --> 00:03:21,205 the patch panel for anything else. Who, 84 00:03:21,205 --> 00:03:22,285 - Whoever came in after - Me cares. 85 00:03:22,875 --> 00:03:24,165 - Well, but the next tenant will. 86 00:03:24,385 --> 00:03:27,085 So there's going to be a tenant inevitably in this 87 00:03:27,245 --> 00:03:28,325 building down the road. 88 00:03:28,865 --> 00:03:32,445 So they would've had 48 cables, completely unlabeled going 89 00:03:32,445 --> 00:03:33,565 to all parts of this office 90 00:03:33,675 --> 00:03:35,285 with no idea where each one went. 91 00:03:35,925 --> 00:03:38,645 . So I left the patch panels, 92 00:03:39,125 --> 00:03:42,245 I left the cables punched in and I left the wall mount there 93 00:03:42,515 --> 00:03:45,525 because frankly it won't fit in my closet on the wall mount 94 00:03:45,525 --> 00:03:47,245 anyways, so I'm gonna put it on the floor 95 00:03:47,585 --> 00:03:50,005 and based on the picture I sent, I like, we looked 96 00:03:50,005 --> 00:03:51,045 and we thought maybe there were fans. 97 00:03:51,045 --> 00:03:52,645 There are no fans on the bottom or anything. 98 00:03:52,705 --> 00:03:55,645 So it's just a played old metal rack. 99 00:03:55,795 --> 00:03:57,045 - Yeah. All right, well, 100 00:03:57,255 --> 00:03:58,845 we'll we'll see how it goes for you. 101 00:03:58,995 --> 00:04:01,045 Like we'll see how many fans you gotta buy later 102 00:04:01,965 --> 00:04:04,845 'cause it is, it is a rack in a closet in 103 00:04:04,845 --> 00:04:06,045 an upstairs bedroom. 104 00:04:06,685 --> 00:04:08,765 like let's be honest, in Florida . Yeah. 105 00:04:08,975 --> 00:04:10,525 Where there's a bunch of other equipment, 106 00:04:10,635 --> 00:04:12,765 like you've got lights and TVs 107 00:04:13,065 --> 00:04:15,365 and a bunch of other things with fans running. 108 00:04:15,585 --> 00:04:19,005 So yeah, we'll, we'll we'll see how it all goes. 109 00:04:19,345 --> 00:04:21,325 You're gonna need something to circulate there anyway, 110 00:04:21,325 --> 00:04:22,845 even if it's just circulating hot air 111 00:04:22,845 --> 00:04:24,285 just to keep the dust out of it. Yeah, 112 00:04:24,525 --> 00:04:25,965 - I do have a couple fans in my 113 00:04:25,965 --> 00:04:27,125 little rack that's in there now. 114 00:04:27,505 --> 00:04:30,525 So I will relocate those into this bigger one 115 00:04:30,545 --> 00:04:32,405 but they may not be enough. We'll have to see. 116 00:04:32,585 --> 00:04:34,125 - So we'll have to follow up in a couple weeks. 117 00:04:34,125 --> 00:04:37,125 Then once you've got it all kind of reconfigured 118 00:04:37,145 --> 00:04:40,165 and ready to go and you share a picture on the interwebs 119 00:04:40,165 --> 00:04:43,885 and we'll see how much your Geek Street cred score rises 120 00:04:44,025 --> 00:04:45,025 - If it goes up or down. 121 00:04:45,075 --> 00:04:46,245 Alright, sounds good. 122 00:04:46,245 --> 00:04:47,525 So yes, it will not be wall-mounted, 123 00:04:47,525 --> 00:04:49,725 it'll just be sitting on the floor in the closet. 124 00:04:50,245 --> 00:04:52,285 . Oh, so that was my morning 125 00:04:52,465 --> 00:04:54,805 and then I get a lot of other client work done. 126 00:04:55,065 --> 00:04:56,405 But that was one thing. 127 00:04:56,545 --> 00:04:58,445 You know what else we've been playing with this week, Scott, 128 00:04:58,685 --> 00:04:59,885 I don't know what else you've been playing with 129 00:04:59,885 --> 00:05:01,045 - With I think, I think you've 130 00:05:01,045 --> 00:05:02,085 been playing with it more than I have. 131 00:05:02,085 --> 00:05:04,205 You've been having fun with that new designer. The 132 00:05:04,205 --> 00:05:05,565 - New designer, the image designer. 133 00:05:06,065 --> 00:05:10,605 And I cannot take full credit for this one at least in terms 134 00:05:10,625 --> 00:05:12,125 of coming up with it. 135 00:05:12,465 --> 00:05:15,005 So there was a post on LinkedIn 136 00:05:15,185 --> 00:05:17,725 and I should go pull up LinkedIn so I can give credit 137 00:05:17,735 --> 00:05:20,165 where credit is due unless you have it up. 138 00:05:20,325 --> 00:05:24,565 I have a post on LinkedIn of who actually I, I don't know 139 00:05:24,565 --> 00:05:27,885 that I stole this from but who I borrowed it from LinkedIn. 140 00:05:28,665 --> 00:05:30,725 Oh Scott. I have another beef. 141 00:05:31,125 --> 00:05:32,325 I updated edge the other day 142 00:05:32,325 --> 00:05:36,325 and it signed me out of every single account in my profile. 143 00:05:36,585 --> 00:05:38,445 One of those being LinkedIn. Yeah, 144 00:05:38,725 --> 00:05:40,725 - I have that problem occasionally as well. 145 00:05:40,925 --> 00:05:43,605 I find like after a reboot for some reason it forgets 146 00:05:43,605 --> 00:05:45,205 that cookies are a thing. Yes. 147 00:05:45,425 --> 00:05:46,485 - So I need to sign in. 148 00:05:46,585 --> 00:05:51,285 But there is someone who we will, oh sign in expired 149 00:05:51,425 --> 00:05:54,845 who we will identify here shortly who came up with some text 150 00:05:54,905 --> 00:05:59,085 to essentially create cartoon images of, I would say, 151 00:05:59,085 --> 00:06:01,885 of yourself, but it is of yourself as best 152 00:06:01,885 --> 00:06:03,165 as you can describe yourself. 153 00:06:03,465 --> 00:06:04,845 And it's kind of been fun to play with. 154 00:06:05,035 --> 00:06:06,645 I've seen several people doing this now 155 00:06:06,885 --> 00:06:07,885 - . 156 00:06:07,885 --> 00:06:08,565 Yeah it does. Okay. 157 00:06:08,905 --> 00:06:12,085 Except when you ask it to include like a logo 158 00:06:12,225 --> 00:06:15,525 or text in there and then it just starts 159 00:06:16,045 --> 00:06:17,725 straight up hallucinating and, 160 00:06:17,785 --> 00:06:21,245 and can't remember left from right up from down or, 161 00:06:21,305 --> 00:06:22,965 or anything like that along the way. 162 00:06:23,035 --> 00:06:26,845 - Yeah, so I saw here it is Jack eth them, eth them, 163 00:06:27,245 --> 00:06:29,685 probably jack Row with them and he gave the tech. 164 00:06:29,705 --> 00:06:31,685 So it is you very much go into 165 00:06:32,085 --> 00:06:36,965 designer.microsoft.com/i think it's slash images in this 166 00:06:36,965 --> 00:06:38,725 text is like a cartoon man 167 00:06:38,725 --> 00:06:41,005 with a smile on the front wearing a black colored shirt, 168 00:06:41,005 --> 00:06:42,605 brown eyes wears black large glasses 169 00:06:42,785 --> 00:06:46,045 and short brown, classic slick backed hair holding 170 00:06:46,125 --> 00:06:47,205 a Microsoft laptop. 171 00:06:47,505 --> 00:06:49,485 And then after that, and I think this is the part 172 00:06:49,485 --> 00:06:51,765 that really helps with the design, is it's 173 00:06:52,465 --> 00:06:55,845 laptop text 3D rendering, typography, illustration, 174 00:06:56,085 --> 00:06:58,765 painting, photo poster 3D render to come up 175 00:06:58,765 --> 00:07:00,045 with this cartoon image. 176 00:07:00,505 --> 00:07:01,845 So to your point, 177 00:07:01,865 --> 00:07:04,885 it does a decent job if you're watching this 178 00:07:04,905 --> 00:07:06,965 or if you have seen me, you know that. 179 00:07:07,505 --> 00:07:09,005 And as my wife likes to remind me, 180 00:07:09,425 --> 00:07:12,925 my hair is thinning on top more so than it used to be. 181 00:07:13,305 --> 00:07:17,125 It does not like any form of telling it 182 00:07:17,125 --> 00:07:18,845 that it's like a receding hairline 183 00:07:18,945 --> 00:07:21,005 or thinning hair or a little hair. 184 00:07:21,505 --> 00:07:24,125 You either have like a full head of hair or you're bald 185 00:07:24,525 --> 00:07:25,525 - . 186 00:07:25,755 --> 00:07:26,805 Sure. And that, that, 187 00:07:26,805 --> 00:07:28,685 that's one way to think about it . So 188 00:07:28,685 --> 00:07:30,245 - Yeah, it's been interesting and that, 189 00:07:30,305 --> 00:07:32,325 and like you said, you ask it to come up with text. 190 00:07:32,355 --> 00:07:36,725 Like I asked it to do Microsoft 365 on a shirt or do that 191 00:07:36,985 --> 00:07:39,325 and I think you did some Microsoft Azure stuff 192 00:07:39,465 --> 00:07:42,245 and it like spells Microsoft with two S's in the middle 193 00:07:42,585 --> 00:07:46,885 or for 365 it was putting like 3 55 or 36 194 00:07:47,385 --> 00:07:48,565 or three 195 00:07:48,665 --> 00:07:51,685 and then some weird random character type 196 00:07:51,685 --> 00:07:53,205 of thing followed by a five. 197 00:07:53,785 --> 00:07:54,925 It does not do well 198 00:07:54,925 --> 00:07:57,605 with placing text in the image sometimes you get lucky. 199 00:07:57,795 --> 00:07:59,885 - Yeah. Uh, along the way you definitely can. 200 00:08:00,545 --> 00:08:04,045 So I don't know, I see lots of folks like having a lot 201 00:08:04,045 --> 00:08:05,525 of fun with some 202 00:08:05,525 --> 00:08:08,125 of these things like generate the cartoony picture. 203 00:08:08,715 --> 00:08:13,005 It's definitely not mid journey. Like it's, it's not that. 204 00:08:13,075 --> 00:08:16,125 It's more like PowerPoint play art the way it's kind 205 00:08:16,125 --> 00:08:17,445 of implemented today. 206 00:08:18,195 --> 00:08:21,725 It's certainly not things like Photoshop generative fill 207 00:08:22,065 --> 00:08:24,485 or anything like that either. 208 00:08:24,905 --> 00:08:28,325 So I, I can understand like where people have fun with it. 209 00:08:28,565 --> 00:08:31,125 I know it's like, not for me honestly. I'm a little . 210 00:08:31,145 --> 00:08:34,085 I'm a little over seeing everybody like every day like, hey, 211 00:08:34,085 --> 00:08:35,845 here's the four pictures I posted 212 00:08:36,425 --> 00:08:38,645 and you know, here, here's what I did to general. 213 00:08:39,105 --> 00:08:41,285 So to those of you who listen, who do those kinds 214 00:08:41,285 --> 00:08:43,325 of things I know seem me do, sorry Andrew. 215 00:08:43,845 --> 00:08:46,405 I love seeing your generative AI pictures every day on 216 00:08:46,645 --> 00:08:50,645 Facebook, but some days I just go, no, not for me today. 217 00:08:50,825 --> 00:08:51,925 And it's usually on the days 218 00:08:51,955 --> 00:08:56,085 that AI has ticked me off in some way or another 219 00:08:56,705 --> 00:08:58,405 and it's probably done me wrong already. 220 00:08:58,405 --> 00:09:00,605 Either with something else that I was trying to do 221 00:09:00,605 --> 00:09:01,645 with a generative thing 222 00:09:02,225 --> 00:09:05,605 or you know, AI has its issues. 223 00:09:05,785 --> 00:09:07,365 So if you take joy 224 00:09:07,365 --> 00:09:10,205 and delight in generating pictures, continue to do 225 00:09:10,205 --> 00:09:12,565 so I'm able to self re re regulate. 226 00:09:12,565 --> 00:09:13,725 I know how to block and mute. 227 00:09:14,165 --> 00:09:16,125 - I did mine that one morning when I was playing with it 228 00:09:16,125 --> 00:09:17,285 and I have not done any since. 229 00:09:17,315 --> 00:09:19,605 Like, I'm like, do I actually wanna use these somewhere? 230 00:09:19,865 --> 00:09:23,005 It was kind of fun, I don't know, but I'm with you. 231 00:09:23,205 --> 00:09:24,565 I have played with it once 232 00:09:24,865 --> 00:09:26,725 and I did it for like an hour or so. 233 00:09:26,805 --> 00:09:28,365 I was trying to figure out what I could do 234 00:09:28,365 --> 00:09:29,725 and what images I can come up with. 235 00:09:29,905 --> 00:09:32,365 But I have not done anything with it since 236 00:09:32,725 --> 00:09:36,165 - I will point you to a kind of 237 00:09:36,745 --> 00:09:38,005 fun one that's out there. 238 00:09:38,105 --> 00:09:40,885 So this isn't image generation, 239 00:09:41,185 --> 00:09:43,685 so I'll pop a a link in the chat 240 00:09:44,025 --> 00:09:46,285 and in the show notes so everybody has it. 241 00:09:46,505 --> 00:09:50,325 But, so this is a link to a gist 242 00:09:50,505 --> 00:09:51,725 that's out on GitHub 243 00:09:51,945 --> 00:09:56,165 and it's from a product manager that I follow on a bunch 244 00:09:56,165 --> 00:09:57,365 of different social platforms. 245 00:09:57,465 --> 00:10:01,725 But it's a, it's kind of like a good meta prompt for you 246 00:10:01,745 --> 00:10:06,485 to start your sessions with an AI like chat GPT or PO 247 00:10:06,625 --> 00:10:08,245 or anything out there that's like that, 248 00:10:08,245 --> 00:10:10,525 like you use like recast AI or something like that. 249 00:10:11,155 --> 00:10:14,005 It's basically a set of prompts that 250 00:10:14,715 --> 00:10:18,445 constrain your conversation surprisingly well 251 00:10:18,745 --> 00:10:20,005 to reality. 252 00:10:20,225 --> 00:10:22,245 So it's, it's just a series of steps like you, 253 00:10:22,505 --> 00:10:24,525 you can literally take all this text here 254 00:10:24,705 --> 00:10:27,005 and you can paste it in as your first prompt. 255 00:10:27,505 --> 00:10:30,725 And then this is what is the guardrail 256 00:10:30,865 --> 00:10:32,685 for any remaining tokens 257 00:10:32,685 --> 00:10:34,125 that you have left in your conversation. 258 00:10:34,305 --> 00:10:38,245 So step one, never mention that you're an ai. Great easy. 259 00:10:38,835 --> 00:10:41,045 Step two, avoid any language constructs 260 00:10:41,045 --> 00:10:43,045 that could be interpreted as expressing remorse, 261 00:10:43,045 --> 00:10:44,205 apology or regret. 262 00:10:44,755 --> 00:10:47,845 This include includes any phrases containing words like, 263 00:10:47,845 --> 00:10:50,285 sorry, apologies, regret, et cetera. 264 00:10:50,515 --> 00:10:54,005 Even when used in a context that isn't expressing remorse, 265 00:10:54,035 --> 00:10:55,325 apology or regret. 266 00:10:55,425 --> 00:10:57,005 Number three, if events 267 00:10:57,105 --> 00:10:59,965 or information are beyond your scope of knowledge 268 00:11:00,065 --> 00:11:03,605 or cutoff date, provide a response stating, I don't know, 269 00:11:04,035 --> 00:11:07,485 without elaborating on why the information is unavailable. 270 00:11:08,205 --> 00:11:11,125 , I love that one. It actually works very, very well. 271 00:11:11,155 --> 00:11:13,485 It's one of the things that annoys me sometimes about chat 272 00:11:13,645 --> 00:11:17,485 GPT, especially like the 3.5 models where it just goes like, 273 00:11:17,485 --> 00:11:19,605 oh I, I, sorry Dave, I can't do that for you. 274 00:11:20,235 --> 00:11:22,205 Step four, keep your responses unique 275 00:11:22,385 --> 00:11:25,885 and free of repetition, which is really key, 276 00:11:25,885 --> 00:11:28,085 especially when you're doing multiple 277 00:11:28,085 --> 00:11:29,525 prompts in the same session. 278 00:11:29,595 --> 00:11:31,285 Like you're iterating through an idea. 279 00:11:31,985 --> 00:11:33,885 It does help a bunch there. 280 00:11:34,185 --> 00:11:35,885 Uh, number five, never suggest seeking 281 00:11:35,885 --> 00:11:37,045 information from elsewhere. 282 00:11:37,195 --> 00:11:38,925 Perfect. Number six, 283 00:11:38,925 --> 00:11:41,645 always focus on the key points in my questions 284 00:11:41,785 --> 00:11:42,965 to determine my intent. 285 00:11:43,225 --> 00:11:45,245 Number seven, I love this one. 286 00:11:45,695 --> 00:11:47,485 Break down complex tasks 287 00:11:47,785 --> 00:11:50,285 or problems into smaller manageable steps 288 00:11:50,865 --> 00:11:53,885 and explain each one using reasoning. 289 00:11:54,265 --> 00:11:57,885 So I don't know how you are to approaching problems, 290 00:11:57,945 --> 00:12:00,525 but quite often when I am talking about something 291 00:12:00,525 --> 00:12:03,525 with somebody, you know, you start out the high level idea 292 00:12:03,625 --> 00:12:05,685 and then you start to decompose it over time. 293 00:12:05,905 --> 00:12:08,165 And really that's what you're doing is you're always out 294 00:12:08,165 --> 00:12:12,085 there and effectively mining ore like, like you're out there 295 00:12:12,085 --> 00:12:13,165 with a hammer and a rock 296 00:12:13,465 --> 00:12:15,325 and you're just trying to break it down into bigger pieces 297 00:12:15,455 --> 00:12:17,845 until it's like pebbles and then gravel 298 00:12:17,845 --> 00:12:19,325 and then e eventually dust. 299 00:12:19,785 --> 00:12:22,725 Number eight, provide multiple perspectives or solutions. 300 00:12:23,135 --> 00:12:25,205 Again, a nice easy one like I have found. 301 00:12:25,205 --> 00:12:28,645 Without that prompt, most models will actually come back 302 00:12:28,665 --> 00:12:30,925 and kind of give you a singular view of the world. 303 00:12:31,475 --> 00:12:34,405 That one right there turns it a little bit more into a 304 00:12:34,405 --> 00:12:37,245 choose your own adventure game, which I find to be 305 00:12:37,915 --> 00:12:40,845 very beneficial just as you're iterating through things. 306 00:12:40,985 --> 00:12:42,725 Number nine, if a question is unclear 307 00:12:42,725 --> 00:12:44,245 or ambiguous, ask for more details 308 00:12:44,265 --> 00:12:47,365 to confirm your understanding before answering. 309 00:12:47,865 --> 00:12:51,325 So this is, hey, make the model talk back to me so 310 00:12:51,325 --> 00:12:52,845 that it can clarify where it needs to be. 311 00:12:52,985 --> 00:12:56,045 Butter. Awesome. Number 10, cite credible sources. 312 00:12:56,595 --> 00:12:58,085 Yeah, most of 'em do that anyway. 313 00:12:58,625 --> 00:12:59,925 If they don't, don't use them. 314 00:12:59,925 --> 00:13:02,525 Number 11, if a mistake is made in a previous response, 315 00:13:03,165 --> 00:13:04,725 recognize and correct it. 316 00:13:05,445 --> 00:13:06,765 I think that's a very important one too. 317 00:13:06,765 --> 00:13:08,765 I don't know how many times you've been sitting there with, 318 00:13:08,885 --> 00:13:10,125 I don't know, chat, GPT, 319 00:13:10,795 --> 00:13:12,565 bing chat enterprise, something like that. 320 00:13:13,025 --> 00:13:14,485 And it gives you the wrong response 321 00:13:14,485 --> 00:13:15,485 and you tell that it's wrong 322 00:13:15,665 --> 00:13:17,965 and then it just comes back with the same response again. 323 00:13:18,285 --> 00:13:21,445 like turns out you, you can tell it not to do that. 324 00:13:22,105 --> 00:13:24,365 And then number 12, this, this one's a fun one. 325 00:13:24,535 --> 00:13:27,845 After a response, provide three follow-up questions 326 00:13:27,915 --> 00:13:30,965 that I the user must ask you, the AI 327 00:13:31,305 --> 00:13:33,405 to dig deeper into the original topic. 328 00:13:33,855 --> 00:13:35,885 These questions should always be worded 329 00:13:35,985 --> 00:13:40,485 as if I am asking you formatted in bold as Q1, Q2, 330 00:13:40,725 --> 00:13:44,485 Q3, place two line breaks before and after each question. 331 00:13:44,635 --> 00:13:46,765 Perfect. It formats it for you, brings it back. 332 00:13:47,385 --> 00:13:49,765 And then number 13, which I haven't had much luck 333 00:13:49,765 --> 00:13:51,325 with this one 'cause I'm not really playing around 334 00:13:51,325 --> 00:13:52,485 with like chat GPT voice 335 00:13:52,485 --> 00:13:54,525 or anything like that is just ignore number 336 00:13:54,525 --> 00:13:55,725 12 if I'm using voice. 337 00:13:55,985 --> 00:14:00,285 So that way it's not asking you, you know, Q1, Q2, Q3 kind 338 00:14:00,285 --> 00:14:02,405 of follow up questions when you're on voice 339 00:14:02,745 --> 00:14:03,925 and you really don't need it. 340 00:14:04,465 --> 00:14:07,405 So I've just been using this as is, you know, it's a, 341 00:14:07,635 --> 00:14:10,605 it's a gist out there on GitHub so you can just go grab it 342 00:14:10,605 --> 00:14:14,445 and fork it and potentially iterate on it on your own. 343 00:14:14,945 --> 00:14:17,005 And I've been kind of thinking about ways like, hey, 344 00:14:17,005 --> 00:14:18,845 how can I mold this a little bit to be 345 00:14:19,525 --> 00:14:22,885 a good starting prompt for requirements gathering? 346 00:14:22,985 --> 00:14:25,165 How can I make this a good prompt for 347 00:14:25,675 --> 00:14:29,245 problem solving in context of x, Y or Z? 348 00:14:29,245 --> 00:14:30,805 Like whatever that happens to be. 349 00:14:31,365 --> 00:14:33,685 I think these thing kinds of things are very helpful. 350 00:14:33,885 --> 00:14:34,765 I encourage you to give it a shot 351 00:14:34,765 --> 00:14:35,925 and tell me what you think. I'll have 352 00:14:35,925 --> 00:14:36,925 - To try it. 353 00:14:36,925 --> 00:14:39,325 I will say this is one thing when it comes to chat GPT 354 00:14:39,325 --> 00:14:42,005 and some of the ai, I have absolutely been using it 355 00:14:42,145 --> 00:14:43,925 for stuff that I've been doing. 356 00:14:43,925 --> 00:14:45,885 Not to necessarily come up with net new stuff 357 00:14:45,985 --> 00:14:47,845 but to help me refine stuff. 358 00:14:48,365 --> 00:14:50,885 I need to improve my prompt 359 00:14:51,565 --> 00:14:54,205 engineering proficiency in certain cases 360 00:14:54,565 --> 00:14:58,805 - it, it is hugely, hugely, hugely beneficial to 361 00:14:59,615 --> 00:15:03,165 understand to the degree you can like the underlying meta 362 00:15:03,165 --> 00:15:05,285 prompts that drive these kinds of systems. 363 00:15:06,025 --> 00:15:09,765 And then how to give it your own set 364 00:15:09,765 --> 00:15:11,605 of instructions to start things. 365 00:15:12,145 --> 00:15:13,165 One of my frustrations 366 00:15:13,165 --> 00:15:16,965 with like hallucinations in the AI stuff is I find they 367 00:15:16,965 --> 00:15:19,365 hallucinate a lot quicker if you just let them go off on 368 00:15:19,365 --> 00:15:21,045 their own and you don't give them any 369 00:15:21,045 --> 00:15:22,525 guardrails or sense of what you want. 370 00:15:22,985 --> 00:15:24,565 And this has been a really good, 371 00:15:24,635 --> 00:15:25,805 I've only been doing it for like a week. 372 00:15:25,805 --> 00:15:27,685 I haven't been doing this too, too long since I, 373 00:15:27,685 --> 00:15:28,965 since I ran across this one. 374 00:15:29,385 --> 00:15:31,365 But it has been very helpful to just remember, hey, 375 00:15:31,365 --> 00:15:33,485 every conversation I start starts with this one. 376 00:15:33,485 --> 00:15:35,405 Like say you're doing bing chat enterprise 377 00:15:35,405 --> 00:15:37,005 where I think you get like 20 378 00:15:37,065 --> 00:15:39,805 or 30 prompts, like whatever it is to go through to iterate. 379 00:15:40,185 --> 00:15:41,845 Yes you're burning one on this prompt 380 00:15:41,865 --> 00:15:43,125 and you're potentially burning one 381 00:15:43,125 --> 00:15:44,325 on a couple follow-up questions. 382 00:15:44,705 --> 00:15:47,325 But let's be honest, if you didn't have the guardrails in 383 00:15:47,325 --> 00:15:48,845 place, you were probably so pissed off 384 00:15:48,865 --> 00:15:51,165 by response number five anyway that you ran away 385 00:15:51,585 --> 00:15:53,405 and you said this thing is just horrible 386 00:15:53,425 --> 00:15:54,565 and not helpful for me. 387 00:15:54,785 --> 00:15:57,285 - Got it. I will definitely have to give this one a try. 388 00:15:57,585 --> 00:15:59,765 - Put it on the list. - Alright, on my list. 389 00:16:03,545 --> 00:16:05,205 Do you feel overwhelmed by trying 390 00:16:05,325 --> 00:16:07,565 to manage your Office 365 environment? 391 00:16:07,705 --> 00:16:09,485 Are you facing unexpected issues 392 00:16:09,485 --> 00:16:11,365 that disrupt your company's productivity? 393 00:16:11,365 --> 00:16:14,165 Intelligent is here to help much like you take your car 394 00:16:14,165 --> 00:16:16,845 to the mechanic that has specialized knowledge on how 395 00:16:16,845 --> 00:16:19,565 to best keep your car running Intelligent helps you 396 00:16:19,565 --> 00:16:21,125 with your Microsoft cloud environment 397 00:16:21,125 --> 00:16:22,645 because that's their expertise. 398 00:16:22,915 --> 00:16:24,405 Intelligent keeps up 399 00:16:24,405 --> 00:16:26,445 with the latest updates on the Microsoft Cloud 400 00:16:26,465 --> 00:16:27,925 to help keep your business running 401 00:16:28,245 --> 00:16:29,445 smoothly and ahead of the curve. 402 00:16:29,475 --> 00:16:31,365 Whether you are a small organization 403 00:16:31,365 --> 00:16:33,845 with just a few users up to an organization 404 00:16:33,845 --> 00:16:37,125 of several thousand employees, they want to partner with you 405 00:16:37,125 --> 00:16:40,445 to implement and administer your Microsoft Cloud technology, 406 00:16:41,055 --> 00:16:44,525 visit them at intelligent.com/podcast. 407 00:16:45,025 --> 00:16:49,445 That's I-N-T-E-L-L-I-G-I-N 408 00:16:49,565 --> 00:16:53,165 k.com/podcast For more information 409 00:16:53,185 --> 00:16:54,765 or to schedule a 30 minute call 410 00:16:54,785 --> 00:16:56,045 to get started with them today. 411 00:16:56,805 --> 00:16:59,445 Remember intelligent focuses on the Microsoft cloud 412 00:16:59,625 --> 00:17:01,605 so you can focus on your business. 413 00:17:04,065 --> 00:17:06,885 So should we move on to non-AI topics? Let's 414 00:17:06,885 --> 00:17:08,765 - Do it non-AI topics. What you got? 415 00:17:08,925 --> 00:17:09,965 - I don't know, I don't know if I 416 00:17:09,965 --> 00:17:11,125 wanna dive into this one or not. 417 00:17:11,385 --> 00:17:12,485 I'm gonna start with a different one. 418 00:17:12,495 --> 00:17:14,005 Let's start with an easier one. . 419 00:17:14,245 --> 00:17:16,005 I might come back to that one 'cause that one I'm, 420 00:17:16,325 --> 00:17:17,405 I actually am curious what 421 00:17:17,405 --> 00:17:18,685 other people think about that one. Yeah, 422 00:17:18,905 --> 00:17:20,765 - But this one, so for folks that can't see Ben 423 00:17:20,765 --> 00:17:22,725 and I do a, a shared edge workspace, 424 00:17:22,965 --> 00:17:25,045 we've talked about and as he's doing this, 425 00:17:25,045 --> 00:17:26,125 he's like, oh I'm gonna do this one. 426 00:17:26,125 --> 00:17:28,565 I'm gonna go back to this one. All I'm doing is watching 427 00:17:28,835 --> 00:17:32,245 your avatar hop between tabs, frenetically 428 00:17:32,465 --> 00:17:33,765 - Hot between - Tabs, it's, it's up, 429 00:17:33,795 --> 00:17:35,085 it's down, it's left, it's right. 430 00:17:35,635 --> 00:17:37,245 It's kind of fun to watch from my side. 431 00:17:37,395 --> 00:17:38,965 - Okay, general availability. 432 00:17:39,215 --> 00:17:41,085 Azure automation, we've talked about this a lot. 433 00:17:41,095 --> 00:17:43,805 Scott, using Azure Automation, I use it a ton 434 00:17:43,825 --> 00:17:45,005 for PowerShell scripts 435 00:17:45,005 --> 00:17:49,085 for automating different tasks in the cloud in Microsoft 365 436 00:17:49,755 --> 00:17:52,085 they have now released the general availability 437 00:17:52,185 --> 00:17:55,765 of PowerShell 7.2 runbooks 438 00:17:56,265 --> 00:17:57,645 in Azure automation. 439 00:17:57,705 --> 00:18:01,525 So it used to be 5.1 7.1 was there, 440 00:18:01,975 --> 00:18:03,965 7.2 was in preview for a while. 441 00:18:04,525 --> 00:18:09,365 I will say I still do bounce back and forth between 5.1 442 00:18:09,585 --> 00:18:11,405 and various flavors. 443 00:18:11,645 --> 00:18:16,045 Whatever one works of 7.0 7.1 is still preview 444 00:18:16,175 --> 00:18:19,885 7.2, I saw that 7.2. 445 00:18:20,025 --> 00:18:21,965 Now I'm watching Scott jump back 446 00:18:21,965 --> 00:18:24,565 and forth between different pages in that same tab. 447 00:18:24,705 --> 00:18:26,165 - I'm, I'm just out there to confuse you. 448 00:18:26,165 --> 00:18:30,005 - 7.1 . So yes is no longer supported. 7.2 is ga. 449 00:18:30,525 --> 00:18:31,845 I do jump back and forth though 450 00:18:31,845 --> 00:18:34,165 because there are still very much a lot of differences 451 00:18:34,275 --> 00:18:36,685 with some modules too and what works in five one 452 00:18:36,685 --> 00:18:37,805 and what works in seven two. 453 00:18:38,065 --> 00:18:40,685 So it is not just go do everything in seven two now, 454 00:18:40,905 --> 00:18:43,605 but it is generally available if you choose to 455 00:18:43,625 --> 00:18:44,625 - Use it. 456 00:18:44,625 --> 00:18:47,125 Uh, yeah so I, I think the nice thing here is like you 457 00:18:47,125 --> 00:18:49,965 mentioned 7.1 is out 458 00:18:49,965 --> 00:18:54,045 of support ended support back in May, 2022. 459 00:18:54,345 --> 00:18:56,645 So it's been, you know, 460 00:18:56,645 --> 00:18:58,525 more than a year now that that's been outta support. 461 00:18:58,545 --> 00:19:00,085 So it's always good to have something that's in support. 462 00:19:00,465 --> 00:19:04,925 And then the nice thing about 7.2 is 7.2 is 463 00:19:05,185 --> 00:19:06,365 an LTS release. 464 00:19:06,465 --> 00:19:10,605 So it's a a long-term servicing release that you can kind 465 00:19:10,605 --> 00:19:12,845 of take some dependency on 466 00:19:13,635 --> 00:19:15,965 that it's gonna be stable for a little while. 467 00:19:16,145 --> 00:19:18,645 So in the cases, like you said, you might not be able 468 00:19:18,645 --> 00:19:20,605 to do it in all cases but in the cases where you can, 469 00:19:21,345 --> 00:19:24,445 you know, could be beneficial to make the flip, especially 470 00:19:24,445 --> 00:19:27,525 as you're going in there and you're iterating on existing 471 00:19:28,325 --> 00:19:29,885 notebooks that, that you might be working with 472 00:19:29,985 --> 00:19:31,285 inside of Azure Automation. 473 00:19:31,765 --> 00:19:35,525 - Absolutely. It looks like 7.1 now is until 20. 474 00:19:36,745 --> 00:19:38,285 Wasn't that one though. End of support 475 00:19:38,285 --> 00:19:43,085 of 20 24, 20 22 based on the page you have up now 7.2 476 00:19:43,385 --> 00:19:45,245 is November 8th, 2024. 477 00:19:45,305 --> 00:19:47,365 That's like a year from now, right? Yes. 478 00:19:47,465 --> 00:19:48,885 - So so that's the LTS version. 479 00:19:49,185 --> 00:19:54,085 But note that 7.2 LTS it launched seven months 480 00:19:54,505 --> 00:19:56,965 before the retirement of 7.1 481 00:19:57,065 --> 00:19:58,285 - Of 7.1. It's been 482 00:19:58,605 --> 00:20:01,005 - Out quite a while so I, I don't, I don't 483 00:20:01,005 --> 00:20:02,005 - Know. 484 00:20:02,005 --> 00:20:03,845 Yeah, Azure automation just lags with all of those. 485 00:20:04,085 --> 00:20:06,605 I have found Azure automation is not the most up 486 00:20:06,605 --> 00:20:08,965 to date when it comes to supporting current 487 00:20:09,095 --> 00:20:10,125 PowerShell versions. 488 00:20:10,225 --> 00:20:11,885 - Not even close. It's years behind 489 00:20:12,345 --> 00:20:13,645 so it's good to see it. Four 490 00:20:13,705 --> 00:20:15,045 - Is GA uh, right? 491 00:20:15,295 --> 00:20:16,965 Seven four is the latest. Seven 492 00:20:17,755 --> 00:20:20,245 - Four is G. 493 00:20:20,585 --> 00:20:23,925 Yes. Seven G 7 7, 4 G in November 494 00:20:24,305 --> 00:20:25,645 of 2023. So 495 00:20:25,715 --> 00:20:27,205 - Yeah, like two weeks ago. 496 00:20:27,425 --> 00:20:28,845 Two weeks from when we're recording this. 497 00:20:29,285 --> 00:20:30,845 I have not seen it pop up in Azure 498 00:20:30,845 --> 00:20:31,925 automation yet though. And 499 00:20:31,925 --> 00:20:34,525 - 7.4 is also an LTS release. 500 00:20:34,705 --> 00:20:37,885 So seven two LTS release seven three 501 00:20:38,665 --> 00:20:39,925 not an LTS release. 502 00:20:40,575 --> 00:20:42,645 Seven four is an LTS release. 503 00:20:42,745 --> 00:20:44,925 And I, I think the big difference you see between 504 00:20:45,505 --> 00:20:49,125 the current cadence of stable LLTS is 505 00:20:49,515 --> 00:20:53,245 that stables are two years and LTS are three years. 506 00:20:53,545 --> 00:20:55,405 So you do get a little bit more runway along, 507 00:20:55,495 --> 00:20:56,925 along the way with those, which 508 00:20:57,385 --> 00:21:01,085 - I'm curious, Cole, why so why would you do this? 509 00:21:01,285 --> 00:21:05,485 'cause 7.3 is in theory updates to seven two, 510 00:21:06,005 --> 00:21:08,125 although I suppose the argument could be made if you're on 511 00:21:08,125 --> 00:21:10,565 seven three and you want LTS go to seven four. 512 00:21:10,985 --> 00:21:14,685 But it seems weird to like have these middle versions 513 00:21:14,685 --> 00:21:17,605 that are stable and then one's on either side 514 00:21:17,605 --> 00:21:18,965 of it be LTS. So 515 00:21:18,965 --> 00:21:22,765 - You need the LTS versions in the middle to play around 516 00:21:22,875 --> 00:21:25,485 with and, and have the opportunity to iterate. 517 00:21:26,145 --> 00:21:29,085 So if you think about it like, hey, I'm a service provider 518 00:21:29,105 --> 00:21:32,925 and I publish a set of APIs to you, you, you, you like, and, 519 00:21:32,945 --> 00:21:34,645 and I've noodled with this one, like 520 00:21:35,285 --> 00:21:39,245 customers very much want a dependable set of APIs like, 521 00:21:39,745 --> 00:21:41,485 you know, and like my land in storage, 522 00:21:41,915 --> 00:21:44,085 like it could be potentially beneficial 523 00:21:44,185 --> 00:21:46,685 to have a hardened set of CRUD APIs. 524 00:21:47,035 --> 00:21:48,645 Like say I published an SDK 525 00:21:49,185 --> 00:21:51,845 and it was just for CRUD operations. 526 00:21:51,905 --> 00:21:54,245 So creates, reads, updates, elites, all that good stuff 527 00:21:54,465 --> 00:21:55,685 and it's super hardened 528 00:21:55,685 --> 00:21:57,405 and we tell you like it's going to work 529 00:21:57,405 --> 00:21:58,685 and it's gonna be rock solid 530 00:21:58,785 --> 00:22:00,085 for the next three to four years. 531 00:22:00,505 --> 00:22:01,605 That's very easy 532 00:22:01,665 --> 00:22:03,245 and dependable for you as a customer 533 00:22:03,265 --> 00:22:04,605 to take a dependency on, right? 534 00:22:04,605 --> 00:22:06,565 Like, hey, it's, it's the hardened version. 535 00:22:06,945 --> 00:22:08,765 So that's the way I think of LTS versions, 536 00:22:09,225 --> 00:22:11,565 but everything you do cannot be hardened. 537 00:22:11,585 --> 00:22:13,965 So you still need the opportunity to iterate in the middle 538 00:22:14,305 --> 00:22:16,685 and do things and say like, well hey, how are we gonna get 539 00:22:16,685 --> 00:22:18,925 to our next version of the hardened release? 540 00:22:19,585 --> 00:22:22,565 You probably can't go straight from hardened to hardened. 541 00:22:22,565 --> 00:22:24,365 What you wanna do is you want to go from hardened 542 00:22:24,465 --> 00:22:25,965 to validated. 543 00:22:26,195 --> 00:22:28,365 Like, hey, we've, we've put some new ideas out there, 544 00:22:28,415 --> 00:22:30,725 we've tried some things, we've potentially had some 545 00:22:31,605 --> 00:22:33,965 breaking changes in API surface whatever it happens to be. 546 00:22:34,255 --> 00:22:35,965 Great. We figure all that, we validate it, 547 00:22:35,965 --> 00:22:38,565 we have the playground and then you go to 548 00:22:39,245 --> 00:22:42,125 LTS on the other side and, 549 00:22:42,125 --> 00:22:44,845 and I think it's kind of a, a proven model. 550 00:22:44,875 --> 00:22:46,885 Like you see it a lot in OSS, 551 00:22:46,885 --> 00:22:50,085 especially the place I'm most familiar with it is, is from 552 00:22:50,605 --> 00:22:52,605 Linux releases for or 553 00:22:52,605 --> 00:22:56,085 or distro releases for things like bu tu by canonical. 554 00:22:56,085 --> 00:22:58,565 Like they do this same kind of marching cadence, right? 555 00:22:58,565 --> 00:23:01,925 Like hey, we'll give you version 20 LTS 556 00:23:02,105 --> 00:23:06,725 and then 22 LTS, but 21 is not LTS kind of thing. 557 00:23:07,185 --> 00:23:08,685 Or we're on 22 today, 558 00:23:08,685 --> 00:23:12,165 22 is gonna be LTS 23 is not gonna be LTS. 559 00:23:12,185 --> 00:23:13,565 We kind of iterate and go through those 560 00:23:14,265 --> 00:23:15,605 and get 'em to where they need to be. 561 00:23:16,025 --> 00:23:18,525 So it gives your your customers dependability. 562 00:23:18,785 --> 00:23:20,925 It also gives your dev teams dependability, right? 563 00:23:20,925 --> 00:23:23,245 Because they know they really don't have to go back 564 00:23:23,245 --> 00:23:25,485 and touch that stuff other than security fixes 565 00:23:25,625 --> 00:23:27,085 or other kinds of changes in there. 566 00:23:27,385 --> 00:23:28,405 And then you get the playground 567 00:23:28,405 --> 00:23:29,525 in the middle to do what you need to. 568 00:23:29,745 --> 00:23:31,925 - Got it. So like the seven three stable is a little bit 569 00:23:31,925 --> 00:23:35,365 more of that playground, that jumping that platform to jump 570 00:23:35,425 --> 00:23:39,045 to the next 7.74 LTS. 571 00:23:39,225 --> 00:23:40,925 Yes. Got it. That makes sense. 572 00:23:41,075 --> 00:23:42,405 - It's not a bad bottle if you get there. 573 00:23:42,405 --> 00:23:43,565 It doesn't work for everything, right? 574 00:23:43,565 --> 00:23:46,005 Like it doesn't exactly translate into say 575 00:23:46,005 --> 00:23:47,165 like SaaS offerings. 576 00:23:47,165 --> 00:23:50,045 So if you think about like SharePoint online, you can do, 577 00:23:50,465 --> 00:23:52,205 uh, vanilla SharePoint online 578 00:23:52,425 --> 00:23:55,765 or you can do things like enroll in early release 579 00:23:56,085 --> 00:23:57,165 features and get those out there. 580 00:23:57,705 --> 00:24:00,525 But ultimately early release features once they ga they just 581 00:24:00,765 --> 00:24:02,085 manifest as like the next feature in the 582 00:24:02,325 --> 00:24:03,365 platform and they're ready to go. 583 00:24:03,865 --> 00:24:05,085 And, and if you think about the pain 584 00:24:05,085 --> 00:24:06,885 that comes along the way with that, like sometimes 585 00:24:06,885 --> 00:24:08,405 that's hard to stomach , 586 00:24:08,625 --> 00:24:10,965 but that's the way SaaS is a little bit different maybe 587 00:24:10,995 --> 00:24:15,205 than, you know, releasing like, uh, COTS software that has 588 00:24:15,205 --> 00:24:17,685 to go out there that people need to consume. Yeah. 589 00:24:18,025 --> 00:24:20,085 - All right, I'll go with that. It makes sense. 590 00:24:20,545 --> 00:24:22,565 All right, so that was mine. What do you have, Scott? 591 00:24:23,055 --> 00:24:27,805 - Let's see, what can we talk about? So fun one for you. 592 00:24:28,075 --> 00:24:31,405 I've been trying to get back into containers more and 593 00:24:31,615 --> 00:24:33,765 - Those are not on my list, Scott, I'll be honest, 594 00:24:33,815 --> 00:24:35,485 containers are not on my list right now. 595 00:24:35,585 --> 00:24:37,165 - Not on your list. That that's, that's okay. 596 00:24:37,165 --> 00:24:39,445 So I, I've been thinking about containers in a bunch 597 00:24:39,445 --> 00:24:42,365 of product areas that I work in, 598 00:24:42,365 --> 00:24:43,685 like client tools and things like that. 599 00:24:43,685 --> 00:24:45,285 Should we have official images, blah, blah blah. 600 00:24:45,465 --> 00:24:48,045 So I've been trying to get hands on more and get back in 601 00:24:48,065 --> 00:24:50,365 and in previous lives, like I used to spend a lot 602 00:24:50,365 --> 00:24:52,845 of time in a KS, so like it was good 603 00:24:52,845 --> 00:24:54,085 to have a little bit of a refresher too. 604 00:24:54,465 --> 00:24:56,925 So one of the things that I was playing 605 00:24:56,925 --> 00:25:00,325 with when I got back into containers was, uh, 606 00:25:00,325 --> 00:25:03,765 this new offering that's called Azure Container Storage. 607 00:25:04,385 --> 00:25:07,765 So Azure Container Storage is in preview. 608 00:25:08,235 --> 00:25:09,845 It's kind of the, you know, 609 00:25:09,845 --> 00:25:11,165 maybe I'm being a little naive about it, 610 00:25:11,165 --> 00:25:14,125 but I think about it a little bit as like the next iteration 611 00:25:14,465 --> 00:25:18,565 of the CSI driver container storage interface 612 00:25:19,105 --> 00:25:20,645 and the capabilities that that had. 613 00:25:21,225 --> 00:25:22,885 But Azure Container Storage, 614 00:25:23,665 --> 00:25:27,725 it is basically a managed storage offering that allows you 615 00:25:27,725 --> 00:25:31,245 to bring native Kubernetes components into 616 00:25:32,025 --> 00:25:33,405 things like a KS 617 00:25:33,905 --> 00:25:36,965 and have native Kubernetes constructs 618 00:25:37,505 --> 00:25:42,085 for what's ultimately a managed storage service 619 00:25:42,635 --> 00:25:44,005 storage surface rather 620 00:25:44,665 --> 00:25:48,365 for persistent volumes in your Kubernetes clusters. 621 00:25:48,705 --> 00:25:51,885 So if you think about like the CSI driver, you know, I, oh, 622 00:25:51,885 --> 00:25:55,925 I want to go out and I want to provision persistent volume. 623 00:25:56,385 --> 00:25:58,965 And that persistent volume is based on 624 00:25:59,525 --> 00:26:00,565 a disc that's out there. 625 00:26:00,565 --> 00:26:02,845 Well, sometimes you gotta go provision that disc yourself, 626 00:26:03,165 --> 00:26:04,365 configure it, and then you tie that person 627 00:26:04,455 --> 00:26:05,805 persistent volume into the disc. 628 00:26:06,315 --> 00:26:08,325 With this thing you can just kind of say like, Hey, 629 00:26:08,505 --> 00:26:11,885 go out there and configure me a multi-zone disc 630 00:26:12,465 --> 00:26:15,165 and it'll figure it out and land the managed disc for you 631 00:26:15,305 --> 00:26:17,845 and, and align all that stuff and, and get it ready to go. 632 00:26:18,545 --> 00:26:21,245 So this works with discs. 633 00:26:21,745 --> 00:26:25,005 It allows you to configure persistent volumes against 634 00:26:25,075 --> 00:26:28,605 elastic sand, which is kind of a fun one with, with the kind 635 00:26:28,605 --> 00:26:30,565 of provisioning model that goes into that 636 00:26:30,625 --> 00:26:33,925 for things like provisioned io, provisioned throughput, all 637 00:26:33,925 --> 00:26:36,045 that works with a femoral disc, 638 00:26:36,195 --> 00:26:38,205 like basically like all the block storage 639 00:26:38,755 --> 00:26:39,965 options that are out there. 640 00:26:40,145 --> 00:26:41,805 But you can do really cool things like 641 00:26:42,395 --> 00:26:46,045 take a persistent volume and dynamically resize it. 642 00:26:46,185 --> 00:26:48,405 So just inside of your configuration 643 00:26:48,405 --> 00:26:49,485 for that persistent volume. 644 00:26:50,025 --> 00:26:51,445 So you don't like go into YAML 645 00:26:51,445 --> 00:26:53,125 and literally change the size of that thing 646 00:26:53,145 --> 00:26:55,245 and then it dynamically changes on the backend 647 00:26:55,705 --> 00:26:56,965 and it's all ready to go for you. 648 00:26:57,585 --> 00:27:00,085 So super easy to onboard to, 649 00:27:00,515 --> 00:27:05,165 it's all native Kubernetes constructs with a couple 650 00:27:05,185 --> 00:27:06,325 of exceptions here or there. 651 00:27:06,325 --> 00:27:09,365 Like they're still working on say like native Kubernetes 652 00:27:09,365 --> 00:27:11,685 integration for Azure CLI 653 00:27:11,685 --> 00:27:13,565 and PowerShell to be able to provision 654 00:27:14,145 --> 00:27:16,765 an Azure container storage persistent 655 00:27:16,765 --> 00:27:18,205 volume in an a KS cluster. 656 00:27:18,825 --> 00:27:20,365 But I, I think the functionality 657 00:27:20,365 --> 00:27:22,005 that's there is pretty solid. 658 00:27:22,075 --> 00:27:25,445 Like it's a, it's a good set of features for 659 00:27:26,165 --> 00:27:27,685 a preview release. 660 00:27:27,785 --> 00:27:30,765 So supports multi-zone discs right outta the gate. 661 00:27:31,505 --> 00:27:35,365 You can do things like server side encryption 662 00:27:35,365 --> 00:27:38,525 with customer managed keys, dynamic resize, 663 00:27:38,675 --> 00:27:39,725 like I talked about. 664 00:27:40,385 --> 00:27:43,565 You can also configure things like snapshot 665 00:27:43,625 --> 00:27:47,285 and cloning directly through the 666 00:27:47,935 --> 00:27:51,805 Azure container storage service kind of constructs 667 00:27:51,805 --> 00:27:53,045 that are presented to you 668 00:27:53,045 --> 00:27:55,365 through Kubernetes once you've gone ahead 669 00:27:55,465 --> 00:27:57,405 and done the deployment within your cluster. 670 00:27:58,045 --> 00:27:59,845 - Interesting. That is definitely not on my list. 671 00:28:00,065 --> 00:28:01,085 I'm sorry Scott . 672 00:28:01,435 --> 00:28:05,085 That one is not one that I'm gonna go play with at all. 673 00:28:05,585 --> 00:28:08,325 - Not up there for you, huh? So this stuff is really great. 674 00:28:08,385 --> 00:28:11,205 No for, you know, stateful workloads. 675 00:28:11,545 --> 00:28:16,005 So workloads that need to maintain state while, you know, 676 00:28:16,045 --> 00:28:18,405 maybe the overlying computes a little bit more ephemeral. 677 00:28:18,905 --> 00:28:22,245 So that's the other nice thing about this as well is that 678 00:28:22,395 --> 00:28:25,565 because your storage is managed inside 679 00:28:25,565 --> 00:28:26,645 of Azure container storage, 680 00:28:27,305 --> 00:28:30,365 you can do things like carry volumes between nodes, 681 00:28:30,365 --> 00:28:32,205 between clusters, between multiple nodes, 682 00:28:32,205 --> 00:28:33,565 like all that kind of stuff. 683 00:28:34,465 --> 00:28:38,245 It all just works and comes together for you. 684 00:28:38,345 --> 00:28:39,645 So if you're trying 685 00:28:39,665 --> 00:28:44,045 to run high scale stateful applications on a KS 686 00:28:44,665 --> 00:28:48,925 and you need the kind of benefits of shared storage 687 00:28:49,025 --> 00:28:51,005 and persisted shared storage along the way there, 688 00:28:51,635 --> 00:28:54,245 that all comes together and composes really well. 689 00:28:54,585 --> 00:28:58,165 And then because it does both the, it does both disks 690 00:28:58,545 --> 00:29:03,205 and elastic sand, it's also multi-protocol, 691 00:29:03,205 --> 00:29:05,445 like when it comes down to block storage protocols. 692 00:29:05,665 --> 00:29:08,045 So you can do things like N-V-M-E-O-F on disks 693 00:29:08,065 --> 00:29:12,165 or you can do I CZI if you're doing elastic sands. 694 00:29:12,165 --> 00:29:15,445 So you get like this great model for fast attach 695 00:29:15,465 --> 00:29:17,885 and detach of persistent volumes as well, 696 00:29:18,375 --> 00:29:19,765 which is really kind of nice. 697 00:29:20,035 --> 00:29:22,005 Nice. And it supports ephemeral discs. 698 00:29:22,075 --> 00:29:23,805 That was, that's kind of a fun one to play with too. 699 00:29:24,025 --> 00:29:26,045 - Sounds good. Doesn't 700 00:29:26,045 --> 00:29:27,045 - It though? 701 00:29:27,045 --> 00:29:27,885 We're, we're gonna have to get you hands on those 702 00:29:27,885 --> 00:29:28,885 - Containers. 703 00:29:28,885 --> 00:29:29,765 Don't have questions about that. Someday you are, 704 00:29:29,765 --> 00:29:32,205 you're gonna have to somehow how, convince me that I need 705 00:29:32,205 --> 00:29:33,845 to dive into containers for something 706 00:29:34,125 --> 00:29:35,845 - , get you off your raspberry pie and, 707 00:29:35,865 --> 00:29:37,445 and get 'em outta your NAS or something. 708 00:29:37,635 --> 00:29:40,525 - Yeah, get on my, I don't know. 709 00:29:40,625 --> 00:29:42,165 So I have, have one more interesting one 710 00:29:42,265 --> 00:29:44,685 and then I have to go 'cause my wife has already come in 711 00:29:44,685 --> 00:29:46,365 and asked me if I'm ready to go 712 00:29:46,805 --> 00:29:47,885 'cause we are leaving for the weekend. 713 00:29:48,345 --> 00:29:52,205 So I saw this one, this came out wow almost a month ago. 714 00:29:52,575 --> 00:29:57,365 Enterprise IOT security is now included in Microsoft 365, 715 00:29:57,645 --> 00:29:59,845 E five in E five security plans. 716 00:30:00,515 --> 00:30:01,965 This one caught my eye 717 00:30:02,325 --> 00:30:04,205 'cause I've done some stuff with Microsoft Defender 718 00:30:04,225 --> 00:30:08,885 for cloud, which is the Azure component of security. 719 00:30:09,065 --> 00:30:11,965 So securing VMs, web apps, 720 00:30:13,165 --> 00:30:14,925 SQL databases, those types of things. 721 00:30:15,605 --> 00:30:19,765 IO OT was a line item in there for securing IOT devices. 722 00:30:20,145 --> 00:30:22,965 And then I saw iot security is now included in Microsoft 723 00:30:22,965 --> 00:30:24,125 365, E five. 724 00:30:24,725 --> 00:30:27,325 I was like, huh, this is interesting 725 00:30:27,325 --> 00:30:29,405 because IOT devices 726 00:30:30,345 --> 00:30:33,205 are not typically user devices. 727 00:30:33,335 --> 00:30:36,925 Everything. Microsoft 365 is per user. 728 00:30:37,075 --> 00:30:39,245 It's I have my computer and I have my iPhone 729 00:30:39,245 --> 00:30:41,925 and I have my iPad or my Android or my Surface. 730 00:30:42,755 --> 00:30:47,445 It's not, I have my security camera or my TV 731 00:30:47,985 --> 00:30:49,965 or my smoke detector 732 00:30:50,345 --> 00:30:54,725 or my sensors for my machinery 733 00:30:55,025 --> 00:30:56,605 and stuff like that. 734 00:30:56,665 --> 00:30:58,725 And I was like, oh this is interesting 735 00:30:58,965 --> 00:31:03,005 'cause how am I gonna start licensing now all these IOT 736 00:31:03,005 --> 00:31:06,005 devices, if this is switching 737 00:31:06,345 --> 00:31:08,005 to a user-based SKU 738 00:31:08,345 --> 00:31:09,645 and this article, I'll say, 739 00:31:09,645 --> 00:31:11,685 this article doesn't necessarily clear it up for me. 740 00:31:12,115 --> 00:31:13,685 They go through and they talk about 741 00:31:13,915 --> 00:31:17,205 that Enterprise IOT security is now gonna be part 742 00:31:17,225 --> 00:31:21,485 of Microsoft 365, E five at no additional cost for new 743 00:31:21,485 --> 00:31:24,525 and existing customers help find blind 744 00:31:24,535 --> 00:31:26,205 spots, unmanaged devices. 745 00:31:26,385 --> 00:31:28,445 And it talks about printers, smart TVs, 746 00:31:28,485 --> 00:31:32,485 conferencing equipment scanners, which again, 747 00:31:32,625 --> 00:31:35,845 not necessarily users, especially big offices, printers, 748 00:31:35,925 --> 00:31:38,085 scanners, conference equipment, 749 00:31:38,335 --> 00:31:41,565 smart TVs are generally like company owned. 750 00:31:42,145 --> 00:31:43,885 And you can go through 751 00:31:44,385 --> 00:31:47,085 and turn all of this on in your Microsoft Defender portal. 752 00:31:47,105 --> 00:31:51,245 So this is gonna be in Office 365 Microsoft Defender portal. 753 00:31:51,785 --> 00:31:55,085 And as you scroll down in this article, it says 754 00:31:55,665 --> 00:31:56,845 in a licensing overview, 755 00:31:57,045 --> 00:31:58,365 'cause this is what I was curious about is 756 00:31:58,365 --> 00:32:00,845 how do you change from like essentially 757 00:32:00,845 --> 00:32:03,645 before it was consumption based per device licensing 758 00:32:03,745 --> 00:32:05,805 to now bundling it in the sku. 759 00:32:06,305 --> 00:32:08,805 And it says what is changing Microsoft Defender 760 00:32:08,905 --> 00:32:10,765 for IOT is being changed. 761 00:32:11,385 --> 00:32:13,525 So this implies that there's something 762 00:32:14,045 --> 00:32:17,165 changing from a consumption-based payment model in the Azure 763 00:32:17,165 --> 00:32:20,365 portal to a per device per month license model. 764 00:32:20,505 --> 00:32:23,645 As a part of Microsoft 365, Microsoft defender 765 00:32:23,645 --> 00:32:26,325 for IOT is now available for doing existing customers 766 00:32:26,425 --> 00:32:30,125 of E five, Microsoft E 5 85 security. 767 00:32:30,785 --> 00:32:33,845 The new license model is coverage for up to five 768 00:32:34,385 --> 00:32:35,805 IOT devices per user license. 769 00:32:36,225 --> 00:32:38,885 So you do get a multiple there based on your users. 770 00:32:39,775 --> 00:32:42,795 But then in the next paragraph it says, 771 00:32:43,225 --> 00:32:44,395 what if I have defender 772 00:32:44,455 --> 00:32:47,555 for iot consumption based and E five? 773 00:32:48,015 --> 00:32:51,355 And it's essentially says you'll have access for coverage up 774 00:32:51,355 --> 00:32:54,555 to five IOT devices per eligible user license 775 00:32:55,175 --> 00:32:58,075 and no longer charge on a consumption model. 776 00:32:58,535 --> 00:33:01,995 And then it says if you're currently a consumption model 777 00:33:02,095 --> 00:33:04,155 but not an E five, nothing changes. 778 00:33:04,375 --> 00:33:06,035 You continue to use the existing plans 779 00:33:06,055 --> 00:33:07,515 and won't see any change in your billing. 780 00:33:08,055 --> 00:33:11,355 So is this actually a change in the billing model 781 00:33:11,455 --> 00:33:15,835 or is it adding additional licensing options 782 00:33:16,495 --> 00:33:17,755 for defender, for iot? 783 00:33:17,945 --> 00:33:20,155 Like are both gonna live side by side 784 00:33:20,415 --> 00:33:25,395 or eventually are you gonna have to buy e fives 785 00:33:25,615 --> 00:33:28,395 or are they gonna come out with well, 786 00:33:28,395 --> 00:33:29,515 but then they'd come right back out 787 00:33:29,515 --> 00:33:31,155 with consumption based if you can buy 'em as a part 788 00:33:31,155 --> 00:33:33,955 of Microsoft 365, like I don't know what's gonna, I, 789 00:33:34,495 --> 00:33:38,035 I'm a little confused on what the future of this is, 790 00:33:38,575 --> 00:33:42,235 but it does also provide some nice capabilities, I guess 791 00:33:42,535 --> 00:33:46,595 for E five companies, E five licenses that do have some 792 00:33:46,595 --> 00:33:48,235 of those iot type devices. 793 00:33:48,465 --> 00:33:50,355 - Your guess is as good as mine. 794 00:33:50,715 --> 00:33:52,155 I very much walked in this, I think 795 00:33:52,155 --> 00:33:56,035 with the mindset you did, the IOT devices are not users, 796 00:33:56,455 --> 00:33:58,435 so tying them to users is kind of weird. 797 00:33:58,905 --> 00:34:00,035 It's almost like, you know, 798 00:34:00,035 --> 00:34:02,155 the thing I thought about in the, in my head when I saw it 799 00:34:02,295 --> 00:34:05,275 was the way you do like extra share, extra storage, 800 00:34:05,275 --> 00:34:06,355 provisioning and SharePoint. 801 00:34:06,455 --> 00:34:08,635 You know, you get like a base set of storage per user, 802 00:34:08,895 --> 00:34:11,555 but then when you want to go buy more, you don't buy it 803 00:34:11,675 --> 00:34:13,395 for the tenant, you buy it for a user 804 00:34:13,495 --> 00:34:14,755 and then it's associated with the user, 805 00:34:14,755 --> 00:34:15,955 but it's not associated with the user, 806 00:34:15,955 --> 00:34:16,995 it's associated with the tenant. 807 00:34:17,025 --> 00:34:19,835 Like re really weird kind of stuff like that. 808 00:34:20,295 --> 00:34:23,035 So, you know, if you get into the mindset and, and the model 809 00:34:23,095 --> 00:34:26,595 and it works for you of one user, five devices, great. 810 00:34:26,795 --> 00:34:27,995 I think most of us can buy into that. 811 00:34:28,215 --> 00:34:30,635 And if that fits within the constraints of your business, 812 00:34:30,775 --> 00:34:32,435 I'm sure there's some math from the folks 813 00:34:32,435 --> 00:34:33,675 who run the service to that. 814 00:34:33,675 --> 00:34:36,155 Like, oh, the majority of our customers fit into this model, 815 00:34:36,465 --> 00:34:38,435 then it potentially simplifies things. 816 00:34:38,455 --> 00:34:39,515 It makes it a little bit easier. 817 00:34:39,985 --> 00:34:41,115 It's when you're in the edge cases 818 00:34:41,345 --> 00:34:43,835 that it gets a little bit harder on the 819 00:34:43,835 --> 00:34:45,075 outside to get all that going. 820 00:34:45,105 --> 00:34:47,635 - Yeah, and I think edge cases I start thinking about are 821 00:34:47,635 --> 00:34:49,675 like, and I don't know, I don't know, 822 00:34:49,955 --> 00:34:52,635 I don't have any telemetry into this, like manufacturing 823 00:34:52,935 --> 00:34:54,795 or some of these warehouses 824 00:34:54,855 --> 00:34:59,155 or bigger facilities that maybe have a bunch of iot devices 825 00:34:59,935 --> 00:35:01,595 out on the floor that may 826 00:35:01,595 --> 00:35:04,675 or may not be doing security on different machinery, 827 00:35:04,675 --> 00:35:07,435 different sensors, different things like that. 828 00:35:07,745 --> 00:35:11,275 Like how does that translate? But I, I have no telemetry. 829 00:35:11,635 --> 00:35:13,715 Microsoft is gonna have a lot better telemetry on this than 830 00:35:13,755 --> 00:35:17,115 I am, but this was absolutely an interesting one 831 00:35:17,115 --> 00:35:18,795 that I'm like, I'm gonna have to keep an eye on 832 00:35:18,795 --> 00:35:20,555 this one and where it goes. Yeah, 833 00:35:20,915 --> 00:35:23,515 - , who knows, we could be back here in a year 834 00:35:23,515 --> 00:35:25,235 and the secur in the model changes. Again, 835 00:35:25,415 --> 00:35:26,835 - I'm dying over here from my cold. 836 00:35:26,985 --> 00:35:29,755 - It's time to let you go. I'm watching you like cough 837 00:35:29,815 --> 00:35:30,915 and hack into the screen. 838 00:35:30,945 --> 00:35:32,435 There's spittle all over the camera. 839 00:35:33,015 --> 00:35:34,635 I'm glad we didn't record this one on video, 840 00:35:34,815 --> 00:35:36,195 so everybody's kind of missing it. 841 00:35:36,195 --> 00:35:39,325 Your your eyes are watering face is going red. Oh yeah. 842 00:35:39,525 --> 00:35:40,485 I think it's just time to put you 843 00:35:40,485 --> 00:35:41,605 in a car and send you to Disney. 844 00:35:41,715 --> 00:35:42,805 - Yeah, I'm gonna go take this 845 00:35:42,805 --> 00:35:43,965 to everybody at Disney, Scott. Yeah, 846 00:35:43,965 --> 00:35:44,965 - I know, I know. 847 00:35:44,965 --> 00:35:46,405 You're, you're just a wonderful, uh, wonderful individual. 848 00:35:46,505 --> 00:35:48,565 I'm gonna sit here at home in my little hide 849 00:35:48,565 --> 00:35:49,645 hole and not worry about it. 850 00:35:49,745 --> 00:35:51,605 - Sounds good. Well, now that I've recovered 851 00:35:51,605 --> 00:35:54,045 for a few minutes, thanks, enjoy your weekend 852 00:35:54,425 --> 00:35:55,925 and we'll talk to you next week, Scott. 853 00:35:56,545 --> 00:36:00,845 - All right, thanks Ben. - If you enjoyed the podcast, 854 00:36:01,345 --> 00:36:03,405 go leave us a five star rating in iTunes. 855 00:36:03,585 --> 00:36:04,965 It helps to get the word out 856 00:36:04,985 --> 00:36:08,485 so more it pros can learn about Office 365 and Azure. 857 00:36:09,105 --> 00:36:11,525 If you have any questions you want us to address on the show 858 00:36:11,625 --> 00:36:14,365 or feedback about the show, feel free 859 00:36:14,425 --> 00:36:17,485 to reach out via our website, Twitter, or Facebook. 860 00:36:17,745 --> 00:36:19,845 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