Episode 361 – TLS updates in Azure

November 23, 2023

Episode Transcript

In Episode 361, Ben and Scott discuss how Ben solved a data analysis problem with Azure Data Explorer and Scott shares some tips and tricks for Kusto.

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,365 --> 00:00:06,135 - Welcome to episode 361 2 00:00:06,135 --> 00:00:08,375 of the Microsoft Cloud IT Pro podcast 3 00:00:08,975 --> 00:00:11,655 recorded live on November 6th, 2023. 4 00:00:12,085 --> 00:00:14,575 This is a show about Microsoft 365 5 00:00:14,575 --> 00:00:16,735 and Azure from the perspective of it pros 6 00:00:16,735 --> 00:00:19,815 and end users where we discuss a topic or recent news 7 00:00:19,875 --> 00:00:21,055 and how it relates to you. 8 00:00:21,475 --> 00:00:24,055 We are back this week with some more KQL goodness 9 00:00:24,075 --> 00:00:27,295 as Ben discusses how he used Azure Data Explorer 10 00:00:27,485 --> 00:00:29,575 with some exchange email analysis. 11 00:00:29,875 --> 00:00:33,175 And Scott shares some additional tips and tricks for custo. 12 00:00:33,445 --> 00:00:35,615 They also discuss some upcoming changes 13 00:00:35,755 --> 00:00:40,735 to various Azure services when it comes to TLS 1.0, 1.1, 14 00:00:40,795 --> 00:00:42,975 1.2 and 1.3. 15 00:00:45,365 --> 00:00:46,415 Okay, so we don't need 16 00:00:46,415 --> 00:00:47,975 to talk about lights on my face anymore. 17 00:00:48,315 --> 00:00:50,535 Do you wanna talk about your suggestion that I followed 18 00:00:50,725 --> 00:00:53,255 because you gave yourself a bit of a pat on the back 19 00:00:53,255 --> 00:00:54,375 for this one and I have 20 00:00:54,375 --> 00:00:56,375 to admit you had a really good idea. Yeah, I 21 00:00:56,375 --> 00:01:00,255 - Think this is a first, so folks need to know that well, 22 00:01:00,255 --> 00:01:03,615 that you actually listened to me that Ben and I chat back 23 00:01:03,615 --> 00:01:06,695 and forth throughout the week and generally break things 24 00:01:06,795 --> 00:01:07,855 and make fun of each other 25 00:01:07,885 --> 00:01:09,375 with the different things we're breaking. 26 00:01:09,955 --> 00:01:12,855 So you were having a little bit of a conniption, 27 00:01:12,855 --> 00:01:14,615 you were dealing with some Excel files 28 00:01:15,115 --> 00:01:16,415 and you were kind of talking about 29 00:01:16,415 --> 00:01:18,535 how they were getting into the hundreds of thousands, 30 00:01:18,595 --> 00:01:20,055 the millions of rows and you needed 31 00:01:20,055 --> 00:01:21,615 to analyze some data in there 32 00:01:22,195 --> 00:01:25,735 and I threw out why not just use Custo. 33 00:01:25,835 --> 00:01:30,015 Yes. So tell me about your CSV journey and custo 34 00:01:30,395 --> 00:01:32,615 and how it did or did not work out for you. 35 00:01:33,055 --> 00:01:34,415 - Custo itself worked out great. 36 00:01:34,515 --> 00:01:37,135 My log files hit or miss a little bit, 37 00:01:37,275 --> 00:01:39,815 but essentially what I was doing, I have a client 38 00:01:40,045 --> 00:01:42,815 that we are working on an exchange migration 39 00:01:42,815 --> 00:01:46,855 for from on-premises to Office 365. 40 00:01:47,315 --> 00:01:51,455 And we were going down this whole debate of do we do hybrid? 41 00:01:51,715 --> 00:01:53,975 Do we do a cutover, bunch of details 42 00:01:53,975 --> 00:01:55,335 around it we don't need to get into. 43 00:01:55,955 --> 00:01:59,415 But essentially it was they have a bunch of devices, 44 00:02:00,295 --> 00:02:02,695 scanners, printers, services 45 00:02:03,395 --> 00:02:05,215 and they are in an unfortunate situation 46 00:02:05,215 --> 00:02:08,415 where they don't have a complete grasp on everything 47 00:02:08,415 --> 00:02:10,655 that's connecting to their on-prem exchange server. 48 00:02:11,075 --> 00:02:14,815 So it was how can we figure out all of the different 49 00:02:15,535 --> 00:02:19,735 services, devices, et cetera, that are relaying 50 00:02:19,735 --> 00:02:22,815 through this on-prem exchange server that we need to account 51 00:02:22,875 --> 00:02:24,495 for when we go to Exchange online. 52 00:02:25,115 --> 00:02:28,615 So we used, there's a handy commandlet, it is 53 00:02:29,125 --> 00:02:30,935 only exchange on premises. 54 00:02:31,035 --> 00:02:34,215 It is get mess, get message tracking log 55 00:02:34,565 --> 00:02:39,415 that essentially gets like a log of every email 56 00:02:39,765 --> 00:02:41,215 that goes through the server. 57 00:02:41,755 --> 00:02:43,455 So I ran this against a server 58 00:02:43,715 --> 00:02:44,815 and this is the text message 59 00:02:45,245 --> 00:02:48,615 that I sent you was it came back with a 60 00:02:50,145 --> 00:02:53,375 350 meg ish file, 61 00:02:53,615 --> 00:02:57,695 I believe 350 megs, 434 62 00:02:58,565 --> 00:03:02,765 rows in my CSV file of emails, 331 Megs, 63 00:03:02,915 --> 00:03:04,685 450,000 rows . 64 00:03:04,885 --> 00:03:06,965 I was like, what could possibly go wrong? 65 00:03:07,265 --> 00:03:10,045 Trying to open the CSV file on a computer, 66 00:03:10,645 --> 00:03:12,885 - easy peasy and then let's complicate things 67 00:03:13,105 --> 00:03:14,325 by you're on a Mac 68 00:03:14,325 --> 00:03:16,965 and it behaves a little weird with Excel anyway, so, 69 00:03:17,105 --> 00:03:19,845 - But I have 128 gigs of RAM and a whole bunch of cores 70 00:03:19,845 --> 00:03:21,365 because why not? 71 00:03:21,705 --> 00:03:25,045 But needless to say, it still does not perform super great. 72 00:03:25,465 --> 00:03:29,925 And then after the fact I realized that wait a minute, 73 00:03:29,925 --> 00:03:31,965 this was just one exchange server that they told me about. 74 00:03:31,965 --> 00:03:34,885 They have two other ones and this get message 75 00:03:35,645 --> 00:03:38,245 tracking log only pulls it from the server you're on 76 00:03:38,265 --> 00:03:39,685 unless you pass a parameter 77 00:03:39,685 --> 00:03:41,765 to get it from a server at a time. 78 00:03:42,305 --> 00:03:43,925 So I went through the other three servers 79 00:03:43,985 --> 00:03:46,525 and this was like the middle of the road CSV. 80 00:03:46,525 --> 00:03:48,245 There was another one I got from another server 81 00:03:48,245 --> 00:03:52,605 that was like 500 megs and another one that was uh, 250 megs 82 00:03:52,605 --> 00:03:54,645 or something all combined. 83 00:03:54,745 --> 00:03:59,685 It was 1.6 million rows of data of exchange tracking logs 84 00:03:59,945 --> 00:04:02,965 and you're, you were like, to your point, throw it in KQL 85 00:04:03,265 --> 00:04:06,285 and huh you know what, Scott's actually a smart guy. 86 00:04:06,285 --> 00:04:07,485 Maybe I should pay attention to him 87 00:04:07,485 --> 00:04:08,725 and listen to him every once in a while. 88 00:04:08,945 --> 00:04:11,885 So that's what I did. I actually used Azure Data Explorer 89 00:04:12,505 --> 00:04:16,765 and the handy little data ingestion, 90 00:04:16,975 --> 00:04:18,885 which makes it super quick. 91 00:04:19,085 --> 00:04:20,165 I mean I had the advantage, 92 00:04:20,305 --> 00:04:22,765 all three files are from Exchange exact same format. 93 00:04:23,185 --> 00:04:24,245 So I just went 94 00:04:24,245 --> 00:04:28,125 and did a little Azure Data Explorer configuration, 95 00:04:28,355 --> 00:04:31,925 said go upload these three CSV files 96 00:04:32,475 --> 00:04:33,725 into this one table 97 00:04:34,105 --> 00:04:37,885 and I can add all three of 'em at once and hit go. 98 00:04:38,385 --> 00:04:39,525 And it took a little bit 99 00:04:39,525 --> 00:04:44,325 because I had to upload like 1.2 gigs of CSVs 100 00:04:44,425 --> 00:04:45,885 to Azure Data Explorer. 101 00:04:46,105 --> 00:04:47,405 But let me tell you, going through 102 00:04:47,405 --> 00:04:51,405 and starting to write queries to find distinct IP addresses 103 00:04:51,745 --> 00:04:56,325 and to find IP addresses that messages were coming from 104 00:04:56,395 --> 00:05:00,885 that only had a single sender which indicated like some 105 00:05:00,885 --> 00:05:03,245 other service or something 106 00:05:03,245 --> 00:05:06,525 that wasn't just here's the bulk email from everybody. 107 00:05:06,945 --> 00:05:09,485 It actually worked out really well Scott, 108 00:05:09,865 --> 00:05:11,125 to sort through it. 109 00:05:11,255 --> 00:05:12,925 There was not some data, 110 00:05:12,925 --> 00:05:15,125 there was some data I would've liked to see in there 111 00:05:15,465 --> 00:05:18,605 to better differentiate from something relaying 112 00:05:18,605 --> 00:05:21,605 through exchange versus Outlook, like to be able 113 00:05:21,605 --> 00:05:24,525 to see the actual client connection versus 114 00:05:24,785 --> 00:05:25,845 IP address and sender. 115 00:05:25,845 --> 00:05:28,245 And I'm still digging through some data 116 00:05:28,585 --> 00:05:31,405 but that had nothing to do with KQL and CSV. 117 00:05:31,435 --> 00:05:34,405 It's purely what get message tracking log contains 118 00:05:34,905 --> 00:05:37,765 and just not quite the level 119 00:05:37,785 --> 00:05:39,965 of data detail I wanted in it. 120 00:05:40,065 --> 00:05:42,685 But in terms of being able to analyze it and sort through it 121 00:05:42,905 --> 00:05:47,405 and all of that, Azure Data Explorer KQL was kind of fun. 122 00:05:47,585 --> 00:05:48,845 It actually, it works really well 123 00:05:49,145 --> 00:05:51,085 for doing this type of thing. It's 124 00:05:51,415 --> 00:05:52,645 - Super easy to do, 125 00:05:52,645 --> 00:05:54,765 especially if you only have a couple million, 126 00:05:54,915 --> 00:05:56,125 even a couple billion records. 127 00:05:56,395 --> 00:05:58,245 Like it's not huge or massive. 128 00:05:58,425 --> 00:06:01,605 You can stand up a a party cluster basically really 129 00:06:01,605 --> 00:06:03,165 quick and get going with it. 130 00:06:03,225 --> 00:06:06,725 So we did this on the other YouTube channel or 131 00:06:06,725 --> 00:06:07,725 or to the cloud channel. 132 00:06:07,945 --> 00:06:09,525 We kind of did a one click ingestion 133 00:06:09,905 --> 00:06:11,805 and looked at how easy some of this stuff is. 134 00:06:12,065 --> 00:06:14,525 But I love that you were able to take that 135 00:06:14,865 --> 00:06:17,525 and turn it around into something practical. 136 00:06:18,005 --> 00:06:19,765 Kusto is near and dear to my heart unfortunately. 137 00:06:19,835 --> 00:06:21,045 Well I, I dunno, fortunately, 138 00:06:21,045 --> 00:06:25,485 unfortunately I spend all my time in Custo Friday 139 00:06:25,875 --> 00:06:30,325 last week I was trying, we collect some telemetry, 140 00:06:30,715 --> 00:06:33,405 very similar kind of thing about clients like what's your 141 00:06:34,195 --> 00:06:35,565 user agent that's coming through? 142 00:06:35,675 --> 00:06:37,565 What are oss, are you on? Things like that. 143 00:06:38,305 --> 00:06:40,725 And being in Azure storage, 144 00:06:41,065 --> 00:06:44,005 we get billions upon billions of requests. 145 00:06:44,425 --> 00:06:47,245 And so I was trying to wrangle this query for one day 146 00:06:47,245 --> 00:06:49,405 of data where it was returning something like 147 00:06:49,435 --> 00:06:51,605 5 billion records in it. 148 00:06:52,075 --> 00:06:53,085 It's kind of a fun thing 149 00:06:53,205 --> 00:06:55,365 'cause it's actually able to kind 150 00:06:55,365 --> 00:06:57,005 of wrangle it and put it together. 151 00:06:57,005 --> 00:06:58,365 Especially if you can think about 152 00:06:59,015 --> 00:07:01,245 doing your queries the right way. 153 00:07:01,745 --> 00:07:03,765 I'm gonna give you a quick kind of pro tip. 154 00:07:03,955 --> 00:07:06,445 - Okay. - For custo specifically, so this is one 155 00:07:06,445 --> 00:07:08,765 that I just learned on Friday 156 00:07:09,345 --> 00:07:13,205 and it's super helpful when you're dealing with 157 00:07:14,155 --> 00:07:17,845 text in custo like a very long uh, 158 00:07:17,965 --> 00:07:19,445 a very long string record. 159 00:07:20,025 --> 00:07:22,805 So think like maybe something spits out a string 160 00:07:23,695 --> 00:07:26,485 where it's actually comma separated like in the string. 161 00:07:26,825 --> 00:07:30,085 So maybe it says like resource equals X 162 00:07:30,615 --> 00:07:32,845 comma client IP equals blah blah blah. 163 00:07:32,905 --> 00:07:34,965 And it's not broken out into different columns. 164 00:07:35,345 --> 00:07:38,125 So there's this operator in custo which is 165 00:07:38,125 --> 00:07:39,165 called parse ware. 166 00:07:39,545 --> 00:07:41,085 So you can do all sorts of parsing in custo. 167 00:07:41,085 --> 00:07:43,605 You can parse JSON and you can parse version numbers 168 00:07:43,905 --> 00:07:47,885 and parse text and but use this parse ware operator 169 00:07:48,345 --> 00:07:50,525 and you can actually point it at that column. 170 00:07:50,585 --> 00:07:54,565 That's the big string and you can throw RegX at it 171 00:07:54,825 --> 00:07:58,445 and it extracts the data out of that string as you need 172 00:07:58,505 --> 00:08:02,365 by RegX and it turns it into calculated columns on the fly 173 00:08:02,785 --> 00:08:04,405 and it's super performance. 174 00:08:04,465 --> 00:08:06,605 So the way you would use this is, like I said, 175 00:08:06,725 --> 00:08:09,405 you have this big long string that you need to decompose. 176 00:08:09,435 --> 00:08:10,605 Like maybe you're gonna, 177 00:08:10,605 --> 00:08:12,725 we're gonna extend it into multiple columns 178 00:08:12,725 --> 00:08:16,165 and do an extend extract, extend extract, extend extract. 179 00:08:16,185 --> 00:08:17,925 Yep. Which is typically how I go about it, 180 00:08:18,055 --> 00:08:19,685 which is super resource intensive, 181 00:08:19,905 --> 00:08:22,245 but this parse wear thing, you just throw a RegX at it 182 00:08:22,505 --> 00:08:24,045 or multiple RegX is even 183 00:08:24,525 --> 00:08:26,325 'cause you can do like RegX per 184 00:08:26,715 --> 00:08:28,325 extracted column kind of thing. 185 00:08:29,095 --> 00:08:30,645 Super duper cool. 186 00:08:30,845 --> 00:08:32,325 I was having a lot of fun with that. Wonder 187 00:08:32,325 --> 00:08:33,325 - If this would work. 188 00:08:33,765 --> 00:08:35,925 I was just looking at my data 189 00:08:35,925 --> 00:08:38,685 because I have one column in here. 190 00:08:39,865 --> 00:08:41,325 Oh see it didn't pull that out. 191 00:08:41,605 --> 00:08:45,045 I don't see it in there but I have seen that even in my CSV 192 00:08:45,045 --> 00:08:47,485 where it's, and I've seen it in other CSVs 193 00:08:47,485 --> 00:08:50,085 that you get from Microsoft where it's absolutely 194 00:08:50,085 --> 00:08:51,525 that it's like ACSV. 195 00:08:51,585 --> 00:08:55,685 But then the last column is like the context or the data 196 00:08:56,065 --> 00:08:58,325 and it's, you have your curly brackets 197 00:08:58,515 --> 00:09:02,165 that are wrapping like a monster Jason string 198 00:09:02,185 --> 00:09:06,005 or an embedded, it's like ACSV embedded in the CSV. So 199 00:09:06,005 --> 00:09:08,285 - Another way I, I'll give you a practical use case. 200 00:09:08,285 --> 00:09:11,805 So I have a table that tracks storage account names. Yep. 201 00:09:12,025 --> 00:09:15,405 And as part of, so there's a column called account name 202 00:09:15,905 --> 00:09:19,405 and in that column the account name is not just the account 203 00:09:19,405 --> 00:09:21,285 name like the string like my account name, 204 00:09:21,795 --> 00:09:24,085 it's my account name semicolon. 205 00:09:24,305 --> 00:09:28,085 And then a Unix date time which is the date time 206 00:09:28,085 --> 00:09:29,245 that the account was created. 207 00:09:29,785 --> 00:09:32,885 Uh, so somebody made the conscientious decision when they 208 00:09:32,885 --> 00:09:34,725 stood up this table that they were going 209 00:09:34,725 --> 00:09:37,645 to include the create time of the account as part 210 00:09:37,645 --> 00:09:41,685 of the account name just so we could have cardinality there 211 00:09:41,685 --> 00:09:42,725 and maintain uniqueness. 212 00:09:43,005 --> 00:09:44,605 'cause you know I could create an account today 213 00:09:44,865 --> 00:09:47,285 and then 30 days later and then I delete it the same day 214 00:09:47,285 --> 00:09:49,645 and then 30 days later you go account, create an account 215 00:09:49,645 --> 00:09:51,405 with the same name over in your subscription. 216 00:09:51,515 --> 00:09:52,965 Technically two different accounts. 217 00:09:53,145 --> 00:09:54,565 But I'm always going through this table 218 00:09:54,705 --> 00:09:56,565 and I'm doing this thing where I say, okay, 219 00:09:56,565 --> 00:09:59,405 take account name, split it on semicolon 220 00:09:59,585 --> 00:10:02,365 and then grab like the first part of the array 221 00:10:02,365 --> 00:10:03,565 and then grab the second part of the array 222 00:10:03,765 --> 00:10:05,245 'cause I want account name and create time 223 00:10:05,245 --> 00:10:06,325 as two separate columns. 224 00:10:06,745 --> 00:10:09,405 And now with this parse wear thing, I just go in 225 00:10:09,405 --> 00:10:11,645 and I say pars wear account name 226 00:10:12,145 --> 00:10:14,325 and then I can just throw a regex in 227 00:10:14,345 --> 00:10:18,325 and automatically split on the semicolon all in one step 228 00:10:18,325 --> 00:10:20,245 without having to extend out into 229 00:10:21,205 --> 00:10:23,965 multiple additional calculated columns on the fly. 230 00:10:24,055 --> 00:10:26,725 Which it turns out is like a nicety that you just kind 231 00:10:26,725 --> 00:10:29,965 of have to type less but it's also more performant 232 00:10:29,965 --> 00:10:33,005 because you're basically relying on a wear C clause rather 233 00:10:33,005 --> 00:10:35,045 than calculating after the wear. 234 00:10:35,505 --> 00:10:38,965 And your wearers tend to kind of be compute heavy anyway. 235 00:10:39,025 --> 00:10:42,005 So why not do both at once and have your cake and eat it too 236 00:10:42,495 --> 00:10:43,495 - Nifty. 237 00:10:43,495 --> 00:10:44,245 I just looked through my data, 238 00:10:44,345 --> 00:10:47,245 my source context one is a mess in this exchange. 239 00:10:47,345 --> 00:10:49,325 So this would not really work for source context 240 00:10:49,395 --> 00:10:52,565 because I don't, you know what the data you get out is nice 241 00:10:52,785 --> 00:10:56,085 but let me tell you, some of the data is so 242 00:10:56,845 --> 00:10:58,725 inconsistent in some of these cases, 243 00:10:58,955 --> 00:11:00,525 like this source context, 244 00:11:01,045 --> 00:11:02,325 - I shall pretend I'm surprised 245 00:11:02,705 --> 00:11:03,925 - One of it's one long string 246 00:11:04,265 --> 00:11:07,565 and then another email has like semicolon 247 00:11:08,125 --> 00:11:09,285 delimited stuff in it. 248 00:11:09,425 --> 00:11:11,605 And then another one is just completely blank. 249 00:11:11,865 --> 00:11:15,325 And I mean I get it, your source context changes from email 250 00:11:15,325 --> 00:11:18,285 to email but it makes it a little bit challenging sometimes 251 00:11:18,345 --> 00:11:22,005 to parse through it when there's no uniformity 252 00:11:22,305 --> 00:11:24,845 to the data format in that column 253 00:11:25,145 --> 00:11:27,605 or none that I've can decipher super easily. 254 00:11:28,035 --> 00:11:30,125 - It's a little rough if you gotta wrangle it that way. 255 00:11:30,545 --> 00:11:32,765 So maybe you wanna know, like my other pro tip 256 00:11:32,765 --> 00:11:35,005 that I do in cases like that is 257 00:11:35,845 --> 00:11:38,125 custo has a case statement selector, 258 00:11:38,445 --> 00:11:39,565 I don't know if you've ever used this. 259 00:11:39,665 --> 00:11:43,925 So sometimes I'll extend columns and then based on case, 260 00:11:44,115 --> 00:11:45,805 because when you do a case statement, 261 00:11:45,805 --> 00:11:48,685 you're basically doing if this then that, if this, then that 262 00:11:48,705 --> 00:11:50,765 and all the way down to having a default. 263 00:11:51,105 --> 00:11:53,085 But the cool thing is your predicate, 264 00:11:53,125 --> 00:11:55,965 like your if statement can be different for each 265 00:11:55,965 --> 00:11:57,845 and every case within that case statement. 266 00:11:58,185 --> 00:12:00,045 So you could have in that case where the, 267 00:12:00,045 --> 00:12:02,245 like the data's a little bit different between the two. 268 00:12:02,625 --> 00:12:03,725 You could say okay, 269 00:12:03,755 --> 00:12:06,325 case A when it meets this predicate then do this. 270 00:12:06,425 --> 00:12:07,965 But then when it meets this other predicate 271 00:12:07,965 --> 00:12:09,045 then format it like this. 272 00:12:09,045 --> 00:12:11,285 But if it does this other predicate format it like this 273 00:12:11,625 --> 00:12:14,005 and then maybe do yeah and then maybe do unknown 274 00:12:14,005 --> 00:12:16,525 or dump something out the other side doesn't work 275 00:12:16,525 --> 00:12:18,485 with billions and billions of records. 276 00:12:18,755 --> 00:12:21,845 I've found like it is a little more than a little compute 277 00:12:21,845 --> 00:12:23,765 heavy but couple billion, 278 00:12:23,785 --> 00:12:26,165 couple hundred million like not a problem, 279 00:12:26,235 --> 00:12:27,365 doesn't even break a sweat. 280 00:12:27,465 --> 00:12:28,765 - So if I can figure out a way 281 00:12:28,765 --> 00:12:31,165 to define my cases, I could use that. 282 00:12:31,425 --> 00:12:32,965 - Yes. If you have a predicate 283 00:12:33,145 --> 00:12:35,245 and you can figure out like basically what 284 00:12:35,245 --> 00:12:38,365 that statement is, like that wearer statement 285 00:12:38,785 --> 00:12:40,485 and split it out, you could technically 286 00:12:40,505 --> 00:12:41,565 put it all in the same column. 287 00:12:42,095 --> 00:12:43,685 - Nifty more stuff to play with, 288 00:12:43,875 --> 00:12:45,125 more data to go dig through. 289 00:12:48,905 --> 00:12:50,645 Do you feel overwhelmed by trying 290 00:12:50,645 --> 00:12:52,925 to manage your Office 365 environment? 291 00:12:53,025 --> 00:12:54,805 Are you facing unexpected issues 292 00:12:54,805 --> 00:12:56,685 that disrupt your company's productivity? 293 00:12:56,715 --> 00:12:59,485 Intelligent is here to help much like you take your car 294 00:12:59,485 --> 00:13:02,125 to the mechanic that has specialized knowledge on how 295 00:13:02,125 --> 00:13:04,845 to best keep your car running Intelligent helps you 296 00:13:04,875 --> 00:13:06,605 with your Microsoft cloud environment 297 00:13:06,605 --> 00:13:08,285 because that's their expertise. 298 00:13:08,435 --> 00:13:09,725 Intelligent keeps up 299 00:13:09,725 --> 00:13:11,765 with the latest updates on the Microsoft cloud 300 00:13:11,785 --> 00:13:13,245 to help keep your business running 301 00:13:13,565 --> 00:13:14,765 smoothly and ahead of the curve. 302 00:13:14,795 --> 00:13:16,725 Whether you are a small organization 303 00:13:16,725 --> 00:13:19,165 with just a few users up to an organization 304 00:13:19,165 --> 00:13:22,245 of several thousand employees they want to partner with you 305 00:13:22,305 --> 00:13:25,925 to implement and administer your Microsoft Cloud technology, 306 00:13:26,495 --> 00:13:29,885 visit them at intelligent.com/podcast. 307 00:13:30,345 --> 00:13:34,805 That's I-N-T-E-L-L-I-G-I-N 308 00:13:34,885 --> 00:13:36,885 k.com/podcast. 309 00:13:37,505 --> 00:13:39,965 For more information or to schedule a 30 minute call 310 00:13:39,965 --> 00:13:41,085 to get started with them today, 311 00:13:42,085 --> 00:13:44,965 remember intelligent focuses on the Microsoft cloud 312 00:13:45,105 --> 00:13:46,925 so you can focus on your business. 313 00:13:49,425 --> 00:13:52,125 Oh, so where do we go from here Scott? 314 00:13:52,265 --> 00:13:53,605 We could go one or two directions, 315 00:13:53,625 --> 00:13:57,685 we could go talk about some changes to TLS 316 00:13:57,685 --> 00:14:00,965 or we could continue down client stories from Ben 317 00:14:01,645 --> 00:14:02,645 - . 318 00:14:02,755 --> 00:14:04,005 It's your show. Take your 319 00:14:04,005 --> 00:14:05,005 - Pick. 320 00:14:05,005 --> 00:14:06,645 No you, I picked the first topic you get to pick if you want 321 00:14:06,645 --> 00:14:08,445 to hear more client cases from Ben 322 00:14:08,445 --> 00:14:09,965 or if you wanna talk about TLS. 323 00:14:10,145 --> 00:14:12,445 - Why don't we talk about TLS? Okay. 324 00:14:12,595 --> 00:14:15,525 I've had some fun at work with TLS the last couple weeks. 325 00:14:16,225 --> 00:14:20,405 So there's a bunch of services in Azure. There 326 00:14:20,405 --> 00:14:22,005 - Are a bunch of services in Azure 327 00:14:22,485 --> 00:14:23,485 - . 328 00:14:23,485 --> 00:14:24,125 Yes, there are a bunch of services in Azure. 329 00:14:24,285 --> 00:14:25,805 I was gonna say, let's take a step back. 330 00:14:25,865 --> 00:14:29,365 So we have this kind of operating principle 331 00:14:29,425 --> 00:14:30,925 of being secure by default. 332 00:14:31,545 --> 00:14:33,325 So maybe at some point we should come back 333 00:14:33,325 --> 00:14:35,565 and talk about the memo that just came out 334 00:14:35,565 --> 00:14:37,125 that was published about Brad Smith 335 00:14:37,145 --> 00:14:39,965 and our security org that kind of talks about our principles 336 00:14:40,025 --> 00:14:42,205 for how we approach secure by default 337 00:14:42,805 --> 00:14:43,845 security first for our customers. 338 00:14:44,345 --> 00:14:46,485 So you're gonna start to see more 339 00:14:46,485 --> 00:14:49,845 and more of this I think across Azure, certainly Azure, 340 00:14:49,875 --> 00:14:50,885 like I'm close to it, 341 00:14:51,025 --> 00:14:53,845 you'll see it across like M 365, 0 365, 342 00:14:54,305 --> 00:14:55,365 the the entire stack. 343 00:14:55,365 --> 00:14:59,045 Things are gonna start to get more, not locked down 344 00:14:59,465 --> 00:15:00,885 but they're gonna get uh, 345 00:15:01,105 --> 00:15:02,805 put into a better default position, 346 00:15:02,815 --> 00:15:05,045 which could mean more work for you as a customer. 347 00:15:05,145 --> 00:15:06,165 So, so I think customers 348 00:15:06,165 --> 00:15:07,205 are gonna need to pay attention to this. 349 00:15:07,465 --> 00:15:11,605 So one of the first ones to kind of hit is 350 00:15:12,275 --> 00:15:16,285 that TLS is changing in a whole bunch of places 351 00:15:16,915 --> 00:15:20,685 with regard to minimum supported TLS 352 00:15:21,165 --> 00:15:23,005 versions first of all. 353 00:15:23,265 --> 00:15:26,205 So there's services today that support like T LSS one 354 00:15:27,045 --> 00:15:29,205 T LS 1.0 1.1, 1.2 355 00:15:29,945 --> 00:15:32,565 and then you're also gonna be see kind 356 00:15:32,565 --> 00:15:35,765 of forward looking changes in what's coming down the pipe 357 00:15:36,345 --> 00:15:40,445 as far as having access to newer TLS versions. 358 00:15:40,635 --> 00:15:42,405 Well newer in that they've been out a while 359 00:15:42,545 --> 00:15:45,645 and we're kind of catching up on them right now. 360 00:15:46,105 --> 00:15:49,325 So particularly with TLS 1.3. 361 00:15:49,545 --> 00:15:51,845 So the first one that's near and dear to my heart is 362 00:15:52,385 --> 00:15:56,245 in storage land we have announced that 363 00:15:56,845 --> 00:15:59,805 TLS 1.2 is going 364 00:15:59,805 --> 00:16:03,325 to become the minimum TLS version for 365 00:16:03,865 --> 00:16:07,365 all Azure storage accounts moving forward 366 00:16:07,935 --> 00:16:10,125 after November 1st, 2024. 367 00:16:10,425 --> 00:16:11,765 And it's not just moving forward, 368 00:16:11,995 --> 00:16:15,845 it's also we're deprecating support for 1.0 369 00:16:16,185 --> 00:16:20,765 and 1.1 for existing accounts as well. 370 00:16:21,425 --> 00:16:23,725 So that's something that folks need 371 00:16:23,725 --> 00:16:26,525 to potentially take a lookout for. 372 00:16:26,545 --> 00:16:31,245 So if you have pinned ATLS version like you've pinned to 373 00:16:31,905 --> 00:16:34,005 TLS 1.0 or 1.1 374 00:16:34,265 --> 00:16:38,405 and you're doing that today, you have a year, you have 375 00:16:38,405 --> 00:16:42,245 until November 1st, 2024 to go ahead 376 00:16:42,585 --> 00:16:43,645 and flip the switch 377 00:16:44,265 --> 00:16:48,125 and get over to at least TLS 1.2 378 00:16:48,425 --> 00:16:51,325 as a minimum supported version. 379 00:16:51,635 --> 00:16:53,765 - Yeah and I sent you a text on this one 380 00:16:53,835 --> 00:16:56,205 because I'm curious if somebody's listening 381 00:16:56,465 --> 00:16:58,285 and has this information. 382 00:16:58,805 --> 00:17:00,725 I have not been able to find it 383 00:17:01,545 --> 00:17:05,045 but there were some Microsoft Cloud workshops 384 00:17:05,505 --> 00:17:09,565 around high availability that I worked on 385 00:17:10,385 --> 00:17:12,165 and that are still out there 386 00:17:12,625 --> 00:17:15,645 and to the best of my knowledge, okay, 387 00:17:15,715 --> 00:17:17,885 backwards a step now I'm going a step 388 00:17:17,885 --> 00:17:19,485 backwards SQL server, 389 00:17:19,555 --> 00:17:20,725 - It's our thing today. Yeah 390 00:17:20,725 --> 00:17:21,925 - It is SQL Server. 391 00:17:21,925 --> 00:17:23,965 If you're doing a high availability cluster 392 00:17:24,425 --> 00:17:26,685 and you want a cloud witness 393 00:17:27,905 --> 00:17:30,405 for your SQL high availability, 394 00:17:31,505 --> 00:17:34,525 you can set it up with a storage count. 395 00:17:34,675 --> 00:17:37,005 It's all built right into SQL Server. 396 00:17:38,115 --> 00:17:41,725 However, if you do not do TLS 1.0, 397 00:17:41,905 --> 00:17:43,365 if you actually do 1.1 398 00:17:43,365 --> 00:17:47,925 or 1.2 a SQL server does not use T LSS 399 00:17:47,925 --> 00:17:50,645 1.2 or will not work with T LSS 1.1 400 00:17:50,665 --> 00:17:53,965 or 1.0 No it won't work with 1.2 401 00:17:54,105 --> 00:17:57,165 or 1.1 when using an Azure storage 402 00:17:57,165 --> 00:17:58,285 account for your cloud witness. 403 00:17:59,005 --> 00:18:03,445 I have not seen anywhere across the intro webs 404 00:18:03,815 --> 00:18:07,805 where the SQL team has updated SQL server so 405 00:18:07,965 --> 00:18:10,285 that it will work with T LSS 1.2 in a storage 406 00:18:10,285 --> 00:18:11,405 account for that cloud witness. 407 00:18:11,585 --> 00:18:14,125 Yet what that means is 408 00:18:14,785 --> 00:18:16,565 if there's somebody from the SQL Server team 409 00:18:16,565 --> 00:18:19,005 that's listening to this, I would recommend making some 410 00:18:19,005 --> 00:18:21,765 changes to SQL Server to support T LSS 1.2. 411 00:18:21,765 --> 00:18:23,965 Are you gonna have a whole bunch of high availability SQL 412 00:18:24,195 --> 00:18:28,445 instances in Azure using an Azure storage account 413 00:18:28,585 --> 00:18:31,805 for your cloud witness that are going to break 414 00:18:32,395 --> 00:18:35,125 come October 31st, 2024? 415 00:18:35,545 --> 00:18:38,485 And then along with that, I don't know which versions 416 00:18:38,485 --> 00:18:39,565 of SQL they would go back 417 00:18:39,585 --> 00:18:43,445 and add this into SQL's expensive depending on 418 00:18:43,465 --> 00:18:46,765 how you license it and how you set it up in Azure. 419 00:18:47,845 --> 00:18:50,085 I know a lot of people still running old versions 420 00:18:50,085 --> 00:18:52,765 of SQL Server, people tend to put SQL server up 421 00:18:52,785 --> 00:18:55,125 and as long as it's working they don't tend to touch it 422 00:18:55,175 --> 00:18:56,325 until it's out of support. 423 00:18:56,905 --> 00:19:00,405 I'm curious to see how one, I don't know 424 00:19:00,405 --> 00:19:01,805 how many people use a cloud witness 425 00:19:02,225 --> 00:19:04,565 for high availability SQL servers and Azure, 426 00:19:05,225 --> 00:19:09,165 but I'm curious to see what effect this has in 427 00:19:09,165 --> 00:19:10,485 that particular scenario. 428 00:19:11,035 --> 00:19:14,085 Just 'cause it's one in particular that I was aware of 429 00:19:14,225 --> 00:19:19,005 and have come across regularly where TLS 1.1 430 00:19:19,005 --> 00:19:21,125 and 1.2 aren't supported yet, particularly 431 00:19:21,505 --> 00:19:23,525 around cloud storage. 432 00:19:23,845 --> 00:19:26,165 - I would've assumed this one would've been 433 00:19:26,165 --> 00:19:27,485 fixed a couple years ago. 434 00:19:27,745 --> 00:19:31,085 So there was a SQL server has 435 00:19:32,185 --> 00:19:35,285 lagged in some areas in the past, so, so I, 436 00:19:36,515 --> 00:19:39,285 it's been a while since I've done a cloud witness so I know 437 00:19:39,785 --> 00:19:41,205 for backups, 438 00:19:41,425 --> 00:19:44,005 so doing like backpack files over to SQL Server. 439 00:19:44,065 --> 00:19:46,685 Yep. That used to be problematic as well 440 00:19:46,685 --> 00:19:48,605 because that from a SQL 441 00:19:48,625 --> 00:19:51,805 to a storage account connection did not support TLS 1.2 442 00:19:52,225 --> 00:19:55,685 but they've basically patched and cumulative updated 443 00:19:55,825 --> 00:19:57,925 and hot fixed their way out of that one. 444 00:19:58,165 --> 00:20:02,325 I would have to go play with a cloud witness and see, 445 00:20:02,375 --> 00:20:04,765 - Maybe we should do this, maybe we should go do a, 446 00:20:04,915 --> 00:20:07,125 - It's been a hot minute since I've tried one but maybe 447 00:20:07,125 --> 00:20:08,765 - We should go do a YouTube video. It's 448 00:20:08,765 --> 00:20:09,765 - A good call out. 449 00:20:09,765 --> 00:20:12,685 And fortuitous timing, I think we're going to talk 450 00:20:12,685 --> 00:20:13,725 to the sequel team in a week 451 00:20:13,725 --> 00:20:15,405 or two here to do our big powwow. 452 00:20:15,425 --> 00:20:16,685 So , I should bring it up with 'em, 453 00:20:16,705 --> 00:20:17,805 - Ask them about this one 454 00:20:17,805 --> 00:20:20,005 because again, I couldn't find anything 455 00:20:20,145 --> 00:20:21,565 and I have the same assumption as you. 456 00:20:21,625 --> 00:20:24,885 I'm like, I would think with sql, whatever we're on now 20, 457 00:20:24,985 --> 00:20:26,165 are we on 2022? 458 00:20:26,165 --> 00:20:29,445 2019 SQL subscription edition 459 00:20:29,445 --> 00:20:31,565 because that's what we're doing with everything now , 460 00:20:31,925 --> 00:20:34,485 I would've doubt they would've fixed this given 461 00:20:34,625 --> 00:20:37,725 to your point how much Microsoft has been trying to get rid 462 00:20:37,725 --> 00:20:40,925 of 1.0 1.1 and really use 1.2 for everything. 463 00:20:41,345 --> 00:20:43,285 But I am not a hundred percent sure 464 00:20:43,525 --> 00:20:45,565 'cause I can't find anything documented 465 00:20:46,105 --> 00:20:47,925 nor have I necessarily gone 466 00:20:47,925 --> 00:20:50,605 and tried this with the most recent up-to-date 467 00:20:50,675 --> 00:20:52,045 patched version of sql. 468 00:20:52,185 --> 00:20:55,605 And I would be also be curious like how far back you can go 469 00:20:55,745 --> 00:20:56,965 before it would break. 470 00:20:57,305 --> 00:20:59,445 So let me know, go talk to the SQL team, 471 00:20:59,705 --> 00:21:00,845 ask them the hard questions. 472 00:21:01,205 --> 00:21:02,925 - I would tend to think most of this is 473 00:21:03,475 --> 00:21:04,645 patched most of the way out. 474 00:21:04,665 --> 00:21:07,525 So I'll throw a link over in the chat just so you have it 475 00:21:07,585 --> 00:21:09,165 and you can maybe take a look through 476 00:21:09,165 --> 00:21:11,245 and let me know if I'm off there. 477 00:21:12,185 --> 00:21:16,725 But it looks like all the current supported major versions 478 00:21:17,035 --> 00:21:20,245 have been patched up to TLS 1.2. 479 00:21:20,705 --> 00:21:23,285 Now that being said, no place in that article 480 00:21:23,305 --> 00:21:24,885 of known issues that it fixes. 481 00:21:24,885 --> 00:21:26,765 Does it call out cloud witnesses? 482 00:21:26,945 --> 00:21:30,325 So mileage might vary with that. May vary with that one. 483 00:21:30,325 --> 00:21:32,685 - Alright, we're gonna go do some testing sometime, 484 00:21:32,945 --> 00:21:34,245 but yeah I've, if you 485 00:21:34,245 --> 00:21:35,525 - Have the ability to spin up a cloud witness 486 00:21:35,525 --> 00:21:36,605 real quick, I wanna try it out. 487 00:21:37,105 --> 00:21:37,845 - I'm not gonna do it right now. 488 00:21:37,845 --> 00:21:39,045 We'll have to do it on a YouTube channel. 489 00:21:39,345 --> 00:21:42,205 We can go through the one of those MCWs or something 490 00:21:42,545 --> 00:21:44,965 or part of the way through it 'cause that one's a long one. 491 00:21:45,065 --> 00:21:47,205 All right. Okay, other TLS stuff. So 492 00:21:47,205 --> 00:21:50,725 - We've got TLS 1.2 for storage is going 493 00:21:50,725 --> 00:21:54,005 to become the minimum supported, per supported version. 494 00:21:54,595 --> 00:21:57,285 That is November 1st, 2024. 495 00:21:57,825 --> 00:22:01,605 The other TLS thing that is out there 496 00:22:02,225 --> 00:22:06,045 is you're gonna start to see services also flip over to 497 00:22:06,985 --> 00:22:11,965 TLS 1.3 and the first one that I saw announced so far 498 00:22:12,545 --> 00:22:14,565 is Azure App Service. 499 00:22:14,985 --> 00:22:16,525 So app service for web apps, 500 00:22:17,055 --> 00:22:21,885 which includes your apps service plans, which also run 501 00:22:22,025 --> 00:22:24,525 for things like functions 502 00:22:25,105 --> 00:22:27,485 and logic apps as well. 503 00:22:28,265 --> 00:22:32,565 So this is kind of rolling out slowly TLS 1.3 504 00:22:32,785 --> 00:22:35,965 for app service, like your underlying kind of compute 505 00:22:35,985 --> 00:22:39,645 and hosting engine is starting to roll out now. 506 00:22:39,995 --> 00:22:42,405 It's going to be rolling out over the course 507 00:22:42,665 --> 00:22:45,245 of the remainder of what we have here in 2023 508 00:22:45,945 --> 00:22:49,045 and 2024 509 00:22:49,745 --> 00:22:51,725 and rollouts worldwide. 510 00:22:52,275 --> 00:22:55,645 I'll put a link in in the show notes for everybody to go 511 00:22:55,825 --> 00:22:57,885 and take a look and see what's going on there. 512 00:22:58,545 --> 00:23:02,285 But basically kind of it goes through canary staging 513 00:23:02,505 --> 00:23:05,285 and the end user acceptance, all that stuff. 514 00:23:05,505 --> 00:23:08,005 And it'll hit us clients first, 515 00:23:08,695 --> 00:23:12,645 which is an interesting one given the presence 516 00:23:12,745 --> 00:23:17,005 of some really big retailers and things 517 00:23:17,025 --> 00:23:19,445 and coming into the holiday season, who knows 518 00:23:19,445 --> 00:23:24,125 who runs preview and who runs on supported GA stuff. 519 00:23:24,225 --> 00:23:25,765 So we shall see. 520 00:23:25,985 --> 00:23:28,965 But I have seen customers here get into trouble like when 521 00:23:28,965 --> 00:23:31,285 they do pinning for things like TLS versions, 522 00:23:31,875 --> 00:23:34,605 when they do cert pinning, all that kind of stuff. 523 00:23:34,635 --> 00:23:36,405 Like I understand why it needs to be done, 524 00:23:36,705 --> 00:23:39,805 but it's a call out that your runway is potentially 525 00:23:39,805 --> 00:23:41,005 limited with some of these things. 526 00:23:41,195 --> 00:23:44,325 - Yeah, well it looks like they already started rolling it 527 00:23:44,325 --> 00:23:46,085 out the end of October. 528 00:23:46,515 --> 00:23:47,565 October 23rd. 529 00:23:47,625 --> 00:23:48,685 It began rolling out 530 00:23:48,945 --> 00:23:50,925 and like you said, kind of through the end of the year 531 00:23:51,265 --> 00:23:53,005 and that's the preview, 532 00:23:54,705 --> 00:23:58,445 we will continue rolling out TLS sometime early 2024. 533 00:23:58,445 --> 00:23:59,765 Yeah, but that's all under the preview. 534 00:24:00,075 --> 00:24:01,845 Will it just be in preview then yet 535 00:24:02,035 --> 00:24:05,485 through January, 2024 is the way I would read this. 536 00:24:05,705 --> 00:24:07,405 - That's the way I, I read it for now. 537 00:24:07,425 --> 00:24:10,125 So I think it's a smart move to do it that way. 538 00:24:10,345 --> 00:24:13,365 So one of the things that happens is now you're going 539 00:24:13,365 --> 00:24:15,965 to have access not just to TLS 1.3 540 00:24:16,345 --> 00:24:19,605 but to new cipher suites within T LSS 1.3. 541 00:24:19,785 --> 00:24:23,085 So you might also have a dependency within your stack on a 542 00:24:23,085 --> 00:24:26,005 certain cipher suite that you've been waiting for. 543 00:24:26,265 --> 00:24:28,925 So now it gives you the chance to kind of potentially play 544 00:24:28,925 --> 00:24:31,405 around with those and see what's what 545 00:24:31,585 --> 00:24:33,765 and what's gonna work and what's gonna break. 546 00:24:34,065 --> 00:24:37,285 - So yes and I would expect, I mean app service for web apps 547 00:24:37,665 --> 00:24:38,685 and then functions 548 00:24:38,685 --> 00:24:41,085 and logic apps going at the same time kind 549 00:24:41,085 --> 00:24:44,205 of makes sense since they all run on the same service. 550 00:24:44,535 --> 00:24:47,085 - Funny enough, it's just web apps though. 551 00:24:47,345 --> 00:24:51,405 It it, so it's the kind of public compute side of web apps. 552 00:24:51,865 --> 00:24:55,365 It is not A-S-E-A-S-E-V one is still kicking around there. 553 00:24:55,565 --> 00:24:57,805 V two is out and about as well. 554 00:24:58,265 --> 00:25:01,685 And surprisingly TLS 1.3 is not there yet. 555 00:25:01,785 --> 00:25:04,045 So again, your mileage may vary huh? 556 00:25:04,145 --> 00:25:06,845 In the ever landing cha ev ever changing land 557 00:25:06,865 --> 00:25:08,125 of Azure previews. 558 00:25:08,385 --> 00:25:11,565 - Yes. And I would imagine we'll start seeing more TLS 559 00:25:11,565 --> 00:25:13,085 1.3 stuff coming. 560 00:25:13,625 --> 00:25:17,285 We have ignite. Well by the time people hear this episode, 561 00:25:18,145 --> 00:25:19,805 unless we switch orders, Scott 562 00:25:20,325 --> 00:25:21,325 Ignite may have already happened. 563 00:25:21,635 --> 00:25:23,125 Well by the time they hear this 564 00:25:23,185 --> 00:25:24,845 one Ignite will have happened. 565 00:25:24,845 --> 00:25:27,125 Whether we have an Ignite episode before this one 566 00:25:27,125 --> 00:25:30,045 or not, we'll have to play with schedules 567 00:25:30,045 --> 00:25:33,685 because Ignite is happening a week from when we're recording 568 00:25:33,715 --> 00:25:35,445 this essentially. Yes, 569 00:25:35,635 --> 00:25:36,925 - Rapidly approaching. 570 00:25:37,025 --> 00:25:38,765 - We shall see. Maybe there will be some TLS 571 00:25:38,765 --> 00:25:40,085 1.3 stuff at Ignite. 572 00:25:40,405 --> 00:25:42,445 I think there will be some interesting 573 00:25:42,645 --> 00:25:43,765 announcements coming out there. 574 00:25:44,065 --> 00:25:46,125 Any other TLS stuff you wanna talk about? Those 575 00:25:46,125 --> 00:25:49,125 - Are the big ones that I'm aware of so far. 576 00:25:49,695 --> 00:25:51,565 We'll see where the rest come in. So 577 00:25:51,565 --> 00:25:54,285 - We're gonna talk about one more deprecation that has kind 578 00:25:54,285 --> 00:25:55,565 of Ben's client woes. 579 00:25:55,565 --> 00:25:57,805 We don't need to get into all my client woes 580 00:25:57,865 --> 00:25:59,805 around this particular announcement. 581 00:26:00,195 --> 00:26:03,325 This is almost sort of an I told you so not 582 00:26:03,465 --> 00:26:05,725 to this particular client but to other people 583 00:26:05,725 --> 00:26:07,645 because I have been saying this for years, 584 00:26:08,065 --> 00:26:09,605 but there was an article today, 585 00:26:10,045 --> 00:26:13,645 Microsoft Deprecates three features in Windows 11 version 586 00:26:13,645 --> 00:26:14,885 23 H two. 587 00:26:15,545 --> 00:26:17,405 And guess which one of those features is? 588 00:26:17,455 --> 00:26:19,965 Scott, you wouldn't guess if I wouldn't have told you this. 589 00:26:20,315 --> 00:26:23,245 - I've been waiting for this one to drop for a long. 590 00:26:23,245 --> 00:26:25,765 Like it was inevitable that this one comes like 591 00:26:25,795 --> 00:26:27,045 - It's totally, and I told you 592 00:26:27,045 --> 00:26:28,805 so it's going to happen. Yes, 593 00:26:29,585 --> 00:26:34,325 - The web client web dev is finally going away. 594 00:26:35,405 --> 00:26:39,605 Woe be to those who continue to use SharePoint 595 00:26:39,985 --> 00:26:41,245 and file explore views. 596 00:26:41,465 --> 00:26:42,845 - Yes. And I have been, 597 00:26:43,375 --> 00:26:45,725 there is one client I've been having this discussion with 598 00:26:45,725 --> 00:26:48,205 and they're like, but it works to open 599 00:26:48,205 --> 00:26:49,685 and file explore on one computer 600 00:26:49,825 --> 00:26:51,125 and not on another computer. 601 00:26:51,425 --> 00:26:53,205 And I'm like, why are we even trying this? 602 00:26:53,845 --> 00:26:56,805 Microsoft should have taken, I mean web dev is going away. 603 00:26:57,025 --> 00:26:59,245 To be fair, Microsoft should have taken this out 604 00:26:59,245 --> 00:27:01,565 of the SharePoint UI like the day 605 00:27:01,645 --> 00:27:02,765 after they came out with it 606 00:27:02,835 --> 00:27:07,645 because it's been giving me woes and heartburn 607 00:27:07,825 --> 00:27:12,605 and all of the bad things since the day it came out 608 00:27:12,635 --> 00:27:17,285 because of all the weirdness, particularly with SharePoint. 609 00:27:17,315 --> 00:27:21,325 There's always been weirdness around file modified dates on 610 00:27:22,245 --> 00:27:25,845 functionality because it's not really doing a sync then it's 611 00:27:25,845 --> 00:27:27,725 opening it like a file server 612 00:27:27,945 --> 00:27:30,205 and there are still people that try to use it 613 00:27:30,505 --> 00:27:32,005 and people that try to use it. 614 00:27:32,085 --> 00:27:33,925 I say stop. It's going to go away. 615 00:27:34,405 --> 00:27:37,565 Microsoft has at least labeled it Legacy up until 616 00:27:38,335 --> 00:27:39,805 today, November 6th. 617 00:27:40,265 --> 00:27:42,085 But you should not be using web dev 618 00:27:42,085 --> 00:27:43,365 to open files and SharePoint. 619 00:27:43,785 --> 00:27:45,965 And now I finally have something to point to 620 00:27:45,965 --> 00:27:48,765 and say you really should not be using web dev to open files 621 00:27:48,765 --> 00:27:51,365 and SharePoint because it has now been 622 00:27:51,365 --> 00:27:53,085 deprecated in Windows. 623 00:27:53,815 --> 00:27:55,885 There have been issues with it now for a while, 624 00:27:55,885 --> 00:27:57,205 ever since Edge came out 625 00:27:57,205 --> 00:28:01,165 because it is a feature, at least it's in SharePoint. 626 00:28:01,245 --> 00:28:03,485 I don't know. I would assume it would affect other places 627 00:28:03,625 --> 00:28:07,285 too because it's part of the HTTP, the hypertext 628 00:28:07,805 --> 00:28:10,125 transfer protocol for those of you that have always heard it 629 00:28:10,125 --> 00:28:13,205 and never actually known what HTP stood for, where you had 630 00:28:13,205 --> 00:28:16,005 to use Internet Explorer to even use web dev. 631 00:28:16,505 --> 00:28:19,205 So as Edge has come out on chromium 632 00:28:19,225 --> 00:28:22,245 and they've started pulling out some of the IE. 633 00:28:22,305 --> 00:28:26,285 Supportability stuff and IE has started getting deprecated 634 00:28:26,385 --> 00:28:27,965 and support for IE has gone away. 635 00:28:28,425 --> 00:28:31,765 Web dev in Evolve itself has already started getting a bit 636 00:28:32,195 --> 00:28:35,565 unpredictable because of losing browser support. 637 00:28:35,755 --> 00:28:37,365 - Just a little unpredictable. 638 00:28:37,365 --> 00:28:39,645 - Yeah. Yeah. A little more unpredictable than it's been 639 00:28:39,645 --> 00:28:40,725 since 2003. 640 00:28:40,945 --> 00:28:44,725 But yes, now it is gone. We can wave goodbye to it. 641 00:28:45,065 --> 00:28:48,085 And if you're still using it, please stop once 642 00:28:48,085 --> 00:28:51,045 and for all , even if it still works on Windows 10 643 00:28:51,225 --> 00:28:54,125 and you have no plans to upgrade to Windows 11, just 644 00:28:54,395 --> 00:28:55,395 - Stop. 645 00:28:55,395 --> 00:28:56,325 That's the plea, huh? Please, 646 00:28:56,325 --> 00:28:57,525 - That's - The plea. Just stop. 647 00:28:58,025 --> 00:29:01,725 - Please just stop before I start crying on the podcast. 648 00:29:02,385 --> 00:29:04,605 - But won't you think of the files come on. 649 00:29:04,885 --> 00:29:06,125 - I do not care for the files 650 00:29:06,945 --> 00:29:09,845 or the pain that goes with dealing with files 651 00:29:09,915 --> 00:29:11,485 that are opened over web dev 652 00:29:11,745 --> 00:29:14,045 or mapped network drives that are SharePoint 653 00:29:14,045 --> 00:29:17,485 because we've had, and we can go find other episodes. 654 00:29:17,485 --> 00:29:19,525 We have talked at length about this so we don't need 655 00:29:19,525 --> 00:29:22,365 to get into that of why SharePoint is not a network file 656 00:29:22,365 --> 00:29:24,405 share, but it is not a network file share, 657 00:29:24,405 --> 00:29:26,005 therefore WebDAV should not be a thing 658 00:29:26,145 --> 00:29:27,805 nor should interacting with SharePoint files 659 00:29:27,945 --> 00:29:28,965 in that way be a thing. 660 00:29:29,185 --> 00:29:31,565 End of soap box off the soap box. 661 00:29:31,905 --> 00:29:34,525 - End of soap box. Well so the interesting thing 662 00:29:34,525 --> 00:29:36,365 that happens here, , 663 00:29:37,085 --> 00:29:38,325 I always kind of cringe a little bit. 664 00:29:38,705 --> 00:29:41,205 So this is a change that's coming in Windows 11. 665 00:29:41,715 --> 00:29:44,165 It's not something that's like being back ported. 666 00:29:44,325 --> 00:29:46,005 'cause we're so far gone from Windows 10 667 00:29:46,505 --> 00:29:48,525 and unfortunately there's still lots of people 668 00:29:48,525 --> 00:29:49,845 that run Windows 10 as well. 669 00:29:49,985 --> 00:29:51,525 So they're in the clear I guess 670 00:29:51,705 --> 00:29:54,165 - Is Windows seven still kicking around out there? 671 00:29:54,765 --> 00:29:55,845 - I imagine it is. 672 00:29:56,005 --> 00:29:58,125 I probably have one or two former employers 673 00:29:58,185 --> 00:30:02,325 who are still running fleets of desktops on Windows seven 674 00:30:02,325 --> 00:30:03,405 because they can, 675 00:30:03,685 --> 00:30:05,685 I mean Windows CE is still kicking around, right? 676 00:30:05,685 --> 00:30:07,645 Like I don't know how it is in other countries, 677 00:30:07,645 --> 00:30:10,485 but over here in the US it powers your favorite uh ATM. 678 00:30:10,665 --> 00:30:13,205 - Tim, what about Windows Me? We can get on the Windows. 679 00:30:13,515 --> 00:30:14,885 - That was the one with the good startup sound. 680 00:30:14,995 --> 00:30:16,445 - Yeah, Sean said in Discord. 681 00:30:16,705 --> 00:30:19,325 Oh it is unfortunately about Windows xp. 682 00:30:19,465 --> 00:30:23,325 So yes, windows XP is still alive and kicking as well. 683 00:30:23,765 --> 00:30:26,285 , that's a whole other topic of conversation. 684 00:30:26,395 --> 00:30:28,245 That one's been outta support for how many years? 685 00:30:28,545 --> 00:30:30,005 - For one or two hot minutes now. 686 00:30:30,275 --> 00:30:34,485 - Yeah, so that is I think our news, oh, 687 00:30:34,545 --> 00:30:36,485 one last bullet points Scott. 688 00:30:36,665 --> 00:30:38,205 We don't need to talk about this either. 689 00:30:38,545 --> 00:30:40,725 We mentioned in a previous episode, 690 00:30:41,025 --> 00:30:43,325 and I'm not gonna say last in case these get out of order 691 00:30:43,325 --> 00:30:46,605 with Ignite the automatic conditional access policies 692 00:30:46,605 --> 00:30:49,245 and Entra being created by Microsoft. 693 00:30:49,265 --> 00:30:50,805 And I didn't have a good reference article 694 00:30:50,805 --> 00:30:52,885 for it today on November 6th. 695 00:30:53,445 --> 00:30:56,645 Microsoft did come out with a blog post about it. 696 00:30:56,825 --> 00:30:58,365 So we'll throw a link to the, 697 00:30:58,795 --> 00:31:01,085 that blog post in the show notes if anybody wanted 698 00:31:01,105 --> 00:31:05,485 to see the Microsoft official announcement today rather than 699 00:31:05,825 --> 00:31:09,765 the stuff that I found on the socials when we recorded 700 00:31:09,765 --> 00:31:11,205 that other episode. Perfect. 701 00:31:11,475 --> 00:31:13,205 - I've been looking out for that one. Good catch. 702 00:31:13,425 --> 00:31:16,525 - You got it. And finally, girls Who Code Scott 703 00:31:16,705 --> 00:31:18,005 or Fundraiser Girls 704 00:31:18,065 --> 00:31:22,285 - Who code tis the season of giving help a 705 00:31:23,095 --> 00:31:25,285 young woman in your life 706 00:31:25,425 --> 00:31:28,085 or contribute to some other young woman's career to 707 00:31:28,655 --> 00:31:32,405 enter the wonderful field of information technology 708 00:31:32,985 --> 00:31:35,725 and give to Girls Who Code. 709 00:31:36,065 --> 00:31:37,925 So if you go to give dot girls 710 00:31:37,945 --> 00:31:42,485 who code.com/ms cloud IT Pro, you can contribute 711 00:31:42,485 --> 00:31:44,325 to our campaign or go ahead 712 00:31:44,325 --> 00:31:48,045 and contribute to another campaign for Girls Who Code if you 713 00:31:48,045 --> 00:31:50,045 so desire, if you get like a match at work 714 00:31:50,045 --> 00:31:51,165 or things like that. 715 00:31:51,705 --> 00:31:53,765 But yeah, go ahead and make it happen. 716 00:31:54,005 --> 00:31:57,205 I would love to see us raise some money for Girls Who code 717 00:31:57,595 --> 00:31:59,805 through the podcast once again this year. 718 00:31:59,945 --> 00:32:02,605 - Yes. And try to beat last year's goal. 719 00:32:02,825 --> 00:32:06,085 So by December 31 we're gonna see if we can better 720 00:32:06,235 --> 00:32:07,325 what we did last year 721 00:32:07,675 --> 00:32:09,765 with those donations to Girls Who Code. 722 00:32:09,945 --> 00:32:11,045 So see what we can do. 723 00:32:11,225 --> 00:32:14,485 And with that Scott, we can sign off for the day. 724 00:32:14,965 --> 00:32:16,685 - Excellent. . Well I 725 00:32:16,685 --> 00:32:17,725 don't get to sign off for the day. 726 00:32:18,225 --> 00:32:19,845 I'm going to Redmond for a work trip. 727 00:32:20,065 --> 00:32:21,525 So I've worked for Microsoft 728 00:32:21,705 --> 00:32:23,885 for three coming on three years now 729 00:32:23,885 --> 00:32:25,765 and I've never met anybody I work with 730 00:32:25,905 --> 00:32:28,485 and I'm going on my first work trip. 731 00:32:28,585 --> 00:32:30,365 So that kind of came in hot 732 00:32:30,385 --> 00:32:32,085 and I had to book tickets the last minute. 733 00:32:32,185 --> 00:32:33,445 But uh, I am going 734 00:32:33,445 --> 00:32:35,805 to Redmond tomorrow and I'll be there for a week. 735 00:32:35,865 --> 00:32:36,965 So that'll be fun. It 736 00:32:36,965 --> 00:32:37,965 - Just clicked. 737 00:32:37,965 --> 00:32:39,685 Scott, you're leaving right before Ignite then. 738 00:32:39,685 --> 00:32:42,765 - Totally. So I think Ignite like the sessions start on 739 00:32:42,765 --> 00:32:43,805 the 14th through the 15th. 740 00:32:43,835 --> 00:32:46,165 I'll be flying back in a red eye on the 14th. . Yeah, 741 00:32:46,305 --> 00:32:47,765 - You should have just stayed two extra days. 742 00:32:48,045 --> 00:32:50,085 - Holidays are coming up. I I got another vacation. 743 00:32:50,125 --> 00:32:51,485 I gotta get to you gotta All right. 744 00:32:51,625 --> 00:32:53,045 My wife would be mad at me. Sounds good. 745 00:32:53,065 --> 00:32:55,485 My dogs will be mad at me. My kids will be mad at me. Hey 746 00:32:55,485 --> 00:32:57,165 - Scott, I won't be mad at you. 747 00:32:57,395 --> 00:32:59,045 - Okay, that's good. I appreciate it. 748 00:32:59,065 --> 00:33:01,125 - I'm here for you. Alright, well enjoy your trip. 749 00:33:01,275 --> 00:33:04,125 Safe travels. Say hello to all the folks in Redmond 750 00:33:04,125 --> 00:33:06,845 for us Bug the sequel team about cloud witnesses 751 00:33:06,905 --> 00:33:11,285 and travel safe and we will see you next week 752 00:33:11,285 --> 00:33:12,925 for Ignite when we talk about all the 753 00:33:12,925 --> 00:33:14,005 fun stuff from that. All 754 00:33:14,005 --> 00:33:15,005 - Right, sounds good. 755 00:33:15,005 --> 00:33:15,605 Thanks Ben. 756 00:33:17,745 --> 00:33:18,885 - If you enjoyed the podcast, 757 00:33:19,425 --> 00:33:21,485 go leave us a five star rating in iTunes. 758 00:33:21,665 --> 00:33:23,005 It helps to get the word out 759 00:33:23,065 --> 00:33:26,565 so more IT pros can learn about Office 365 and Azure. 760 00:33:27,305 --> 00:33:29,805 If you have any questions you want us to address on the show 761 00:33:29,865 --> 00:33:32,205 or feedback about the show, feel free 762 00:33:32,205 --> 00:33:35,565 to reach out via our website, Twitter, or Facebook. 763 00:33:35,825 --> 00:33:37,925 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