Episode 418 – An Anti-AI Adventure with Cat Schneider: SharePoint, Power Automate, and Conference Shenanigans

January 01, 2026

Episode Transcript

Welcome to Episode 418 of the Microsoft Cloud IT Pro Podcast. In this episode, Ben sits down with Cat Schneider during a lively conference to discuss a variety of topics, focusing on the theme of “anti-AI.” They reflect on life and technology before AI became prominent, sharing tales of conferences, hackathons, and explorations of older tech solutions. They also discuss some of Cat’s adventures in SharePoint and Power Platform, including managing SharePoint permissions with flows, the challenges of migrating file shares to SharePoint, syncing issues with OneDrive, and practical uses of Power BI for troubleshooting and managing SharePoint data. Additionally, they dive into humorous conference anecdotes from the inaugural Workplace Ninjas US, including accidental late-night adventures.

Cat Schneider is an experienced data specialist and Power Platform, SharePoint, and Teams enthusiast with a demonstrated history of innovation for almost 15 years in the public sector. Cat is skilled in Microsoft-based applications, quality assurance, and databases. She is a strong community and social services professional with a Bachelor of Science (B.S.) in Biology from Florida State University. In addition to being a self-taught coder with a never-ending thirst for learning more—and helping others learn and improve their coding skills—she is also co-leader of the Power Platform UX/UI and Accessibility (A11y) Global User Group.

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,439 --> 00:00:05,839 Welcome to episode 418 2 00:00:05,839 --> 00:00:08,419 of the Microsoft Cloud IT Pro podcast, 3 00:00:08,720 --> 00:00:11,300 our first episode of 2026, 4 00:00:11,439 --> 00:00:15,324 recorded live from Workplace Ninjas US in December 5 00:00:15,324 --> 00:00:16,135 2025. 6 00:00:16,355 --> 00:00:18,675 This is a show about Microsoft three sixty 7 00:00:18,675 --> 00:00:20,835 five and Azure from the perspective of IT 8 00:00:20,835 --> 00:00:23,074 pros and end users, where we discuss a 9 00:00:23,074 --> 00:00:25,314 topic or recent news and how it relates 10 00:00:25,314 --> 00:00:25,974 to you. 11 00:00:26,274 --> 00:00:29,329 In today's episode, Kat Schneider and I just 12 00:00:29,329 --> 00:00:31,329 sit down with a goal of having an 13 00:00:31,329 --> 00:00:34,289 anti AI chat with no real idea where 14 00:00:34,289 --> 00:00:36,369 this adventure might take us. In the end, 15 00:00:36,369 --> 00:00:38,530 we enjoyed a conversation about some of the 16 00:00:38,530 --> 00:00:41,250 solutions Kat has built using the Power Platform 17 00:00:41,250 --> 00:00:41,909 and SharePoint. 18 00:00:42,245 --> 00:00:44,325 We talk a bit about OneDrive sync and 19 00:00:44,325 --> 00:00:46,725 libraries in SharePoint, and just some of the 20 00:00:46,725 --> 00:00:49,125 fun times from the conference, which you should 21 00:00:49,125 --> 00:00:52,164 totally join us for in February 2027 in 22 00:00:52,164 --> 00:00:52,664 Arizona. 23 00:00:53,125 --> 00:00:56,164 Hope you enjoy the anti episode chat with 24 00:00:56,164 --> 00:00:56,460 Cat. 25 00:00:58,700 --> 00:01:01,259 We are sitting here with Kat Schneider. I 26 00:01:01,259 --> 00:01:03,259 said it right. Right? You're listening right? Perfect. 27 00:01:03,259 --> 00:01:05,819 Yeah. Kat Schneider at Workplace Ninjas again. This 28 00:01:05,819 --> 00:01:07,500 is like my third fourth? I think it's 29 00:01:07,659 --> 00:01:09,920 Forty third? Fourth? No. Fourth episode 30 00:01:10,459 --> 00:01:12,944 Oh. I've recorded while I'm here. Wow. It's 31 00:01:12,944 --> 00:01:15,744 been busy. It Yeah. It's been hopping around 32 00:01:15,744 --> 00:01:17,104 here. It has been it's been a good 33 00:01:17,104 --> 00:01:20,465 conference. Yeah. I've I've enjoyed it. I've never 34 00:01:20,465 --> 00:01:22,165 gone to a security conference before. 35 00:01:23,584 --> 00:01:25,504 How do you feel about a bunch of 36 00:01:25,504 --> 00:01:27,045 security people at a conference? 37 00:01:27,730 --> 00:01:29,409 I feel like there's not enough talk of 38 00:01:29,409 --> 00:01:31,650 security yet. Is it has it reached a 39 00:01:31,650 --> 00:01:33,510 new level of nerd? It definitely 40 00:01:34,209 --> 00:01:35,590 has been an interesting 41 00:01:36,130 --> 00:01:38,450 experience for sure. It's definitely not a Power 42 00:01:38,450 --> 00:01:41,030 Platform conference. No. Definitely not a Power Platform. 43 00:01:41,250 --> 00:01:42,549 And it is not 44 00:01:42,995 --> 00:01:44,055 an AI conference. 45 00:01:44,435 --> 00:01:46,515 Definitely not. Which is what we're doing. We 46 00:01:46,515 --> 00:01:48,454 came up with this. We did a hackathon 47 00:01:48,995 --> 00:01:49,575 a day. 48 00:01:49,954 --> 00:01:50,454 Monday. 49 00:01:50,915 --> 00:01:53,034 Yep. Monday. Monday. Today's Wednesday. Is that when 50 00:01:53,034 --> 00:01:54,594 we were talking about recording this? And we 51 00:01:54,594 --> 00:01:56,614 said we're gonna do an anti AI episode. 52 00:01:57,040 --> 00:01:58,340 Yeah. We did. 53 00:01:59,280 --> 00:02:00,719 It was at the speakers dinner on the 54 00:02:00,719 --> 00:02:03,200 way to speakers dinner. Something like that. It 55 00:02:03,200 --> 00:02:05,200 was That was probably the problem of coming 56 00:02:05,200 --> 00:02:07,359 up with this. Yeah. And we said We're 57 00:02:07,359 --> 00:02:09,039 gonna do an anti AI episode. So we're 58 00:02:09,039 --> 00:02:11,219 sitting down to record an anti AI episode. 59 00:02:11,615 --> 00:02:13,555 We're like, what do we talk about? 60 00:02:14,574 --> 00:02:16,254 I didn't tell somebody how to be asked. 61 00:02:16,254 --> 00:02:18,254 So What is the opposite of AI? What 62 00:02:18,254 --> 00:02:20,895 is the opposite of AI? Or what was 63 00:02:20,895 --> 00:02:21,395 life 64 00:02:21,694 --> 00:02:23,855 This is like a time capsule episode. What 65 00:02:23,855 --> 00:02:25,074 was life like 66 00:02:25,509 --> 00:02:27,509 back when I was a kid before we 67 00:02:27,509 --> 00:02:29,689 had a high? Back in my day. 68 00:02:30,150 --> 00:02:32,229 I had to walk uphill both ways to 69 00:02:32,229 --> 00:02:33,530 school in the snow. In snow. 70 00:02:34,389 --> 00:02:36,710 Yeah. My god. All the way back to 71 00:02:36,710 --> 00:02:38,090 my dad's days. Jesus. 72 00:02:38,425 --> 00:02:40,104 Right? Well, it's funny because I've been talking 73 00:02:40,104 --> 00:02:41,944 to people here and I'm like, I got 74 00:02:41,944 --> 00:02:44,205 my start in like, Cheerpoint 2003, 75 00:02:44,425 --> 00:02:46,604 2007. I was still in school. 76 00:02:47,625 --> 00:02:49,544 Yeah. We were in the car the other 77 00:02:49,544 --> 00:02:51,224 day and Jay said, he's like, Ben, we're 78 00:02:51,224 --> 00:02:52,685 the old men in the car. 79 00:02:54,789 --> 00:02:56,150 Awesome. Oh. I think I was the youngest 80 00:02:56,150 --> 00:02:57,209 one in the car. 81 00:02:57,909 --> 00:02:59,989 I was like, is it really come to 82 00:02:59,989 --> 00:03:01,590 that that I'm now the old man at 83 00:03:01,590 --> 00:03:03,590 these conferences? I used to be the one 84 00:03:03,590 --> 00:03:05,430 that I go to these conferences at like, 85 00:03:05,430 --> 00:03:07,509 when I was doing SharePoint 2007 and they're 86 00:03:07,509 --> 00:03:10,264 like, they're talking about before SharePoint 2001. I'm 87 00:03:10,264 --> 00:03:11,944 like, I was in kindergarten when you did 88 00:03:11,944 --> 00:03:12,444 that. 89 00:03:12,824 --> 00:03:14,824 I'm on the opposite side of that now. 90 00:03:14,824 --> 00:03:15,724 Yeah. Now 91 00:03:16,105 --> 00:03:18,745 you're the guy that everybody talks about. In 92 00:03:18,745 --> 00:03:19,485 a good way. 93 00:03:20,344 --> 00:03:22,264 What are they saying about me? Because my 94 00:03:22,264 --> 00:03:24,739 sessions have got little we may have gotten 95 00:03:24,739 --> 00:03:26,580 a little wild this week in our sessions. 96 00:03:26,580 --> 00:03:28,180 Did you have you heard about any of 97 00:03:28,180 --> 00:03:30,099 our sessions? I have not heard a peep 98 00:03:30,099 --> 00:03:31,860 about any of the sessions, but I also 99 00:03:31,860 --> 00:03:34,439 have been a little off the rails myself. 100 00:03:34,500 --> 00:03:36,659 It was we may have so there's a 101 00:03:36,659 --> 00:03:38,715 bunch of people with Tim Tams here. Yes. 102 00:03:38,794 --> 00:03:40,955 Okay. So about this conference, so many Tim 103 00:03:40,955 --> 00:03:43,435 Tams here. So many. And another thing about 104 00:03:43,435 --> 00:03:45,514 this conference that as I look back, I 105 00:03:45,514 --> 00:03:46,715 I didn't know how it was gonna go 106 00:03:46,715 --> 00:03:48,314 going into it. I really like it. You 107 00:03:48,314 --> 00:03:51,034 have clippy bucks at this conference. So many 108 00:03:51,034 --> 00:03:53,009 clippy bucks. That we get as speakers and 109 00:03:53,009 --> 00:03:54,289 we can hand them out. And we get 110 00:03:54,289 --> 00:03:56,530 to make it rain. Yes. And we can 111 00:03:56,530 --> 00:03:58,389 use them to bribe attendees. 112 00:03:58,770 --> 00:04:00,469 Yes. 100%. 113 00:04:00,530 --> 00:04:03,330 Or incentivize them. Which I think one thing, 114 00:04:03,330 --> 00:04:07,425 it's definitely incentivized conversations. People here have talked 115 00:04:07,665 --> 00:04:10,385 way more freely, asked way more questions, been 116 00:04:10,385 --> 00:04:11,044 way more 117 00:04:11,344 --> 00:04:11,844 participatory, 118 00:04:12,465 --> 00:04:15,264 is that a word? Participants are. Yes. Designed 119 00:04:15,264 --> 00:04:15,764 sessions. 120 00:04:16,144 --> 00:04:18,324 Because of these, we tried to get attendees 121 00:04:18,705 --> 00:04:20,949 last night in our session to go steal 122 00:04:20,949 --> 00:04:23,289 Tim Tam's from the session next to ours 123 00:04:23,430 --> 00:04:25,829 with Clippy Bucks. Oh my god. It didn't 124 00:04:25,829 --> 00:04:27,349 work. Damn. But it would have been really 125 00:04:27,349 --> 00:04:29,349 funny Yeah. To see them, like, run out 126 00:04:29,349 --> 00:04:30,949 and try to run back in with Tim 127 00:04:30,949 --> 00:04:32,245 Tam's and hear the session next to ours. 128 00:04:32,245 --> 00:04:33,050 That would be fantastic. 129 00:04:33,589 --> 00:04:35,430 Yeah. Anyways, that's the type of sessions we've 130 00:04:35,430 --> 00:04:37,454 had this week. Yeah. No. I definitely have 131 00:04:37,454 --> 00:04:39,294 talked a lot about AI in sessions this 132 00:04:39,294 --> 00:04:41,235 week, which is why I was anti AI. 133 00:04:41,294 --> 00:04:43,935 Okay. But So what did we do? Anti 134 00:04:43,935 --> 00:04:46,354 AI back when we were kids Oh, my 135 00:04:46,414 --> 00:04:48,930 gosh. And we were doing this, you were 136 00:04:48,930 --> 00:04:49,990 talking about 137 00:04:50,529 --> 00:04:51,889 We don't know what we're gonna talk. We 138 00:04:51,889 --> 00:04:54,310 tried to come up with ideas. Flows, SharePoint, 139 00:04:54,529 --> 00:04:57,650 like, before AI. Yeah. We can't talk about 140 00:04:57,650 --> 00:04:59,350 AI, so we can't compare and contrast. 141 00:04:59,889 --> 00:05:02,175 Yeah. But I think some of these solutions, 142 00:05:02,175 --> 00:05:03,774 like you were talking about some of the 143 00:05:03,774 --> 00:05:06,254 flows you built Mhmm. Because it was flow 144 00:05:06,254 --> 00:05:08,095 back then. Yeah. It was We started talking 145 00:05:08,095 --> 00:05:09,454 about flow, and we both knew what we 146 00:05:09,454 --> 00:05:10,654 were talking about. Yeah. Even though it's power 147 00:05:10,654 --> 00:05:11,534 automate. And you were like, oh, wait. No. 148 00:05:11,534 --> 00:05:13,935 It's power automate. Definitely power automate. Definitely did 149 00:05:13,935 --> 00:05:15,074 not mix that one up. 150 00:05:15,375 --> 00:05:16,590 It I was like, we should just sit 151 00:05:16,590 --> 00:05:18,509 and talk about, like, some of what we 152 00:05:18,509 --> 00:05:21,970 did Yeah. Before AI because I think there's 153 00:05:22,030 --> 00:05:25,389 so many conversations about AI now that sometimes 154 00:05:25,389 --> 00:05:28,030 you we forget about Mhmm. Let's go do 155 00:05:28,030 --> 00:05:31,365 something that's not AI Yeah. That's anti AI. 156 00:05:31,524 --> 00:05:33,604 Because it's so refreshing to be, like, back 157 00:05:33,604 --> 00:05:35,845 to basics. Yeah. And one of them you 158 00:05:35,845 --> 00:05:37,925 were talking about that I'm, like, I never 159 00:05:37,925 --> 00:05:40,644 thought about this was SharePoint permissions with flows 160 00:05:40,884 --> 00:05:43,444 Yes. Was something you did. Yes. So tell 161 00:05:43,444 --> 00:05:45,604 us about SharePoint permissions and flows and the 162 00:05:45,604 --> 00:05:46,664 solution. Okay. 163 00:05:47,339 --> 00:05:48,699 Okay. What we were trying to do is 164 00:05:48,699 --> 00:05:51,599 we were trying to manage our SharePoint permissions. 165 00:05:51,819 --> 00:05:52,800 We were trying to 166 00:05:53,259 --> 00:05:53,759 identify 167 00:05:54,699 --> 00:05:57,419 who was in what cost center doing what 168 00:05:57,419 --> 00:05:59,919 job and how they were all involved and 169 00:06:04,165 --> 00:06:04,665 have 170 00:06:05,125 --> 00:06:05,785 a nice landing page for 171 00:06:07,285 --> 00:06:09,444 a call center so people knew, like, oh, 172 00:06:09,444 --> 00:06:10,964 okay. This is who I go to and 173 00:06:10,964 --> 00:06:12,725 this is where I can ask questions and 174 00:06:12,725 --> 00:06:15,944 whatnot. Okay. And so I was like, well, 175 00:06:16,220 --> 00:06:19,100 if we're gonna do that and we're gonna 176 00:06:19,100 --> 00:06:22,139 have this information already in SharePoint because it's 177 00:06:22,139 --> 00:06:25,259 associated with people pickers Yep. Like, why not 178 00:06:25,259 --> 00:06:26,639 just put it in a list 179 00:06:27,100 --> 00:06:28,720 that somebody can manage? 180 00:06:29,074 --> 00:06:31,154 They literally, the cost center manager will be 181 00:06:31,154 --> 00:06:32,595 like, oh, hey, I got a new manager. 182 00:06:32,595 --> 00:06:34,274 I'm gonna go put my new manager's name 183 00:06:34,274 --> 00:06:36,514 over here so people know that, hey, this 184 00:06:36,514 --> 00:06:39,314 is my new manager. Okay. Like, the managers 185 00:06:39,314 --> 00:06:41,634 can manage the people that work for them 186 00:06:41,634 --> 00:06:42,375 and below. 187 00:06:42,680 --> 00:06:44,199 Kinda makes sense. Right? Isn't that what they're 188 00:06:44,199 --> 00:06:45,500 supposed to do? It's so 189 00:06:45,959 --> 00:06:48,220 crazy idea. It was Mind blowing. 190 00:06:48,839 --> 00:06:49,580 Breaking technology. 191 00:06:51,879 --> 00:06:54,040 I'm like, why don't we just, I don't 192 00:06:54,040 --> 00:06:56,220 know, do what we're supposed to be doing 193 00:06:56,360 --> 00:06:58,685 and manage the permissions this way? And so 194 00:06:58,685 --> 00:07:01,004 I ended up building a list Yeah. Right. 195 00:07:01,245 --> 00:07:02,144 That incorporate, 196 00:07:02,444 --> 00:07:05,105 like, that that thing back in the day, 197 00:07:05,404 --> 00:07:07,024 the code called JSON. 198 00:07:07,644 --> 00:07:09,745 Yes. Yeah. Where you could, like, 199 00:07:10,470 --> 00:07:13,689 show the list in very specific format and, 200 00:07:13,910 --> 00:07:15,990 you know, there was tools that you could 201 00:07:15,990 --> 00:07:18,410 have in browser so that you could format 202 00:07:18,470 --> 00:07:21,990 your the SP formatter tool. Yep. Fantastic tool. 203 00:07:21,990 --> 00:07:23,349 I love that tool. And that's even newer 204 00:07:23,349 --> 00:07:25,644 than I mentioned SharePoint Designer and you laughed 205 00:07:25,644 --> 00:07:26,305 at me. 206 00:07:26,685 --> 00:07:28,365 Oh, I've used SharePoint Designer and I was 207 00:07:28,365 --> 00:07:30,305 like, oh, I hated that thing so much. 208 00:07:30,685 --> 00:07:31,664 Hated it. Okay. 209 00:07:32,125 --> 00:07:34,365 Anyways, back to Visual Studio Code and JSON. 210 00:07:34,365 --> 00:07:36,524 Yes. Well, no, because I'm still in the 211 00:07:36,524 --> 00:07:37,964 browser. I haven't even made it to Visual 212 00:07:37,964 --> 00:07:39,939 Studio Code yet. Oh, yes. That's right. Yeah. 213 00:07:39,939 --> 00:07:41,000 No. So JSON, 214 00:07:41,379 --> 00:07:43,139 we're managing that list in JSON. So I 215 00:07:43,139 --> 00:07:45,060 could have, like, their picture from their profile, 216 00:07:45,060 --> 00:07:46,740 like, show up nice and big. Doing the 217 00:07:46,740 --> 00:07:48,259 whole list formatting. Yeah. I was I was 218 00:07:48,259 --> 00:07:50,360 doing all kinds of fancy things. And then 219 00:07:50,420 --> 00:07:52,819 I was also incorporating the list on the 220 00:07:52,819 --> 00:07:55,915 front page, like, the home page. Okay. And 221 00:07:55,915 --> 00:07:56,415 so 222 00:07:56,875 --> 00:07:58,495 you could click on the person's 223 00:07:59,035 --> 00:07:59,855 or their picture 224 00:08:00,155 --> 00:08:02,235 or click on the little email icon that 225 00:08:02,235 --> 00:08:04,235 I incorporated with it, and then you could 226 00:08:04,235 --> 00:08:05,754 send them an email or you could open 227 00:08:05,754 --> 00:08:07,355 up a Teams chat and, like, you could 228 00:08:07,355 --> 00:08:09,410 do all these crazy things. And then when 229 00:08:09,410 --> 00:08:11,189 somebody moved in or out 230 00:08:11,649 --> 00:08:15,270 of a position, like, say, somebody moved on 231 00:08:15,410 --> 00:08:16,149 to another 232 00:08:16,449 --> 00:08:18,370 spot within the agency and I wasn't managing 233 00:08:18,370 --> 00:08:19,889 their SharePoint collection and they had to do 234 00:08:19,889 --> 00:08:21,895 their own thing Uh-huh. They just got moved 235 00:08:21,895 --> 00:08:23,735 out and they lost all their permissions to 236 00:08:23,735 --> 00:08:26,375 access anything in Teams or any of the 237 00:08:26,375 --> 00:08:28,535 SharePoint that it was being managed by. Like, 238 00:08:28,535 --> 00:08:31,495 I was managing lots of permissions, like, even 239 00:08:31,495 --> 00:08:32,235 for Teams 240 00:08:32,774 --> 00:08:35,480 groups and whatnot from the SharePoint list. From 241 00:08:35,480 --> 00:08:38,039 the SharePoint. So was that, like, one central 242 00:08:38,039 --> 00:08:40,039 SharePoint list that everybody was in there? Did 243 00:08:40,039 --> 00:08:41,980 you have separate SharePoint list for each 244 00:08:42,839 --> 00:08:46,039 call center? Or For each call center, I 245 00:08:46,039 --> 00:08:48,524 had their own site collection because I didn't 246 00:08:48,524 --> 00:08:51,245 want finance and accounting to be able to 247 00:08:51,245 --> 00:08:54,764 manage To change permissions for another department. For 248 00:08:54,764 --> 00:08:57,365 them to be changing permissions for HR and 249 00:08:57,644 --> 00:08:59,004 Yeah. Yeah. That's what I'm saying. It was 250 00:08:59,004 --> 00:09:00,365 all over the place. So I was like, 251 00:09:00,365 --> 00:09:02,044 you get a site collection and you get 252 00:09:02,044 --> 00:09:03,970 a site collection. I was just Oprah. Oh, 253 00:09:03,970 --> 00:09:05,809 yeah. Just handing out site collections left and 254 00:09:05,809 --> 00:09:07,690 right. Yeah. Even though the SharePoint team was 255 00:09:07,690 --> 00:09:11,110 like about governance of SharePoint sites. Yeah. So 256 00:09:11,570 --> 00:09:12,230 I ended 257 00:09:12,850 --> 00:09:15,169 up being really close friends with our SharePoint 258 00:09:15,169 --> 00:09:17,715 governance Why? Folks. And I was like, I 259 00:09:17,715 --> 00:09:19,634 need another site collection. I'm like, oh, would 260 00:09:19,634 --> 00:09:21,335 you please just use the form? 261 00:09:22,595 --> 00:09:24,115 And I'm like, I will, but just know 262 00:09:24,115 --> 00:09:25,475 it's coming and this is what I want 263 00:09:25,475 --> 00:09:27,235 it to be named and don't go naming 264 00:09:27,235 --> 00:09:28,294 it anything crazy. 265 00:09:28,595 --> 00:09:30,434 So, like, there was all of that. And 266 00:09:30,434 --> 00:09:32,779 then I would be the site collection administrator 267 00:09:33,159 --> 00:09:34,519 and go in there and do all of 268 00:09:34,519 --> 00:09:37,000 that fun stuff. Okay. But, yeah. The I 269 00:09:37,000 --> 00:09:38,039 would go in there. I would set it 270 00:09:38,039 --> 00:09:39,320 up for them. I would set up their 271 00:09:39,320 --> 00:09:39,820 teams 272 00:09:40,360 --> 00:09:43,320 and get this one single SharePoint list. And 273 00:09:43,320 --> 00:09:45,019 then every time it got updated, 274 00:09:45,335 --> 00:09:47,335 it would kick off a Power Automate instant 275 00:09:47,335 --> 00:09:50,054 flow. Okay. Like a, automated flow. That's a 276 00:09:50,054 --> 00:09:53,654 mouthful. A Power Automate instant flow. Yeah. And 277 00:09:53,654 --> 00:09:56,715 it would say, oh, hey. This list item 278 00:09:56,934 --> 00:09:57,434 changed. 279 00:09:57,894 --> 00:09:59,115 What was the change? 280 00:09:59,590 --> 00:10:01,110 And I actually got it to the point 281 00:10:01,110 --> 00:10:03,110 I was able to go back into the 282 00:10:03,110 --> 00:10:04,409 previous version 283 00:10:05,190 --> 00:10:07,690 of that list item to see what was 284 00:10:08,149 --> 00:10:10,670 the value of that people picker before Uh-huh. 285 00:10:10,870 --> 00:10:12,309 And what is the value of the people 286 00:10:12,309 --> 00:10:13,129 picker now 287 00:10:13,434 --> 00:10:15,434 and be able to revoke permissions and grant 288 00:10:15,434 --> 00:10:16,815 permissions based on 289 00:10:17,195 --> 00:10:19,115 which it was. So So you're just adding 290 00:10:19,115 --> 00:10:20,654 and removing people then from the SharePoint 291 00:10:21,115 --> 00:10:24,075 permission group SharePoint groups. Yeah. Yeah. Like, I 292 00:10:24,075 --> 00:10:25,295 would have individual 293 00:10:25,835 --> 00:10:28,235 specific permissions, and then I would make it 294 00:10:28,235 --> 00:10:31,240 so that, like, that specific list, I didn't 295 00:10:31,240 --> 00:10:33,899 use groups per se, but everywhere else, 296 00:10:34,200 --> 00:10:36,200 there were groups. There were groups. Yeah. And 297 00:10:36,200 --> 00:10:38,519 then managers could essentially manage their own users' 298 00:10:38,519 --> 00:10:40,440 permission. Were they owners of their own SharePoint 299 00:10:40,440 --> 00:10:42,200 sites, or did this let you manage their 300 00:10:42,200 --> 00:10:44,205 permissions without them being owners of the sites? 301 00:10:44,365 --> 00:10:44,865 So 302 00:10:45,404 --> 00:10:47,644 I would not allow them to be full 303 00:10:47,644 --> 00:10:48,144 owners. 304 00:10:48,524 --> 00:10:50,684 Okay. Because if you let them be full 305 00:10:50,684 --> 00:10:53,004 owners, then they'll go in and delete something, 306 00:10:53,004 --> 00:10:54,625 and you're like, what are you doing? 307 00:10:55,485 --> 00:10:57,819 Because while version history was a thing, you 308 00:10:57,819 --> 00:10:59,899 can still delete something and then not be 309 00:10:59,899 --> 00:11:01,259 able to recover it. And then I wanted 310 00:11:01,259 --> 00:11:03,419 to murder people. But, you know Yeah. Working 311 00:11:03,419 --> 00:11:05,679 for the state, murder's frowned upon. 312 00:11:07,740 --> 00:11:10,639 I'm I'm I'm glad you refrained 313 00:11:11,100 --> 00:11:12,539 that we get to sit here and have 314 00:11:12,539 --> 00:11:13,279 this conversation 315 00:11:13,794 --> 00:11:15,335 here versus in jail somewhere? 316 00:11:17,075 --> 00:11:20,375 She was having this conversation with barks between 317 00:11:20,754 --> 00:11:23,014 us. Why would I why are you incarcerated? 318 00:11:23,394 --> 00:11:25,075 Jail so I can interview Kat about her 319 00:11:25,075 --> 00:11:27,779 SharePoint work and Why were you incarcerated? Because 320 00:11:27,779 --> 00:11:29,960 I murdered somebody for their SharePoint permissions? 321 00:11:31,220 --> 00:11:32,440 Oh, that would be fantastic. 322 00:11:33,139 --> 00:11:36,340 My. That's like a whole other side quest 323 00:11:36,340 --> 00:11:37,559 that I feel like 324 00:11:37,860 --> 00:11:39,639 needs to be unlocked somewhere. 325 00:11:40,019 --> 00:11:40,759 Oh, god. 326 00:11:41,524 --> 00:11:43,205 This is going even more off the rails 327 00:11:43,205 --> 00:11:46,105 than my sessions this week. Too much caffeine, 328 00:11:46,644 --> 00:11:49,625 too little sleep. And way too many shenanigans. 329 00:11:50,085 --> 00:11:52,585 Too many shenanigans. Actually, it was the ninjas. 330 00:11:52,725 --> 00:11:54,404 I blame it on the ninjas. The ninjas? 331 00:11:54,404 --> 00:11:56,379 I got a selfie with the ninjas. Oh, 332 00:11:56,379 --> 00:11:58,019 did you? I did. Oh, you did? I 333 00:11:58,019 --> 00:11:59,419 did that. I was in the speaker room 334 00:11:59,419 --> 00:12:00,860 and they were like, oh, can we take 335 00:12:00,860 --> 00:12:02,879 a picture? Because there was a workplace Ninjas 336 00:12:03,419 --> 00:12:04,699 sign on the door. Yeah. They went on 337 00:12:04,699 --> 00:12:06,299 a picture with them behind the glass with 338 00:12:06,299 --> 00:12:08,059 a sign in front. So I'm like sitting 339 00:12:08,059 --> 00:12:09,980 here working away and they're off behind me 340 00:12:09,980 --> 00:12:11,955 and doing their photo op. 341 00:12:12,514 --> 00:12:13,654 And I'm like, Can I get a picture? 342 00:12:15,315 --> 00:12:17,495 A 100%, that was definitely required. 343 00:12:17,795 --> 00:12:20,115 Yes. And accidentally going out at night, that 344 00:12:20,115 --> 00:12:21,335 was something else that came up this week. 345 00:12:21,335 --> 00:12:22,915 Yeah. But we couldn't accidentally go out at 346 00:12:22,915 --> 00:12:23,495 night. But 347 00:12:24,035 --> 00:12:25,634 I I started to see how it happened 348 00:12:25,634 --> 00:12:28,290 because we came back from, we went out 349 00:12:28,290 --> 00:12:30,450 to watch the Dallas Stars game last night. 350 00:12:30,450 --> 00:12:31,809 We came back and Jay and I were 351 00:12:31,809 --> 00:12:33,009 both like, oh, we're tired we need to 352 00:12:33,009 --> 00:12:34,129 go to bed, we need to get work 353 00:12:34,129 --> 00:12:34,950 done. And 354 00:12:35,330 --> 00:12:37,570 we walked out of the lobby. And we 355 00:12:37,570 --> 00:12:39,570 accidentally sat down in the lobby with a 356 00:12:39,570 --> 00:12:41,410 bunch of other people and got up an 357 00:12:41,410 --> 00:12:42,149 hour later. 358 00:12:43,384 --> 00:12:44,745 Yeah. I heard there were a lot of 359 00:12:44,745 --> 00:12:47,544 sushi boats involved last night. I saw a 360 00:12:47,544 --> 00:12:49,225 picture. I do not eat sushi, so I 361 00:12:49,225 --> 00:12:51,144 don't have the appreciation for it. But the 362 00:12:51,144 --> 00:12:53,304 pictures, it was a lot of sushi. I 363 00:12:53,384 --> 00:12:55,464 So I didn't see all of these pictures 364 00:12:55,464 --> 00:12:57,790 that apparently are going around, but I got 365 00:12:57,790 --> 00:13:00,350 one picture of one boat. One boat with 366 00:13:00,350 --> 00:13:02,990 92 pieces of sushi in one boat? Yes. 367 00:13:02,990 --> 00:13:04,430 And there were I heard there were at 368 00:13:04,430 --> 00:13:06,830 least three boats. I heard somebody ate one 369 00:13:06,830 --> 00:13:08,590 boat all on their own. I wonder if 370 00:13:08,590 --> 00:13:10,750 they're here today or They are? Are they 371 00:13:10,750 --> 00:13:11,570 doing okay? 372 00:13:12,164 --> 00:13:14,084 They seem to be standing on their own 373 00:13:14,084 --> 00:13:16,424 two feet, but just fine. Alright. 374 00:13:17,205 --> 00:13:18,884 That was a lot of sushi. That's a 375 00:13:18,884 --> 00:13:19,865 lot of sushi. 376 00:13:20,644 --> 00:13:23,945 Wow. And our friend who may have accidentally 377 00:13:24,084 --> 00:13:26,399 gone out. Did he? He accidentally went out 378 00:13:26,399 --> 00:13:28,399 with them. Accidentally go out with them? I 379 00:13:28,399 --> 00:13:30,419 have I have not seen him yet today. 380 00:13:30,559 --> 00:13:32,820 Oh, there is a reason why. Okay. 381 00:13:34,960 --> 00:13:36,960 But he is a good boy. Same as 382 00:13:36,960 --> 00:13:37,700 said friend 383 00:13:38,184 --> 00:13:40,425 also was really mad yesterday that his session 384 00:13:40,425 --> 00:13:41,785 was at 9AM in the morning. He's like, 385 00:13:41,785 --> 00:13:44,524 nobody ever schedules me for sessions before 2PM 386 00:13:44,745 --> 00:13:45,245 because 387 00:13:45,545 --> 00:13:47,965 said friend apparently has a habit of accidentally 388 00:13:48,184 --> 00:13:49,004 going out. 389 00:13:49,465 --> 00:13:52,110 So many times. Accidentally going out. I love 390 00:13:52,110 --> 00:13:54,169 him to death though. Okay. He's fantastic. 391 00:13:54,629 --> 00:13:56,090 Yes. It is 392 00:13:56,629 --> 00:13:57,289 he has 393 00:13:57,669 --> 00:14:00,789 made for many adventures this weekend. Our Uber 394 00:14:00,789 --> 00:14:02,710 driver he had our Uber drive I'm glad 395 00:14:02,710 --> 00:14:04,470 our Uber driver could drive safely with how 396 00:14:04,470 --> 00:14:06,570 hard our Uber driver was laughing 397 00:14:06,985 --> 00:14:07,725 when we 398 00:14:08,345 --> 00:14:09,725 were hearing about shenanigans 399 00:14:10,105 --> 00:14:12,024 on the car. And as I was arguing 400 00:14:12,024 --> 00:14:13,644 with him to tell the story correctly. 401 00:14:14,665 --> 00:14:17,865 So many shenanigans. Okay. Anyway, SharePoint. For real. 402 00:14:17,865 --> 00:14:18,365 SharePoint. 403 00:14:22,879 --> 00:14:24,959 Do you feel overwhelmed by trying to manage 404 00:14:24,959 --> 00:14:27,279 your Office three sixty five environment? Are you 405 00:14:27,279 --> 00:14:30,580 facing unexpected issues that disrupt your company's productivity? 406 00:14:30,799 --> 00:14:32,799 Intelligink is here to help. Much like you 407 00:14:32,799 --> 00:14:34,639 take your car to the mechanic that has 408 00:14:34,639 --> 00:14:36,799 specialized knowledge on how to best keep your 409 00:14:36,799 --> 00:14:39,804 car running, Intelligent helps you with your Microsoft 410 00:14:39,865 --> 00:14:42,044 cloud environment because that's their expertise. 411 00:14:42,504 --> 00:14:44,745 Intelligent keeps up with the latest updates in 412 00:14:44,745 --> 00:14:46,985 the Microsoft cloud to help keep your business 413 00:14:46,985 --> 00:14:49,144 running smoothly and ahead of the curve. Whether 414 00:14:49,144 --> 00:14:51,225 you are a small organization with just a 415 00:14:51,225 --> 00:14:53,639 few users up to an organization of several 416 00:14:53,639 --> 00:14:54,699 thousand employees, 417 00:14:55,079 --> 00:14:57,000 they want to partner with you to implement 418 00:14:57,000 --> 00:14:59,740 and administer your Microsoft cloud technology. 419 00:15:00,519 --> 00:15:04,059 Visit them at inteliginc.com/podcast. 420 00:15:04,279 --> 00:15:11,024 That's intelligink.com/podcast 421 00:15:11,325 --> 00:15:13,565 for more information or to schedule a thirty 422 00:15:13,565 --> 00:15:15,584 minute call to get started with them today. 423 00:15:15,804 --> 00:15:19,245 Remember, Intelligink focuses on the Microsoft cloud so 424 00:15:19,245 --> 00:15:20,850 you can focus on your business. 425 00:15:23,089 --> 00:15:25,409 So that was flows in SharePoint. Another one 426 00:15:25,409 --> 00:15:27,889 we talked about, this is interesting. We're gonna 427 00:15:27,889 --> 00:15:30,949 go to another it's a pre AI topic 428 00:15:31,169 --> 00:15:34,065 that keeps coming up over and over again. 429 00:15:34,065 --> 00:15:35,524 Mhmm. I've had this conversation 430 00:15:36,144 --> 00:15:38,705 at least twice this week at a security 431 00:15:38,705 --> 00:15:41,105 conference Mhmm. And you and I were talking 432 00:15:41,105 --> 00:15:43,365 about it. You've had experience with this SharePoint 433 00:15:43,904 --> 00:15:47,105 and file shares Mhmm. And syncing Mhmm. And 434 00:15:47,105 --> 00:15:47,605 migrations 435 00:15:48,590 --> 00:15:49,809 and MSPs 436 00:15:50,110 --> 00:15:51,170 that are trying 437 00:15:51,550 --> 00:15:54,050 to Yes. Do file syncs for their clients 438 00:15:54,269 --> 00:15:56,590 and treat it like it's still a file 439 00:15:56,590 --> 00:15:58,830 share. Yes. And we've talked about this. I 440 00:15:58,830 --> 00:16:00,190 know we've had at least one. We've probably 441 00:16:00,190 --> 00:16:01,629 had two or three episodes already on the 442 00:16:01,629 --> 00:16:03,149 podcast about it, but we've been going for 443 00:16:03,149 --> 00:16:05,095 nine years and people still don't seem to 444 00:16:05,095 --> 00:16:07,254 get the message. So we're gonna talk about 445 00:16:07,254 --> 00:16:09,334 this again. Alright. I'm gonna get I'm gonna 446 00:16:09,334 --> 00:16:11,495 beat this horse and hopefully it doesn't end 447 00:16:11,495 --> 00:16:12,394 me up in jail. 448 00:16:13,495 --> 00:16:15,194 It'll probably end up in a co pilot. 449 00:16:15,894 --> 00:16:18,694 No. Anti AI. No AI. No co pilot. 450 00:16:18,694 --> 00:16:21,950 No co pilot. Okay. SharePoint lists. Yep. What 451 00:16:21,950 --> 00:16:24,830 has your experience been guidance from you. Scott 452 00:16:24,830 --> 00:16:26,590 and I have beat this horse. It's time 453 00:16:26,590 --> 00:16:28,450 for somebody else to beat the horse. Alright. 454 00:16:28,669 --> 00:16:32,370 SharePoint lists are just Library. Libraries. SharePoint libraries. 455 00:16:32,429 --> 00:16:35,514 Files. Syncing. Because, I mean, SharePoint is really 456 00:16:35,514 --> 00:16:37,134 just SharePoint's third listception. 457 00:16:37,595 --> 00:16:39,754 Okay. True. So we could phrase those lists, 458 00:16:39,754 --> 00:16:41,754 but technically, you can't sync a list. Well, 459 00:16:41,754 --> 00:16:43,195 you can't sync a list that's not a 460 00:16:43,195 --> 00:16:45,120 library. You can't sync a list 461 00:16:45,519 --> 00:16:47,519 to a library, but you can sync a 462 00:16:47,519 --> 00:16:50,399 list to an Excel. Oh. We could talk 463 00:16:50,399 --> 00:16:52,639 about that too. Mhmm. Have you done much 464 00:16:52,639 --> 00:16:54,639 with syncing list to Excel? Uh-huh. Does it 465 00:16:54,639 --> 00:16:56,480 still work? I don't know if it still 466 00:16:56,480 --> 00:16:58,240 works, but it definitely did work when I 467 00:16:58,240 --> 00:16:59,975 was doing it. Okay. Talk to me about 468 00:16:59,975 --> 00:17:02,075 your SharePoint syncing list to Excel. 469 00:17:03,095 --> 00:17:05,575 So it's one of these things where what 470 00:17:05,575 --> 00:17:07,815 is it? You you still have to so 471 00:17:07,815 --> 00:17:10,134 it's in the trust center where, like, you 472 00:17:10,134 --> 00:17:12,474 can turn on and off, like, macros, 473 00:17:12,950 --> 00:17:15,210 but it's not a macro per se. 474 00:17:15,509 --> 00:17:18,410 No. It's like whether hey, this is connected. 475 00:17:18,789 --> 00:17:20,869 Do you really wanna do this? Yep. It's 476 00:17:20,869 --> 00:17:22,230 an o date. Was it o date of 477 00:17:22,230 --> 00:17:24,230 queries? I think it was o date of 478 00:17:24,230 --> 00:17:25,829 queries. Yes. You're like But you could turn 479 00:17:25,829 --> 00:17:27,884 it on and off. Yeah. And then even 480 00:17:27,884 --> 00:17:30,465 if that didn't work, you could still use 481 00:17:30,605 --> 00:17:32,384 Power Query within Excel 482 00:17:32,845 --> 00:17:35,965 to access the list and generate the data 483 00:17:35,965 --> 00:17:37,644 in Excel, which is why I had so 484 00:17:37,644 --> 00:17:39,565 many issues with people like, no, I can't 485 00:17:39,565 --> 00:17:41,640 use like, all of my Excel data lives 486 00:17:41,640 --> 00:17:44,119 in it's I can't put it on SharePoint 487 00:17:44,119 --> 00:17:45,880 because then it doesn't sync. And then it 488 00:17:46,200 --> 00:17:48,519 I get so many problems with trying to 489 00:17:48,519 --> 00:17:50,519 access this because it says it wants to 490 00:17:50,519 --> 00:17:52,759 get into a local file share and I 491 00:17:52,759 --> 00:17:54,599 can't access and it's like, well, if you 492 00:17:54,599 --> 00:17:57,160 put it in SharePoint Mhmm. You can either 493 00:17:57,160 --> 00:17:59,275 put it in a list, like export it 494 00:17:59,275 --> 00:18:02,634 from Excel into a list Yep. Or put 495 00:18:02,634 --> 00:18:04,955 the file in a document library, and you 496 00:18:04,955 --> 00:18:07,275 can sync it from there and make sure 497 00:18:07,275 --> 00:18:09,595 you change every single location that you're pointing 498 00:18:09,595 --> 00:18:11,674 it to every other workbook that you're pointing 499 00:18:11,674 --> 00:18:13,950 to. And that is no longer listed in 500 00:18:13,950 --> 00:18:15,789 a file share because now it's all in 501 00:18:15,789 --> 00:18:17,009 SharePoint. And 502 00:18:17,309 --> 00:18:17,809 I 503 00:18:18,190 --> 00:18:20,450 I had one client, bless his heart, 504 00:18:20,990 --> 00:18:22,529 62 Excel files 505 00:18:22,830 --> 00:18:23,970 that he would create 506 00:18:24,349 --> 00:18:27,075 every single year in order to manage all 507 00:18:27,075 --> 00:18:27,974 of the financials 508 00:18:28,355 --> 00:18:30,914 for his organization. Were they all linked together 509 00:18:30,914 --> 00:18:31,974 too? Every 510 00:18:32,355 --> 00:18:32,855 single 511 00:18:33,154 --> 00:18:35,095 one of them with macros, 512 00:18:35,795 --> 00:18:38,595 all point like, trying to open up one 513 00:18:38,595 --> 00:18:39,095 Excel, 514 00:18:40,500 --> 00:18:41,799 that took some patience. 515 00:18:43,460 --> 00:18:45,299 Because it's like, it would go to load, 516 00:18:45,299 --> 00:18:47,140 and then it was, like, waiting to connect 517 00:18:47,140 --> 00:18:47,799 to SharePoint. 518 00:18:48,100 --> 00:18:50,920 And then it was just spinning and spinning, 519 00:18:50,980 --> 00:18:53,220 and it's like, well, how's the kids? How 520 00:18:53,220 --> 00:18:54,279 are things going? 521 00:18:54,984 --> 00:18:56,984 Eventually, it would load. It opened. So did 522 00:18:56,984 --> 00:18:58,585 you help him get that into a SharePoint 523 00:18:58,585 --> 00:19:00,585 list? No. I ended up not getting the 524 00:19:00,585 --> 00:19:03,144 project because when we quoted them for how 525 00:19:03,224 --> 00:19:05,784 I was like, it's really not gonna cost 526 00:19:05,784 --> 00:19:08,159 that much for us to do it. But 527 00:19:08,159 --> 00:19:10,079 you're trying to make me put a number 528 00:19:10,079 --> 00:19:11,379 on it. And 529 00:19:11,759 --> 00:19:15,200 they almost croaked at the number Okay. Because 530 00:19:15,200 --> 00:19:18,000 they wanted everything moved for the last twenty 531 00:19:18,000 --> 00:19:18,500 years. 532 00:19:19,200 --> 00:19:21,224 Oh. Yeah. And And I was like, yo, 533 00:19:21,224 --> 00:19:23,224 that's not gonna be so whoever they end 534 00:19:23,305 --> 00:19:25,565 did end up going with, I was like, 535 00:19:25,785 --> 00:19:27,805 you undersold it, first of all. 536 00:19:29,865 --> 00:19:31,305 You did not think this went all the 537 00:19:31,305 --> 00:19:33,464 way through. Or there were lots of change 538 00:19:33,464 --> 00:19:36,170 orders. There had to have been. Happened before 539 00:19:36,170 --> 00:19:38,670 too. It had to have been. But, like, 540 00:19:38,809 --> 00:19:41,390 the guy so they call me a wizard. 541 00:19:41,450 --> 00:19:43,289 I don't call myself a wizard. I just 542 00:19:43,289 --> 00:19:46,330 ran with it. Okay. Like, they they told 543 00:19:46,330 --> 00:19:48,170 me, you're gonna get into tech. You're gonna 544 00:19:48,170 --> 00:19:49,884 need a name. And I was like, I 545 00:19:49,884 --> 00:19:51,964 don't know. Like, I don't know. Everybody just 546 00:19:51,964 --> 00:19:53,805 calls me a wizard. That's Whatever. You're a 547 00:19:53,805 --> 00:19:56,525 wizard cat. That's my name. But this guy 548 00:19:56,525 --> 00:19:57,904 was the CFO 549 00:19:58,285 --> 00:20:00,684 for his organization. He's Okay. The only one 550 00:20:00,684 --> 00:20:03,059 who touched this Excel document because he had 551 00:20:03,059 --> 00:20:05,779 to change it every year. He was very 552 00:20:05,779 --> 00:20:08,099 particular about this, like, to the point that 553 00:20:08,099 --> 00:20:10,099 the person who was supposed to be coming 554 00:20:10,099 --> 00:20:11,880 in after him when he retired 555 00:20:12,259 --> 00:20:15,059 Uh-huh. He wouldn't even share the password to 556 00:20:15,059 --> 00:20:16,119 get into the macros 557 00:20:16,424 --> 00:20:18,184 with her made her leave the room so 558 00:20:18,184 --> 00:20:19,945 that he could tell me by writing it 559 00:20:19,945 --> 00:20:21,465 on a piece of paper and showing me 560 00:20:21,465 --> 00:20:23,705 the camera showing it to the camera so 561 00:20:23,705 --> 00:20:25,225 that I could get into it and I 562 00:20:25,225 --> 00:20:27,225 could see what the macros were doing. I 563 00:20:27,225 --> 00:20:29,384 mean, at least he was security conscious and 564 00:20:29,384 --> 00:20:32,180 he wasn't. Trying to be Yeah. Very much. 565 00:20:32,400 --> 00:20:34,079 But I sat on a call I sat 566 00:20:34,079 --> 00:20:35,519 on two different calls with him for a 567 00:20:35,519 --> 00:20:38,319 grand total about six hours Okay. Where he 568 00:20:38,319 --> 00:20:38,819 explained 569 00:20:39,200 --> 00:20:42,339 the entire process The process of, oh, wow. 570 00:20:42,667 --> 00:20:44,134 Of this is what we have to do 571 00:20:44,134 --> 00:20:45,974 every year at the beginning of the year. 572 00:20:45,974 --> 00:20:47,894 This is what happens. This is where all 573 00:20:47,894 --> 00:20:49,815 the changes are made. Every quarter, we have 574 00:20:49,815 --> 00:20:51,095 to do this. We have to create this 575 00:20:51,095 --> 00:20:53,174 whole financial book. This all has to get 576 00:20:53,174 --> 00:20:54,934 printed out in very specific ways so that 577 00:20:54,934 --> 00:20:56,920 it can be then given to the CEO, 578 00:20:56,920 --> 00:20:58,680 and then all these decisions can be and 579 00:20:58,680 --> 00:21:01,500 it was six, six and a half hours 580 00:21:01,720 --> 00:21:02,220 straight, 581 00:21:02,600 --> 00:21:03,740 beginning to end. 582 00:21:04,119 --> 00:21:05,640 At one point in time, I was like, 583 00:21:05,640 --> 00:21:07,900 thank God we are able to record this, 584 00:21:08,359 --> 00:21:10,380 and I can get, like, transcripts, 585 00:21:10,855 --> 00:21:12,214 because there's no way I would have been 586 00:21:12,214 --> 00:21:14,134 able to do this. But after the first, 587 00:21:14,134 --> 00:21:16,214 like, two hour session that I had with 588 00:21:16,214 --> 00:21:18,934 him, of him just, like, explaining everything, and 589 00:21:18,934 --> 00:21:20,375 we went to go meet for the second 590 00:21:20,375 --> 00:21:21,815 session, and I was like, this is what 591 00:21:21,815 --> 00:21:23,575 I understood from the first session. He was 592 00:21:23,575 --> 00:21:24,759 like, yes. 593 00:21:25,619 --> 00:21:28,039 I'm supposed to retire in six months. Absolutely. 594 00:21:28,179 --> 00:21:29,460 I believe 100% 595 00:21:29,460 --> 00:21:32,119 without a doubt, if anything was to happen, 596 00:21:32,179 --> 00:21:33,539 that you guys could do it because you 597 00:21:33,539 --> 00:21:34,980 have the person there who understands it. And 598 00:21:34,980 --> 00:21:37,000 I was like, Excel is my jam, man. 599 00:21:37,539 --> 00:21:40,085 Like, I could fix this for you. Like, 600 00:21:40,085 --> 00:21:42,184 I re that was my biggest problem 601 00:21:42,644 --> 00:21:46,164 working at an MSP Okay. Was seeing people 602 00:21:46,164 --> 00:21:48,964 struggling with their Excels and being like, I 603 00:21:48,964 --> 00:21:51,569 could fix this for you right now. Like, 604 00:21:51,649 --> 00:21:53,409 I could make your life so much easier 605 00:21:53,409 --> 00:21:55,569 for you right now, and it would take 606 00:21:55,569 --> 00:21:57,889 me less than ten minutes. Like, can we 607 00:21:57,889 --> 00:22:00,690 please please stop hurting yourself? Yeah. Can I 608 00:22:00,690 --> 00:22:02,389 give you years back on your life? 609 00:22:03,569 --> 00:22:04,634 So yeah. No. 610 00:22:05,115 --> 00:22:06,714 I enjoy that work. But So what else 611 00:22:06,714 --> 00:22:08,474 did you do with SharePoint lists and Excel? 612 00:22:08,474 --> 00:22:10,555 Did you I did everything with them. I 613 00:22:10,555 --> 00:22:12,815 tried to get everybody off of using Excel. 614 00:22:12,954 --> 00:22:15,595 Okay. If you could use SharePoint and lists 615 00:22:15,595 --> 00:22:17,434 and you didn't want everybody to have access 616 00:22:17,434 --> 00:22:19,855 to every single list item Uh-huh. 617 00:22:20,170 --> 00:22:21,849 Like, I don't I can only share this 618 00:22:21,849 --> 00:22:23,369 much of this Excel with you, or I'm 619 00:22:23,369 --> 00:22:24,650 gonna have to split it up into six 620 00:22:24,650 --> 00:22:26,250 different Excels so they can share the information 621 00:22:26,250 --> 00:22:27,849 that's relevant from this one with that person, 622 00:22:27,849 --> 00:22:29,369 and this one with that person. Like, I 623 00:22:29,369 --> 00:22:30,730 was like, why why do that? Put it 624 00:22:30,730 --> 00:22:33,164 in a list. Yeah. You can provide individual 625 00:22:33,224 --> 00:22:34,904 permissions, and you can say, oh, hey. This 626 00:22:34,904 --> 00:22:36,345 is supposed to be for financial, and this 627 00:22:36,345 --> 00:22:37,724 is supposed to be for HR. 628 00:22:38,105 --> 00:22:39,865 Excuse me. That was a burp. You can 629 00:22:39,865 --> 00:22:40,765 check that out. 630 00:22:41,144 --> 00:22:43,065 I had a lot of Coke today. And 631 00:22:43,065 --> 00:22:43,565 cola. 632 00:22:43,945 --> 00:22:44,765 Coca cola. 633 00:22:45,450 --> 00:22:47,950 Pop. Yes. I'm from Michigan. It's pop. 634 00:22:48,730 --> 00:22:51,369 I'm from Florida. It's Coca Cola. It's 635 00:22:52,649 --> 00:22:53,769 No. I would try to get them off 636 00:22:53,769 --> 00:22:55,450 of it because I'm like, it's so much 637 00:22:55,450 --> 00:22:57,230 easier to manage your permissions 638 00:22:57,884 --> 00:22:59,884 using Flow. As long as you set the 639 00:22:59,884 --> 00:23:02,525 logic, it's not that difficult. Yep. And I 640 00:23:02,525 --> 00:23:04,285 was like, if it's gonna be, oh, I 641 00:23:04,285 --> 00:23:06,125 only need these three people to have access 642 00:23:06,125 --> 00:23:08,125 to it, you can either put a group 643 00:23:08,125 --> 00:23:09,724 together and put those three people in it 644 00:23:09,724 --> 00:23:11,105 and assign that group. 645 00:23:11,484 --> 00:23:14,099 Or if it's just, hey, this one time, 646 00:23:14,099 --> 00:23:15,619 I just need these people to have access 647 00:23:15,619 --> 00:23:17,220 to it, put them in a people picker 648 00:23:17,220 --> 00:23:18,900 field, give them the permission, and when they're 649 00:23:18,900 --> 00:23:20,259 not in the people picker field, take it 650 00:23:20,259 --> 00:23:22,359 away. Take it away and remove their permissions. 651 00:23:22,660 --> 00:23:24,420 Yeah. Like, I was using Flow to manage 652 00:23:24,420 --> 00:23:27,080 permissions all the time. Flow. Power automate. 653 00:23:28,515 --> 00:23:30,214 But it was Flow when you did it? 654 00:23:30,275 --> 00:23:32,275 I think it Probably? It was, like, right 655 00:23:32,275 --> 00:23:34,835 around the time between Flow and Power Automate 656 00:23:34,835 --> 00:23:36,214 name change. Okay. 657 00:23:36,515 --> 00:23:38,275 So it was I was, like, I don't 658 00:23:38,275 --> 00:23:40,035 understand why they called it Power Automate, but 659 00:23:40,035 --> 00:23:41,460 okay. And then it was like, oh, there's 660 00:23:41,460 --> 00:23:43,220 a Power Platform and everything's gonna be Power. 661 00:23:43,220 --> 00:23:44,819 And we've got Power Automate and Power Apps 662 00:23:44,819 --> 00:23:46,259 and Power BI. And then they're gonna take 663 00:23:46,259 --> 00:23:48,259 Power BI off the Chrome. Marketing had to 664 00:23:48,259 --> 00:23:51,160 justify their Yeah. Marketing needs to their existence. 665 00:23:51,220 --> 00:23:52,440 Every six months. 666 00:23:53,664 --> 00:23:55,744 Oh. So So the other one with an 667 00:23:55,744 --> 00:23:56,244 MSP. 668 00:23:56,545 --> 00:23:59,585 Yeah. Going back to syncing, OneDrive syncing. Mhmm. 669 00:23:59,585 --> 00:24:02,384 File syncing. Yep. Like, this is one that 670 00:24:02,384 --> 00:24:02,884 I 671 00:24:03,505 --> 00:24:06,224 Again, pre AI it's a problem. Post AI 672 00:24:06,224 --> 00:24:06,964 it's a problem. 673 00:24:07,299 --> 00:24:09,220 AI does nothing to help with this. Nope, 674 00:24:09,220 --> 00:24:11,859 absolutely not. And it just continues to be 675 00:24:11,859 --> 00:24:12,839 a problem is, 676 00:24:13,140 --> 00:24:14,980 I'm guessing with an MSP, you saw it 677 00:24:14,980 --> 00:24:16,259 as well, you go in and people are 678 00:24:16,259 --> 00:24:18,019 like, we need to migrate file shares to 679 00:24:18,019 --> 00:24:19,914 SharePoint because we're done with file shares. And 680 00:24:19,914 --> 00:24:22,914 they like take their entire file share and 681 00:24:22,914 --> 00:24:24,555 say And dump it in home. It's going 682 00:24:24,555 --> 00:24:26,714 in this SharePoint site and then everybody can 683 00:24:26,714 --> 00:24:28,795 sync it and life will be dandy because 684 00:24:28,795 --> 00:24:29,994 we don't have a file share and it's 685 00:24:29,994 --> 00:24:31,755 all in SharePoint. And then they wanted to 686 00:24:31,755 --> 00:24:32,255 immediately 687 00:24:32,634 --> 00:24:34,460 sync back to it so that everybody could 688 00:24:34,460 --> 00:24:35,900 access it? Yeah. They're like, why is this 689 00:24:35,900 --> 00:24:37,660 taking eight hours to sync back? Or why 690 00:24:37,660 --> 00:24:39,980 isn't everything staying updated? That's like, well, you 691 00:24:39,980 --> 00:24:42,640 understand there's a fundamental difference here between SharePoint 692 00:24:42,779 --> 00:24:45,500 and between file shares. Like, file shares, you're 693 00:24:45,500 --> 00:24:47,804 actually accessing it on the file share. SharePoint, 694 00:24:47,804 --> 00:24:49,804 you're doing it locally and syncing it. And 695 00:24:49,804 --> 00:24:53,664 if you try to sync 590,000 696 00:24:53,724 --> 00:24:54,224 files, 697 00:24:54,684 --> 00:24:56,365 one, I'm surprised it would even work. And 698 00:24:56,365 --> 00:24:59,404 if it does, it will take hours to 699 00:24:59,404 --> 00:25:01,325 keep everything up to date. I might have 700 00:25:01,325 --> 00:25:02,924 had a client. I might have had a 701 00:25:02,924 --> 00:25:04,869 client who had 702 00:25:05,490 --> 00:25:06,450 74 703 00:25:06,450 --> 00:25:08,230 layers of files 704 00:25:08,609 --> 00:25:11,649 or seventy seventy four Folders? Folders. They didn't 705 00:25:11,649 --> 00:25:12,549 hit the, like, 706 00:25:12,929 --> 00:25:14,529 name blank. No. A whole whole whole whole 707 00:25:14,529 --> 00:25:16,159 whole whole whole whole whole whole whole, please. 708 00:25:17,335 --> 00:25:19,914 Okay. I'll be patient. 74 709 00:25:20,134 --> 00:25:21,835 levels of folders 710 00:25:22,295 --> 00:25:23,755 in their document library. 711 00:25:24,134 --> 00:25:24,634 Okay. 712 00:25:24,934 --> 00:25:29,515 And there were over 672,000 713 00:25:29,735 --> 00:25:30,235 files 714 00:25:30,695 --> 00:25:33,080 that were in here. And every time they 715 00:25:33,080 --> 00:25:36,140 would go to move a file in there, 716 00:25:36,519 --> 00:25:38,279 it would take forever for it to go 717 00:25:38,279 --> 00:25:39,880 or it would stop. Uh-huh. And then they 718 00:25:39,880 --> 00:25:42,600 were trying to automate this using Power Automate 719 00:25:42,600 --> 00:25:44,779 and not understanding why the flow would break. 720 00:25:45,080 --> 00:25:48,275 Oh my. And I was like, first of 721 00:25:48,494 --> 00:25:49,555 all, oh my god. 722 00:25:50,575 --> 00:25:51,555 Second of all, 723 00:25:51,934 --> 00:25:52,835 oh my god. 724 00:25:53,455 --> 00:25:55,215 Third of all, that's never going to work 725 00:25:55,215 --> 00:25:56,355 in a million years. 726 00:25:56,894 --> 00:25:59,695 Like, there's a limit on how deep you 727 00:25:59,695 --> 00:26:01,375 can go because there's a limit on the 728 00:26:01,375 --> 00:26:04,710 number of characters that are allowed. And 74 729 00:26:04,710 --> 00:26:07,190 of those characters are already used by forward 730 00:26:07,190 --> 00:26:07,690 slashes. 731 00:26:09,430 --> 00:26:11,690 Wow. Which is also where I found out, 732 00:26:11,750 --> 00:26:12,650 don't use spaces. 733 00:26:13,029 --> 00:26:14,710 Dear God, do not put spaces Don't use 734 00:26:14,789 --> 00:26:16,944 in your folders. No. It's I feel like 735 00:26:16,944 --> 00:26:19,424 it they've done something. It's gotten a little 736 00:26:19,424 --> 00:26:20,565 bit better. 737 00:26:20,865 --> 00:26:21,845 Maybe? Maybe. 738 00:26:22,384 --> 00:26:24,144 I still don't like folders or spaces and 739 00:26:24,144 --> 00:26:25,825 folders. What was I gonna say about that? 740 00:26:25,825 --> 00:26:27,524 There was something else. Moving files 741 00:26:29,160 --> 00:26:30,140 I don't know. It's gone. 742 00:26:30,440 --> 00:26:32,359 I had something I was thinking of that 743 00:26:32,359 --> 00:26:34,279 I was gonna relate that to. Yeah. I 744 00:26:34,279 --> 00:26:35,720 don't know. Yeah. No. That was a fun 745 00:26:35,720 --> 00:26:37,080 project. I was like, you you guys do 746 00:26:37,080 --> 00:26:40,059 know that you don't need folders 747 00:26:40,599 --> 00:26:42,380 in order to store your files. 748 00:26:42,734 --> 00:26:45,315 Right? Like, you can have actual, 749 00:26:45,775 --> 00:26:48,575 like, views Like, yeah. Set up. And then 750 00:26:48,575 --> 00:26:50,275 we can set up filters 751 00:26:50,734 --> 00:26:53,295 because the first level was all of their 752 00:26:53,295 --> 00:26:55,394 clients, and then the next level 753 00:26:55,930 --> 00:26:58,250 was individual folders that they needed for those 754 00:26:58,250 --> 00:27:00,009 clients. And then it was like, well, this 755 00:27:00,009 --> 00:27:01,450 is for quarter one, and this is for 756 00:27:01,450 --> 00:27:03,049 quarter two, and this is for quarter three. 757 00:27:03,049 --> 00:27:04,730 And then it was just Got it. It 758 00:27:04,730 --> 00:27:06,650 was years and years of data. And I 759 00:27:06,650 --> 00:27:07,869 was like, oh, 760 00:27:08,490 --> 00:27:11,085 this is gonna be fun. And then Microsoft 761 00:27:11,305 --> 00:27:14,105 came up with channels and teams that created 762 00:27:14,105 --> 00:27:14,605 folders, 763 00:27:14,985 --> 00:27:15,805 and I said, 764 00:27:16,184 --> 00:27:17,085 I give up. 765 00:27:17,705 --> 00:27:19,785 I can't keep telling people to stop creating 766 00:27:19,785 --> 00:27:22,585 folders because Microsoft says to stop creating folders. 767 00:27:22,585 --> 00:27:24,184 And then they create folders. When they create 768 00:27:24,184 --> 00:27:26,039 folders and channels, they're like, it's a losing 769 00:27:26,039 --> 00:27:28,220 battle. Go create folders to your hard content. 770 00:27:28,279 --> 00:27:29,720 Oh, I remember what I was gonna ask. 771 00:27:29,720 --> 00:27:31,320 Okay. So have you ever seen this when 772 00:27:31,320 --> 00:27:34,220 you start getting that many files and folders? 773 00:27:34,440 --> 00:27:35,720 And I feel like I've seen this a 774 00:27:35,720 --> 00:27:37,640 couple times where, like, two people will sync 775 00:27:37,640 --> 00:27:39,974 it. Mhmm. One person will go to move 776 00:27:39,974 --> 00:27:42,375 it. And because it takes so long to 777 00:27:42,375 --> 00:27:42,875 sync, 778 00:27:43,335 --> 00:27:44,315 the other person's 779 00:27:45,174 --> 00:27:47,494 computer back in there. Gets confused and, like, 780 00:27:47,494 --> 00:27:49,575 puts it back as people are moving it 781 00:27:49,575 --> 00:27:52,695 out, and you end up with Multiple No. 782 00:27:52,775 --> 00:27:56,349 Multiple copies because it takes so long to 783 00:27:56,349 --> 00:27:56,849 sync 784 00:27:57,150 --> 00:27:58,829 that the two OneDrive clients on the two 785 00:27:58,829 --> 00:28:01,730 different computers That's awful. Lose track 786 00:28:02,109 --> 00:28:04,529 of what's going on. That's so awful. 787 00:28:04,910 --> 00:28:06,289 Like, this user 788 00:28:06,670 --> 00:28:08,585 will put I think this is the other 789 00:28:08,585 --> 00:28:10,445 one I've seen. User a 790 00:28:10,825 --> 00:28:13,484 will like add files to the folder. Mhmm. 791 00:28:13,545 --> 00:28:16,904 User b takes takes like the whole folder 792 00:28:17,065 --> 00:28:19,305 And while user a is still waiting to 793 00:28:19,305 --> 00:28:19,805 synchronize, 794 00:28:20,119 --> 00:28:23,100 so then user a recreates the folder 795 00:28:23,480 --> 00:28:25,320 and puts the new files in it. So 796 00:28:25,320 --> 00:28:27,799 now you have not duplicate files, but you 797 00:28:27,799 --> 00:28:29,019 have duplicate folders 798 00:28:29,320 --> 00:28:32,279 In different places. In different files. Yeah. User 799 00:28:32,279 --> 00:28:34,184 b is like, I'm missing files that user 800 00:28:34,184 --> 00:28:35,865 a was supposed to add and user a 801 00:28:35,865 --> 00:28:37,464 is like, where'd all the files go that 802 00:28:37,464 --> 00:28:38,904 were supposed to be in this folder that 803 00:28:38,904 --> 00:28:41,304 I added these other ones to? Oh. And 804 00:28:41,304 --> 00:28:43,784 then it's turned into a massive confusion and 805 00:28:43,784 --> 00:28:45,565 it's one of those things where it's, 806 00:28:46,105 --> 00:28:47,884 again, beating this horse of 807 00:28:48,279 --> 00:28:50,700 SharePoint is not a file share. 808 00:28:51,160 --> 00:28:53,480 Please, I get you want your users to 809 00:28:53,480 --> 00:28:55,720 feel comfortable with SharePoint and OneDrive and syncing 810 00:28:55,720 --> 00:28:57,720 and all that, but don't try to make 811 00:28:57,720 --> 00:29:00,680 OneDrive a file share. Yeah. No. What I 812 00:29:00,680 --> 00:29:02,220 have found really helpful 813 00:29:02,664 --> 00:29:04,204 is Power BI use 814 00:29:04,664 --> 00:29:05,805 with SharePoint. 815 00:29:06,825 --> 00:29:09,085 Okay. Because I can point a URL, 816 00:29:09,384 --> 00:29:11,865 like, in Power Query and Power BI to 817 00:29:11,865 --> 00:29:14,605 a document, like, a document library URL. Okay. 818 00:29:14,744 --> 00:29:16,345 And then I can see all of my 819 00:29:16,345 --> 00:29:16,845 files 820 00:29:17,320 --> 00:29:18,840 in that library. Like, I can break it 821 00:29:18,840 --> 00:29:20,440 down. Oh, because it flattens them all out? 822 00:29:20,440 --> 00:29:22,440 It flattens the whole thing. And so then 823 00:29:22,440 --> 00:29:24,840 you can see, oh, hey. Well, here's this 824 00:29:24,840 --> 00:29:27,160 file in this folder, and here's the same 825 00:29:27,160 --> 00:29:29,160 file in this other folder. But if you 826 00:29:29,160 --> 00:29:31,880 look at the URL for where these files 827 00:29:31,880 --> 00:29:33,764 are at, you can see there's a big 828 00:29:33,764 --> 00:29:36,244 difference in the URL length and how this 829 00:29:36,244 --> 00:29:38,244 is all set. It's fantastic. I haven't tried 830 00:29:38,244 --> 00:29:41,284 that yet. Dude, I 100% guarantee it's, like, 831 00:29:41,284 --> 00:29:42,804 mind blowing. When you get in there, you're 832 00:29:42,804 --> 00:29:43,304 like, 833 00:29:43,924 --> 00:29:46,085 this is beautiful. It's blowing my end right 834 00:29:46,085 --> 00:29:47,700 now. I'm gonna have to go try this. 835 00:29:47,859 --> 00:29:48,359 You 836 00:29:48,740 --> 00:29:50,259 should There are so many things that I've 837 00:29:50,259 --> 00:29:53,159 done with Power BI and that you probably 838 00:29:53,220 --> 00:29:55,220 should not have ever done or be able 839 00:29:55,220 --> 00:29:57,220 to do. But, like, I use Power BI 840 00:29:57,220 --> 00:29:58,899 to unzip files from 841 00:29:59,460 --> 00:30:00,599 Okay. Yeah. 842 00:30:01,299 --> 00:30:01,799 Explain. 843 00:30:02,579 --> 00:30:04,355 Okay. So I actually 844 00:30:04,734 --> 00:30:07,695 started on this project for PowerApps and Canvas 845 00:30:07,695 --> 00:30:10,654 apps Okay. Where I wanted to know the 846 00:30:10,654 --> 00:30:11,634 in internal 847 00:30:12,335 --> 00:30:14,335 guts of what was in a Canvas app. 848 00:30:14,335 --> 00:30:15,934 But when you export it, it comes out 849 00:30:15,934 --> 00:30:18,015 as an MS app file. Yep. Dot MS 850 00:30:18,015 --> 00:30:20,470 app. Well, inside the dot MS app file, 851 00:30:20,529 --> 00:30:23,109 like any other Microsoft file that is created, 852 00:30:23,409 --> 00:30:24,230 is a bunch 853 00:30:24,769 --> 00:30:27,890 of XML files and JSON files and all 854 00:30:27,890 --> 00:30:30,149 of that. So, like, if you change the 855 00:30:30,369 --> 00:30:32,929 extension of the file to dot zip and 856 00:30:32,929 --> 00:30:34,545 unzip it, you can now see all of 857 00:30:34,545 --> 00:30:36,125 the internal guts and glory. 858 00:30:37,625 --> 00:30:39,164 And so there are 859 00:30:39,625 --> 00:30:41,384 different tools that are out there. I think 860 00:30:41,384 --> 00:30:43,965 I found it somebody had it on GitHub, 861 00:30:44,025 --> 00:30:46,125 I think, for how do you decompress 862 00:30:46,745 --> 00:30:49,404 a file using Power BI. Okay. 863 00:30:49,779 --> 00:30:51,880 And so I have gone in and I've 864 00:30:52,180 --> 00:30:54,420 fiddled with that myself. Okay. And I've made 865 00:30:54,420 --> 00:30:55,859 it so that I can point it to 866 00:30:55,859 --> 00:30:57,000 a document library 867 00:30:57,299 --> 00:30:57,960 in OneDrive. 868 00:30:58,339 --> 00:31:01,079 Okay. And I can unzip every single file 869 00:31:01,299 --> 00:31:03,140 that is in that document library and see 870 00:31:03,140 --> 00:31:05,595 the internal contents of this file, so that 871 00:31:05,595 --> 00:31:08,634 I can then verify what's in the file, 872 00:31:08,634 --> 00:31:10,394 where it should be, how it's supposed to 873 00:31:10,394 --> 00:31:12,634 be set, like Can you actually unzip it 874 00:31:12,634 --> 00:31:14,315 too and have it go back to SharePoint 875 00:31:14,315 --> 00:31:16,634 as an unzipped file? Well, no. Because Power 876 00:31:16,634 --> 00:31:18,950 Query doesn't actually physically Doesn't go right back. 877 00:31:19,029 --> 00:31:21,110 You can actually do the reporting or the 878 00:31:21,269 --> 00:31:23,190 Yeah. Look at it. Yeah. So like if 879 00:31:23,190 --> 00:31:25,529 there was a like an Excel file, say, 880 00:31:25,750 --> 00:31:27,350 that's got a whole bunch of financial data 881 00:31:27,350 --> 00:31:28,869 in it, and you have another Excel file 882 00:31:28,869 --> 00:31:30,730 and another SharePoint list somewhere 883 00:31:31,115 --> 00:31:33,355 or SharePoint document library with some other financial 884 00:31:33,355 --> 00:31:34,634 data in it, and you wanted to compare 885 00:31:34,634 --> 00:31:36,154 the two, you could pull it into Power 886 00:31:36,154 --> 00:31:37,615 Query, Power BI, and 887 00:31:37,914 --> 00:31:41,195 and validate. And compare. Yeah. And never actually 888 00:31:41,195 --> 00:31:43,450 physically touch the files. To say, I have 889 00:31:43,450 --> 00:31:44,890 never done this. I'm gonna have to go 890 00:31:44,890 --> 00:31:46,890 start playing with it. This might be part 891 00:31:46,890 --> 00:31:48,250 of the reason why they call me a 892 00:31:48,250 --> 00:31:50,970 wizard. No. Because I find all these little 893 00:31:50,970 --> 00:31:53,289 hacks that nobody thinks about. Did you know 894 00:31:53,289 --> 00:31:54,410 you could do that with have you ever 895 00:31:54,410 --> 00:31:56,170 done that to an office document too? Change 896 00:31:56,170 --> 00:31:58,934 the name to that zip? Yeah. It's fascinating. 897 00:31:59,075 --> 00:32:01,494 Office document, Excel document, PowerPoint documents, 898 00:32:01,954 --> 00:32:04,514 every single one of them, even Power BI 899 00:32:04,514 --> 00:32:05,014 files. 900 00:32:05,394 --> 00:32:07,474 Are just zip files? Every single one of 901 00:32:07,474 --> 00:32:08,615 them is zip file. Everything after 902 00:32:09,714 --> 00:32:11,014 Office 2007. 903 00:32:11,154 --> 00:32:13,289 Yes. The when they added the x to 904 00:32:13,450 --> 00:32:16,410 the document extension. Yeah. Yep. Even the template 905 00:32:16,410 --> 00:32:18,269 files and everything is great. 906 00:32:18,570 --> 00:32:20,809 Very cool. It's how I wanted to start 907 00:32:20,809 --> 00:32:22,730 building crap. I'm like, oh, I can just 908 00:32:22,730 --> 00:32:24,650 change it to to dot zip and unpack 909 00:32:24,650 --> 00:32:26,090 it, and then I can just put whatever 910 00:32:26,090 --> 00:32:27,295 I want in it and zip it back 911 00:32:27,295 --> 00:32:28,734 up and change the extension to whatever it 912 00:32:28,734 --> 00:32:30,575 is. Just randomly tried it now with every 913 00:32:30,575 --> 00:32:32,015 file you get is just change it to 914 00:32:32,015 --> 00:32:34,015 dot zip to see what happens. Yep. A 915 00:32:34,015 --> 00:32:37,234 100%. I've actually saved my bacon before because 916 00:32:37,615 --> 00:32:39,715 I was working on a Power BI report. 917 00:32:40,000 --> 00:32:40,500 Okay. 918 00:32:40,880 --> 00:32:43,039 I accidentally made a change in which it 919 00:32:43,039 --> 00:32:44,960 froze the whole thing up, and I forgot 920 00:32:44,960 --> 00:32:45,700 to save 921 00:32:46,319 --> 00:32:48,819 after working on this for twelve hours. 922 00:32:49,200 --> 00:32:49,940 Oh, no. 923 00:32:50,240 --> 00:32:52,559 Thank god I always turn on the auto 924 00:32:52,559 --> 00:32:53,779 save part. Yep. 925 00:32:54,224 --> 00:32:55,825 But then I tried to open up the 926 00:32:55,825 --> 00:32:56,724 backup file 927 00:32:57,105 --> 00:32:57,505 Okay. 928 00:32:57,904 --> 00:33:00,304 And it had saved it with the error 929 00:33:00,304 --> 00:33:02,384 in place so that it was frozen as 930 00:33:02,384 --> 00:33:03,365 soon as it opened. 931 00:33:03,744 --> 00:33:06,944 Oh. And I was like, oh, no. This 932 00:33:06,944 --> 00:33:09,360 is not good. Because the number of power 933 00:33:09,360 --> 00:33:12,240 query, like, changes that I had made Twelve 934 00:33:12,240 --> 00:33:14,880 hours worth. I was never going to remember 935 00:33:14,880 --> 00:33:16,480 exactly how I had done it. Yeah. And 936 00:33:16,480 --> 00:33:18,660 I was like, oh, wait. I can change 937 00:33:18,720 --> 00:33:20,774 this file to dot zip, and I can 938 00:33:20,774 --> 00:33:22,375 open it up and look at it in 939 00:33:22,375 --> 00:33:23,734 Versus Code, and I can get all of 940 00:33:23,734 --> 00:33:24,615 the Power Query 941 00:33:24,934 --> 00:33:26,615 Okay. Out of there and make sure that 942 00:33:26,615 --> 00:33:29,254 I change the one specific part that was 943 00:33:29,254 --> 00:33:30,234 freezing everything. 944 00:33:31,654 --> 00:33:34,294 No. You can't. Yes. You can. No Power 945 00:33:34,294 --> 00:33:36,539 Query. It's John. It's John. Very stupid. No. 946 00:33:36,539 --> 00:33:38,539 It is not. Blah blah blah. It is 947 00:33:38,539 --> 00:33:40,460 the Let's go do some KQL over at 948 00:33:40,460 --> 00:33:43,579 it. Christ. I talked about KQL earlier. I 949 00:33:43,579 --> 00:33:45,339 do? Yeah. You have to talk really loud, 950 00:33:45,339 --> 00:33:46,460 John, so you get picked up on the 951 00:33:46,460 --> 00:33:48,140 mic for the podcast. Oh, you're on a 952 00:33:48,140 --> 00:33:50,944 podcast? Yeah. Now you are too. Nice. We 953 00:33:50,944 --> 00:33:53,204 just got joined by John the mastermind 954 00:33:54,224 --> 00:33:54,724 behind 955 00:33:55,424 --> 00:33:57,984 the workplace ninjas conference. As you get all 956 00:33:57,984 --> 00:34:00,545 the feedback from my microphone. Hello. Just like 957 00:34:00,545 --> 00:34:02,224 I told him at the MVP summit, the 958 00:34:02,224 --> 00:34:03,765 only person that you have to learn KQL 959 00:34:03,809 --> 00:34:05,490 are people who do defender are, like, Nathan 960 00:34:05,490 --> 00:34:07,490 McNulty. Making everybody else learn it is cruel 961 00:34:07,490 --> 00:34:08,230 and evil. 962 00:34:08,690 --> 00:34:10,210 Now I'm gonna go away. You're gonna go 963 00:34:10,210 --> 00:34:12,930 away. Alright. Thanks, John. Can't wait for are 964 00:34:12,930 --> 00:34:15,090 we allowed to talk about next year? We 965 00:34:15,090 --> 00:34:16,469 are announcing Is it public? 966 00:34:16,815 --> 00:34:18,255 At 05:30PM, 967 00:34:18,255 --> 00:34:20,175 we are announcing the 2027 968 00:34:20,175 --> 00:34:21,234 date and venue. 969 00:34:21,534 --> 00:34:23,775 Okay. So this podcast will come out after 970 00:34:23,775 --> 00:34:25,214 that, so we will talk about it. You 971 00:34:25,214 --> 00:34:26,894 can announce the fact that it is going 972 00:34:26,894 --> 00:34:28,914 to be at the Scott And Scottsdale 973 00:34:29,295 --> 00:34:31,940 The Scott? Next week of February Okay. 2027. 974 00:34:31,940 --> 00:34:32,920 The Scott And Scottsdale, 975 00:34:33,460 --> 00:34:35,400 last week, 2027. 976 00:34:35,460 --> 00:34:37,480 You should absolutely come and accidentally 977 00:34:38,900 --> 00:34:40,679 go out. Go out at night. 978 00:34:41,619 --> 00:34:44,760 Enjoy all the shenanigans at which 100% shenanigans. 979 00:34:44,900 --> 00:34:46,775 This is I don't know as many people 980 00:34:46,775 --> 00:34:48,934 at this conference as when I go to 981 00:34:48,934 --> 00:34:50,615 some of the other ones. Mhmm. This is 982 00:34:50,615 --> 00:34:52,695 by far the most fun I have ever 983 00:34:52,695 --> 00:34:53,195 had 984 00:34:53,575 --> 00:34:54,315 at a conference. 985 00:34:54,934 --> 00:34:56,615 To be fair, I found out today that 986 00:34:56,615 --> 00:34:57,275 I'm royalty. 987 00:34:57,590 --> 00:34:59,429 I did not know this. You're not only 988 00:34:59,429 --> 00:35:01,829 a wizard, but you're royalty. I'm apparently royalty. 989 00:35:01,829 --> 00:35:03,909 I'm MVP royalty, and I did not know 990 00:35:03,909 --> 00:35:05,289 this. Like, some of Congratulations. 991 00:35:05,829 --> 00:35:09,269 Yeah. I so, Ramona g Oh, yeah. I 992 00:35:09,269 --> 00:35:11,744 know. Ramona's awesome. Yeah. So I went down 993 00:35:11,744 --> 00:35:13,824 to her session before and, like, I only 994 00:35:13,824 --> 00:35:16,784 met her through WhatsApp chat, like, a few 995 00:35:16,784 --> 00:35:18,945 weeks ago. Okay. Two months ago, something like 996 00:35:18,945 --> 00:35:20,945 that. And I walked into her session and 997 00:35:20,945 --> 00:35:22,945 there's, like, there's a handful of people or 998 00:35:22,945 --> 00:35:24,385 whatever because they put her out in the 999 00:35:24,385 --> 00:35:26,039 middle of nowhere land like they did to 1000 00:35:26,039 --> 00:35:28,920 me yesterday. I'm sorry. And definitely did not 1001 00:35:28,920 --> 00:35:31,480 complain to John about that several times with 1002 00:35:31,480 --> 00:35:32,539 a number of expletives. 1003 00:35:34,199 --> 00:35:36,460 And so That never would have imagined. 1004 00:35:37,864 --> 00:35:40,025 I went walked into her session, and she 1005 00:35:40,025 --> 00:35:42,025 got, like, got all super excited and whatnot. 1006 00:35:42,025 --> 00:35:43,464 And then, like, at at the end of 1007 00:35:43,464 --> 00:35:45,704 her session, like, my friend, he wanted me 1008 00:35:45,704 --> 00:35:46,605 to come introduce, 1009 00:35:47,144 --> 00:35:49,324 like, him to her. He's like, she's fantastic. 1010 00:35:49,704 --> 00:35:50,905 And I was like Is this the same 1011 00:35:50,905 --> 00:35:53,019 friend that accidentally goes out? This is a 1012 00:35:53,019 --> 00:35:54,319 different friend? Okay. 1013 00:35:54,779 --> 00:35:56,380 And so he's like, you need to come 1014 00:35:56,380 --> 00:35:58,059 introduce me. And I was like, I'm pretty 1015 00:35:58,059 --> 00:35:59,819 sure she knows me, but sure. I'll come 1016 00:35:59,819 --> 00:36:01,440 down there and I'll make an introduction. 1017 00:36:01,739 --> 00:36:04,219 And so at the end, he, like, he 1018 00:36:04,219 --> 00:36:06,159 jumps up and he's like, hey, I'm gonna 1019 00:36:06,525 --> 00:36:08,545 do and so I was like, okay. Okay. 1020 00:36:08,764 --> 00:36:11,244 And she's like, yeah. This is royalty right 1021 00:36:11,244 --> 00:36:12,784 here. And I was like, what? 1022 00:36:13,724 --> 00:36:15,244 This is the fun part. We just get 1023 00:36:15,244 --> 00:36:17,005 random people stopping that. Yeah. Yeah. John I 1024 00:36:17,005 --> 00:36:18,284 thought you were just shooting the shit now 1025 00:36:18,284 --> 00:36:20,764 because No. This is that's the fun part 1026 00:36:20,764 --> 00:36:22,933 of the podcast. Here's this is random Yeah. 1027 00:36:23,039 --> 00:36:23,860 Just into 1028 00:36:24,239 --> 00:36:25,920 the Lindsay came to say hi. We have 1029 00:36:25,920 --> 00:36:28,820 Lindsay. We have Lindsay Shelton here from Epic 1030 00:36:29,599 --> 00:36:30,500 with a q. 1031 00:36:30,800 --> 00:36:32,340 So and Lindsay is epic. 1032 00:36:32,640 --> 00:36:34,720 She is epic. She works at Epic and 1033 00:36:34,720 --> 00:36:36,019 is epic. Exactly. 1034 00:36:36,394 --> 00:36:37,295 Except I know how 1035 00:36:37,855 --> 00:36:38,355 to 1036 00:36:38,914 --> 00:36:39,414 spell 1037 00:36:39,974 --> 00:36:40,474 epic. 1038 00:36:41,034 --> 00:36:43,114 Oh my. But I love my work, I 1039 00:36:43,114 --> 00:36:45,194 love my employer. Alright. Yes. In case they'll 1040 00:36:45,194 --> 00:36:46,795 send to this case later. We'll make sure 1041 00:36:46,795 --> 00:36:48,255 that is noted 1042 00:36:48,714 --> 00:36:50,175 and Yes. Acknowledged. 1043 00:36:50,795 --> 00:36:52,289 Alright. But we should probably wrap 1044 00:36:52,589 --> 00:36:53,630 up. I don't even know how long we've 1045 00:36:53,630 --> 00:36:57,069 been recording for. Anything else that's anti AI 1046 00:36:57,069 --> 00:36:59,329 that we wanted? We did well for anti 1047 00:36:59,389 --> 00:37:01,949 AI. We did. A little I mean off 1048 00:37:01,949 --> 00:37:03,650 the wall on everything. I did mention CoPilot 1049 00:37:03,710 --> 00:37:06,005 once, but, you know, I feel like that 1050 00:37:06,005 --> 00:37:08,005 you have to as an MVP for anything 1051 00:37:08,005 --> 00:37:09,684 that you're speaking at least mention it one 1052 00:37:09,684 --> 00:37:12,005 time. It's yeah. It's an obligation. I think 1053 00:37:12,005 --> 00:37:14,264 we signed something that says It's actually obligated. 1054 00:37:14,565 --> 00:37:16,565 Time we talk, we will mention Copilot at 1055 00:37:16,565 --> 00:37:17,224 least once. 1056 00:37:17,880 --> 00:37:19,900 So I think we have done our contractual 1057 00:37:20,119 --> 00:37:22,599 obligation. Well, thanks, guys. This was a lot 1058 00:37:22,599 --> 00:37:23,980 of fun. It was. 1059 00:37:24,519 --> 00:37:26,119 I will put links in the show notes 1060 00:37:26,119 --> 00:37:27,659 to anybody that wants to 1061 00:37:27,960 --> 00:37:29,739 meet Kat, the royal 1062 00:37:30,119 --> 00:37:30,619 wizard. 1063 00:37:30,920 --> 00:37:32,139 The royal wizard. 1064 00:37:34,905 --> 00:37:36,125 You need a new handle. 1065 00:37:36,425 --> 00:37:37,724 Half the royal wizard. 1066 00:37:38,184 --> 00:37:40,744 I've added a dinosaur to my LinkedIn name. 1067 00:37:40,744 --> 00:37:43,485 Now, like, what more can you ask? Perfect. 1068 00:37:44,025 --> 00:37:46,744 Alright. Well, thank you so much. This was 1069 00:37:46,744 --> 00:37:48,900 a lot of fun. Yeah. And we will 1070 00:37:48,900 --> 00:37:50,579 have to do it again sometime. Yes. For 1071 00:37:50,579 --> 00:37:52,579 sure. Alright. Alright. Thanks, Kat. We'll talk to 1072 00:37:52,579 --> 00:37:54,199 you later. K. Bye. 1073 00:37:56,500 --> 00:37:58,819 If you enjoyed the podcast, go leave us 1074 00:37:58,819 --> 00:38:01,059 a five star rating in iTunes. It helps 1075 00:38:01,059 --> 00:38:02,765 to get the word out so more IT 1076 00:38:02,765 --> 00:38:04,844 pros can learn about Office three sixty five 1077 00:38:04,844 --> 00:38:05,585 and Azure. 1078 00:38:06,125 --> 00:38:07,805 If you have any questions you want us 1079 00:38:07,805 --> 00:38:09,885 to address on the show, or feedback about 1080 00:38:09,885 --> 00:38:12,285 the show, feel free to reach out via 1081 00:38:12,285 --> 00:38:14,465 our website, Twitter, or Facebook. 1082 00:38:14,765 --> 00:38:16,684 Thanks again for listening, and have a great 1083 00:38:16,684 --> 00:38:17,184 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