Episode 417 – Workplace Ninjas US, Zero Trust, and Conditional Access!

December 18, 2025

Episode Transcript

Welcome to Episode 417 of the Microsoft Cloud IT Pro Podcast. In this episode of the Microsoft Cloud IT Pro Podcast, Jay Leask joins Ben once more as the two of them recap their experience at Workplace Ninjas US in Dallas, Texas. They discuss conference highlights, the unique hackathon, engaging sessions, the Clippy Bucks system, and the importance of community and inclusion. The conversation also covers upcoming events, memorable attendee interactions, and new traditions for future conferences.

Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options.

Show Notes

About the sponsors

Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

See full episode transcriptTranscript is autogenerated by AI

1 00:00:03,359 --> 00:00:05,839 Welcome to episode 417 2 00:00:05,839 --> 00:00:08,960 of the Microsoft Cloud IT Pro podcast recorded 3 00:00:08,960 --> 00:00:11,539 live on 12/10/2025. 4 00:00:11,759 --> 00:00:14,000 This is a show about Microsoft three sixty 5 00:00:14,000 --> 00:00:16,114 five and Azure from the perspective of IT 6 00:00:16,114 --> 00:00:18,195 pros and end users, where we discuss a 7 00:00:18,195 --> 00:00:20,515 topic or recent news and how it relates 8 00:00:20,515 --> 00:00:23,074 to you. Don't worry. I haven't kicked Scott 9 00:00:23,074 --> 00:00:25,094 off the show. He'll be back on eventually. 10 00:00:25,314 --> 00:00:28,035 But today, you have been joined by Jay 11 00:00:28,035 --> 00:00:30,809 Leesk once more. We just wrapped up the 12 00:00:30,809 --> 00:00:33,850 Workplace Ninjas US Conference, where we presented two 13 00:00:33,850 --> 00:00:36,489 sessions, one on zero trust in Microsoft three 14 00:00:36,489 --> 00:00:38,409 sixty five and the other one on conditional 15 00:00:38,409 --> 00:00:41,369 access. Jay and I both thoroughly enjoyed the 16 00:00:41,369 --> 00:00:43,435 conference, so we decided to sit sit down 17 00:00:43,435 --> 00:00:45,054 and chat for a bit about the conference, 18 00:00:45,114 --> 00:00:47,195 our experience, and just a little bit about 19 00:00:47,195 --> 00:00:48,575 the sessions we presented. 20 00:00:50,395 --> 00:00:52,554 Welcome to the Microsoft Cloud IT Pro podcast 21 00:00:52,554 --> 00:00:54,075 where I have no idea which episode this 22 00:00:54,075 --> 00:00:56,875 will be because I'm on interview number 23 00:00:57,510 --> 00:01:00,649 interview conversation. Not really interview. Conversation number 24 00:01:01,109 --> 00:01:04,810 something. Five, six. Let's call it follow-up to 25 00:01:05,270 --> 00:01:08,230 episode 400. 410. You're very proud of episode 26 00:01:08,230 --> 00:01:10,165 410, aren't you? I am. For those of 27 00:01:10,165 --> 00:01:12,405 you that don't recognize the voice, Jay is 28 00:01:12,405 --> 00:01:14,665 back without Joy, which means hopefully. 29 00:01:15,284 --> 00:01:16,965 Aw. I'm like I don't mean to be 30 00:01:16,965 --> 00:01:19,944 without Joy. Like, I'm happy. You are happy 31 00:01:20,805 --> 00:01:22,504 without Joy Apple. 32 00:01:22,939 --> 00:01:24,079 Should we clarify? 33 00:01:24,459 --> 00:01:27,100 Good afternoon, everybody. This is Jay Leesk. It's 34 00:01:27,100 --> 00:01:28,799 a pleasure to speak with you all again. 35 00:01:28,859 --> 00:01:30,459 Has it has been a while since episode 36 00:01:30,459 --> 00:01:32,780 four ten, but No. I well, it might 37 00:01:32,780 --> 00:01:34,140 be by the time this comes out, but 38 00:01:34,140 --> 00:01:35,280 it's only 04:16 39 00:01:35,340 --> 00:01:37,145 is gonna just came out or came out 40 00:01:37,145 --> 00:01:39,704 tomorrow. Yeah. There's one coming out tomorrow. I 41 00:01:39,704 --> 00:01:40,765 realized Fantastic. 42 00:01:41,305 --> 00:01:42,825 To come out tomorrow? I realized I have 43 00:01:42,825 --> 00:01:44,424 one coming out tomorrow that I need to, 44 00:01:44,424 --> 00:01:45,405 like, actually 45 00:01:45,784 --> 00:01:48,265 do stuff for. Yeah. Because it's Wednesday. We 46 00:01:48,265 --> 00:01:50,505 should probably, like, get into the conversation before 47 00:01:50,505 --> 00:01:51,939 we lose your listeners. What do you wanna 48 00:01:51,939 --> 00:01:53,939 talk about today? If this episode is after 49 00:01:53,939 --> 00:01:55,299 the one I just did with Kat, the 50 00:01:55,299 --> 00:01:56,599 listeners may all be gone. 51 00:01:58,099 --> 00:02:00,180 Oh, that's beautiful. Yes. I just feel joy. 52 00:02:00,180 --> 00:02:02,579 Somehow, we ended up on recording podcasts in 53 00:02:02,579 --> 00:02:04,900 jail with Kat. Yeah. I don't know that 54 00:02:04,900 --> 00:02:07,415 we should strive to lose them even more. 55 00:02:07,415 --> 00:02:09,014 Well, to be clear with by what you 56 00:02:09,014 --> 00:02:10,854 mean there, you ended up talking about what 57 00:02:10,854 --> 00:02:12,615 it would be like to record a podcast 58 00:02:12,615 --> 00:02:14,694 in jail. Yep. You didn't actually record a 59 00:02:14,694 --> 00:02:17,335 podcast in jail. Okay. Okay. And are we 60 00:02:17,335 --> 00:02:19,340 talking about, like, the m three sixty five 61 00:02:19,340 --> 00:02:21,259 jail? Like, is this a Is there an 62 00:02:21,259 --> 00:02:23,099 m three sixty five jail? There really I 63 00:02:23,099 --> 00:02:25,900 mean, maybe something in some report in Sentinel 64 00:02:25,900 --> 00:02:27,259 of some sort? I feel like there's an 65 00:02:27,259 --> 00:02:30,139 MVP jail. There is there? I don't know. 66 00:02:30,139 --> 00:02:32,000 I've said I think there's an MVP blacklist. 67 00:02:32,139 --> 00:02:33,805 I'm gonna get in trouble. Do you wanna 68 00:02:33,805 --> 00:02:35,745 start over? No. 69 00:02:36,125 --> 00:02:37,824 Sorry. Just ignore that. 70 00:02:38,205 --> 00:02:39,485 So it's a pleasure to be speaking with 71 00:02:39,485 --> 00:02:41,965 you. We're at Workplace Ninjas US here in 72 00:02:41,965 --> 00:02:45,905 Dallas, Texas. Today is, what, the December 7? 73 00:02:45,965 --> 00:02:48,790 Six You're off by, like, three days. I'm 74 00:02:48,790 --> 00:02:49,610 a fix my 75 00:02:50,069 --> 00:02:52,490 watch. This my watch says it's the seventh. 76 00:02:55,030 --> 00:02:56,550 And now we know why Jay hasn't been 77 00:02:56,550 --> 00:02:58,389 showing up on time. He has his dates 78 00:02:58,389 --> 00:03:02,550 and times all confused. Hey. It's +1, 234550 79 00:03:02,710 --> 00:03:04,555 450. What? 450. 80 00:03:04,615 --> 00:03:07,175 Yes. Yes. 450. Yeah. My bad. On the 81 00:03:07,175 --> 00:03:09,495 December 10. Right. Right. Right. At the very 82 00:03:09,495 --> 00:03:11,735 end of Workplace Ninjas. Yeah. Which was a 83 00:03:11,735 --> 00:03:14,055 really great conference. It was. And next year, 84 00:03:14,055 --> 00:03:16,215 I have permission from John to say this 85 00:03:16,215 --> 00:03:18,455 because he's announcing it in the keynote or 86 00:03:18,455 --> 00:03:21,479 later tonight Okay. That 2027 87 00:03:21,539 --> 00:03:23,079 is at Scott's. 88 00:03:23,379 --> 00:03:25,219 I think that's what he said, Scott's in 89 00:03:25,219 --> 00:03:28,439 Scottsdale, Arizona. Like Originally named for Scottsdale 90 00:03:28,819 --> 00:03:30,750 the February 91 00:03:30,750 --> 00:03:32,439 2027. 92 00:03:32,500 --> 00:03:35,055 Yes. Very excited to hear about that. Fourteen 93 00:03:35,055 --> 00:03:37,455 months from now. Yeah. I'm not necessarily excited 94 00:03:37,455 --> 00:03:40,014 to hear about Scottsdale. Although, the other people 95 00:03:40,014 --> 00:03:42,254 involved are all excited about Scottsdale. I've never 96 00:03:42,254 --> 00:03:44,735 been to Scottsdale. Acknowledging that I have never 97 00:03:44,735 --> 00:03:46,735 been to Scottsdale. I just also never Isn't 98 00:03:46,735 --> 00:03:48,275 there a golf course in Scottsdale? 99 00:03:48,889 --> 00:03:50,810 Sure. I think there's lots of golf courses. 100 00:03:50,810 --> 00:03:52,569 I thought there was a PGA Tour golf 101 00:03:52,569 --> 00:03:54,650 course in Scottsdale. There could be. I don't 102 00:03:54,650 --> 00:03:57,689 golf particularly much, so it's not a Wonder 103 00:03:57,689 --> 00:03:59,310 if there's ninjas in Scottsdale. 104 00:03:59,930 --> 00:04:01,150 There were ninjas here. 105 00:04:01,449 --> 00:04:03,530 There were. I had a conversation with them 106 00:04:03,530 --> 00:04:04,430 as a former 107 00:04:05,155 --> 00:04:07,555 taekwondo student, and I may go back to 108 00:04:07,555 --> 00:04:08,775 it. I was curious 109 00:04:09,074 --> 00:04:11,474 what form of martial arts they studied, and 110 00:04:11,474 --> 00:04:13,715 they just started listing things off. And I'm 111 00:04:13,715 --> 00:04:15,314 like, okay. Well, I will never be a 112 00:04:15,314 --> 00:04:17,759 ninja if that's the requirement list. I could 113 00:04:17,759 --> 00:04:19,600 never do what they did. I saw I 114 00:04:19,600 --> 00:04:21,600 could not see them because of the way 115 00:04:21,600 --> 00:04:23,360 the layout was. Yeah. That was a little 116 00:04:23,360 --> 00:04:25,600 awkward. Video of it. Mhmm. Yeah. I'm never 117 00:04:25,600 --> 00:04:27,120 gonna be a ninja just based on that 118 00:04:27,120 --> 00:04:29,040 video. Yeah. But should we just talk about 119 00:04:29,040 --> 00:04:31,045 the should we do, like, a conference debrief? 120 00:04:31,045 --> 00:04:32,938 Let's do a conference debrief. I think it 121 00:04:32,938 --> 00:04:34,884 is. This out sooner than later than if 122 00:04:34,884 --> 00:04:36,085 we're gonna do a conference. That's true. I 123 00:04:36,085 --> 00:04:38,324 might flip this one. Maybe this one will 124 00:04:38,324 --> 00:04:41,205 come out Episode four seventeen. Or I might 125 00:04:41,205 --> 00:04:43,785 do this one tomorrow. I have time. Well, 126 00:04:44,050 --> 00:04:45,490 if the other one might already be added 127 00:04:45,490 --> 00:04:46,770 in. This one may have to come out 128 00:04:46,770 --> 00:04:47,970 in a couple weeks or maybe even a 129 00:04:47,970 --> 00:04:49,410 bonus one. I have enough interviews. I may 130 00:04:49,410 --> 00:04:51,889 do a bonus one. Okay. So I'm curious. 131 00:04:51,889 --> 00:04:53,970 I told this to Kat. I'm curious your 132 00:04:53,970 --> 00:04:55,350 thoughts. I believe 133 00:04:55,730 --> 00:04:57,314 I don't know a lot of people here. 134 00:04:57,314 --> 00:04:59,735 Okay. So I'm a relatively new security MVP. 135 00:04:59,795 --> 00:05:02,935 I come as people Are you security MVP? 136 00:05:03,154 --> 00:05:04,675 Yeah. I knew you were an MVP. I 137 00:05:04,675 --> 00:05:06,675 didn't realize you were security. Microsoft three sixty 138 00:05:06,675 --> 00:05:08,295 five and security. Congratulations. 139 00:05:08,834 --> 00:05:10,595 Round of applause. Sorry. Editor, please put a 140 00:05:10,595 --> 00:05:12,055 round of applause in. Okay. 141 00:05:12,509 --> 00:05:14,349 But I started as m three sixty five 142 00:05:14,349 --> 00:05:16,449 in Teams. Yeah. My background is all SharePoint. 143 00:05:16,589 --> 00:05:18,430 Right. I know way more people on the 144 00:05:18,430 --> 00:05:19,870 modern work side of things than I do 145 00:05:19,870 --> 00:05:21,949 security. Like, this group of people are all 146 00:05:21,949 --> 00:05:24,029 new to me. Yeah. Me too. That being 147 00:05:24,029 --> 00:05:25,250 said, without 148 00:05:25,704 --> 00:05:27,865 knowing too many people here, like, I know 149 00:05:27,865 --> 00:05:31,564 you and Kat and Lindsay Yep. And Mona 150 00:05:32,024 --> 00:05:34,264 were some of the people here. And this 151 00:05:34,264 --> 00:05:36,904 is one of the most fun times I've 152 00:05:36,904 --> 00:05:38,044 had at a conference. 153 00:05:38,389 --> 00:05:39,750 Yes. And I think one of the things 154 00:05:39,750 --> 00:05:41,670 that was really interesting about it so day 155 00:05:41,670 --> 00:05:43,930 one of the conference or the preshow day 156 00:05:43,990 --> 00:05:46,310 was a hackathon, which none of us had 157 00:05:46,310 --> 00:05:49,350 any information on going into. No. But we 158 00:05:49,350 --> 00:05:51,375 were on the same team with Kat Yep. 159 00:05:51,615 --> 00:05:53,855 And Kat of the episode of the future, 160 00:05:53,855 --> 00:05:54,355 apparently. 161 00:05:54,975 --> 00:05:57,214 And as we sat down and John explained 162 00:05:57,214 --> 00:05:59,295 the rules to us, we had no idea 163 00:05:59,295 --> 00:06:01,214 of what the heck was going to be. 164 00:06:01,214 --> 00:06:03,935 And it was really cool to walk into 165 00:06:03,935 --> 00:06:06,459 what I was thinking was a security minded 166 00:06:06,459 --> 00:06:06,959 conference 167 00:06:07,419 --> 00:06:10,079 and being encouraged for the hackathon to build 168 00:06:10,300 --> 00:06:12,620 a solution, whether it be an agent or 169 00:06:12,620 --> 00:06:15,120 an app or a website or whatever, 170 00:06:15,660 --> 00:06:17,279 that helped to encourage 171 00:06:18,024 --> 00:06:20,524 DE and I practices across your organization. 172 00:06:20,904 --> 00:06:22,845 And that was pretty much the only rule 173 00:06:22,985 --> 00:06:25,144 of, like, the goals that is. It wasn't 174 00:06:25,144 --> 00:06:26,504 the only rule. It was the only goal. 175 00:06:26,504 --> 00:06:28,985 Right. And the cool part was so we 176 00:06:28,985 --> 00:06:31,310 had five teams. I'm explaining this to the 177 00:06:31,310 --> 00:06:33,229 audience, not you. Because if I'm explaining this 178 00:06:33,229 --> 00:06:35,069 to you, that's awkward. No. Explain it to 179 00:06:35,069 --> 00:06:36,750 the audience for me. So there were five 180 00:06:36,750 --> 00:06:37,250 teams 181 00:06:37,629 --> 00:06:38,129 of 182 00:06:38,509 --> 00:06:39,009 primarily 183 00:06:39,310 --> 00:06:42,129 speakers with, I guess, one or two attendees 184 00:06:42,189 --> 00:06:43,754 per group. And then 185 00:06:44,134 --> 00:06:46,875 the rest of the people in the hackathon 186 00:06:47,175 --> 00:06:49,735 were just attendees of the conference watching us 187 00:06:49,735 --> 00:06:52,875 like cattle on a cattle drive Yes. Which, 188 00:06:52,935 --> 00:06:55,254 I guess, as I think about it, was 189 00:06:55,254 --> 00:06:56,535 a good way for them to get to 190 00:06:56,535 --> 00:06:58,620 know us a little bit, which is cool. 191 00:06:58,860 --> 00:07:00,459 It was. And I would be interested to 192 00:07:00,459 --> 00:07:03,019 hear what the attendees thought. And If only 193 00:07:03,019 --> 00:07:04,000 there was a mechanism 194 00:07:04,459 --> 00:07:06,779 with which you could find that information. Well, 195 00:07:06,779 --> 00:07:08,699 but not all the attendees were there. Right? 196 00:07:08,699 --> 00:07:10,060 Right. It was kind of a pre day. 197 00:07:10,060 --> 00:07:11,819 So I don't know. May what? There were 198 00:07:11,819 --> 00:07:12,319 maybe 199 00:07:12,824 --> 00:07:13,805 30 ish 200 00:07:14,105 --> 00:07:16,824 attendees there? Maybe a few more, 40? Maybe. 201 00:07:16,824 --> 00:07:19,144 Yeah. I had no concept of counting. Somewhere 202 00:07:19,144 --> 00:07:20,824 in there. But I would say not only 203 00:07:21,064 --> 00:07:22,665 and it wasn't that they were just watching 204 00:07:22,665 --> 00:07:25,139 us. Like, it was in a bar Yeah. 205 00:07:25,460 --> 00:07:28,660 With drinks and food. Yes. We started we. 206 00:07:28,660 --> 00:07:31,460 I drink Coke. Other people started drinking. I 207 00:07:31,460 --> 00:07:33,379 won't name any names. Mhmm. At, like, 9AM 208 00:07:33,540 --> 00:07:35,166 Certainly not the people sitting at the table. 209 00:07:35,353 --> 00:07:38,025 It started at 10AM. Yeah. Like, we started 210 00:07:38,025 --> 00:07:39,384 drinking and eating, like, we I had a 211 00:07:39,384 --> 00:07:42,105 breakfast beer. That's valid. And drinking a breakfast 212 00:07:42,105 --> 00:07:44,925 beer at 10AM. Yep. Doing this hackathon. 213 00:07:46,025 --> 00:07:48,345 The one that John had so John organized 214 00:07:48,345 --> 00:07:50,345 this, had, like, a wheel that you could 215 00:07:50,345 --> 00:07:53,029 spin to punish teams Yes. Or help teams. 216 00:07:53,169 --> 00:07:54,610 Yeah. The one I think I wish you 217 00:07:54,610 --> 00:07:56,289 would have done more to your point about 218 00:07:56,449 --> 00:07:58,209 one of them was just, like, an interview 219 00:07:58,209 --> 00:08:00,769 question or ask the speaker a question. I 220 00:08:00,769 --> 00:08:02,949 think it would have been cool to do 221 00:08:03,329 --> 00:08:04,930 have more of those where the speakers could 222 00:08:04,930 --> 00:08:07,089 have introduced themselves to the attendees a little 223 00:08:07,089 --> 00:08:08,964 bit more. Yeah. He made me get up 224 00:08:09,104 --> 00:08:11,664 and tell a thing about me with no 225 00:08:11,664 --> 00:08:14,224 background. He's like, tell the people something interesting 226 00:08:14,224 --> 00:08:16,384 about you. I'm like, okay. But, no, it 227 00:08:16,384 --> 00:08:18,305 was cool. It was like a pre party 228 00:08:18,384 --> 00:08:21,730 Yeah. To the actual conference. It did give 229 00:08:21,730 --> 00:08:22,850 us a way to get to know each 230 00:08:22,850 --> 00:08:25,089 other, meet some attendees, meet some of the 231 00:08:25,089 --> 00:08:27,410 other people before the conference started. So then 232 00:08:27,410 --> 00:08:28,930 you come into the conference on day one, 233 00:08:28,930 --> 00:08:31,730 and you're you already know people Yeah. Because 234 00:08:31,730 --> 00:08:35,110 of just this Hangout hackathon day beforehand. Yes. 235 00:08:35,330 --> 00:08:35,830 Now 236 00:08:36,294 --> 00:08:38,315 then the conference kicked off 237 00:08:38,695 --> 00:08:41,215 there. So it's a two day conference after 238 00:08:41,215 --> 00:08:41,915 the hackathon 239 00:08:42,455 --> 00:08:45,575 running, I think, about five concurrent sessions at 240 00:08:45,575 --> 00:08:48,695 a time Yep. Four time blocks per day. 241 00:08:48,695 --> 00:08:50,960 Plus today, there was an MSP track, which 242 00:08:50,960 --> 00:08:53,120 I thought was really clever because a lot 243 00:08:53,120 --> 00:08:56,720 of the attendees at conferences like this, you're 244 00:08:56,720 --> 00:08:58,399 either you some of you work for a 245 00:08:58,399 --> 00:08:58,899 company 246 00:08:59,279 --> 00:09:00,960 to to do your own security or your 247 00:09:00,960 --> 00:09:03,279 own m three sixty five management, and then 248 00:09:03,279 --> 00:09:06,875 others, there's a large practice of MSP and 249 00:09:06,875 --> 00:09:07,375 MSSPs 250 00:09:08,074 --> 00:09:10,794 that are running this technology on behalf of 251 00:09:10,794 --> 00:09:12,574 another org. And so it's 252 00:09:12,875 --> 00:09:15,595 really interesting to see that was called out 253 00:09:15,595 --> 00:09:16,975 as a top as a particular 254 00:09:17,330 --> 00:09:19,250 track. Yeah. There's a lot of things, I 255 00:09:19,250 --> 00:09:21,250 think, that were done really well about this 256 00:09:21,250 --> 00:09:23,730 that made it I mean, legitimately just made 257 00:09:23,730 --> 00:09:25,570 it a ton of fun. Yeah. Like our 258 00:09:25,570 --> 00:09:26,070 sessions. 259 00:09:26,450 --> 00:09:28,389 Yeah. Let me allow us to transition. 260 00:09:28,929 --> 00:09:31,169 Our sessions. I have never had a session 261 00:09:31,169 --> 00:09:32,230 quite like these. 262 00:09:32,955 --> 00:09:33,455 Yeah. 263 00:09:33,995 --> 00:09:35,375 The conference. Okay. 264 00:09:35,995 --> 00:09:37,535 You're welcome, by the way. 265 00:09:37,915 --> 00:09:39,934 Yeah. I think that's a combination of you. 266 00:09:40,075 --> 00:09:42,154 No. It's that it is partly you because 267 00:09:42,154 --> 00:09:43,355 we have a lot of fun with our 268 00:09:43,355 --> 00:09:45,274 sessions. We do. Yeah. But part of it 269 00:09:45,274 --> 00:09:47,620 was some of what John did with this 270 00:09:47,620 --> 00:09:48,120 conference. 271 00:09:48,580 --> 00:09:50,980 Oh, yeah. Yeah. The big thing that he 272 00:09:50,980 --> 00:09:53,860 did to help the speakers engage with the 273 00:09:53,860 --> 00:09:56,100 attendees And the attendees to engage with the 274 00:09:56,100 --> 00:09:57,860 speakers. Yes. I think it it was a 275 00:09:57,860 --> 00:09:58,580 two way 276 00:09:59,220 --> 00:10:01,164 Yep. For those of you not looking at 277 00:10:01,164 --> 00:10:03,164 my badge at the moment, which should be, 278 00:10:03,164 --> 00:10:04,684 I'd say, a 100% of you. None of 279 00:10:04,684 --> 00:10:06,065 you? I can make your badge, 280 00:10:06,524 --> 00:10:08,605 the artwork Okay. For the episode. I love 281 00:10:08,605 --> 00:10:10,865 it. In fact, you're already looked at it. 282 00:10:11,164 --> 00:10:13,345 So the badge is magnetic, 283 00:10:13,720 --> 00:10:14,779 which is pretty cool. 284 00:10:15,080 --> 00:10:17,980 And there's your name and your company. 285 00:10:18,600 --> 00:10:21,159 Mine has a big Microsoft tile, and yours, 286 00:10:21,159 --> 00:10:23,399 of course, is the MVP tile. But then 287 00:10:23,399 --> 00:10:26,299 there are these smaller tiles which are tradable. 288 00:10:27,080 --> 00:10:28,299 And the 289 00:10:28,924 --> 00:10:29,904 tiles have 290 00:10:30,524 --> 00:10:33,904 if John made a unique value to them 291 00:10:33,964 --> 00:10:35,725 in the sense that he printed more of 292 00:10:35,725 --> 00:10:37,824 some than others, so there were rare ones. 293 00:10:38,125 --> 00:10:40,365 And then as an attendee, you could go 294 00:10:40,365 --> 00:10:40,865 buy 295 00:10:41,339 --> 00:10:44,059 tokens of particular interest, whether it's a CoPilot 296 00:10:44,059 --> 00:10:46,620 logo or a neurodiversity logo or a Disney 297 00:10:46,620 --> 00:10:49,179 thing or a meme that's been turned into 298 00:10:49,179 --> 00:10:52,299 a token. Really fantastic ideas all collected through 299 00:10:52,299 --> 00:10:55,065 the speaker group. And then you to buy 300 00:10:55,065 --> 00:10:55,804 the tokens, 301 00:10:56,105 --> 00:10:59,065 you used Clippy Bucks. And Clippy Bucks were 302 00:10:59,065 --> 00:11:00,665 handed out by speakers, and we had a 303 00:11:00,665 --> 00:11:03,325 lot of fun handing out Clippy Bucks for 304 00:11:03,545 --> 00:11:07,620 attending sessions or asking questions or simply, like, 305 00:11:07,700 --> 00:11:09,539 I think we gave, like, 10 clippy bucks 306 00:11:09,539 --> 00:11:11,559 to someone who stumped us with a question. 307 00:11:11,940 --> 00:11:12,679 And then 308 00:11:13,059 --> 00:11:15,059 someone else in the room educated us on 309 00:11:15,059 --> 00:11:17,539 the answer. So it was really just fun, 310 00:11:17,539 --> 00:11:20,065 a fun way to engage with people. Yeah. 311 00:11:20,065 --> 00:11:21,985 And it wasn't just in sessions. Like, I 312 00:11:21,985 --> 00:11:24,065 was walking around and people are like, hey, 313 00:11:24,065 --> 00:11:26,144 you do this podcast that some of you 314 00:11:26,144 --> 00:11:27,845 are listening to right now. I was like, 315 00:11:28,225 --> 00:11:28,725 sweet. 316 00:11:29,504 --> 00:11:31,824 They're all listening to us. Some of you 317 00:11:31,824 --> 00:11:34,324 are listening to. This is why our sessions 318 00:11:34,559 --> 00:11:36,799 went a little wild. Yes. I was like, 319 00:11:36,799 --> 00:11:39,059 sweet. Here. Have a clip you back. Mhmm. 320 00:11:39,440 --> 00:11:41,600 It was a lot of fun. Yeah. So 321 00:11:41,600 --> 00:11:43,519 we did those are the sessions. We did 322 00:11:43,519 --> 00:11:46,575 a zero trust session, which is a part 323 00:11:46,735 --> 00:11:48,415 of the work of the session we did 324 00:11:48,415 --> 00:11:50,815 at North American Collaboration Summit. Yes. And we 325 00:11:50,815 --> 00:11:52,654 did this in Philly too. We did this 326 00:11:52,654 --> 00:11:54,495 several times now. We didn't have So we 327 00:11:54,495 --> 00:11:56,915 did it in I know. And then Philly. 328 00:11:57,455 --> 00:11:59,370 We did the full day version of it 329 00:11:59,769 --> 00:12:01,929 in Branson, and then we went back to 330 00:12:01,929 --> 00:12:04,089 just the, like, one hour whiteboarding session here. 331 00:12:04,089 --> 00:12:06,250 And the really fun part was we had 332 00:12:06,250 --> 00:12:08,509 a couple of repeat people from Branson, 333 00:12:08,970 --> 00:12:10,570 and one of them said this was he 334 00:12:10,570 --> 00:12:12,330 learned even more this time. So we're getting 335 00:12:12,330 --> 00:12:13,870 better or he was more receptive, 336 00:12:14,195 --> 00:12:15,154 but it was a ton of fun. He 337 00:12:15,154 --> 00:12:17,735 got bored listening to us for eight hours 338 00:12:18,034 --> 00:12:19,875 and was like, one hour is all I 339 00:12:19,875 --> 00:12:22,274 can handle of these two. But then I 340 00:12:22,274 --> 00:12:23,875 really appreciate that you asked me to do 341 00:12:23,875 --> 00:12:25,095 this is today, 342 00:12:25,475 --> 00:12:28,214 we did a deep dive just into 343 00:12:29,220 --> 00:12:29,959 conditional access. 344 00:12:30,259 --> 00:12:32,839 And conditional access, when it comes to security, 345 00:12:33,379 --> 00:12:36,039 conditional access is really fun because 346 00:12:36,579 --> 00:12:39,379 after doing the zero trust whiteboard, you get 347 00:12:39,379 --> 00:12:41,639 the opportunity to take all of the pieces 348 00:12:41,779 --> 00:12:44,534 of zero trust and connect dots. And so 349 00:12:44,534 --> 00:12:46,154 if you're any kind of neurodiverse 350 00:12:46,615 --> 00:12:49,174 and you like to, like, connect dots on 351 00:12:49,174 --> 00:12:49,674 things, 352 00:12:50,054 --> 00:12:52,375 conditional access is, like, the place to deep 353 00:12:52,375 --> 00:12:54,695 dive because you can do things like Jay 354 00:12:54,695 --> 00:12:57,335 is authenticating, and he's authenticating on a corporate 355 00:12:57,335 --> 00:12:59,514 device, and that corporate device is on 356 00:12:59,929 --> 00:13:01,149 trusted or approved 357 00:13:01,529 --> 00:13:02,029 network. 358 00:13:02,649 --> 00:13:04,350 And he's trying to access 359 00:13:04,970 --> 00:13:06,029 sensitive content, 360 00:13:06,409 --> 00:13:09,129 and he wants to do a certain activity 361 00:13:09,129 --> 00:13:10,730 with it. And when you connect all of 362 00:13:10,730 --> 00:13:13,049 those different signals together, you can decide whether 363 00:13:13,049 --> 00:13:14,409 or not he should be allowed to do 364 00:13:14,409 --> 00:13:16,154 it. Yeah. I think it's one of those 365 00:13:16,154 --> 00:13:18,955 areas that you could really rabbit hole on 366 00:13:18,955 --> 00:13:21,434 in a bad way. But, also, if you 367 00:13:21,434 --> 00:13:23,915 have really sensitive content, it's a really good 368 00:13:23,915 --> 00:13:26,715 way to add protections to it other than 369 00:13:26,715 --> 00:13:29,115 putting a password on it. So Yeah. And 370 00:13:29,115 --> 00:13:31,080 it was the one today. We had a 371 00:13:31,080 --> 00:13:33,879 plan for today. It went off the rails 372 00:13:33,879 --> 00:13:35,960 so fast. Yeah. So it was I can't 373 00:13:35,960 --> 00:13:38,360 remember. It was, like, the session title we 374 00:13:38,360 --> 00:13:40,360 forget. Joke to people. People are like, what 375 00:13:40,360 --> 00:13:41,960 session are you doing? I'm like, I have 376 00:13:41,960 --> 00:13:43,559 absolutely no idea because I can't remember what 377 00:13:43,559 --> 00:13:44,865 the title is. I just know the topic. 378 00:13:45,024 --> 00:13:46,485 Yeah. We were going to 379 00:13:47,024 --> 00:13:49,424 introduce kinda conditional access. Here's what it is. 380 00:13:49,424 --> 00:13:51,105 Yep. And then just kinda walk through, here's 381 00:13:51,105 --> 00:13:52,485 how you start building policies. 382 00:13:52,865 --> 00:13:55,424 Yeah. We sort of got through the intro. 383 00:13:55,424 --> 00:13:57,345 We got through the intro. Intro. Pretty well. 384 00:13:57,345 --> 00:13:59,539 We got through that well. We went well. 385 00:13:59,539 --> 00:14:01,379 But then you raised you asked, raise your 386 00:14:01,379 --> 00:14:03,879 hand if you use conditional access, and literally 387 00:14:04,019 --> 00:14:05,700 every hand in the room went up. I 388 00:14:05,700 --> 00:14:07,139 think that's where it started. Because at that 389 00:14:07,139 --> 00:14:08,179 point in time, I was like, I might 390 00:14:08,179 --> 00:14:09,539 as well just walk out. You guys can 391 00:14:09,539 --> 00:14:12,165 all just, like, teach your own class. But 392 00:14:12,165 --> 00:14:13,764 at the same time, it was really cool 393 00:14:13,764 --> 00:14:14,825 because everybody 394 00:14:15,365 --> 00:14:17,684 was familiar with it. Yeah. And this is, 395 00:14:17,684 --> 00:14:20,665 I think, where the Clippy Bucks really 396 00:14:21,125 --> 00:14:23,065 drove engagement Right. Was, 397 00:14:23,605 --> 00:14:26,240 one, people knew we would, like, make it 398 00:14:26,240 --> 00:14:27,919 rain with Clippy Bucks. Some of them had 399 00:14:27,919 --> 00:14:30,080 been in our first session, and they were 400 00:14:30,080 --> 00:14:32,720 like, these guys give out Clippy Bucks if 401 00:14:32,720 --> 00:14:33,459 I participate. 402 00:14:33,759 --> 00:14:37,120 Yes. And I asked, who's those conditional access? 403 00:14:37,120 --> 00:14:38,559 All the hands went up. And I was 404 00:14:38,559 --> 00:14:41,235 like, okay. You got you all have clearly 405 00:14:41,295 --> 00:14:43,134 done this. Yep. What do you wanna learn? 406 00:14:43,134 --> 00:14:45,054 What do you wanna learn about? Yeah. And 407 00:14:45,054 --> 00:14:46,654 even though they'd all done it, like, 10 408 00:14:46,654 --> 00:14:49,054 hands shot up. Yep. Like, this is gonna 409 00:14:49,054 --> 00:14:52,514 be interesting. So instead of going through it, 410 00:14:52,670 --> 00:14:54,190 we got through a couple of them. People 411 00:14:54,190 --> 00:14:56,430 had not seen agents with conditional access. That 412 00:14:56,430 --> 00:14:58,350 was a big one. Yeah. So we were 413 00:14:58,350 --> 00:15:00,830 able to demo some of that. Yep. But 414 00:15:00,830 --> 00:15:03,090 the rest of the time, it was 415 00:15:03,870 --> 00:15:06,815 driven by users just asking questions. 416 00:15:07,355 --> 00:15:09,514 Well, and, actually, even that one, like, the 417 00:15:09,514 --> 00:15:11,934 first big topic that came up was authentication 418 00:15:12,235 --> 00:15:12,815 and context. 419 00:15:13,195 --> 00:15:15,035 What are you trying to access, and what 420 00:15:15,035 --> 00:15:16,315 can you lock down around that? And Jay 421 00:15:16,315 --> 00:15:18,610 was like, hey, Ben. Yeah. Have fun. Well, 422 00:15:18,610 --> 00:15:20,210 the funny thing is and that's on me. 423 00:15:20,210 --> 00:15:21,910 Right? Like, so admittedly, 424 00:15:22,529 --> 00:15:24,950 in this particular topic, I know 425 00:15:25,330 --> 00:15:28,950 a broad swath but surface level detail, and 426 00:15:29,090 --> 00:15:30,850 you know the topic deeply. You could have 427 00:15:30,850 --> 00:15:32,610 run this by yourself. You were gracious enough 428 00:15:32,610 --> 00:15:33,754 to bring me in because we have a 429 00:15:33,754 --> 00:15:35,495 lot of fun together. We absolutely 430 00:15:35,875 --> 00:15:37,715 we were told we have good chemistry this 431 00:15:37,715 --> 00:15:39,014 week. We were. 432 00:15:39,394 --> 00:15:43,554 I had literally just described authentication context as 433 00:15:43,554 --> 00:15:46,720 an example without using that those words. And 434 00:15:46,720 --> 00:15:48,320 then they asked me to describe and they 435 00:15:48,320 --> 00:15:50,080 asked me those words. I'm like, I don't, 436 00:15:50,080 --> 00:15:51,379 Ben, save me. 437 00:15:51,759 --> 00:15:53,759 And then you then answered with what I 438 00:15:53,759 --> 00:15:55,440 just described, and I'm like, oh, I could 439 00:15:55,440 --> 00:15:57,200 have answered that. I just didn't know I 440 00:15:57,200 --> 00:15:59,039 could have answered that. And so I learned 441 00:15:59,039 --> 00:16:01,675 a bunch of stuff with more detail and 442 00:16:01,675 --> 00:16:03,754 from a screen perspective too because I don't 443 00:16:03,754 --> 00:16:05,595 live in this world. So that's also really 444 00:16:05,595 --> 00:16:07,514 cool. So that was a big topic. That 445 00:16:07,514 --> 00:16:09,434 was, like, a twenty minute conversation. Then we 446 00:16:09,434 --> 00:16:11,675 had a topic around someone else brought up 447 00:16:11,675 --> 00:16:13,754 the the context of, okay. So I have 448 00:16:13,754 --> 00:16:15,134 someone who travels to 449 00:16:15,730 --> 00:16:18,450 Russia and The Ukraine and this other place 450 00:16:18,450 --> 00:16:20,710 for scouting potential employees, and 451 00:16:21,170 --> 00:16:22,929 how do I protect what they're doing? So 452 00:16:22,929 --> 00:16:24,470 we got to dive deep into 453 00:16:24,850 --> 00:16:26,230 location based controls, 454 00:16:26,690 --> 00:16:28,049 and then someone else 455 00:16:28,674 --> 00:16:30,754 even the agents won. The last ten minutes 456 00:16:30,754 --> 00:16:32,754 of the session, someone said, what can we 457 00:16:32,754 --> 00:16:34,915 do with agents? And so even though that 458 00:16:34,915 --> 00:16:36,915 was the one thing we had planned, we 459 00:16:36,915 --> 00:16:39,235 just got this opportunity to deep dive on, 460 00:16:39,235 --> 00:16:40,455 like, four scenarios 461 00:16:41,039 --> 00:16:42,879 that, honestly, if if we had written in 462 00:16:42,879 --> 00:16:44,559 the session, we're gonna deep dive on four 463 00:16:44,559 --> 00:16:47,039 scenarios of your choice. Like, it would it 464 00:16:47,039 --> 00:16:49,600 it was perfect. It was awesome. Absolutely. And, 465 00:16:49,600 --> 00:16:51,360 again, I'm gonna hammer on this because I 466 00:16:51,360 --> 00:16:53,620 would love to see more conferences do this. 467 00:16:53,679 --> 00:16:56,174 I think the Clippy Bucks. Yeah. Like, people 468 00:16:56,174 --> 00:16:58,335 legitimately have questions. Yeah. But a lot of 469 00:16:58,335 --> 00:17:00,815 times, people are like, oh, I don't wanna 470 00:17:00,815 --> 00:17:02,335 answer or I don't wanna ask. I don't 471 00:17:02,335 --> 00:17:04,414 wanna seem stupid. I don't want people to 472 00:17:04,414 --> 00:17:06,174 make fun of me. But because of these 473 00:17:06,174 --> 00:17:09,339 Clippy Bucks, everyone's like, I want clippy bucks. 474 00:17:09,339 --> 00:17:11,900 Yeah. I don't care. I'm going to ask 475 00:17:11,900 --> 00:17:13,980 my question That's fair. Because I want a 476 00:17:13,980 --> 00:17:16,059 clippy buck so I can go get these 477 00:17:16,059 --> 00:17:18,940 tokens for these badge. One person had a 478 00:17:18,940 --> 00:17:20,299 goal. They're like, I need to come out 479 00:17:20,299 --> 00:17:22,174 of the session with, like, 25 flippy bucks 480 00:17:22,335 --> 00:17:24,414 Right. Because I want to buy this token 481 00:17:24,414 --> 00:17:26,174 from to take home to my daughter. Yep. 482 00:17:26,174 --> 00:17:27,695 Yep. So we had to make sure they 483 00:17:27,695 --> 00:17:29,875 didn't hog the whole session, but they were 484 00:17:30,095 --> 00:17:32,095 full of they only had 25. I think 485 00:17:32,095 --> 00:17:33,359 they wanted to get to 50. 486 00:17:33,839 --> 00:17:35,599 Just looking at his badge No. How much 487 00:17:35,599 --> 00:17:36,799 do they cost? Well, first of all, I'm 488 00:17:36,799 --> 00:17:38,720 looking at yours because mine doesn't have this 489 00:17:38,720 --> 00:17:40,559 description on the back. Oh. I'm I'm looking 490 00:17:40,559 --> 00:17:43,039 at it because I didn't realize that you 491 00:17:43,039 --> 00:17:45,119 have a the podcast that we are on 492 00:17:45,119 --> 00:17:47,684 right now has a token. And it is 493 00:17:47,684 --> 00:17:49,845 the only one. That was the only one. 494 00:17:49,924 --> 00:17:50,424 Rare. 495 00:17:50,964 --> 00:17:53,204 He made one just for you. Just for 496 00:17:53,204 --> 00:17:54,964 me? That's awesome. But if you would have 497 00:17:54,964 --> 00:17:56,325 sent in your picture, you would have gotten 498 00:17:56,325 --> 00:17:58,980 something that I've gotten into. That's my fault. 499 00:17:59,299 --> 00:18:02,099 Which Yeah. Now what's funny, I now have 500 00:18:02,099 --> 00:18:02,599 a 501 00:18:02,900 --> 00:18:05,140 silhouette that I would have submitted You could've 502 00:18:05,380 --> 00:18:07,779 if I had that earlier. Phoenix twenty twenty 503 00:18:07,779 --> 00:18:09,859 seven. There we go. But no. Because people 504 00:18:09,859 --> 00:18:11,595 wanted those, they were not afraid 505 00:18:12,075 --> 00:18:14,234 to ask questions. Right. In some cases, they 506 00:18:14,234 --> 00:18:17,454 were even looking for how can I participate 507 00:18:17,994 --> 00:18:20,634 in this session Yep? To get Clippy Bucks, 508 00:18:20,634 --> 00:18:22,474 which I don't know I don't know how 509 00:18:22,474 --> 00:18:24,154 all presenters feel. I won't speak for all 510 00:18:24,154 --> 00:18:27,140 presenters. For me, I absolutely love it. 511 00:18:30,720 --> 00:18:32,880 Do you feel overwhelmed by trying to manage 512 00:18:32,880 --> 00:18:35,119 your Office three sixty five environment? Are you 513 00:18:35,119 --> 00:18:38,420 facing unexpected issues that disrupt your company's productivity? 514 00:18:38,720 --> 00:18:40,720 Intelligink is here to help. Much like you 515 00:18:40,720 --> 00:18:42,615 take your car to the mechanic that has 516 00:18:42,615 --> 00:18:44,695 specialized knowledge on how to best keep your 517 00:18:44,695 --> 00:18:47,674 car running, Intelligink helps you with your Microsoft 518 00:18:47,734 --> 00:18:51,255 cloud environment because that's their expertise. Intelligink keeps 519 00:18:51,255 --> 00:18:53,275 up with the latest updates in the Microsoft 520 00:18:53,335 --> 00:18:55,654 cloud to help keep your business running smoothly 521 00:18:55,654 --> 00:18:57,400 and ahead of the curve. Whether you are 522 00:18:57,400 --> 00:18:59,799 a small organization with just a few users 523 00:18:59,799 --> 00:19:02,619 up to an organization of several thousand employees, 524 00:19:02,920 --> 00:19:04,920 they want to partner with you to implement 525 00:19:04,920 --> 00:19:07,579 and administer your Microsoft Cloud technology. 526 00:19:08,359 --> 00:19:11,904 Visit them at inteliginc.com/podcast. 527 00:19:12,205 --> 00:19:18,865 That's intelligink.com/podcast 528 00:19:19,325 --> 00:19:21,404 for more information or to schedule a thirty 529 00:19:21,404 --> 00:19:23,505 minute call to get started with them today. 530 00:19:23,805 --> 00:19:27,140 Remember, Intelligink focuses on the Microsoft cloud so 531 00:19:27,140 --> 00:19:28,839 you can focus on your business. 532 00:19:31,140 --> 00:19:32,900 Back to, I would absolutely do those sessions. 533 00:19:32,900 --> 00:19:34,579 The problem is you don't know that. Yeah. 534 00:19:34,579 --> 00:19:36,740 And I feel like of all again, of 535 00:19:36,740 --> 00:19:38,674 all the councils that I've been to, most 536 00:19:38,674 --> 00:19:39,174 participation 537 00:19:39,714 --> 00:19:41,714 ever out of an audience at this one. 538 00:19:41,714 --> 00:19:43,554 And I truly do think it was in 539 00:19:43,554 --> 00:19:45,394 part due to Clippy Bucks and people just 540 00:19:45,394 --> 00:19:47,554 wanting them and us being able to motivate 541 00:19:47,554 --> 00:19:49,075 them. I may have even tried to bribe 542 00:19:49,075 --> 00:19:51,394 attendees to steal Tim Tams from the session 543 00:19:51,394 --> 00:19:53,894 next door to us with Clippy Bucks here. 544 00:19:54,169 --> 00:19:55,690 For those of you who aren't familiar, Tim 545 00:19:55,690 --> 00:19:58,329 Tams are a delicious chocolate treat. It's a 546 00:19:58,329 --> 00:20:01,049 cookie or a biscuit because it's you're It's 547 00:20:01,049 --> 00:20:03,210 not Australian, so it's a biscuit. So it's 548 00:20:03,210 --> 00:20:05,130 a two layer biscuit filled with a chocolate 549 00:20:05,130 --> 00:20:07,835 cream covered in a chocolate shell. And then 550 00:20:08,295 --> 00:20:09,815 you can eat it normally, like, you would 551 00:20:09,815 --> 00:20:11,414 just take bites of it. But there's something 552 00:20:11,414 --> 00:20:13,414 called a temtem slam, where if you bite 553 00:20:13,414 --> 00:20:15,015 off one corner and then you bite off 554 00:20:15,015 --> 00:20:16,234 the opposite corner, 555 00:20:16,535 --> 00:20:18,694 you can dip it in I do it 556 00:20:18,694 --> 00:20:20,214 with coffee. Kids can do it with hot 557 00:20:20,214 --> 00:20:22,070 chocolate or tea. You dip it in there, 558 00:20:22,070 --> 00:20:23,190 and you hold it in there, and then 559 00:20:23,190 --> 00:20:25,910 you use it like a straw. And it 560 00:20:25,910 --> 00:20:27,990 melts the chocolate cream on the inside. It 561 00:20:27,990 --> 00:20:29,990 softens the cook the biscuit. It makes it 562 00:20:29,990 --> 00:20:32,789 delicious. It's awesome. Highly recommended. And by the 563 00:20:32,789 --> 00:20:34,869 way, they sell Tim Tams at grocery stores 564 00:20:34,869 --> 00:20:36,845 in America now. Not all. But there are 565 00:20:36,845 --> 00:20:39,565 grocery stores. Find some. Yes. But yeah. It's 566 00:20:39,565 --> 00:20:40,065 just 567 00:20:40,605 --> 00:20:42,924 that type of stuff, though, made it more 568 00:20:42,924 --> 00:20:43,805 engaging Yeah. 569 00:20:44,445 --> 00:20:47,404 From all aspects by just having fun with 570 00:20:47,404 --> 00:20:50,899 attendees with it to, I think, driving value 571 00:20:50,960 --> 00:20:53,519 and learning Yes. Out of the sessions through 572 00:20:53,519 --> 00:20:54,419 some of that participation. 573 00:20:54,720 --> 00:20:57,119 Yep. There's also again, I walked into this 574 00:20:57,119 --> 00:20:59,279 thinking it was a security conference, but there 575 00:20:59,279 --> 00:21:01,359 was a women in tech conversation, which was 576 00:21:01,359 --> 00:21:03,440 great. Yep. The conversation's the wrong word. There 577 00:21:03,440 --> 00:21:05,174 was a session on women in technology, a 578 00:21:05,255 --> 00:21:07,195 panel. There was also a panel on neurodiversity, 579 00:21:07,335 --> 00:21:09,414 which I thought was really excellent. They had 580 00:21:09,414 --> 00:21:13,174 three panelists up there with completely different perspectives 581 00:21:13,494 --> 00:21:16,315 not perspectives, completely different Different experiences? 582 00:21:16,695 --> 00:21:19,140 Thank you. With completely different please delete that. 583 00:21:19,220 --> 00:21:21,160 They had a panel on neurodiversity 584 00:21:21,619 --> 00:21:24,359 with three panelists with completely different experiences 585 00:21:25,140 --> 00:21:25,960 in in neurodiversity 586 00:21:26,339 --> 00:21:28,740 with the the way it showed for them, 587 00:21:28,740 --> 00:21:30,680 the way it helped them, the way 588 00:21:31,059 --> 00:21:32,894 it made the I guess, the way it 589 00:21:32,894 --> 00:21:35,454 affected their behavior and their energy and all 590 00:21:35,454 --> 00:21:37,294 of that. And they got to talk through 591 00:21:37,294 --> 00:21:38,034 those experiences, 592 00:21:38,335 --> 00:21:40,674 and I think everyone in the room saw 593 00:21:40,894 --> 00:21:43,054 something about them represented on stage. And it 594 00:21:43,054 --> 00:21:44,894 was super cool to see that at a 595 00:21:44,894 --> 00:21:47,660 technology conference. I think it's just really great 596 00:21:47,660 --> 00:21:49,839 to celebrate what makes us all different 597 00:21:50,140 --> 00:21:51,119 and what 598 00:21:51,500 --> 00:21:53,119 gives us our superpowers, 599 00:21:53,579 --> 00:21:55,500 and it was really it was fun. Yeah. 600 00:21:55,500 --> 00:21:57,759 And a big shout out to John for 601 00:21:57,820 --> 00:21:59,359 organizing this and orchestrating 602 00:21:59,740 --> 00:22:01,339 that part of the conference. Like, that was 603 00:22:01,339 --> 00:22:04,115 super important to him Yep. Going into this 604 00:22:04,115 --> 00:22:05,734 conference to have 605 00:22:06,115 --> 00:22:07,095 that focus 606 00:22:07,634 --> 00:22:09,795 and that that focus and that component and 607 00:22:09,795 --> 00:22:12,035 that aspect to the conference the last couple 608 00:22:12,035 --> 00:22:15,234 days. Yeah. Absolutely. John really busted his tail, 609 00:22:15,234 --> 00:22:16,134 and his team 610 00:22:16,609 --> 00:22:18,769 really busted their tails to make sure that 611 00:22:18,769 --> 00:22:19,509 we had 612 00:22:20,609 --> 00:22:22,230 an a venue, an opportunity, 613 00:22:22,690 --> 00:22:25,109 a place of safety and connectivity. 614 00:22:25,650 --> 00:22:27,650 It was awesome. So my hats off to 615 00:22:27,650 --> 00:22:30,755 them. As someone who has run events not 616 00:22:30,755 --> 00:22:33,414 of quite of this scale, but run events, 617 00:22:34,115 --> 00:22:36,855 pulled schedules together, brought in sponsors, 618 00:22:37,554 --> 00:22:39,794 this was a top notch community event. Yeah. 619 00:22:39,794 --> 00:22:41,474 You have an event coming up. I do. 620 00:22:41,474 --> 00:22:44,054 Are there gonna be Clippy Bucks? Not currently 621 00:22:44,115 --> 00:22:46,089 planned. I'll say it that way. Although, I 622 00:22:46,089 --> 00:22:48,589 don't know. Clippy Bucks might be J bucks. 623 00:22:48,730 --> 00:22:50,269 J bucks. That's too much. 624 00:22:50,889 --> 00:22:53,210 Anyway, so, yes, m $3.65 625 00:22:53,210 --> 00:22:55,690 DC is coming up at the January. It's 626 00:22:55,690 --> 00:22:56,669 a two day event. 627 00:22:57,049 --> 00:23:00,169 I wanna say it's the January. 628 00:23:00,169 --> 00:23:01,309 It's that Thursday, Friday. 629 00:23:01,634 --> 00:23:03,555 The first day, Thursday is gonna be a 630 00:23:03,555 --> 00:23:05,894 workshop day. Okay. So we have 631 00:23:07,555 --> 00:23:09,634 two time slots, a morning workshop and an 632 00:23:09,634 --> 00:23:11,795 afternoon workshop. Three hours each, we'll have lunch 633 00:23:11,795 --> 00:23:13,335 in between. And then 634 00:23:13,669 --> 00:23:15,669 I think we're running six workshops that day. 635 00:23:15,669 --> 00:23:17,029 So three in the morning, three in the 636 00:23:17,029 --> 00:23:20,150 afternoon. Okay. And then the second day and 637 00:23:20,150 --> 00:23:22,470 they are separate tickets just because we wanna 638 00:23:22,470 --> 00:23:23,130 make sure, 639 00:23:23,509 --> 00:23:24,869 a, we don't have as much space on 640 00:23:24,869 --> 00:23:26,390 the workshop day. We wanna give it a 641 00:23:26,390 --> 00:23:27,529 little bit more intimacy 642 00:23:28,054 --> 00:23:30,294 from an education and networking perspective. And then 643 00:23:30,294 --> 00:23:32,234 the second day is all one hour panels 644 00:23:32,454 --> 00:23:35,015 or workshop one hour sessions. And I think 645 00:23:35,015 --> 00:23:37,494 we're targeting something like 50 sessions on the 646 00:23:37,494 --> 00:23:40,134 second day. Nice. Yeah. And, unfortunately, none of 647 00:23:40,134 --> 00:23:41,799 them are gonna be ours. You're running it, 648 00:23:41,799 --> 00:23:43,559 and you have I don't present it things 649 00:23:43,559 --> 00:23:44,859 I run. Yeah. Ours. 650 00:23:45,240 --> 00:23:46,920 I had thought about it. And then you 651 00:23:46,920 --> 00:23:48,619 went, I don't need to go to DC. 652 00:23:49,160 --> 00:23:50,840 Well, it was a little bit late. I've 653 00:23:50,840 --> 00:23:52,700 been doing a conference a month since 654 00:23:53,160 --> 00:23:54,680 August. Yeah. And 655 00:23:55,080 --> 00:23:56,299 As you all know. 656 00:23:56,914 --> 00:23:58,694 Yeah. And then starting in February, 657 00:23:58,994 --> 00:23:59,734 I have 658 00:24:00,355 --> 00:24:03,015 one a one a month, February, March, April. 659 00:24:03,794 --> 00:24:06,515 May, I think. May. I think. Yes. And 660 00:24:06,515 --> 00:24:07,875 your family would like to see you? My 661 00:24:07,875 --> 00:24:09,954 family would like to see me, and my 662 00:24:09,954 --> 00:24:11,714 clients would like to see me get work 663 00:24:11,714 --> 00:24:13,559 done. Yes. Which Yes. 664 00:24:14,039 --> 00:24:16,299 I always go into these with good intentions. 665 00:24:16,359 --> 00:24:18,200 So Yeah. Taking January off, so if you 666 00:24:18,200 --> 00:24:19,099 want to see 667 00:24:20,119 --> 00:24:23,180 a zero trust whiteboard or a conditional access 668 00:24:23,240 --> 00:24:25,400 off the rails, I am officially renaming that 669 00:24:25,400 --> 00:24:27,259 session. It's a good one to do now. 670 00:24:27,394 --> 00:24:28,294 To condition Conditionally 671 00:24:28,674 --> 00:24:29,174 accessed. 672 00:24:29,554 --> 00:24:32,194 Un on on anyway. Yes. Yes. Off the 673 00:24:32,194 --> 00:24:33,634 rails. I don't know when we're gonna do 674 00:24:33,634 --> 00:24:35,154 it again, though. We don't have it. Like, 675 00:24:35,154 --> 00:24:37,234 I have those conferences Yeah. But we don't 676 00:24:37,234 --> 00:24:38,595 have our sessions at any of those. We 677 00:24:38,595 --> 00:24:40,919 need to get on this. Yeah. I should 678 00:24:40,919 --> 00:24:43,159 submit one for m three sixty five conference 679 00:24:43,159 --> 00:24:44,759 Vegas. Maybe I can get us in that 680 00:24:44,759 --> 00:24:47,079 way. When is that one? April. That was 681 00:24:47,079 --> 00:24:49,000 in Orlando. No. Yes. I have a workshop 682 00:24:49,000 --> 00:24:50,539 there. They already picked sessions. 683 00:24:51,000 --> 00:24:53,799 They did, but Microsoft employee sessions haven't been 684 00:24:53,799 --> 00:24:54,299 finalized. 685 00:24:54,694 --> 00:24:56,054 Do you have some you should get one 686 00:24:56,054 --> 00:24:57,414 in, and then I'll come do it with 687 00:24:57,414 --> 00:24:59,414 you. Even if I'm not, like, formally on 688 00:24:59,414 --> 00:25:01,414 the agenda, I'll just show up. Okay. I'll 689 00:25:01,414 --> 00:25:03,095 get that submitted. We'll see what happens. Okay. 690 00:25:03,095 --> 00:25:04,554 I don't know. I'm getting a little 691 00:25:04,855 --> 00:25:07,335 a little sausage make there that maybe I 692 00:25:07,335 --> 00:25:09,710 shouldn't be, but, yes, I will we'll see 693 00:25:09,710 --> 00:25:11,970 about April. How about that? April in Orlando, 694 00:25:12,110 --> 00:25:14,690 the other one we could potentially see about, 695 00:25:14,830 --> 00:25:16,369 how do you feel about Chicago 696 00:25:17,309 --> 00:25:17,809 in 697 00:25:18,190 --> 00:25:18,690 June? 698 00:25:18,990 --> 00:25:21,230 I have not decided if I'm submitting for 699 00:25:21,230 --> 00:25:23,914 Chicago in June. I probably will. Okay. Which 700 00:25:23,914 --> 00:25:25,595 means that I will be gone in February, 701 00:25:25,595 --> 00:25:27,595 March, April, May, and June. Yeah. But those 702 00:25:27,595 --> 00:25:29,195 are fun. Yeah. We should see about maybe 703 00:25:29,195 --> 00:25:30,955 doing one in June, m three sixty five 704 00:25:30,955 --> 00:25:33,755 conference in Chicago. Because that email and everything 705 00:25:33,755 --> 00:25:36,529 just came out. Yeah. Well, either way, if 706 00:25:36,529 --> 00:25:38,690 you're listening to this show by the way, 707 00:25:38,690 --> 00:25:40,930 as an outside observer to the MS Cloud 708 00:25:40,930 --> 00:25:42,769 IT Pro, even though I am a one 709 00:25:42,769 --> 00:25:44,609 time host of the show, I will say 710 00:25:44,609 --> 00:25:46,630 this. You people are awesome. 711 00:25:47,009 --> 00:25:50,289 And I'm specifically referring to the listeners by 712 00:25:50,289 --> 00:25:50,894 you people. 713 00:25:51,375 --> 00:25:53,455 I've met, I don't know, like four people 714 00:25:53,455 --> 00:25:55,695 at this conference. Shocked how many people here 715 00:25:56,095 --> 00:25:58,434 Yep. Had listened to the show because 716 00:25:58,815 --> 00:26:00,095 How many of them do you remember by 717 00:26:00,095 --> 00:26:01,775 name? Love what? How many of them do 718 00:26:01,775 --> 00:26:03,234 you remember by name? Jose. 719 00:26:03,559 --> 00:26:05,960 Jonathan. Jonathan. From the Dallas Stars. I gotta 720 00:26:05,960 --> 00:26:07,179 say that. I'm 721 00:26:07,960 --> 00:26:10,200 a huge Dallas Stars fan. So to nerd 722 00:26:10,200 --> 00:26:12,200 out with with one of the Jonathan, to 723 00:26:12,200 --> 00:26:13,240 nerd out with you is a lot of 724 00:26:13,240 --> 00:26:15,000 fun. So thank you for that. I fell 725 00:26:15,000 --> 00:26:16,919 into your trap of naming names. And if 726 00:26:16,919 --> 00:26:19,875 I forget somebody, I think Felix was one. 727 00:26:20,015 --> 00:26:22,115 You totally fell into my trap. 728 00:26:23,055 --> 00:26:25,134 If you met at the conference and he 729 00:26:25,134 --> 00:26:27,134 forgot to name you here, it's entirely my 730 00:26:27,134 --> 00:26:29,214 fault. It is Jay's fault. Blame him. You 731 00:26:29,214 --> 00:26:31,075 can see what our sessions are like. 732 00:26:32,639 --> 00:26:34,399 I feel like there was one other one, 733 00:26:34,399 --> 00:26:36,559 and I'm sorry I'm forgetting names. I'm gonna 734 00:26:36,559 --> 00:26:37,960 start writing them down. I'm gonna start writing 735 00:26:37,960 --> 00:26:39,839 them down. Who I'm at. You should start 736 00:26:39,839 --> 00:26:42,079 selfie ing. Okay. So here's the thing. Need 737 00:26:42,079 --> 00:26:44,240 to selfie. New rule. If you meet Ben 738 00:26:44,240 --> 00:26:46,704 at a conference, one, you have to say, 739 00:26:46,704 --> 00:26:49,105 hey. I listen to the show. Give me 740 00:26:49,105 --> 00:26:51,204 a sticker. That's the first thing. Yes. Absolutely. 741 00:26:51,664 --> 00:26:53,105 Extra points if you ask for a clippy 742 00:26:53,105 --> 00:26:54,544 buck, which he won't have on him. I 743 00:26:54,544 --> 00:26:56,384 should be able to let him take some 744 00:26:56,384 --> 00:26:59,019 hold. And then two, demand a selfie so 745 00:26:59,019 --> 00:27:00,299 that he can post it. I know you 746 00:27:00,299 --> 00:27:02,859 have social media. Yeah. Demand a selfie that 747 00:27:02,859 --> 00:27:05,340 he can post on social media so that 748 00:27:05,340 --> 00:27:06,779 he can start to to get to know 749 00:27:06,779 --> 00:27:07,980 you all. Yes. And make me do it 750 00:27:07,980 --> 00:27:09,900 because I get back from these conferences, and 751 00:27:09,900 --> 00:27:12,320 I'm like, everybody's posting selfies, and I'm notoriously 752 00:27:12,700 --> 00:27:15,774 bad Yeah. About selfies for So it whatever 753 00:27:15,774 --> 00:27:17,855 reason. So if you're on social media and 754 00:27:17,855 --> 00:27:18,414 you see this 755 00:27:19,375 --> 00:27:21,375 oh, this is terrible. The lighting here is 756 00:27:21,375 --> 00:27:24,095 awful. I'm not trying yeah. The right thanks. 757 00:27:24,095 --> 00:27:26,289 No. Do that. That's where we go. So 758 00:27:26,289 --> 00:27:26,869 if you 759 00:27:27,170 --> 00:27:28,470 see this selfie 760 00:27:28,930 --> 00:27:31,170 that we just took while talking about taking 761 00:27:31,170 --> 00:27:33,250 a selfie, know that this is the new 762 00:27:33,250 --> 00:27:34,529 tradition is you need to take a selfie 763 00:27:34,529 --> 00:27:36,930 with this. And absolutely And Scott. I'm sorry. 764 00:27:36,930 --> 00:27:38,309 Scott. Yes. And Scott. 765 00:27:38,674 --> 00:27:41,394 I May maybe one week's episode, I'll actually 766 00:27:41,394 --> 00:27:43,154 do an episode with Scott just for I 767 00:27:43,234 --> 00:27:45,154 Scott is not gonna trust me anymore after 768 00:27:45,154 --> 00:27:47,394 this week to do podcast episodes. He's gonna 769 00:27:47,394 --> 00:27:49,335 start coming to conferences with me 770 00:27:49,794 --> 00:27:50,855 just to 771 00:27:51,869 --> 00:27:54,269 make sure I don't do anything I'd later 772 00:27:54,269 --> 00:27:56,690 regret on the podcast. It's then mission accomplished. 773 00:27:56,910 --> 00:27:59,329 Yeah. No. But I what is this? Absolutely 774 00:27:59,390 --> 00:28:00,990 come up to me and Scott. Like, I 775 00:28:00,990 --> 00:28:03,230 love meeting people and talking to people that 776 00:28:03,230 --> 00:28:05,009 listen to the show. Yeah. And 777 00:28:05,474 --> 00:28:08,755 I know from an attendee perspective, I have 778 00:28:08,755 --> 00:28:09,974 been an attendee 779 00:28:10,434 --> 00:28:13,234 where, like, do you see certain speakers or 780 00:28:13,234 --> 00:28:15,554 podcasters, like, I don't know that I wanna 781 00:28:15,554 --> 00:28:17,075 talk to them. I wanna Right. Stay in 782 00:28:17,075 --> 00:28:19,220 my little bubble. Please don't ever feel that 783 00:28:19,220 --> 00:28:21,379 way with Scott and I. Like, legitimately just 784 00:28:21,379 --> 00:28:22,579 come up and say, hey. I listened to 785 00:28:22,579 --> 00:28:24,740 the show, or I recognize your voice. That's 786 00:28:24,740 --> 00:28:26,419 the most common one I get. I heard 787 00:28:26,419 --> 00:28:29,299 that. Podcast. I know that voice. Yeah. That's 788 00:28:29,299 --> 00:28:31,940 awesome. It's fun. I absolutely love it. Yeah. 789 00:28:31,940 --> 00:28:34,055 So Alright. For that, we I feel like 790 00:28:34,055 --> 00:28:35,815 we should wrap. We should because we need 791 00:28:35,815 --> 00:28:37,095 to go find out who won Flip the 792 00:28:37,095 --> 00:28:39,174 Awards. Okay. But it was neither you nor 793 00:28:39,174 --> 00:28:40,955 I because we weren't nominated. 794 00:28:41,894 --> 00:28:43,575 Yeah. I was kinda sad about that. There 795 00:28:43,575 --> 00:28:44,474 should have been, like, 796 00:28:44,775 --> 00:28:45,515 a new 797 00:28:45,974 --> 00:28:48,455 new to the workplace ninjas clip Yeah. And 798 00:28:48,455 --> 00:28:49,630 I was kinda new to the whole thing, 799 00:28:49,630 --> 00:28:51,630 and I didn't quite know how nominations work 800 00:28:51,630 --> 00:28:53,309 or how people got in there. Wasn't even 801 00:28:53,309 --> 00:28:54,829 on my phone. Had I known, I would 802 00:28:54,829 --> 00:28:56,589 have nominated you. You could have nominated me, 803 00:28:56,589 --> 00:28:57,890 and we would have been in there. 804 00:28:58,670 --> 00:29:00,049 It would have been a fix. 805 00:29:00,670 --> 00:29:03,284 Listen. It's been fun. MS Cloud IT Pro 806 00:29:03,284 --> 00:29:04,804 listeners, thank you so much for joining us 807 00:29:04,804 --> 00:29:07,765 for another episode of Jay's Takeover on Hot 808 00:29:07,765 --> 00:29:10,484 Stop. Takeover. Alright. Thanks, Jay. We'll talk to 809 00:29:10,484 --> 00:29:12,024 you next time. Take care. 810 00:29:14,005 --> 00:29:16,244 If you enjoyed the podcast, go leave us 811 00:29:16,244 --> 00:29:18,440 a five star rating in iTunes. It helps 812 00:29:18,440 --> 00:29:20,119 to get the word out so more IT 813 00:29:20,119 --> 00:29:22,279 pros can learn about Office three sixty five 814 00:29:22,279 --> 00:29:22,940 and Azure. 815 00:29:23,480 --> 00:29:25,160 If you have any questions you want us 816 00:29:25,160 --> 00:29:27,320 to address on the show, or feedback about 817 00:29:27,320 --> 00:29:29,720 the show, feel free to reach out via 818 00:29:29,720 --> 00:29:31,900 our website, Twitter, or Facebook. 819 00:29:32,289 --> 00:29:34,049 Thanks again for listening, and have a great 820 00:29:34,049 --> 00:29:34,549 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