Episode 406 – Agents of Insight: Copilot in Action and Sentinel on the Move

July 17, 2025

Episode Transcript

Welcome to Episode 406 of the Microsoft Cloud IT Pro Podcast. In this episode, Ben and Scott discuss their recent experiences and thoughts on Microsoft’s Copilot features and agents, specifically focusing on the Researcher and Analyst agents. They share practical applications and benefits of these tools, such as using Researcher for meeting preparations and Analyst for exploring data, summarizing data, and even coming up with python script to use with data. Additionally, they cover the upcoming migration of Microsoft Sentinel to the Defender portal, discussing its implications and potential future changes for other security tools. The episode ends with a teaser about an upcoming discussion on MCPs for AI!

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,520 --> 00:00:05,679 Welcome to episode 406 2 00:00:05,679 --> 00:00:08,960 of the Microsoft Cloud IT Pro podcast recorded 3 00:00:08,960 --> 00:00:11,539 live on 07/11/2025. 4 00:00:11,679 --> 00:00:14,000 This is a show about Microsoft three sixty 5 00:00:14,000 --> 00:00:16,144 five and Azure from the perspective of IT 6 00:00:16,144 --> 00:00:18,304 pros and end users, where we discuss a 7 00:00:18,304 --> 00:00:20,625 topic or recent news and how it relates 8 00:00:20,625 --> 00:00:23,265 to you. In this episode, we had this 9 00:00:23,265 --> 00:00:25,664 grand plan of talking about something other than 10 00:00:25,664 --> 00:00:27,989 Copilot, but then the analyst 11 00:00:28,949 --> 00:00:30,949 research agent came up and maybe we got 12 00:00:30,949 --> 00:00:33,429 a little carried away. So we kick off 13 00:00:33,429 --> 00:00:35,429 the show by spending a bit talking about 14 00:00:35,429 --> 00:00:38,149 these two first party agents from Microsoft that 15 00:00:38,149 --> 00:00:39,609 have recently been released, 16 00:00:40,149 --> 00:00:42,554 how we use them, and what our experience 17 00:00:42,554 --> 00:00:44,795 has been with both the researcher and the 18 00:00:44,795 --> 00:00:47,755 analyst agent. From there, we actually do manage 19 00:00:47,755 --> 00:00:50,075 to move into some non AI news as 20 00:00:50,075 --> 00:00:52,575 we talk about the recent announcement from Microsoft 21 00:00:52,875 --> 00:00:56,270 about the Microsoft Sentinel portal in Azure going 22 00:00:56,270 --> 00:00:59,469 away and transitioning fully to the Microsoft Defender 23 00:00:59,469 --> 00:01:01,250 portal. Enjoy the show. 24 00:01:03,469 --> 00:01:05,069 Do you ever walk on a plane and 25 00:01:05,069 --> 00:01:06,829 you feel like there's a kid flying the 26 00:01:06,829 --> 00:01:08,144 plane that you're getting on? 27 00:01:09,185 --> 00:01:10,704 I'll let you know tomorrow when I hop 28 00:01:10,704 --> 00:01:12,144 on one thing. That always makes me feel 29 00:01:12,144 --> 00:01:13,905 old. I'm like, oh, man. The pile I 30 00:01:13,905 --> 00:01:15,744 don't know why. I don't know why the 31 00:01:15,744 --> 00:01:17,344 pilot of an airplane, I feel like a 32 00:01:17,344 --> 00:01:19,104 pilot should be older than me. I know 33 00:01:19,104 --> 00:01:19,765 some pilots 34 00:01:20,224 --> 00:01:22,244 who are older than me and have retired, 35 00:01:22,619 --> 00:01:24,959 and I'm kind of glad they retired. 36 00:01:25,739 --> 00:01:27,659 Joshua Foer: See, there is also that point. 37 00:01:27,659 --> 00:01:28,159 Yeah. 38 00:01:28,459 --> 00:01:31,019 Joshua Foer: I've been feeling especially old this 39 00:01:31,019 --> 00:01:31,840 week, so 40 00:01:32,379 --> 00:01:32,879 my 41 00:01:33,340 --> 00:01:33,840 youngest 42 00:01:34,379 --> 00:01:34,879 child 43 00:01:35,500 --> 00:01:37,599 is turning 16. Joshua Foer: Oh, congratulations, 44 00:01:38,355 --> 00:01:39,895 I think. Is this a congratulations? 45 00:01:40,515 --> 00:01:43,234 Sure. I like, it's we're getting closer taxi 46 00:01:43,234 --> 00:01:45,415 service? We're getting closer to having 47 00:01:45,715 --> 00:01:47,314 yet another one out of the house, so 48 00:01:47,475 --> 00:01:48,995 but, like, this is a weird year. So 49 00:01:48,995 --> 00:01:51,155 my oldest is going to college, my youngest 50 00:01:51,155 --> 00:01:52,295 is turning 16, 51 00:01:53,099 --> 00:01:55,260 And then I didn't realize it this week, 52 00:01:55,260 --> 00:01:57,260 but, you know, I don't know how much 53 00:01:57,260 --> 00:01:59,760 you kinda think about like your parents 54 00:02:00,140 --> 00:02:02,379 and kinda people in your family aging as 55 00:02:02,379 --> 00:02:05,420 well. It was my dad's birthday this week, 56 00:02:05,420 --> 00:02:07,359 and my dad is 76. 57 00:02:07,775 --> 00:02:09,215 And I was looking around, and I was 58 00:02:09,215 --> 00:02:10,735 like, oh, I've got a 16 year old. 59 00:02:10,735 --> 00:02:12,974 I got my dad who's, like, 76 over 60 00:02:12,974 --> 00:02:15,134 here. I'm 45 and feel like I'm a 61 00:02:15,134 --> 00:02:17,455 pretty broken person, so, like, I can't even 62 00:02:17,455 --> 00:02:19,854 imagine, like, making it to 76 like my 63 00:02:19,854 --> 00:02:20,915 dad at this point. 64 00:02:21,900 --> 00:02:23,740 So I've been thinking a lot about age 65 00:02:23,740 --> 00:02:25,980 this week. Yeah. You know what? One hit 66 00:02:25,980 --> 00:02:28,080 me with my parents. My parents 67 00:02:28,460 --> 00:02:30,540 are getting older as well. What my dad 68 00:02:30,540 --> 00:02:32,860 was my dad just turned 70. So he's 69 00:02:32,860 --> 00:02:34,379 a few years younger than your dad, but 70 00:02:34,379 --> 00:02:36,165 they bought a new 71 00:02:36,625 --> 00:02:37,125 vehicle, 72 00:02:37,585 --> 00:02:40,224 like, last summer. And my mom made the 73 00:02:40,224 --> 00:02:42,485 comment of this might be the last vehicle 74 00:02:42,784 --> 00:02:45,264 that we'll ever buy because by the time 75 00:02:45,264 --> 00:02:47,889 this vehicle it was a newer vehicle. By 76 00:02:47,889 --> 00:02:48,629 the time the vehicle hits 77 00:02:48,930 --> 00:02:50,150 mileage, breaks, whatever, 78 00:02:50,449 --> 00:02:51,830 they won't be driving anymore. 79 00:02:52,289 --> 00:02:54,289 And that one hit me. I'm like, oh, 80 00:02:54,289 --> 00:02:56,209 no. My my parents can't be that old 81 00:02:56,209 --> 00:02:58,229 that they're not ever gonna buy another vehicle. 82 00:02:59,965 --> 00:03:01,805 Depending on the age your kids get to, 83 00:03:01,805 --> 00:03:03,724 by the parent time your parents age out 84 00:03:03,724 --> 00:03:05,245 of that vehicle, you might be looking forward 85 00:03:05,245 --> 00:03:06,465 to it. So 86 00:03:07,245 --> 00:03:08,685 with an 18 year old and a 16 87 00:03:08,685 --> 00:03:10,364 year old, we had to break down and 88 00:03:10,364 --> 00:03:12,604 buy a third car because we were tired 89 00:03:12,604 --> 00:03:14,384 of just shepherding people around 90 00:03:15,210 --> 00:03:18,330 jobs and things like that, but we absolutely 91 00:03:18,330 --> 00:03:20,330 had the conversation. I remember my wife and 92 00:03:20,330 --> 00:03:21,389 I had it. We're like, 93 00:03:21,689 --> 00:03:23,770 which one of our parents is old enough 94 00:03:23,770 --> 00:03:25,930 that they're not gonna be driving soon, so 95 00:03:25,930 --> 00:03:27,615 maybe we can go get a cheap car? 96 00:03:28,254 --> 00:03:29,935 Yeah. Not work out that way because all 97 00:03:29,935 --> 00:03:32,094 of our parents are still driving, so we 98 00:03:32,094 --> 00:03:32,915 had to go find 99 00:03:33,215 --> 00:03:34,995 a a cheap one off marketplace, 100 00:03:36,094 --> 00:03:37,855 one of my wife's friends, things like that. 101 00:03:37,855 --> 00:03:40,650 So, yeah, the but your kids, 102 00:03:42,250 --> 00:03:44,169 we've talked about this on the side. Few. 103 00:03:44,169 --> 00:03:45,610 I still think your kids are, like, three 104 00:03:45,610 --> 00:03:47,610 years old when in fact they're not. But 105 00:03:47,610 --> 00:03:49,049 by the time your kids are old enough 106 00:03:49,049 --> 00:03:49,709 to drive, 107 00:03:50,090 --> 00:03:51,769 especially the younger the ones who are younger 108 00:03:51,769 --> 00:03:52,269 today, 109 00:03:52,985 --> 00:03:54,504 maybe that car that your parents got, if 110 00:03:54,504 --> 00:03:55,944 they take good care of it, it'll be 111 00:03:55,944 --> 00:03:57,705 passed down to you. It might be. Yeah. 112 00:03:57,705 --> 00:03:59,625 Because I'll have kids driving anywhere from the 113 00:03:59,625 --> 00:04:00,844 next, like, three 114 00:04:01,305 --> 00:04:03,544 and a half ish years to ten years. 115 00:04:03,544 --> 00:04:05,224 Yeah. Which we just bought a new car. 116 00:04:05,224 --> 00:04:07,659 I was borderline of, like, three years is 117 00:04:07,659 --> 00:04:09,759 a little bit too long to save 118 00:04:10,139 --> 00:04:12,620 our old vehicle. And I won't lie. I'm 119 00:04:12,620 --> 00:04:14,699 not sure that when our kids start driving, 120 00:04:14,699 --> 00:04:16,939 they're gonna wanna drive around a Sienna, a 121 00:04:16,939 --> 00:04:19,579 Toyota Sienna minivan with a 110,000 122 00:04:19,579 --> 00:04:21,694 miles on it. So a few more years, 123 00:04:21,694 --> 00:04:23,214 I'm gonna be in your boat, Scott, looking 124 00:04:23,214 --> 00:04:26,115 for a replacement car. Well, you can ask 125 00:04:26,175 --> 00:04:28,675 Microsoft Researcher or Copilot researcher 126 00:04:29,455 --> 00:04:33,475 or Researcher Copilot. Researcher for Copilot. Researcher agent 127 00:04:34,254 --> 00:04:35,795 inside of Microsoft 128 00:04:36,459 --> 00:04:37,759 three sixty five Copilot, 129 00:04:38,459 --> 00:04:40,000 I think I got all that right. 130 00:04:40,779 --> 00:04:43,740 Yeah. Something like that is now out and 131 00:04:43,740 --> 00:04:45,180 available. Have you had a chance to play 132 00:04:45,180 --> 00:04:47,180 around with this one yet? I have. I 133 00:04:47,180 --> 00:04:49,500 will I have not used analyst as available 134 00:04:49,500 --> 00:04:51,019 too. We'll just preface that in case we 135 00:04:51,019 --> 00:04:53,205 jump between them. Analyst and researcher, both agents 136 00:04:53,205 --> 00:04:53,944 when available. 137 00:04:54,324 --> 00:04:56,884 Research I actually really like researcher, Scott, and 138 00:04:56,884 --> 00:04:57,625 it is 139 00:04:58,004 --> 00:05:00,245 we could debate the validity of all these 140 00:05:00,245 --> 00:05:03,365 different Copilot tools, ChattGPT, Claude, etcetera, what they 141 00:05:03,365 --> 00:05:06,199 do. You're gonna laugh. What I use Researcher 142 00:05:06,259 --> 00:05:08,019 for, I get you can book a meeting 143 00:05:08,019 --> 00:05:10,339 with me through my website. Like, if anybody 144 00:05:10,339 --> 00:05:12,019 goes to intelligent.com, 145 00:05:12,019 --> 00:05:13,300 wants to find out more, they can book 146 00:05:13,300 --> 00:05:15,379 a meeting. There's a bunch of links out 147 00:05:15,379 --> 00:05:17,459 there to book meetings with me, and I 148 00:05:17,459 --> 00:05:19,485 get whether it's new clients or just people 149 00:05:19,485 --> 00:05:22,305 that stumble across my website, I'll get requests 150 00:05:22,764 --> 00:05:25,165 for meetings of and I'm like, who is 151 00:05:25,165 --> 00:05:27,404 this person? Like, it'll be super vague. It'll 152 00:05:27,404 --> 00:05:29,404 maybe come from a personal email address and 153 00:05:29,404 --> 00:05:30,785 not a work email address. 154 00:05:31,165 --> 00:05:31,665 LinkedIn, 155 00:05:32,040 --> 00:05:33,800 I don't always like people to know that 156 00:05:33,800 --> 00:05:35,639 I went and, like, started stalking them on 157 00:05:35,639 --> 00:05:37,560 LinkedIn, where so and so looked at your 158 00:05:37,560 --> 00:05:39,240 profile or so and so from this company 159 00:05:39,240 --> 00:05:40,220 looked at your profile. 160 00:05:40,520 --> 00:05:42,920 I use Researcher, and I'll, like, go search 161 00:05:42,920 --> 00:05:45,520 Bing or Google, get their LinkedIn URL if 162 00:05:45,520 --> 00:05:47,384 I can find them, and, like, go tell 163 00:05:47,384 --> 00:05:49,964 Researcher, hey, go tell me about this person 164 00:05:50,024 --> 00:05:52,204 or give me a background of this person. 165 00:05:52,664 --> 00:05:53,884 I've done this for companies, 166 00:05:54,185 --> 00:05:56,504 new clients. Before my first meeting with them, 167 00:05:56,504 --> 00:05:58,264 I'll go in and tell Researcher, hey, can 168 00:05:58,264 --> 00:05:59,884 you give me a background of this company? 169 00:06:00,319 --> 00:06:03,040 And it'll, like, give me a three or 170 00:06:03,040 --> 00:06:04,420 four page report 171 00:06:04,879 --> 00:06:08,720 on this person's job history, whatever researcher can 172 00:06:08,720 --> 00:06:10,639 find out on the Internet about a particular 173 00:06:10,639 --> 00:06:13,040 person or company, and it's actually helpful. It, 174 00:06:13,040 --> 00:06:15,220 like, gives me a good background 175 00:06:15,884 --> 00:06:16,384 of 176 00:06:16,685 --> 00:06:17,504 that particular 177 00:06:17,805 --> 00:06:20,685 person, that particular company just so I don't 178 00:06:20,685 --> 00:06:22,384 have to go scour a bunch of websites 179 00:06:22,444 --> 00:06:25,004 and can have a little bit more context 180 00:06:25,004 --> 00:06:26,604 of who this person is or who this 181 00:06:26,604 --> 00:06:28,284 company is before I meet with them the 182 00:06:28,284 --> 00:06:30,784 first time. And from what I've seen, 183 00:06:31,129 --> 00:06:32,810 it does a really good job of it. 184 00:06:32,810 --> 00:06:33,550 It's surprisingly 185 00:06:34,009 --> 00:06:34,509 good, 186 00:06:35,290 --> 00:06:37,290 very dependent on, I think, the context you 187 00:06:37,290 --> 00:06:39,370 can give it and what you pump in. 188 00:06:39,370 --> 00:06:42,269 So it's definitely one of those tools, like, 189 00:06:42,569 --> 00:06:44,889 what you put in is what you get 190 00:06:44,889 --> 00:06:46,189 out of it kind of thing 191 00:06:46,694 --> 00:06:47,194 that 192 00:06:47,654 --> 00:06:48,794 can help you out. So 193 00:06:50,454 --> 00:06:52,074 I've seen folks on 194 00:06:52,615 --> 00:06:54,694 my team using it in a couple of 195 00:06:54,694 --> 00:06:56,314 different ways, and 196 00:06:56,774 --> 00:06:58,134 we definitely have some 197 00:06:58,759 --> 00:07:00,519 I have some members of my team who 198 00:07:00,519 --> 00:07:02,279 totally lean in. I think they live all 199 00:07:02,279 --> 00:07:03,800 day in CoPilot, and then I have some 200 00:07:03,800 --> 00:07:05,479 other ones that dip their toes in the 201 00:07:05,479 --> 00:07:05,979 water 202 00:07:06,759 --> 00:07:08,839 and try it out and everything in between, 203 00:07:08,839 --> 00:07:11,240 but we've had a couple folks get hands 204 00:07:11,240 --> 00:07:12,539 on with Researcher, 205 00:07:13,079 --> 00:07:13,579 so 206 00:07:15,134 --> 00:07:17,855 funny enough, we just went through performance review 207 00:07:17,855 --> 00:07:20,355 season. Okay. I was kinda comparing and contrasting 208 00:07:20,415 --> 00:07:23,134 results here between regular Copilot and the researcher 209 00:07:23,134 --> 00:07:25,634 agent, and the researcher agent does a surprisingly 210 00:07:25,855 --> 00:07:27,935 good job. Like, if you pump in things 211 00:07:27,935 --> 00:07:31,639 like, here's my past performance reviews, here's how 212 00:07:31,639 --> 00:07:34,060 I wrote my self assessment for this year, 213 00:07:34,600 --> 00:07:36,839 help me structure my thinking in the right 214 00:07:36,839 --> 00:07:39,100 way, help me quantify my impact 215 00:07:40,759 --> 00:07:42,439 as an individual, as a member of a 216 00:07:42,439 --> 00:07:42,939 team. 217 00:07:43,324 --> 00:07:45,745 The company I work for, we have multiple 218 00:07:45,805 --> 00:07:46,305 dimensions 219 00:07:46,764 --> 00:07:48,225 to person evaluations, 220 00:07:49,084 --> 00:07:50,685 so you can kind of pump those into 221 00:07:50,685 --> 00:07:52,764 as context and say, hey, in the company 222 00:07:52,764 --> 00:07:55,084 I work in, here's how I'm evaluated as 223 00:07:55,084 --> 00:07:57,165 an individual. Here's how my peers are evaluated, 224 00:07:57,165 --> 00:07:58,064 things like that. 225 00:07:58,920 --> 00:08:00,139 Surprisingly good job 226 00:08:00,600 --> 00:08:01,819 to the point where 227 00:08:02,279 --> 00:08:04,300 I could see it being helpful for folks 228 00:08:04,520 --> 00:08:06,360 or even helpful for maybe me as like 229 00:08:06,360 --> 00:08:07,580 a manager in the future 230 00:08:07,960 --> 00:08:09,560 to be able to structure my thinking and 231 00:08:09,560 --> 00:08:12,759 get better insights into things like helping team 232 00:08:12,759 --> 00:08:14,725 members get promoted and going 233 00:08:15,105 --> 00:08:17,745 through promo docs and things like that. I've 234 00:08:17,745 --> 00:08:18,725 used it for 235 00:08:19,345 --> 00:08:22,785 PRDs, so for, like, product requirement documents, like, 236 00:08:22,785 --> 00:08:23,285 justifications, 237 00:08:23,745 --> 00:08:24,245 specifications, 238 00:08:24,625 --> 00:08:27,444 things like that. It's been really good there, 239 00:08:27,824 --> 00:08:28,884 especially when, 240 00:08:29,779 --> 00:08:32,419 in my world, I'm often kinda comparing my 241 00:08:32,419 --> 00:08:34,600 thinking and trying to ground it 242 00:08:35,379 --> 00:08:38,100 in capabilities that exist within our competitors. So 243 00:08:38,100 --> 00:08:39,700 that might be like, hey. I'm in Azure 244 00:08:39,700 --> 00:08:41,639 storage, so that could be, like, 245 00:08:42,100 --> 00:08:42,600 AWS 246 00:08:42,934 --> 00:08:45,834 or GCP, Oracle with like OCI. 247 00:08:46,534 --> 00:08:49,174 It could be just a generic more generic 248 00:08:49,174 --> 00:08:51,975 like cloud competitor like Wasabi, things like that 249 00:08:51,975 --> 00:08:53,815 that are out there. So it's been really 250 00:08:53,815 --> 00:08:55,980 good for those kinds of things where I'm 251 00:08:55,980 --> 00:08:57,980 not always an expert in them, like and 252 00:08:57,980 --> 00:08:59,740 I'm still close enough to technology that, like, 253 00:08:59,740 --> 00:09:01,019 yeah, I could go out and do it, 254 00:09:01,019 --> 00:09:02,779 but I don't always have time to hop 255 00:09:02,779 --> 00:09:04,459 in and get, like, super deep and hands 256 00:09:04,459 --> 00:09:07,200 on with, like, the latest AWS feature, whereas 257 00:09:07,820 --> 00:09:09,519 I can point this to documentation, 258 00:09:10,379 --> 00:09:10,879 to 259 00:09:11,714 --> 00:09:14,434 YouTube transcripts, things like that, and have it 260 00:09:14,434 --> 00:09:15,174 come together. 261 00:09:15,634 --> 00:09:17,554 So it's been super helpful there. And then 262 00:09:17,554 --> 00:09:19,554 the last category I've seen folks using it 263 00:09:19,554 --> 00:09:20,855 for is 264 00:09:21,394 --> 00:09:22,454 to help them 265 00:09:22,995 --> 00:09:23,735 put together 266 00:09:24,209 --> 00:09:27,269 really good structured thinking around things like supportability 267 00:09:27,809 --> 00:09:28,309 and 268 00:09:28,929 --> 00:09:29,909 quality analysis 269 00:09:30,610 --> 00:09:33,089 within our within some of our products. So 270 00:09:33,089 --> 00:09:34,370 I've got a couple of folks who have 271 00:09:34,370 --> 00:09:36,449 been able to wrangle Researcher into a thing 272 00:09:36,449 --> 00:09:36,949 where 273 00:09:37,295 --> 00:09:39,394 it's able actually able to help them rationalize, 274 00:09:39,455 --> 00:09:42,014 like, insights based on, like, customer support cases 275 00:09:42,014 --> 00:09:44,735 and things like that and drive us into 276 00:09:44,735 --> 00:09:46,415 areas that we can go improve our products. 277 00:09:46,415 --> 00:09:48,254 Right? Like, how do we improve supportability? How 278 00:09:48,254 --> 00:09:49,394 do we improve quality? 279 00:09:49,899 --> 00:09:52,059 All those kinds of things that are out 280 00:09:52,059 --> 00:09:54,299 there. So I think just as a generic 281 00:09:54,299 --> 00:09:55,360 agent that's available 282 00:09:55,740 --> 00:09:58,240 out there to Microsoft three sixty five subscribers, 283 00:09:58,299 --> 00:09:59,120 super cool. 284 00:09:59,740 --> 00:10:01,440 It was also recently announced, 285 00:10:02,014 --> 00:10:03,134 and I'll put a link in the show 286 00:10:03,134 --> 00:10:04,815 notes. I'll grab one. It was also recently 287 00:10:04,815 --> 00:10:05,634 announced that 288 00:10:06,014 --> 00:10:09,934 the capabilities of a researcher agent, so things 289 00:10:09,934 --> 00:10:12,414 like the internal reasoning and all that, are 290 00:10:12,414 --> 00:10:15,054 also being pulled into things like Azure AI 291 00:10:15,054 --> 00:10:15,554 Foundry. 292 00:10:15,860 --> 00:10:17,779 So if you're an AI Foundry customer, you're 293 00:10:17,779 --> 00:10:19,060 gonna be able to go be able to 294 00:10:19,060 --> 00:10:20,600 go basically programmatically 295 00:10:21,220 --> 00:10:21,720 create 296 00:10:22,420 --> 00:10:25,800 your own researcher agents, which I think is 297 00:10:26,019 --> 00:10:26,519 a 298 00:10:26,899 --> 00:10:29,060 super cool and nifty thing as well. Yeah. 299 00:10:29,060 --> 00:10:30,554 I've been a fan of Researcher, and it 300 00:10:30,794 --> 00:10:32,394 uses a lot of like, if you've used 301 00:10:32,394 --> 00:10:33,774 the OpenAI Researcher, 302 00:10:34,235 --> 00:10:36,475 this is using or the DeepResearch. This is 303 00:10:36,475 --> 00:10:37,934 using OpenAI's DeepResearch. 304 00:10:38,714 --> 00:10:41,294 It also says that this is using, 305 00:10:41,914 --> 00:10:45,455 like, some special Microsoft three sixty five advanced 306 00:10:45,639 --> 00:10:47,659 orchestration and deep search capabilities. 307 00:10:48,120 --> 00:10:50,039 The one thing that's always interesting about these 308 00:10:50,360 --> 00:10:52,199 and it makes sense. Right? Like, Copilot, you 309 00:10:52,199 --> 00:10:53,399 go in and chat, you get an answer 310 00:10:53,399 --> 00:10:55,639 back really quick. Some of this research one, 311 00:10:55,639 --> 00:10:57,079 you go type it in, and you might 312 00:10:57,079 --> 00:10:59,179 have to wait, like, five or ten minutes 313 00:10:59,285 --> 00:11:01,445 for it to finish typing up all the 314 00:11:01,445 --> 00:11:03,945 details because it's really going out and 315 00:11:04,644 --> 00:11:05,144 scouring 316 00:11:05,684 --> 00:11:08,884 the Internet, looking at your Microsoft three sixty 317 00:11:08,884 --> 00:11:11,384 five data, looking at all the things. 318 00:11:12,165 --> 00:11:13,684 Just like if you were gonna go in 319 00:11:13,684 --> 00:11:15,899 and do a bunch of research, it takes 320 00:11:15,899 --> 00:11:17,500 you a little longer than just a quick 321 00:11:17,500 --> 00:11:20,779 search. So don't, like, expect researcher to pull 322 00:11:20,779 --> 00:11:22,220 you a bunch of data, like, two minutes 323 00:11:22,220 --> 00:11:24,379 before a meeting starts. Plan ahead a little 324 00:11:24,379 --> 00:11:25,980 bit if you're gonna run a deep research 325 00:11:25,980 --> 00:11:29,679 or researcher query. All things, it's kinda, like, 326 00:11:29,855 --> 00:11:31,295 only as good as the inputs you give 327 00:11:31,295 --> 00:11:33,815 it. I've noticed this more and more that 328 00:11:33,815 --> 00:11:36,175 a lot of the examples for these things 329 00:11:36,335 --> 00:11:37,615 and even if you go, like, look at, 330 00:11:37,615 --> 00:11:39,634 like, the blog post that announces this, 331 00:11:40,175 --> 00:11:40,995 they're very 332 00:11:41,295 --> 00:11:43,455 simplistic in the nature of the prompts that 333 00:11:43,455 --> 00:11:45,360 are fed into these things, right? They 334 00:11:45,919 --> 00:11:47,379 they're trying to give people, 335 00:11:48,320 --> 00:11:49,919 I think a little bit of a view 336 00:11:49,919 --> 00:11:51,519 that, like, oh, yeah, you can just type 337 00:11:51,519 --> 00:11:53,379 two sentences and get this really 338 00:11:53,839 --> 00:11:55,779 deep, meaningful thing out of it. 339 00:11:56,159 --> 00:11:58,574 My experience is that, yeah, you can do 340 00:11:58,574 --> 00:12:00,975 the two sentence thing, and you'll get something 341 00:12:00,975 --> 00:12:03,134 that looks deep and meaningful, but the reality 342 00:12:03,134 --> 00:12:04,914 is it's just a bunch of AI slop. 343 00:12:05,375 --> 00:12:07,954 You do still have to come in and 344 00:12:08,014 --> 00:12:10,814 put on your prompt engineering hat, provide all 345 00:12:10,814 --> 00:12:13,610 the context that you need, all the directions. 346 00:12:14,629 --> 00:12:16,169 You you do have to go through 347 00:12:16,789 --> 00:12:19,429 the those iterations and machinations along the way. 348 00:12:19,429 --> 00:12:21,590 Like like, to date, there's no way around 349 00:12:21,590 --> 00:12:23,269 that, but I think that's a good thing. 350 00:12:23,269 --> 00:12:25,029 Right? Because it still kinda grounds us as 351 00:12:25,029 --> 00:12:27,475 humans to go in there and perform some 352 00:12:27,475 --> 00:12:28,615 of that stuff ourselves, 353 00:12:29,875 --> 00:12:32,674 which I think is where, like, humans continue 354 00:12:32,674 --> 00:12:34,115 to have a bunch of the value too 355 00:12:34,115 --> 00:12:35,475 in, like, the chain of, like, how we 356 00:12:35,475 --> 00:12:36,934 use these AI tools 357 00:12:37,394 --> 00:12:39,335 is in the ability to 358 00:12:40,115 --> 00:12:42,860 see, like, the good patterns, the crappy patterns, 359 00:12:42,860 --> 00:12:45,120 the in between patterns, all the things that 360 00:12:45,419 --> 00:12:47,419 they spit out, and then be able to 361 00:12:47,419 --> 00:12:47,919 kinda, 362 00:12:49,419 --> 00:12:52,320 rationalize those and then refine them and 363 00:12:52,860 --> 00:12:53,360 continue 364 00:12:53,820 --> 00:12:55,519 to push them through. So 365 00:12:55,944 --> 00:12:58,584 I'm excited to see, even outside of just 366 00:12:58,584 --> 00:12:59,725 Researcher, more 367 00:13:00,105 --> 00:13:02,105 agents that are kinda built in like this 368 00:13:02,105 --> 00:13:03,245 and ready to go. 369 00:13:03,704 --> 00:13:04,764 And the directionality 370 00:13:05,065 --> 00:13:08,584 of, hey, agent structured agent x y zed 371 00:13:08,584 --> 00:13:10,409 shows up in m three sixty five chat, 372 00:13:10,490 --> 00:13:11,870 like Researcher, for example. 373 00:13:12,329 --> 00:13:15,449 And then it also comes as more of 374 00:13:15,449 --> 00:13:16,909 an agentic workflow 375 00:13:17,289 --> 00:13:20,409 with a Researcher capability inside Copilot Studio, and 376 00:13:20,409 --> 00:13:22,750 then it also comes with a full programmatic 377 00:13:22,970 --> 00:13:26,735 capability inside of Azure AI Foundry. So you 378 00:13:26,735 --> 00:13:28,815 eventually get to this, like, pretty cool three 379 00:13:28,815 --> 00:13:30,975 sixty view of the world where you can 380 00:13:30,975 --> 00:13:32,815 either meet your customers where they are if 381 00:13:32,815 --> 00:13:34,735 you're a company who's developing things on top 382 00:13:34,735 --> 00:13:35,475 of these tools, 383 00:13:35,934 --> 00:13:38,014 or your user base can just, like, use 384 00:13:38,014 --> 00:13:39,294 them out of the box, right, if you're 385 00:13:39,294 --> 00:13:41,960 an m three Copilot customer. Yep. You know 386 00:13:41,960 --> 00:13:43,960 what else I wanna see in agents, Scott? 387 00:13:43,960 --> 00:13:46,440 We're not gonna dive into this teaser. Future 388 00:13:46,440 --> 00:13:48,360 podcast episode, we'll talk more about these. I 389 00:13:48,360 --> 00:13:49,420 wanna see MCPs 390 00:13:49,879 --> 00:13:50,540 in agents 391 00:13:51,080 --> 00:13:52,920 in Copilot. That stuff is out there as 392 00:13:52,920 --> 00:13:55,164 well. For another day. Researchers out there. The 393 00:13:55,164 --> 00:13:56,924 other one that's out there is analyst. I 394 00:13:56,924 --> 00:13:58,205 don't know if you've had a chance to 395 00:13:58,205 --> 00:14:00,445 get hands on with analyst or I have 396 00:14:00,445 --> 00:14:02,125 not. Find a use case for that one 397 00:14:02,125 --> 00:14:04,785 yet. No. I don't do a lot of 398 00:14:05,245 --> 00:14:07,745 like, this one points more towards data scientists 399 00:14:07,940 --> 00:14:09,720 feeding in a bunch of raw data. 400 00:14:10,259 --> 00:14:12,339 This one's built on just going through some 401 00:14:12,339 --> 00:14:14,200 of the announcements here on OpenAI's 402 00:14:15,299 --> 00:14:17,959 o three mini reasoning model 403 00:14:18,259 --> 00:14:20,740 and really optimizing more for data or a 404 00:14:20,740 --> 00:14:23,855 data analyst type of job. I don't have 405 00:14:23,855 --> 00:14:25,695 a lot of that. I do have some 406 00:14:25,695 --> 00:14:27,695 data. It would be interesting to see if 407 00:14:27,695 --> 00:14:29,454 I could get it in here and spit 408 00:14:29,454 --> 00:14:32,174 something out where I've generated, like, a whole 409 00:14:32,174 --> 00:14:34,574 bunch of data around sharing links to prep 410 00:14:34,574 --> 00:14:36,034 for Copilot and 411 00:14:36,379 --> 00:14:38,000 have it kinda analyze 412 00:14:38,779 --> 00:14:40,879 that. But, no, in my day to day, 413 00:14:41,339 --> 00:14:43,419 I am doing a lot more research type 414 00:14:43,419 --> 00:14:45,820 stuff than analyst type stuff. So this is 415 00:14:45,820 --> 00:14:48,220 when I had just it's just because it 416 00:14:48,220 --> 00:14:49,740 hasn't applied to what I do day to 417 00:14:49,740 --> 00:14:52,085 day, I haven't spent as much time playing 418 00:14:52,085 --> 00:14:53,524 with that one. I think it is very 419 00:14:53,524 --> 00:14:56,164 specific to a role, right, like depending on 420 00:14:56,164 --> 00:14:57,205 how you get in there and what you 421 00:14:57,205 --> 00:14:57,705 use. 422 00:14:58,325 --> 00:14:59,065 My roles 423 00:14:59,605 --> 00:15:01,365 and the folks on my team, we end 424 00:15:01,365 --> 00:15:02,725 up wearing a little bit of, I think, 425 00:15:02,725 --> 00:15:04,264 of a data science hat. Like, 426 00:15:04,970 --> 00:15:06,829 I spend a lot of time in things 427 00:15:06,889 --> 00:15:08,110 like service telemetry, 428 00:15:08,649 --> 00:15:09,789 Kusto telemetry, 429 00:15:10,409 --> 00:15:13,049 trying to understand, like, feature usage. Right? Like, 430 00:15:13,049 --> 00:15:14,909 hey. We just rolled out this new feature. 431 00:15:15,049 --> 00:15:17,449 How many customers have it enabled? How long 432 00:15:17,449 --> 00:15:19,789 have they had it enabled? What's the churn? 433 00:15:20,465 --> 00:15:23,264 All sorts of things within that. So quite 434 00:15:23,264 --> 00:15:25,285 often the telemetry that I'm dealing with 435 00:15:25,665 --> 00:15:26,165 is, 436 00:15:26,705 --> 00:15:30,325 just really big numbers. Right? I could see 437 00:15:30,625 --> 00:15:31,845 hundreds of millions 438 00:15:32,304 --> 00:15:33,365 to billions 439 00:15:33,904 --> 00:15:35,684 to trillions of 440 00:15:36,069 --> 00:15:37,589 calls a day if I'm looking at something 441 00:15:37,589 --> 00:15:38,970 like transaction patterns. 442 00:15:39,509 --> 00:15:41,990 It could be hundreds of millions of storage 443 00:15:41,990 --> 00:15:44,149 accounts, things like that. So I've been trying 444 00:15:44,149 --> 00:15:46,329 to use this particularly when I build 445 00:15:47,509 --> 00:15:49,909 new reports or, like, new PBIs and things 446 00:15:49,909 --> 00:15:51,850 like that as we launch new things. Like, 447 00:15:52,044 --> 00:15:54,365 I've had not so decent luck with, like, 448 00:15:54,365 --> 00:15:56,365 Copilot inside of Power BI and things like 449 00:15:56,365 --> 00:15:57,644 that to help me figure out, like, what's 450 00:15:57,644 --> 00:15:59,644 a new view, or what's a way that 451 00:15:59,644 --> 00:16:01,644 I could present this data in a meaningful 452 00:16:01,644 --> 00:16:04,285 way that helps me rationalize it or helps 453 00:16:04,285 --> 00:16:05,184 others? Like, 454 00:16:06,040 --> 00:16:07,559 hey. I'm me as a product manager. I 455 00:16:07,559 --> 00:16:09,000 wanna see this. What would maybe, like, one 456 00:16:09,000 --> 00:16:11,399 of my VPs wanna see kinda thing? But 457 00:16:11,399 --> 00:16:12,920 analyst has been good for that. So I 458 00:16:12,920 --> 00:16:14,840 can't pump in all the data that I 459 00:16:14,840 --> 00:16:16,759 have, but I've been able to find that 460 00:16:16,759 --> 00:16:19,365 I can pump in truncated datasets. Okay. And 461 00:16:19,365 --> 00:16:20,904 then because it's 462 00:16:21,764 --> 00:16:23,065 because it's integrated 463 00:16:23,445 --> 00:16:24,585 and it understands 464 00:16:25,365 --> 00:16:27,225 how to write Python 465 00:16:28,165 --> 00:16:31,144 and spit out things like use like pandas 466 00:16:31,445 --> 00:16:33,945 and Yep. Pandas extensions, things like that, 467 00:16:34,329 --> 00:16:36,089 So you can spin in a smaller dataset, 468 00:16:36,089 --> 00:16:37,529 and you can have it kinda churn on 469 00:16:37,529 --> 00:16:39,209 it and figure it out. But the things 470 00:16:39,209 --> 00:16:41,289 that it'll give you is it will give 471 00:16:41,289 --> 00:16:43,690 you, like, the Python code to then go 472 00:16:43,690 --> 00:16:45,769 and put that in, like, a Jupyter notebook 473 00:16:45,769 --> 00:16:47,529 or things like that and be able to 474 00:16:47,529 --> 00:16:49,629 run it on, like, a broader scale 475 00:16:50,115 --> 00:16:52,434 and a bigger dataset. So it's been helpful 476 00:16:52,434 --> 00:16:54,195 for some of that stuff. The other one 477 00:16:54,195 --> 00:16:56,214 that I've seen it's helpful for is 478 00:16:56,595 --> 00:16:57,894 because it's doing Python 479 00:16:58,595 --> 00:16:59,815 and it's doing 480 00:17:00,514 --> 00:17:03,070 Pandas extensions and things like that is if 481 00:17:03,070 --> 00:17:05,470 you're somebody who's maybe new to Python and 482 00:17:05,470 --> 00:17:06,910 Excel and you're trying to figure out some 483 00:17:06,910 --> 00:17:09,309 of like the visualization capabilities and things like 484 00:17:09,309 --> 00:17:10,130 that are available, 485 00:17:10,589 --> 00:17:12,109 it can be really good for just like 486 00:17:12,109 --> 00:17:13,950 leaning you really quick into out of the 487 00:17:13,950 --> 00:17:15,970 box Python functions that are available 488 00:17:16,349 --> 00:17:17,890 that are gonna help you visualize 489 00:17:18,424 --> 00:17:21,065 your data in different ways and kinda kinda 490 00:17:21,065 --> 00:17:22,365 take a new pivot and 491 00:17:22,825 --> 00:17:24,265 understand it. So I think it's one that 492 00:17:24,265 --> 00:17:26,265 I still need to spend more time and 493 00:17:26,265 --> 00:17:27,865 get a little bit more hands on with 494 00:17:27,865 --> 00:17:29,164 to, like, really see 495 00:17:29,704 --> 00:17:31,384 where's the value and what goes on. But 496 00:17:31,384 --> 00:17:32,744 I could see, like, a whole bunch of 497 00:17:32,744 --> 00:17:34,720 folks, particularly in organizations 498 00:17:35,100 --> 00:17:36,860 that maybe they're not like me where I'm 499 00:17:36,860 --> 00:17:39,680 coming in with, like, a massive dataset that's 500 00:17:39,980 --> 00:17:41,900 gigabytes and gigabytes of data coming out of 501 00:17:41,900 --> 00:17:44,460 a database, but just a spreadsheet. Maybe I'm, 502 00:17:44,460 --> 00:17:46,480 like, tracking my POs in a spreadsheet. 503 00:17:47,555 --> 00:17:48,775 I'm doing, like, logistics. 504 00:17:49,634 --> 00:17:52,535 Like you said, hey. I'm tracking this analysis 505 00:17:52,755 --> 00:17:54,835 of sharing links or things like that. Like, 506 00:17:54,835 --> 00:17:56,355 if it's just sitting there in Excel, it's 507 00:17:56,355 --> 00:17:58,674 ultimately consumable by a tool like this, which 508 00:17:58,674 --> 00:17:59,734 makes it pretty turnkey. 509 00:18:03,779 --> 00:18:05,940 Do you feel overwhelmed by trying to manage 510 00:18:05,940 --> 00:18:08,179 your Office three sixty five environment? Are you 511 00:18:08,179 --> 00:18:11,480 facing unexpected issues that disrupt your company's productivity? 512 00:18:11,700 --> 00:18:13,700 Intelligink is here to help. Much like you 513 00:18:13,700 --> 00:18:15,539 take your car to the mechanic that has 514 00:18:15,539 --> 00:18:17,700 specialized knowledge on how to best keep your 515 00:18:17,700 --> 00:18:20,734 car running, Intelligent helps you with your Microsoft 516 00:18:20,734 --> 00:18:22,994 cloud environment because that's their expertise. 517 00:18:23,454 --> 00:18:25,694 Intelligent keeps up with the latest updates in 518 00:18:25,694 --> 00:18:27,855 the Microsoft cloud to help keep your business 519 00:18:27,855 --> 00:18:30,174 running smoothly and ahead of the curve. Whether 520 00:18:30,174 --> 00:18:32,179 you are a small organization with just a 521 00:18:32,179 --> 00:18:34,579 few users up to an organization of several 522 00:18:34,579 --> 00:18:37,380 thousand employees, they want to partner with you 523 00:18:37,380 --> 00:18:40,759 to implement and administer your Microsoft cloud technology. 524 00:18:41,380 --> 00:18:44,920 Visit them at inteliginc.com/podcast. 525 00:18:45,220 --> 00:18:51,944 That's intelligink.com/podcast 526 00:18:52,325 --> 00:18:54,484 for more information or to schedule a thirty 527 00:18:54,484 --> 00:18:56,505 minute call to get started with them today. 528 00:18:56,804 --> 00:19:00,164 Remember, Intelligink focuses on the Microsoft cloud so 529 00:19:00,164 --> 00:19:01,920 you can focus on your business. 530 00:19:04,160 --> 00:19:05,680 One of my questions was gonna be what 531 00:19:05,680 --> 00:19:08,240 you mentioned in terms of, like, how much 532 00:19:08,240 --> 00:19:10,559 data you can pump in. It says you 533 00:19:10,559 --> 00:19:12,400 can pump in Excel spreadsheet. You can pump 534 00:19:12,400 --> 00:19:14,980 in, like, CSVs or TSV files. 535 00:19:15,440 --> 00:19:17,894 But I was curious, like, are we 536 00:19:18,355 --> 00:19:21,234 talking thousands of rows, hundreds of thousands of 537 00:19:21,234 --> 00:19:21,734 rows? 538 00:19:22,275 --> 00:19:25,414 Have you found, like, where that breaking point 539 00:19:25,795 --> 00:19:29,394 is by doing truncated datasets? I've just assumed 540 00:19:29,394 --> 00:19:30,830 that it's not gonna be able to deal 541 00:19:30,830 --> 00:19:33,070 with, like, tens of millions of rows or 542 00:19:33,070 --> 00:19:35,230 things like that. So what I've been tending 543 00:19:35,230 --> 00:19:37,070 to doing is stick to a 100,000 rows 544 00:19:37,070 --> 00:19:39,950 or less, and that's been okay. Like so 545 00:19:39,950 --> 00:19:41,470 if, like, if I'm writing a big SQL 546 00:19:41,470 --> 00:19:43,894 query to pull out what would be 20,000,000 547 00:19:43,894 --> 00:19:46,075 rows a day for the past seven days, 548 00:19:46,454 --> 00:19:48,214 I'll write that query in a way where 549 00:19:48,214 --> 00:19:51,734 it's actually, hey, just give me 10,000 rows 550 00:19:51,734 --> 00:19:53,654 a day for the past seven days, but 551 00:19:53,654 --> 00:19:55,255 then help me go and put that in 552 00:19:55,255 --> 00:19:56,615 a spreadsheet. And then, like I said, I 553 00:19:56,615 --> 00:19:58,054 use this, I think, as a little bit 554 00:19:58,054 --> 00:19:58,714 as the 555 00:19:59,130 --> 00:20:01,529 the starting point to help me wrap my 556 00:20:01,529 --> 00:20:03,849 brain around it and see, like, what kind 557 00:20:03,849 --> 00:20:05,309 of insights can be derived 558 00:20:05,690 --> 00:20:07,769 versus me just having to ultimately, like, go 559 00:20:07,769 --> 00:20:09,369 in and, like, stare at that data and 560 00:20:09,369 --> 00:20:11,150 just drag things around randomly, 561 00:20:11,609 --> 00:20:13,549 see, like, what's the right way to 562 00:20:14,075 --> 00:20:15,595 to present this because I'm not a full 563 00:20:15,595 --> 00:20:17,755 time data scientist, right? Like arguably, I'm not 564 00:20:17,755 --> 00:20:20,474 a data scientist, and arguably, I'm overfunctioning by 565 00:20:20,474 --> 00:20:21,835 doing some of these things, and I'm probably 566 00:20:21,835 --> 00:20:24,255 doing my job. That said, I still 567 00:20:24,555 --> 00:20:26,154 do them, and they're still a part of 568 00:20:26,154 --> 00:20:27,674 my role today. So being that it's not 569 00:20:27,674 --> 00:20:28,575 one of my superpowers, 570 00:20:29,289 --> 00:20:31,450 this is one of those things that's a 571 00:20:31,450 --> 00:20:32,269 pretty good, 572 00:20:33,849 --> 00:20:35,630 a pretty good crotch slash enabler 573 00:20:35,930 --> 00:20:37,130 for me to be able to lean on. 574 00:20:37,130 --> 00:20:38,730 You mean it's a good co pilot to 575 00:20:38,730 --> 00:20:40,670 help you lean on and assist you? 576 00:20:41,210 --> 00:20:42,569 I could've just done that. I could've just 577 00:20:42,569 --> 00:20:45,255 said, hey, it's that copilot thing. Yeah. It's 578 00:20:45,335 --> 00:20:47,815 I'm hoping, like I said, that beyond researcher 579 00:20:47,815 --> 00:20:49,194 and analyst and 580 00:20:50,375 --> 00:20:52,375 prompt coach and writing coach and some of 581 00:20:52,375 --> 00:20:54,375 these other things that are out there as 582 00:20:54,375 --> 00:20:55,355 baked in agents, 583 00:20:55,734 --> 00:20:56,875 I continue to hope 584 00:20:57,470 --> 00:20:58,609 that market grows 585 00:20:58,910 --> 00:20:59,410 as 586 00:20:59,950 --> 00:21:02,609 a direct first party offering from Microsoft. 587 00:21:03,230 --> 00:21:04,830 And I think like where you really see 588 00:21:04,830 --> 00:21:06,029 like the rubber hit the road, like I 589 00:21:06,029 --> 00:21:08,029 said, is when these things grow out of 590 00:21:08,029 --> 00:21:08,769 like M365 591 00:21:09,230 --> 00:21:10,875 Copilot, and and then they start to bleed 592 00:21:10,875 --> 00:21:13,835 in a Copilot studio, AI Foundry, and then 593 00:21:13,835 --> 00:21:15,134 customers can kinda 594 00:21:15,434 --> 00:21:18,015 pick them up from wherever they are 595 00:21:18,394 --> 00:21:20,335 in in in their life cycle of things. 596 00:21:20,394 --> 00:21:21,535 But Researcher, 597 00:21:21,835 --> 00:21:25,179 by far, like, super cool, super super powerful. 598 00:21:25,179 --> 00:21:26,940 Like, folks should definitely go take a look 599 00:21:26,940 --> 00:21:28,140 at that one if they have access to 600 00:21:28,140 --> 00:21:30,140 it. Absolutely. And if you are looking for 601 00:21:30,140 --> 00:21:31,980 it, we should mention that too. Because I've 602 00:21:31,980 --> 00:21:33,339 had a few people that'd be like, not 603 00:21:33,339 --> 00:21:35,019 an app researcher yet. Like you said, it 604 00:21:35,019 --> 00:21:37,679 is an agent. So if you're in Teams, 605 00:21:38,125 --> 00:21:40,525 it's not gonna show up by default yet. 606 00:21:40,525 --> 00:21:42,525 You should have, like, the agent panel up 607 00:21:42,525 --> 00:21:44,444 there where you can go click to get 608 00:21:44,444 --> 00:21:46,865 agents, and then you go click, get agents. 609 00:21:47,325 --> 00:21:50,784 Researcher, analyst should both show up for you 610 00:21:50,924 --> 00:21:52,144 as available agents 611 00:21:52,529 --> 00:21:54,609 assuming you have that Microsoft three sixty five 612 00:21:54,609 --> 00:21:56,690 Copilot license, and then you can just go 613 00:21:56,690 --> 00:21:58,529 click to add that agent to Teams, and 614 00:21:58,529 --> 00:21:59,970 then it shows up as one of those 615 00:21:59,970 --> 00:22:02,529 available agents in your list of agents. This 616 00:22:02,529 --> 00:22:04,210 goes back to an earlier conversation we had. 617 00:22:04,210 --> 00:22:06,049 Right? Like, that depends on your entry point 618 00:22:06,049 --> 00:22:06,710 to Copilot 619 00:22:07,015 --> 00:22:08,535 and how you get there. So that's the 620 00:22:08,535 --> 00:22:10,214 team side. If you're just going into, like, 621 00:22:10,214 --> 00:22:10,954 that new 622 00:22:11,494 --> 00:22:13,335 Copilot if you're going into the Copilot app 623 00:22:13,335 --> 00:22:15,654 or, like, the default landing page, hey, you 624 00:22:15,654 --> 00:22:16,934 go portal.office.com, 625 00:22:16,934 --> 00:22:17,595 get redirected 626 00:22:18,134 --> 00:22:20,630 over to blah blah blah .microsoft.cloud, 627 00:22:20,630 --> 00:22:22,630 whatever it is today. Whatever that one is. 628 00:22:22,630 --> 00:22:25,430 Yeah. Whatever that one is. You'll also see 629 00:22:25,430 --> 00:22:26,250 it there. 630 00:22:26,710 --> 00:22:29,349 So agents appear above your chats, but they're 631 00:22:29,349 --> 00:22:31,609 in the same kinda chat section. 632 00:22:32,295 --> 00:22:34,535 So so, yeah, the they just lead right 633 00:22:34,535 --> 00:22:35,674 up there. Absolutely. 634 00:22:35,975 --> 00:22:37,575 So if you don't have it, go look 635 00:22:37,575 --> 00:22:39,575 for it. Try to install that agent. Add 636 00:22:39,575 --> 00:22:41,575 that agent. There are some other cool agents 637 00:22:41,575 --> 00:22:42,775 out there. I haven't done as much with 638 00:22:42,775 --> 00:22:44,455 the other one. Like, there's an idea coach 639 00:22:44,455 --> 00:22:46,934 and, the visual creator is an agent and 640 00:22:46,934 --> 00:22:49,319 some of those. So go check out the 641 00:22:49,319 --> 00:22:51,079 agents. Only as good as what you put 642 00:22:51,079 --> 00:22:52,619 in is what you get out. 643 00:22:53,160 --> 00:22:55,400 Don't take the example prompts that you see 644 00:22:55,400 --> 00:22:56,920 in blog posts and things like that. It's 645 00:22:56,920 --> 00:22:58,599 like that's, like, not the amount of effort 646 00:22:58,599 --> 00:23:00,119 you should be putting into these things. You 647 00:23:00,119 --> 00:23:01,339 should be putting in more. 648 00:23:01,644 --> 00:23:04,045 There's actually an agent out there which is 649 00:23:04,045 --> 00:23:05,184 a prompt coach. 650 00:23:05,565 --> 00:23:07,724 I believe it's available to everybody. Let me 651 00:23:07,724 --> 00:23:10,125 go look here. But yeah. We can take 652 00:23:10,125 --> 00:23:12,204 a look real quick. Yeah. Right there. Prompt 653 00:23:12,204 --> 00:23:13,424 coach. So 654 00:23:13,724 --> 00:23:16,740 you can use things like prompt coach to 655 00:23:16,740 --> 00:23:18,740 go and think about your prompts and what 656 00:23:18,740 --> 00:23:19,960 you're gonna put in there. 657 00:23:20,259 --> 00:23:22,019 So like, hey, help me generate a prompt 658 00:23:22,019 --> 00:23:24,259 that I'm gonna use in Researcher to perform 659 00:23:24,259 --> 00:23:27,380 this research. I I'm hoping for this expected 660 00:23:27,380 --> 00:23:30,039 outcome, this set of outputs, things like that, 661 00:23:30,464 --> 00:23:32,464 and it'll help you kind of along the 662 00:23:32,464 --> 00:23:34,464 way. So if you're struggling with ideas there 663 00:23:34,464 --> 00:23:35,924 about, like, how to write a good prompt, 664 00:23:36,144 --> 00:23:37,984 prompt coach is another good one. Yeah. That 665 00:23:37,984 --> 00:23:39,424 was one other thing I was gonna say. 666 00:23:39,424 --> 00:23:40,944 Researcher does help a little bit with that 667 00:23:40,944 --> 00:23:42,304 too, I've noticed. Like, if I put in 668 00:23:42,304 --> 00:23:45,349 a super short researcher prompt, it will actually 669 00:23:45,490 --> 00:23:47,569 ask me for more details sometimes. It'll be 670 00:23:47,569 --> 00:23:49,089 like, well, what do you want? Do you 671 00:23:49,089 --> 00:23:51,250 want this or this? Or it'll say, just 672 00:23:51,250 --> 00:23:53,190 tell me go ahead, and it'll make its 673 00:23:53,410 --> 00:23:56,049 best guess. But researcher does do a little 674 00:23:56,049 --> 00:23:58,375 bit more to try to at least encourage 675 00:23:58,434 --> 00:23:59,414 you to write, 676 00:23:59,714 --> 00:24:01,414 I would say, more complete 677 00:24:01,875 --> 00:24:03,974 prompts versus just a single sentence. 678 00:24:04,595 --> 00:24:05,095 So 679 00:24:05,394 --> 00:24:07,794 that be that. Scott, are you ready for 680 00:24:07,794 --> 00:24:08,454 some noncopilot 681 00:24:08,835 --> 00:24:09,335 news? 682 00:24:10,250 --> 00:24:11,850 Funny enough, we set out to do today. 683 00:24:11,850 --> 00:24:13,369 I didn't think I was gonna spend time 684 00:24:13,369 --> 00:24:15,549 talking about being old and just about Researcher 685 00:24:15,609 --> 00:24:17,369 for that long, but, yeah, here we are 686 00:24:17,369 --> 00:24:19,769 once again. Here we are. It happens. We 687 00:24:19,769 --> 00:24:22,670 do what we do. This was an announcement 688 00:24:22,730 --> 00:24:24,970 I caught today. I don't know when this 689 00:24:24,970 --> 00:24:25,609 one actually 690 00:24:26,134 --> 00:24:28,615 July 1. Oh, man, Scott. I'm old. We're 691 00:24:28,615 --> 00:24:30,934 out I'm behind on my news. This was, 692 00:24:30,934 --> 00:24:32,615 like, a week and a half ago for 693 00:24:32,615 --> 00:24:34,475 when I'm recording this, but 694 00:24:34,934 --> 00:24:37,434 this one, I found interesting. So 695 00:24:37,815 --> 00:24:38,315 back 696 00:24:38,880 --> 00:24:40,420 November, 697 00:24:40,640 --> 00:24:42,640 so a couple years ago no. A year 698 00:24:42,640 --> 00:24:43,940 and a half ago, Microsoft 699 00:24:44,799 --> 00:24:45,299 unified 700 00:24:45,839 --> 00:24:47,380 or not necessarily unified, 701 00:24:47,680 --> 00:24:49,460 but pulled Microsoft 702 00:24:49,920 --> 00:24:50,420 Sentinel 703 00:24:50,815 --> 00:24:54,894 into Defender XDR or the Defender portal, security.microsoft.com, 704 00:24:54,894 --> 00:24:56,994 so that you could go into Defender 705 00:24:57,535 --> 00:24:58,035 and 706 00:24:58,575 --> 00:25:00,654 add Sentinel in there. You can manage Sentinel. 707 00:25:00,654 --> 00:25:03,234 You can write your Sentinel queries. Like, almost 708 00:25:03,295 --> 00:25:03,955 the full 709 00:25:04,470 --> 00:25:08,250 interaction with Sentinel, right in Defender. Well, come 710 00:25:08,309 --> 00:25:09,910 07/01/2025 711 00:25:09,910 --> 00:25:12,789 now, Microsoft announced that they are moving to 712 00:25:12,789 --> 00:25:14,730 the next phase of the transition 713 00:25:15,269 --> 00:25:18,775 with a target to retire the Azure portal 714 00:25:18,775 --> 00:25:22,714 for Microsoft Sentinel by 07/01/2026. 715 00:25:22,934 --> 00:25:24,954 So gave you twelve months 716 00:25:25,335 --> 00:25:25,835 where 717 00:25:26,375 --> 00:25:26,875 Sentinel's 718 00:25:27,174 --> 00:25:30,134 just gonna go away in Azure at least 719 00:25:30,134 --> 00:25:32,900 from the portal aspect. Like, this is one 720 00:25:32,900 --> 00:25:35,539 that I wanna see where this goes. Say 721 00:25:35,539 --> 00:25:37,700 customers not using the Defender portal should plan 722 00:25:37,700 --> 00:25:38,919 their transition accordingly. 723 00:25:39,619 --> 00:25:41,779 I mean, I have a few thoughts here. 724 00:25:41,779 --> 00:25:44,919 One, this makes sense. Right? Let's unify 725 00:25:45,815 --> 00:25:46,315 security 726 00:25:46,694 --> 00:25:49,434 in the security center. Let's make one portal, 727 00:25:49,575 --> 00:25:51,335 security.microsoft.com, 728 00:25:51,335 --> 00:25:52,934 to do all the security stuff. I mean, 729 00:25:52,934 --> 00:25:54,855 it's single pane of glass. Right. That's a 730 00:25:54,855 --> 00:25:57,974 good thing from an experience perspective, right, especially 731 00:25:57,974 --> 00:25:59,990 if you are Yes. The folks who have 732 00:25:59,990 --> 00:26:02,230 to wrangle and manage these services. Like, they 733 00:26:02,230 --> 00:26:03,129 they have been 734 00:26:03,669 --> 00:26:06,549 fairly disparate, and I think that does make 735 00:26:06,549 --> 00:26:07,990 it tough. So, yeah, putting them all under 736 00:26:07,990 --> 00:26:09,049 the Defender umbrella 737 00:26:09,589 --> 00:26:10,889 makes sense. It's probably 738 00:26:11,269 --> 00:26:13,994 more about the way the capabilities manifest within 739 00:26:13,994 --> 00:26:17,194 there, right, like, depending on how you interact 740 00:26:17,194 --> 00:26:18,875 with them and how they come across. So 741 00:26:19,115 --> 00:26:21,274 It'll be interesting to see because Sentinel is 742 00:26:21,274 --> 00:26:23,375 really I don't wanna call it 743 00:26:23,754 --> 00:26:25,674 an add on, but it kind of is. 744 00:26:25,674 --> 00:26:27,355 It's almost like an add on to log 745 00:26:27,355 --> 00:26:29,730 analytics. Like, it sits on top of 746 00:26:30,029 --> 00:26:31,650 a log analytics workspace, 747 00:26:32,190 --> 00:26:33,410 Azure Monitor workspace, 748 00:26:33,869 --> 00:26:36,589 however you wanna describe it, to the point 749 00:26:36,589 --> 00:26:38,750 of, I've done this before, Scott. I don't 750 00:26:38,750 --> 00:26:40,349 know if this is supported or not, so 751 00:26:40,349 --> 00:26:42,345 nobody do this and tell me that it's 752 00:26:42,345 --> 00:26:44,105 unsupported. It may or may not be. Where 753 00:26:44,105 --> 00:26:46,505 I've had to move Sentinel from one Azure 754 00:26:46,505 --> 00:26:48,424 subscription to the next because it is tied 755 00:26:48,424 --> 00:26:50,025 to a subscription or resource group, all of 756 00:26:50,025 --> 00:26:52,204 that, you can actually uninstall 757 00:26:52,825 --> 00:26:55,484 sent you can't move Sentinel from one subscription 758 00:26:55,544 --> 00:26:58,160 to another, but you can uninstall Sentinel from 759 00:26:58,160 --> 00:26:59,460 your log analytics workspace, 760 00:26:59,840 --> 00:27:02,240 move the log analytics workspace, then reinstall Sentinel 761 00:27:02,240 --> 00:27:04,080 on top of the log analytics workspace to 762 00:27:04,080 --> 00:27:05,840 move it. But that leads to there's a 763 00:27:05,840 --> 00:27:08,880 lot of Azure y stuff yet involved in 764 00:27:08,880 --> 00:27:10,980 Sentinel from the log analytics workspace. 765 00:27:11,884 --> 00:27:13,424 Sentinel is still a 766 00:27:13,804 --> 00:27:15,664 pay per use type of 767 00:27:16,044 --> 00:27:16,544 construct 768 00:27:16,924 --> 00:27:19,244 based on an Azure subscription. And, like, are 769 00:27:19,244 --> 00:27:21,004 they gonna pull this in where it's gonna 770 00:27:21,004 --> 00:27:22,784 be similar to, like, the SharePoint 771 00:27:23,085 --> 00:27:25,085 I think it's still called Syntex, but it's 772 00:27:25,085 --> 00:27:26,304 essentially all the SharePoint 773 00:27:26,650 --> 00:27:28,890 PAYGo stuff where now you're still gonna have 774 00:27:28,890 --> 00:27:30,750 to, like, tie your security 775 00:27:31,049 --> 00:27:33,470 center to an Azure subscription 776 00:27:34,329 --> 00:27:36,009 so that you can do all the PAYGo 777 00:27:36,009 --> 00:27:38,490 stuff. And there's also a few things yet 778 00:27:38,490 --> 00:27:40,544 within Sentinel. I had it up here. Where'd 779 00:27:40,544 --> 00:27:42,644 my Sentinel go? Like, the workspace 780 00:27:43,345 --> 00:27:45,845 manager where you can manage multiple 781 00:27:46,144 --> 00:27:47,125 Sentinel workspaces 782 00:27:47,505 --> 00:27:48,484 within Sentinel. 783 00:27:49,105 --> 00:27:49,605 And 784 00:27:50,144 --> 00:27:51,044 some of these, 785 00:27:51,345 --> 00:27:53,505 I would say, they're more intricacies of Sentinel 786 00:27:53,505 --> 00:27:56,609 that aren't there yet in Defender for now. 787 00:27:56,670 --> 00:27:58,509 Again, my assumption is they're gonna bring all 788 00:27:58,509 --> 00:28:00,369 that stuff over. They're gonna start 789 00:28:00,750 --> 00:28:03,230 migrating all the UI over, but it does 790 00:28:03,230 --> 00:28:05,650 still leave me with some questions on how 791 00:28:05,710 --> 00:28:07,835 some of that's gonna work a year from 792 00:28:07,835 --> 00:28:09,674 now. Like all things, you see a little 793 00:28:09,674 --> 00:28:11,355 bit more of some of the stuff that's 794 00:28:11,355 --> 00:28:13,355 been pretty thematic lately where, like, with these 795 00:28:13,355 --> 00:28:16,315 SaaSy products or it's software as a service, 796 00:28:16,315 --> 00:28:18,955 and it's moving around and doing those kinds 797 00:28:18,955 --> 00:28:19,615 of things. 798 00:28:20,235 --> 00:28:22,720 I imagine over time, it all gets incorporated 799 00:28:23,099 --> 00:28:24,240 in a similar way, 800 00:28:24,619 --> 00:28:27,039 hopefully, without too much, like, 801 00:28:28,059 --> 00:28:30,220 who moved my cheese kinda pain along the 802 00:28:30,220 --> 00:28:33,259 way. Yeah. And Microsoft's gonna start redirecting you. 803 00:28:33,259 --> 00:28:35,099 So they say in here preparing for the 804 00:28:35,099 --> 00:28:35,599 retirement. 805 00:28:36,065 --> 00:28:38,865 They're committed to supporting every single customer making 806 00:28:38,865 --> 00:28:41,984 that transition, Scott. But beginning July 807 00:28:41,984 --> 00:28:42,785 1, 808 00:28:42,785 --> 00:28:44,785 so twelve months from now, users are gonna 809 00:28:44,785 --> 00:28:48,005 start getting automatically redirected over the security center. 810 00:28:48,304 --> 00:28:50,230 If you haven't done it now, like, I 811 00:28:50,230 --> 00:28:51,750 also encourage you if you haven't done this 812 00:28:51,750 --> 00:28:53,589 yet, you can already connect the two. If 813 00:28:53,589 --> 00:28:55,909 you're using Sentinel, go into your security center 814 00:28:55,909 --> 00:28:57,909 and connect it all up because it does 815 00:28:57,909 --> 00:29:00,230 give you that single pane of glass, single 816 00:29:00,230 --> 00:29:02,549 place to go. I'm also curious with this, 817 00:29:02,549 --> 00:29:04,605 Scott, how close behind 818 00:29:06,025 --> 00:29:09,224 Microsoft Defender for Cloud will be because that's 819 00:29:09,224 --> 00:29:10,765 going to be the remaining 820 00:29:11,545 --> 00:29:12,684 security construct. 821 00:29:13,625 --> 00:29:14,845 So that was a question 822 00:29:15,299 --> 00:29:16,980 in the back of my head, right? There's 823 00:29:16,980 --> 00:29:18,820 a whole ton of stuff under Defender for 824 00:29:18,820 --> 00:29:19,880 Cloud, which is 825 00:29:20,740 --> 00:29:21,619 100% 826 00:29:21,619 --> 00:29:23,000 Azure only, like 827 00:29:23,299 --> 00:29:24,360 and doesn't 828 00:29:24,900 --> 00:29:27,160 manifest in any other way, at least 829 00:29:27,794 --> 00:29:29,075 I'm maybe a little close to home for 830 00:29:29,075 --> 00:29:31,875 me in storage land. There's Microsoft Defender for 831 00:29:31,875 --> 00:29:34,274 storage, which is part of Defender for cloud, 832 00:29:34,274 --> 00:29:36,674 and that's Defender for Azure storage. That's not 833 00:29:36,674 --> 00:29:37,815 Defender for 834 00:29:38,194 --> 00:29:38,694 for 835 00:29:39,075 --> 00:29:41,875 every other object storage provider that's out there 836 00:29:41,875 --> 00:29:42,934 kind of thing. So 837 00:29:43,289 --> 00:29:46,090 I don't know, but I I one one 838 00:29:46,090 --> 00:29:48,970 would wonder because Defender for Cloud is, like, 839 00:29:48,970 --> 00:29:50,730 the whole other part of the issue that 840 00:29:50,730 --> 00:29:52,509 still hasn't dropped. I would speculate. 841 00:29:52,809 --> 00:29:54,730 I would dare to bet that we will 842 00:29:54,730 --> 00:29:55,630 see an announcement 843 00:29:56,250 --> 00:29:58,404 sometime in the next year. Because in the 844 00:29:58,404 --> 00:30:00,565 next year, we've got Ignite coming up. We 845 00:30:00,565 --> 00:30:02,805 have different events coming up. We got another 846 00:30:02,805 --> 00:30:05,765 Ignite, a build. Yeah. Yep. I would guess 847 00:30:05,765 --> 00:30:08,325 one of those, we're gonna see some type 848 00:30:08,325 --> 00:30:10,805 of announcement, not that Defender for Cloud is 849 00:30:10,805 --> 00:30:13,380 retiring, but that it starts getting pulled into 850 00:30:13,380 --> 00:30:15,559 Security Center. To me, it makes sense. 851 00:30:15,859 --> 00:30:17,700 It started. I would say Defender 852 00:30:18,179 --> 00:30:20,099 I call it Security Center. It's not even 853 00:30:20,099 --> 00:30:23,720 Security Center anymore. Microsoft Defender started as security 854 00:30:23,859 --> 00:30:26,295 and compliance for Microsoft March. 855 00:30:26,375 --> 00:30:28,315 But even as you look at it now, 856 00:30:28,375 --> 00:30:30,535 like, you have your vulnerability management for your 857 00:30:30,535 --> 00:30:33,174 endpoints on there. You have Sentinel in there 858 00:30:33,174 --> 00:30:33,674 now. 859 00:30:34,055 --> 00:30:35,994 You have different exposure management, 860 00:30:36,615 --> 00:30:38,154 Defender for cloud apps. 861 00:30:38,630 --> 00:30:41,210 Security Center already has started transitioning, 862 00:30:41,750 --> 00:30:43,910 I would say or Defender. I need to 863 00:30:43,910 --> 00:30:46,009 call it the right thing. Microsoft Defender 864 00:30:46,309 --> 00:30:48,970 already has started transitioning to a broader 865 00:30:49,430 --> 00:30:51,769 this is your Microsoft cloud 866 00:30:52,515 --> 00:30:53,015 security 867 00:30:53,555 --> 00:30:55,654 portal for all things, for endpoints, 868 00:30:56,115 --> 00:30:56,775 for identities. 869 00:30:57,234 --> 00:30:59,555 Because let's face it, we say Defender for 870 00:30:59,555 --> 00:31:01,234 Cloud is the whole Azure aspect of it, 871 00:31:01,234 --> 00:31:02,855 but you're still gonna have identities, 872 00:31:03,234 --> 00:31:05,494 which are already in Defender. 873 00:31:05,869 --> 00:31:06,690 So it kinda 874 00:31:07,230 --> 00:31:10,029 makes sense that we would just see all 875 00:31:10,029 --> 00:31:10,769 of these 876 00:31:11,070 --> 00:31:12,769 Defender for Cloud, Sentinel, 877 00:31:13,470 --> 00:31:15,869 all the Microsoft three sixty five security stuff, 878 00:31:15,869 --> 00:31:17,250 like a single 879 00:31:17,630 --> 00:31:20,805 portal for all things Microsoft cloud security? Yeah. 880 00:31:20,805 --> 00:31:22,644 The single pane of glass isn't bad. I'm 881 00:31:22,644 --> 00:31:25,045 not saying there's anything bad about it. I 882 00:31:25,045 --> 00:31:27,705 do wonder sometimes about just the 883 00:31:28,085 --> 00:31:30,244 the spread of services that show up because 884 00:31:30,244 --> 00:31:31,625 I think in a lot of organizations, 885 00:31:32,840 --> 00:31:34,220 the folks who do security, 886 00:31:34,920 --> 00:31:36,279 it's one thing to say we have a 887 00:31:36,279 --> 00:31:37,880 security org, but I would bet within most 888 00:31:37,880 --> 00:31:39,960 security orgs you have the folks who work 889 00:31:39,960 --> 00:31:40,619 on identity, 890 00:31:40,920 --> 00:31:43,019 and you have the folks who work on 891 00:31:43,400 --> 00:31:43,900 endpoints, 892 00:31:44,200 --> 00:31:46,539 and you have the folks who work on 893 00:31:47,375 --> 00:31:47,855 your 894 00:31:48,335 --> 00:31:50,654 even your differentiated endpoints, maybe just like your 895 00:31:50,654 --> 00:31:53,554 virtual machines or your cloud hosted things. So 896 00:31:54,095 --> 00:31:56,654 that still seems pretty prevalent. And so so 897 00:31:56,654 --> 00:31:58,174 I do wonder how that manifests in a 898 00:31:58,174 --> 00:32:00,460 single pane of glass experience. Right? Like, does 899 00:32:00,460 --> 00:32:02,860 this thing eventually get our backed to the 900 00:32:02,860 --> 00:32:03,360 end 901 00:32:03,900 --> 00:32:06,059 of nothingness where you come in and, like, 902 00:32:06,059 --> 00:32:07,740 hey. I log in, and I'm only an 903 00:32:07,740 --> 00:32:11,019 admin for Defender for cloud, and, specifically, like, 904 00:32:11,019 --> 00:32:12,974 all I can see is storage accounts. Like, 905 00:32:13,054 --> 00:32:14,815 does now that home page just become a 906 00:32:14,815 --> 00:32:16,494 blank page and a blank view for me 907 00:32:16,494 --> 00:32:17,634 kinda thing? So, 908 00:32:18,015 --> 00:32:20,174 yeah, I don't know. We'll see how it 909 00:32:20,174 --> 00:32:22,974 manifests over time. I'm sure there's somebody else 910 00:32:22,974 --> 00:32:24,575 who's getting paid way more money than you 911 00:32:24,575 --> 00:32:25,694 or I to think about it. So I 912 00:32:25,694 --> 00:32:27,535 mean, I think it does. You already have 913 00:32:27,535 --> 00:32:30,259 it somewhat. Like, you can go in already 914 00:32:30,480 --> 00:32:32,960 to your security center and your permissions and 915 00:32:32,960 --> 00:32:35,200 look at roles for cloud apps. Because this 916 00:32:35,200 --> 00:32:36,900 is another one that's kinda been 917 00:32:37,200 --> 00:32:39,920 rolled in over time as Microsoft Defender for 918 00:32:39,920 --> 00:32:41,600 cloud app or it used to be cloud 919 00:32:41,600 --> 00:32:44,695 app security, MCAS, Microsoft cloud app security, where 920 00:32:44,695 --> 00:32:46,875 you can now go in and set roles 921 00:32:47,095 --> 00:32:47,595 for, 922 00:32:48,535 --> 00:32:49,994 different cloud discovery, 923 00:32:50,455 --> 00:32:53,914 or there's security operator roles. There's app instance 924 00:32:53,974 --> 00:32:56,869 roles. Is that every global admin? So I 925 00:32:56,869 --> 00:32:59,750 think you're right in that you start like, 926 00:32:59,750 --> 00:33:02,250 there's a whole section for endpoint roles and 927 00:33:02,630 --> 00:33:05,210 what roles you wanna assign people for endpoints 928 00:33:05,350 --> 00:33:06,090 and defender. 929 00:33:06,470 --> 00:33:08,390 So I think you are gonna see that 930 00:33:08,390 --> 00:33:11,255 RBAC come into play where people are going 931 00:33:11,255 --> 00:33:11,755 to 932 00:33:12,214 --> 00:33:14,394 you could still limit people to just certain 933 00:33:14,615 --> 00:33:17,414 security roles in the Defender portal. I think 934 00:33:17,414 --> 00:33:18,695 it's one of those things we'll have to 935 00:33:18,695 --> 00:33:21,174 watch over the next year, two years depending 936 00:33:21,174 --> 00:33:23,549 on if timeline shift, things like that? This 937 00:33:23,549 --> 00:33:25,630 was an interesting one. I'm actually kinda looking 938 00:33:25,630 --> 00:33:27,230 forward to this, keeping an eye on this, 939 00:33:27,230 --> 00:33:30,429 how it manifests itself over the coming months. 940 00:33:30,429 --> 00:33:31,789 I think it's great for you, like, as 941 00:33:31,789 --> 00:33:33,549 a service provider. Right? Like, if you could 942 00:33:33,549 --> 00:33:36,269 hop into a customer's environment, get access, have 943 00:33:36,269 --> 00:33:38,289 that one stop shopping and that, like, 944 00:33:38,884 --> 00:33:41,365 great, like, top down view of everything that's 945 00:33:41,365 --> 00:33:43,784 out there. Like, that that that's all goodness. 946 00:33:44,164 --> 00:33:46,585 I think I'd wanna see the balance between, 947 00:33:46,884 --> 00:33:48,884 like, folks like you doing that kind of 948 00:33:48,884 --> 00:33:49,944 activity versus 949 00:33:50,484 --> 00:33:52,884 maybe far more granular, like, hey. I'm down 950 00:33:52,884 --> 00:33:55,049 here, and this is, like, the one part 951 00:33:55,049 --> 00:33:56,730 of the sandbox that I play in. I 952 00:33:56,730 --> 00:33:58,909 don't care about seeing cloud apps and email 953 00:33:59,130 --> 00:33:59,710 and collaboration 954 00:34:00,009 --> 00:34:02,009 and identities because to your point, all I'm 955 00:34:02,009 --> 00:34:03,609 worried about is endpoint or all I'm worried 956 00:34:03,609 --> 00:34:05,149 about, even within endpoint, 957 00:34:05,769 --> 00:34:08,465 is IoT security. That's a thing as well 958 00:34:08,465 --> 00:34:11,105 in some big companies where people are just 959 00:34:11,105 --> 00:34:14,405 focused on security for IoT. Yeah. Makes sense. 960 00:34:14,465 --> 00:34:15,985 Alright. Turns out we made it through another 961 00:34:15,985 --> 00:34:17,585 one. We did. And we still had a 962 00:34:17,585 --> 00:34:19,530 topic or two to talk about that we'll 963 00:34:19,530 --> 00:34:21,530 have to maybe talk about later. But I'm 964 00:34:21,530 --> 00:34:22,510 also excited 965 00:34:22,809 --> 00:34:25,130 to talk about MCPs, Scott. I've been playing 966 00:34:25,130 --> 00:34:26,969 with these. We started talking about this a 967 00:34:26,969 --> 00:34:29,130 week ago. I've been planning for this episode, 968 00:34:29,130 --> 00:34:30,670 Scott. I've got all kinds of thoughts. 969 00:34:31,769 --> 00:34:33,929 Yeah. Teaser. Did I put something on your 970 00:34:33,929 --> 00:34:35,735 list that you're actually into? Oh, yeah. You 971 00:34:35,735 --> 00:34:37,575 absolutely put something on my list. I should 972 00:34:37,575 --> 00:34:39,655 have been doing client work last night. Instead, 973 00:34:39,655 --> 00:34:41,414 I was up from, like I don't know. 974 00:34:41,414 --> 00:34:42,614 I put the kids to bed at nine. 975 00:34:42,614 --> 00:34:44,555 I think I was playing with just different 976 00:34:44,614 --> 00:34:46,775 MCPs and playing around with some things from, 977 00:34:46,775 --> 00:34:49,929 like, 09:00 until, like, 12:30 or one last 978 00:34:49,929 --> 00:34:50,429 night. 979 00:34:51,929 --> 00:34:52,429 Perfect. 980 00:34:52,889 --> 00:34:54,569 We'll have to talk about, like, how many 981 00:34:54,569 --> 00:34:57,150 ports are open for weird little MPM servers 982 00:34:57,369 --> 00:34:58,829 running on your local desktop. 983 00:35:00,255 --> 00:35:01,934 But we'll leave that for we'll leave that 984 00:35:01,934 --> 00:35:03,074 for another episode. 985 00:35:03,375 --> 00:35:04,994 Teaser for upcoming episodes, 986 00:35:05,375 --> 00:35:07,074 MCPs, or if you have questions. 987 00:35:07,375 --> 00:35:08,894 So if you're still listening and you have 988 00:35:08,894 --> 00:35:11,474 questions about MCPs or thoughts about MCPs 989 00:35:11,934 --> 00:35:13,855 that you would like covered in a future 990 00:35:13,855 --> 00:35:16,269 episode, Let us know. Reach out LinkedIn, 991 00:35:16,730 --> 00:35:18,190 contact form on the website, 992 00:35:18,730 --> 00:35:20,250 book a meeting with me now that you 993 00:35:20,250 --> 00:35:21,929 can do that on my website, and then 994 00:35:21,929 --> 00:35:24,010 I will send researcher after you to learn 995 00:35:24,010 --> 00:35:24,909 all about you. 996 00:35:25,369 --> 00:35:27,369 However you would like to reach out via 997 00:35:27,369 --> 00:35:30,535 the social media or website, if there's anything 998 00:35:30,535 --> 00:35:31,914 you wanna know, we'll include 999 00:35:32,454 --> 00:35:35,894 questions, comments in our MCP episode when we 1000 00:35:35,894 --> 00:35:38,055 record that one. But until next time 1001 00:35:38,775 --> 00:35:40,375 Sounds good. I'm gonna go keep playing with 1002 00:35:40,375 --> 00:35:41,909 MCP, so I got a whole bunch more 1003 00:35:41,909 --> 00:35:42,730 to talk about. 1004 00:35:43,989 --> 00:35:46,070 Perfect. Alright. Thanks, Scott. We'll talk to you 1005 00:35:46,070 --> 00:35:46,809 next time. 1006 00:35:48,710 --> 00:35:50,949 If you enjoyed the podcast, go leave us 1007 00:35:50,949 --> 00:35:53,190 a five star rating in iTunes. It helps 1008 00:35:53,190 --> 00:35:54,869 to get the word out so more IT 1009 00:35:54,869 --> 00:35:56,925 pros can learn about Office three sixty sixty 1010 00:35:56,925 --> 00:35:57,664 five and Azure. 1011 00:35:58,285 --> 00:35:59,965 If you have any questions you want us 1012 00:35:59,965 --> 00:36:02,045 to address on the show, or feedback about 1013 00:36:02,045 --> 00:36:04,445 the show, feel free to reach out via 1014 00:36:04,445 --> 00:36:06,625 our website, Twitter, or Facebook. 1015 00:36:06,925 --> 00:36:08,765 Thanks again for listening, and have a great 1016 00:36:08,765 --> 00:36:09,265 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