Episode 389: Microsoft Ignite 2024: Redefining AI, Productivity, and Edge Computing

November 21, 2024

Episode Transcript

Welcome to Episode 389 of the Microsoft Cloud IT Pro Podcast. In this special episode, we recap the game-changing announcements from Microsoft Ignite, Microsoft’s premier conference unveiling innovations across Microsoft 365 and Azure.We explore advancements in Agentic AI and multi-modal models that seamlessly accept and produce text, voice, and graphics. Discover how Copilot is evolving with features like reasoning over on-screen content (coming to Teams in CY25) and enhanced capabilities in tools like Word, PowerPoint, and Excel—bringing automated summaries, dynamic graphics, and effortless data analysis to the forefront.

Learn how Copilot Pages enable collaborative editing, while Copilot Extensibility and Agents allow businesses to create customized AI-powered helpers with ease. Imagine every SharePoint site having a built-in agent by default, making tasks more intuitive than ever.

We also cover new updates in edge AI—a “distributed computing fabric” blending Azure Local bare-metal solutions and Windows 365 Link thin clients. Innovations in AI-ready silicon underpin these transformative changes.

Like what you hear and want to support the show? 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:04,740 Welcome to episode 2 00:00:05,200 --> 00:00:05,700 389 3 00:00:06,000 --> 00:00:09,220 of the Microsoft Cloud IT Pro Podcast recorded 4 00:00:09,279 --> 00:00:11,539 live on November 19, 2024. 5 00:00:12,400 --> 00:00:14,880 This is a show about Microsoft 365 and 6 00:00:14,880 --> 00:00:17,244 Azure from the perspective of IT pros and 7 00:00:17,244 --> 00:00:19,484 end users, where we discuss the topic or 8 00:00:19,484 --> 00:00:21,744 recent news and how it relates to you. 9 00:00:21,804 --> 00:00:24,364 It's time to finally bring an episode recorded 10 00:00:24,364 --> 00:00:27,484 live from Microsoft Ignite, the first in person 11 00:00:27,484 --> 00:00:30,519 Microsoft Ignite Scott and Ben have attended since 12 00:00:30,519 --> 00:00:31,019 2019. 13 00:00:32,039 --> 00:00:32,939 In this episode, 14 00:00:33,320 --> 00:00:35,399 we have the goal of presenting our insights 15 00:00:35,399 --> 00:00:37,960 on the Microsoft Ignite keynote, but ended up 16 00:00:37,960 --> 00:00:39,975 focused just on the copilot announcements 17 00:00:40,454 --> 00:00:40,954 keynote. 18 00:00:41,335 --> 00:00:44,134 And we'll have more Ignite episodes coming out 19 00:00:44,134 --> 00:00:46,854 soon with more great announcements and our thoughts 20 00:00:46,854 --> 00:00:49,494 about them from the Microsoft Ignite keynote. We'll 21 00:00:49,494 --> 00:00:51,655 maybe even drop in a bonus episode or 22 00:00:51,655 --> 00:00:54,695 2 over the next few weeks. So, enjoy 23 00:00:54,695 --> 00:00:55,229 the show. 24 00:00:57,630 --> 00:00:59,489 So here we are Scott, sitting 25 00:01:00,030 --> 00:01:00,850 in the hotel, 26 00:01:01,309 --> 00:01:02,129 in Chicago. 27 00:01:02,590 --> 00:01:03,950 Is it So is this day 1 of 28 00:01:03,950 --> 00:01:06,030 Ignite or day 2 of Ignite? Technically, it's 29 00:01:06,030 --> 00:01:07,790 the pre day day 1 and this is 30 00:01:07,790 --> 00:01:09,465 day 2? This is the pre day late. 31 00:01:09,644 --> 00:01:11,424 Day 1 of Ignite. We have we have 32 00:01:11,484 --> 00:01:14,045 we have the keynote. We we sat. We 33 00:01:14,045 --> 00:01:15,265 saw. We survived. 34 00:01:15,885 --> 00:01:18,045 I think we should talk through the keynote 35 00:01:18,045 --> 00:01:19,665 a little bit and some of the announcements. 36 00:01:19,724 --> 00:01:22,560 We should. It was a long keynote. It 37 00:01:22,560 --> 00:01:24,600 was an interesting keynote this year. 2 and 38 00:01:24,600 --> 00:01:26,819 a half hours. I don't know your thoughts. 39 00:01:26,959 --> 00:01:28,319 I would say if somebody wants to go 40 00:01:28,319 --> 00:01:29,520 back and watch it, so we can post 41 00:01:29,520 --> 00:01:31,120 the link. I'm pretty sure the keynote will 42 00:01:31,120 --> 00:01:32,020 be publicly 43 00:01:32,480 --> 00:01:32,980 available 44 00:01:33,584 --> 00:01:34,245 somewhere either 45 00:01:35,105 --> 00:01:36,145 I don't know if it'll make it on 46 00:01:36,145 --> 00:01:37,844 YouTube or if it'll just be 47 00:01:38,224 --> 00:01:39,605 on the Microsoft website. 48 00:01:40,224 --> 00:01:41,424 It will be. We will find it. Yeah. 49 00:01:41,424 --> 00:01:42,465 We will find it, but I would say 50 00:01:42,465 --> 00:01:43,984 you can watch, like, the first hour and 51 00:01:43,984 --> 00:01:46,640 15 minutes. Like, Satya Nadella got up an 52 00:01:46,640 --> 00:01:48,319 hour and 15 minutes, went through a bunch 53 00:01:48,319 --> 00:01:49,920 of the stuff we'll talk about post links 54 00:01:49,920 --> 00:01:51,680 to. I would say the second hour and 55 00:01:51,680 --> 00:01:52,579 15 minutes, 56 00:01:53,040 --> 00:01:55,859 maybe not something you need to watch 57 00:01:56,319 --> 00:01:57,060 as closely. 58 00:01:57,920 --> 00:01:59,280 It ended up with some repeat in it. 59 00:01:59,280 --> 00:02:00,825 It was a little bit of I would 60 00:02:00,825 --> 00:02:02,505 say it was an odd keynote this year 61 00:02:02,505 --> 00:02:04,344 with the way the first half and the 62 00:02:04,344 --> 00:02:06,265 second half went. I think you're right. Like, 63 00:02:06,265 --> 00:02:07,625 if you're gonna go back and watch it 64 00:02:07,625 --> 00:02:09,865 and you haven't watched it, watch the Satcha 65 00:02:09,865 --> 00:02:10,365 section 66 00:02:11,064 --> 00:02:12,844 about an hour, hour 15. 67 00:02:13,370 --> 00:02:15,289 You will get all the highlights that you 68 00:02:15,289 --> 00:02:17,609 need. And if you want deep dives, there's 69 00:02:17,609 --> 00:02:19,769 deep dives on all of that. The remainder 70 00:02:19,769 --> 00:02:22,030 of the keynote is kind of the 71 00:02:22,969 --> 00:02:26,409 the repeat section where it's potentially deeper dives 72 00:02:26,409 --> 00:02:28,675 on some of the announcements around, like, Copilot 73 00:02:28,814 --> 00:02:31,314 and 3 65, same thing with Azure. 74 00:02:32,254 --> 00:02:34,175 But, you know, you probably want deeper dives 75 00:02:34,175 --> 00:02:36,895 on those anyway, so easier to go find 76 00:02:36,895 --> 00:02:37,395 them 77 00:02:37,775 --> 00:02:40,275 elsewhere. Yeah. Copilot. You mean there was Copilot 78 00:02:40,335 --> 00:02:42,139 in the keynote? Yeah. I mean That caught 79 00:02:42,139 --> 00:02:43,439 me totally off guard. 80 00:02:44,379 --> 00:02:47,180 I'm gonna steal a Scott Hanselman here. The 81 00:02:47,180 --> 00:02:49,120 the Copilots will keep on coming 82 00:02:49,420 --> 00:02:50,719 until morale improves. 83 00:02:51,340 --> 00:02:51,840 It's 84 00:02:52,219 --> 00:02:52,719 it's 85 00:02:53,099 --> 00:02:55,360 kind of where we're at with Copilot. 86 00:02:55,819 --> 00:02:56,319 So 87 00:02:56,620 --> 00:02:57,074 it's 88 00:02:58,114 --> 00:03:00,435 it's a marketing term, but I do think 89 00:03:00,435 --> 00:03:01,574 that some of the capabilities 90 00:03:01,875 --> 00:03:02,375 there 91 00:03:02,675 --> 00:03:05,715 are super interesting. So we were kinda going 92 00:03:05,715 --> 00:03:08,514 around after the keynote and asking people on 93 00:03:08,514 --> 00:03:10,129 their thoughts and and 94 00:03:10,510 --> 00:03:12,750 and just kinda how things compose in their 95 00:03:12,750 --> 00:03:13,250 head. 96 00:03:13,629 --> 00:03:16,189 And, yeah, there's a lot of fatigue about 97 00:03:16,189 --> 00:03:17,490 Copilot and AI, 98 00:03:17,790 --> 00:03:20,210 but there's excitement about certain 99 00:03:20,669 --> 00:03:22,669 workloads. And I think what are starting to 100 00:03:22,669 --> 00:03:23,810 be some of the 101 00:03:24,224 --> 00:03:25,525 canonical use cases 102 00:03:26,224 --> 00:03:26,724 for 103 00:03:27,344 --> 00:03:29,125 both large language models 104 00:03:29,985 --> 00:03:31,425 and being able to do some of the 105 00:03:31,425 --> 00:03:32,324 things that 106 00:03:33,104 --> 00:03:35,104 they're good at, like a transformer is good 107 00:03:35,104 --> 00:03:35,764 at summarization. 108 00:03:36,145 --> 00:03:39,169 So let's take Teams premium licensing and the 109 00:03:39,169 --> 00:03:39,669 ability 110 00:03:40,050 --> 00:03:41,510 to record a transcript 111 00:03:42,050 --> 00:03:44,770 in your Teams calls and then have AI 112 00:03:44,770 --> 00:03:47,090 driven summaries out of that. I think we've 113 00:03:47,090 --> 00:03:49,090 talked about in the past, I'm completely addicted 114 00:03:49,090 --> 00:03:51,495 to those AI summaries. Oh, 100%. I just 115 00:03:51,574 --> 00:03:54,134 turn those on for every single meeting that 116 00:03:54,134 --> 00:03:56,775 I'm in. And you know what? They they 117 00:03:56,775 --> 00:03:59,894 work really good, and they're great. And today, 118 00:03:59,894 --> 00:04:01,275 they announced that 119 00:04:02,134 --> 00:04:03,014 they're gonna have some, 120 00:04:03,989 --> 00:04:06,650 computer vision and reasoning capabilities 121 00:04:07,030 --> 00:04:08,889 on top of the transcription, 122 00:04:09,669 --> 00:04:11,669 capabilities that are already there and and kind 123 00:04:11,669 --> 00:04:13,829 of summarization. So one of the things that's 124 00:04:13,829 --> 00:04:16,389 gonna come out of that in calendar year 125 00:04:16,389 --> 00:04:16,889 2025 126 00:04:17,589 --> 00:04:19,129 for Microsoft Teams 127 00:04:19,544 --> 00:04:22,524 is the ability for that AI engine 128 00:04:22,985 --> 00:04:25,305 to follow along with what's being shared on 129 00:04:25,305 --> 00:04:28,365 the screen. So say you're sharing a presentation, 130 00:04:29,225 --> 00:04:30,524 and that presentation 131 00:04:30,904 --> 00:04:33,089 has I don't know. You're you're running down 132 00:04:33,089 --> 00:04:34,689 the sales figures for the year and it 133 00:04:34,689 --> 00:04:35,829 has the final charts 134 00:04:36,209 --> 00:04:38,449 for the sales figures and things like that. 135 00:04:38,449 --> 00:04:40,389 You'll actually be able to go into Copilot, 136 00:04:40,610 --> 00:04:42,629 and you'll be able to ask it questions 137 00:04:43,169 --> 00:04:44,229 about that slide 138 00:04:44,529 --> 00:04:45,669 through Teams 139 00:04:46,125 --> 00:04:49,085 because Teams is basically taking screenshots the entire 140 00:04:49,085 --> 00:04:51,904 time, very similar to what's been announced with 141 00:04:51,964 --> 00:04:54,145 some other Windows capabilities like recall, 142 00:04:54,605 --> 00:04:57,004 and it's going to pump those right back 143 00:04:57,004 --> 00:04:59,324 for you. So, you know, it's gonna happen 144 00:04:59,324 --> 00:05:00,064 in the background 145 00:05:00,589 --> 00:05:01,729 all automatically, 146 00:05:02,189 --> 00:05:04,529 and that's just a further augmentation 147 00:05:05,229 --> 00:05:06,289 of that summarization 148 00:05:06,589 --> 00:05:08,370 capability that's there in Teams. 149 00:05:08,829 --> 00:05:11,389 Makes perfect sense logically. Right? It it slots 150 00:05:11,389 --> 00:05:13,814 right in, and I think that's a great 151 00:05:13,814 --> 00:05:15,814 use case. Like, not many people are gonna 152 00:05:15,814 --> 00:05:17,414 be creeped out by it because they've already 153 00:05:17,414 --> 00:05:20,055 been recorded by the transcription engine for the 154 00:05:20,055 --> 00:05:23,095 past, what, year? Right. Plus, like yep. However 155 00:05:23,095 --> 00:05:25,014 long that's been, and now you get this, 156 00:05:25,014 --> 00:05:28,129 like, nifty new capability. Hopefully, that nifty new 157 00:05:28,129 --> 00:05:30,769 capability is built into the existing licenses, and 158 00:05:30,769 --> 00:05:32,370 there's not a new SKU or something like 159 00:05:32,370 --> 00:05:34,370 that. But, you know, time will time will 160 00:05:34,370 --> 00:05:36,050 tell on that one. So I so I 161 00:05:36,050 --> 00:05:38,844 think there's things like that, And, you know, 162 00:05:38,844 --> 00:05:40,604 Teams tends to be, like, my go to 163 00:05:40,604 --> 00:05:42,844 use case of this is just amazing, and 164 00:05:42,844 --> 00:05:45,245 it just works. And it's one of those, 165 00:05:45,644 --> 00:05:46,625 delightful things. 166 00:05:47,084 --> 00:05:49,724 There was a whole bunch around Copilot in 167 00:05:49,724 --> 00:05:52,925 general, especially in the embedded experiences across office 168 00:05:52,925 --> 00:05:53,425 clients. 169 00:05:53,939 --> 00:05:57,459 So that's things like Copilot Pages, the ability 170 00:05:57,459 --> 00:05:58,759 to do collaborative 171 00:05:59,379 --> 00:05:59,879 editing 172 00:06:00,339 --> 00:06:01,639 on Copilot responses. 173 00:06:02,019 --> 00:06:04,180 I still don't know where Copilot Pages sit 174 00:06:04,180 --> 00:06:06,439 with me in comparison to things like, say, 175 00:06:06,794 --> 00:06:09,035 a loop that we both share, and maybe 176 00:06:09,035 --> 00:06:11,035 we both have Copilot components going in a 177 00:06:11,035 --> 00:06:12,794 loop component at the same time or a 178 00:06:12,794 --> 00:06:14,475 loop page at the same time. So we'll 179 00:06:14,475 --> 00:06:16,574 see where some of that stuff pans out. 180 00:06:17,035 --> 00:06:19,774 You know, Word is getting some new capabilities, 181 00:06:20,350 --> 00:06:22,850 so you'll be able to generate Word documents 182 00:06:23,389 --> 00:06:26,910 based on other documents and other artifacts. Like, 183 00:06:26,910 --> 00:06:29,790 just from scratch, generate me a new document. 184 00:06:29,790 --> 00:06:32,830 That sounds kinda cool. You've got automated summaries 185 00:06:32,830 --> 00:06:34,830 in Word. I don't know how valuable those 186 00:06:34,830 --> 00:06:36,914 are. I don't know that I've ever opened 187 00:06:36,914 --> 00:06:38,754 one up in in a Word document that 188 00:06:38,754 --> 00:06:40,194 I've seen, but, you know, some people might 189 00:06:40,194 --> 00:06:43,574 like those. There's some niceties around PowerPoint with 190 00:06:44,194 --> 00:06:46,214 Gen AI, particularly for graphics, 191 00:06:46,834 --> 00:06:49,235 certainly being able to, like, generate slide contents, 192 00:06:49,235 --> 00:06:50,214 things like that. 193 00:06:50,699 --> 00:06:53,740 Excel is an interesting one. So Copilot for 194 00:06:53,740 --> 00:06:55,419 Excel has been there for a hot minute 195 00:06:55,419 --> 00:06:57,899 already. You've been able to do things like 196 00:06:57,899 --> 00:07:01,339 ask it to generate formulas for you and 197 00:07:01,339 --> 00:07:03,495 and kind of walk down those paths. It's 198 00:07:03,495 --> 00:07:05,574 getting a little bit smarter in that it 199 00:07:05,574 --> 00:07:06,235 can actually 200 00:07:06,615 --> 00:07:07,115 do, 201 00:07:07,895 --> 00:07:10,455 some more base analysis for you. It wasn't 202 00:07:10,455 --> 00:07:12,615 clear to me whether it's, like, Excel is 203 00:07:12,615 --> 00:07:13,975 the tool to do that in, or do 204 00:07:13,975 --> 00:07:15,655 I take my Excel and maybe import it 205 00:07:15,655 --> 00:07:17,495 into Power BI and then use Copilot in 206 00:07:17,495 --> 00:07:19,539 Power BI? Because maybe I just wanna visualize 207 00:07:19,539 --> 00:07:21,220 the whole thing. So I think, like, folks 208 00:07:21,220 --> 00:07:22,740 are gonna have to rationalize which way that 209 00:07:22,740 --> 00:07:24,680 goes, but that stuff was all there. 210 00:07:25,220 --> 00:07:28,259 There was an interesting quote from Satcha around 211 00:07:28,259 --> 00:07:31,459 Excel. He kinda leaned into spreadsheets make the 212 00:07:31,459 --> 00:07:34,915 world go round and especially Excel spreadsheets. It's 213 00:07:34,975 --> 00:07:37,774 amazing. Yeah. Continues to be a thing. But 214 00:07:37,774 --> 00:07:39,214 he had this quote. He said, it makes 215 00:07:39,214 --> 00:07:42,115 data analysis available to everyone with a spreadsheet, 216 00:07:42,335 --> 00:07:44,095 and I think that's super powerful. Like, if 217 00:07:44,095 --> 00:07:46,754 you've ever opened a spreadsheet and tried to, 218 00:07:47,139 --> 00:07:49,300 say, create a pivot chart, and that pivot 219 00:07:49,300 --> 00:07:51,379 chart just, like, doesn't have the right dimensions, 220 00:07:51,379 --> 00:07:54,020 it doesn't have the right series, or you've 221 00:07:54,020 --> 00:07:56,500 gotta flip something around. Maybe you're creating, like, 222 00:07:56,500 --> 00:07:57,939 a time chart, and you need to flip 223 00:07:57,939 --> 00:08:00,100 an axis or a line chart, things like 224 00:08:00,100 --> 00:08:01,960 that. You're creating, like, a stack column chart. 225 00:08:02,125 --> 00:08:03,745 Working with charts in Excel is 226 00:08:04,125 --> 00:08:06,125 surprisingly hard, like, if you're not an if 227 00:08:06,125 --> 00:08:08,204 you're not a chart expert. So things like 228 00:08:08,204 --> 00:08:10,704 that should help. It's really democratization 229 00:08:11,004 --> 00:08:12,544 of data because, 230 00:08:12,845 --> 00:08:14,444 you know, data is good, but I think 231 00:08:14,444 --> 00:08:16,524 we're seeing more and more, like, visualization and 232 00:08:16,524 --> 00:08:19,500 visualization engines kinda tack onto that. So if 233 00:08:19,500 --> 00:08:22,060 you can drive that into Excel without a 234 00:08:22,060 --> 00:08:23,199 Power BI license 235 00:08:23,580 --> 00:08:25,500 or the need for Power BI or anything 236 00:08:25,500 --> 00:08:27,500 like that, which is frankly yet another tool 237 00:08:27,500 --> 00:08:28,939 you need to go learn, like, if you 238 00:08:28,939 --> 00:08:30,540 never need to learn DAX and all you 239 00:08:30,540 --> 00:08:32,240 need to learn is Excel formulas, 240 00:08:33,414 --> 00:08:35,815 and Copilot can help you with things like 241 00:08:35,815 --> 00:08:38,554 data analysis using using Python 242 00:08:39,174 --> 00:08:42,294 and Pandas libraries, like, why not? Right? Like, 243 00:08:42,294 --> 00:08:43,834 you're not gonna need to be, 244 00:08:44,375 --> 00:08:46,300 an expert along the way. So I I 245 00:08:46,300 --> 00:08:48,620 think things like that kind of accrue to 246 00:08:48,620 --> 00:08:51,200 the greater good. They're not necessarily, like, whizbang 247 00:08:51,340 --> 00:08:52,320 features, but, 248 00:08:52,940 --> 00:08:54,000 they are there. 249 00:08:54,460 --> 00:08:56,720 Some of the more interesting stuff with Copilot, 250 00:08:57,180 --> 00:08:58,379 I don't know how you feel about this 251 00:08:58,379 --> 00:09:00,460 one. There there was a a quote about 252 00:09:00,460 --> 00:09:01,600 Copilot actions. 253 00:09:01,924 --> 00:09:04,664 And the way Satya described Copilot actions 254 00:09:05,125 --> 00:09:07,365 is this is Outlook rules for the age 255 00:09:07,365 --> 00:09:07,944 of AI. 256 00:09:08,245 --> 00:09:11,064 So that's basically saying we're taking the ability 257 00:09:11,204 --> 00:09:11,704 to, 258 00:09:12,644 --> 00:09:15,605 you know, have automated engines like we do 259 00:09:15,605 --> 00:09:18,059 with our Outlook rules, but then pull those 260 00:09:18,059 --> 00:09:19,279 things into 261 00:09:19,659 --> 00:09:22,480 other parts of the Office suite, like Excel 262 00:09:22,860 --> 00:09:23,519 and Word 263 00:09:24,059 --> 00:09:26,059 and things like that. So, like, for a 264 00:09:26,059 --> 00:09:26,959 practical example, 265 00:09:27,500 --> 00:09:29,500 I send out a business report once a 266 00:09:29,500 --> 00:09:30,959 week. It takes me 267 00:09:31,315 --> 00:09:32,995 at least an hour to put that business 268 00:09:32,995 --> 00:09:35,075 report together. I need to go to multiple 269 00:09:35,075 --> 00:09:37,634 sources, log in to multiple websites. Sometimes it's, 270 00:09:37,634 --> 00:09:40,115 like, taking a screenshot of a thing. Sometimes 271 00:09:40,115 --> 00:09:43,154 it's running a SQL query and just or 272 00:09:43,154 --> 00:09:45,370 it's going into, like, an Excel spreadsheet and 273 00:09:45,370 --> 00:09:47,210 clicking the refresh button. If I can have 274 00:09:47,210 --> 00:09:49,129 an AI do all that stuff for me, 275 00:09:49,129 --> 00:09:51,210 that just buys me back an hour, if 276 00:09:51,210 --> 00:09:52,970 it works. And even if it gets me 277 00:09:52,970 --> 00:09:54,810 50% of the way there, it just bought 278 00:09:54,810 --> 00:09:56,715 me back at least 30 minutes a day. 279 00:09:56,875 --> 00:09:59,115 Like, that is a powerful thing, and it's 280 00:09:59,115 --> 00:10:02,254 a powerful accelerator. So I'm looking forward to 281 00:10:02,634 --> 00:10:05,195 Copilot actions, TBD. Like, I think I gotta 282 00:10:05,195 --> 00:10:07,055 go sit in some sessions and see 283 00:10:07,434 --> 00:10:09,990 how that actually works. Like, is it computer 284 00:10:09,990 --> 00:10:11,350 vision? Is it gonna be able to click 285 00:10:11,350 --> 00:10:13,509 the buttons on the screen for you? Is 286 00:10:13,509 --> 00:10:15,370 it more you're dependent on 287 00:10:16,230 --> 00:10:19,110 an extension inside of Word or Excel? Like, 288 00:10:19,110 --> 00:10:20,549 I don't know how all that stuff's gonna 289 00:10:20,549 --> 00:10:23,029 come together and how it's gonna work. Continuing 290 00:10:23,029 --> 00:10:24,835 down the Copilot path, Copilot 291 00:10:25,615 --> 00:10:28,754 agents. So Copilot agents are out there today. 292 00:10:29,375 --> 00:10:33,715 They're available in both the Office chat experience. 293 00:10:33,774 --> 00:10:35,934 So if you go to, like, Copilot for 294 00:10:35,934 --> 00:10:36,995 work, so office.com/chat, 295 00:10:38,440 --> 00:10:41,000 You have an agent experience there, and you 296 00:10:41,000 --> 00:10:43,399 also have an agent experience that's going to 297 00:10:43,399 --> 00:10:44,940 come to every SharePoint 298 00:10:45,320 --> 00:10:47,180 every SharePoint site automatically. 299 00:10:47,960 --> 00:10:50,860 Super interesting. So you you have this capability 300 00:10:50,920 --> 00:10:52,139 with Copilot agents 301 00:10:52,654 --> 00:10:55,215 to basically do a low code. And I 302 00:10:55,215 --> 00:10:56,735 mean, when I say low code, it's basically 303 00:10:56,735 --> 00:10:58,735 no code, but it's a next, next, next 304 00:10:58,735 --> 00:10:59,235 experience 305 00:10:59,695 --> 00:11:01,774 where you can fire up a custom agent. 306 00:11:01,774 --> 00:11:03,615 You can point it at data that lives 307 00:11:03,615 --> 00:11:04,995 in a SharePoint site, 308 00:11:05,470 --> 00:11:05,970 and 309 00:11:06,429 --> 00:11:08,769 you that could be like a document library. 310 00:11:08,910 --> 00:11:11,230 It could be the entire SharePoint site itself, 311 00:11:11,230 --> 00:11:13,549 which is the way, like, SharePoint Copilot agents, 312 00:11:13,870 --> 00:11:15,490 seem like they're gonna be working. 313 00:11:15,950 --> 00:11:18,590 And you just spin that thing up, and 314 00:11:18,590 --> 00:11:19,970 you have this little 315 00:11:20,445 --> 00:11:21,985 custom agent that's 316 00:11:22,365 --> 00:11:22,865 using 317 00:11:23,325 --> 00:11:23,825 rag 318 00:11:24,205 --> 00:11:27,565 with your documents as grounding. So it's doing 319 00:11:27,565 --> 00:11:29,024 retrieval augmented generation. 320 00:11:29,404 --> 00:11:30,924 So what that means is, like, the base 321 00:11:30,924 --> 00:11:32,845 model is there and say you have an 322 00:11:32,845 --> 00:11:35,184 e a Copilot agent that's pointed at, like, 323 00:11:35,299 --> 00:11:37,620 2 SharePoint sites. You have, like, all your 324 00:11:37,620 --> 00:11:39,860 sales figures go in this SharePoint site over 325 00:11:39,860 --> 00:11:42,419 here, and then maybe you have some other 326 00:11:42,419 --> 00:11:44,179 SharePoint site for, like, your road map and 327 00:11:44,179 --> 00:11:47,059 upcoming features. You could potentially ask that thing 328 00:11:47,059 --> 00:11:49,434 now, like, tie a custom agent together that 329 00:11:49,434 --> 00:11:52,074 blends the data from those two sites. And 330 00:11:52,074 --> 00:11:53,514 you might be able to do things like 331 00:11:53,514 --> 00:11:56,314 reason over it and say, show me, you 332 00:11:56,314 --> 00:11:59,034 know, which figure which things on my road 333 00:11:59,034 --> 00:12:00,814 map or which features were released 334 00:12:01,434 --> 00:12:03,294 most greatly accelerated sales. 335 00:12:03,600 --> 00:12:05,120 And, you know, maybe that's something you already 336 00:12:05,120 --> 00:12:06,279 track in your company, but I know there's 337 00:12:06,279 --> 00:12:07,679 a lot of companies that don't track things 338 00:12:07,679 --> 00:12:09,519 like that because it's hard to just blend 339 00:12:09,519 --> 00:12:11,379 that data and put it together. So 340 00:12:11,759 --> 00:12:13,139 that engine can 341 00:12:13,600 --> 00:12:16,259 sit in the middle and do those things 342 00:12:16,704 --> 00:12:19,264 for you. Why why not? Like, that's that's 343 00:12:19,264 --> 00:12:20,164 exciting stuff. 344 00:12:20,625 --> 00:12:23,024 And to be brutally honest, like, I'm not 345 00:12:23,024 --> 00:12:25,745 a developer anymore, and I went around and 346 00:12:25,745 --> 00:12:27,605 and played around with the SharePoint agent. 347 00:12:28,065 --> 00:12:28,565 And 348 00:12:28,959 --> 00:12:30,639 it it can do everything from, like, tell 349 00:12:30,639 --> 00:12:32,000 you how to set the permissions on your 350 00:12:32,000 --> 00:12:35,200 SharePoint site to go look at these 3 351 00:12:35,200 --> 00:12:35,700 documents 352 00:12:36,080 --> 00:12:37,759 without having to be in, like, Copilot chat. 353 00:12:37,759 --> 00:12:39,440 You can just say, like, go to this 354 00:12:39,440 --> 00:12:41,759 document library and tell me about this thing, 355 00:12:41,759 --> 00:12:44,019 and it'll spit that data back to you. 356 00:12:44,214 --> 00:12:46,615 Same thing with this the generic Copilot agents. 357 00:12:46,615 --> 00:12:48,875 They're super easy to use. 358 00:12:49,414 --> 00:12:51,254 You ground them, like I said, in in 359 00:12:51,254 --> 00:12:54,214 data that resides in SharePoint today. Hopefully, they 360 00:12:54,214 --> 00:12:55,815 open that up and let you just ground 361 00:12:55,815 --> 00:12:56,714 it in SharePoint 362 00:12:57,039 --> 00:13:00,160 plus maybe public website or other things. Like, 363 00:13:00,160 --> 00:13:02,480 there's potential, like, who knows, copyright issues and 364 00:13:02,480 --> 00:13:03,539 other things there. 365 00:13:04,000 --> 00:13:06,259 But, you know, even just being in SharePoint, 366 00:13:06,480 --> 00:13:08,639 powerful stuff. So you can create, like, a 367 00:13:08,639 --> 00:13:09,539 custom agent. 368 00:13:10,080 --> 00:13:12,019 I created one the other day for 369 00:13:12,605 --> 00:13:15,245 for some supportability stuff. So I took one 370 00:13:15,245 --> 00:13:17,004 of our products that we have and I 371 00:13:17,004 --> 00:13:19,805 pulled the wikis together, all the support wikis 372 00:13:19,805 --> 00:13:21,725 for it that we have, and I created 373 00:13:21,725 --> 00:13:24,125 a custom agent that I called, you know, 374 00:13:24,125 --> 00:13:26,605 like, my product help desk. And now I 375 00:13:26,605 --> 00:13:28,225 can go and ask that thing questions. 376 00:13:28,759 --> 00:13:31,000 So I can say, like, I have a 377 00:13:31,000 --> 00:13:33,320 user who had this issue, and it just 378 00:13:33,320 --> 00:13:34,919 crawls through the Wiki for me, and it 379 00:13:34,919 --> 00:13:36,279 finds that. So I don't need to know 380 00:13:36,279 --> 00:13:38,840 the specific article. It gives me the steps 381 00:13:38,840 --> 00:13:40,299 to resolve it right there. 382 00:13:40,754 --> 00:13:43,475 You can ground those agents even further, so 383 00:13:43,475 --> 00:13:45,634 you can do things like have seeder prompts 384 00:13:45,634 --> 00:13:47,715 in them. So kinda like you have just 385 00:13:47,715 --> 00:13:50,115 the entire prompt engine inside of office or 386 00:13:50,115 --> 00:13:52,054 in inside of Copilot chat today. 387 00:13:52,514 --> 00:13:53,875 You know, you can seed it with your 388 00:13:53,875 --> 00:13:55,870 own custom prompts and all those things. And 389 00:13:55,870 --> 00:13:58,110 then you can take those agents, and you 390 00:13:58,110 --> 00:14:00,429 can share them with other people. So, like, 391 00:14:00,429 --> 00:14:02,269 my custom product agent, I was able to 392 00:14:02,269 --> 00:14:03,629 take that and share that with all the 393 00:14:03,629 --> 00:14:05,870 PMs on my team and say, hey. Here's 394 00:14:05,870 --> 00:14:07,754 a new tool that we have. Right? And 395 00:14:07,835 --> 00:14:08,495 for me, 396 00:14:08,875 --> 00:14:12,154 the work wasn't in developing the Copilot agent. 397 00:14:12,154 --> 00:14:14,154 It wasn't in clicking next, next, next. It 398 00:14:14,154 --> 00:14:15,674 was more in, like, figuring out which data 399 00:14:15,674 --> 00:14:17,934 I wanted to pull into that thing. So 400 00:14:18,634 --> 00:14:22,090 that's all kinda, like, super powerful stuff. Right? 401 00:14:22,090 --> 00:14:24,250 Like, I I don't know that maybe the 402 00:14:24,250 --> 00:14:26,970 the Copilot stuff lands inside of the individual 403 00:14:26,970 --> 00:14:28,649 Office clients, maybe other than that stuff in 404 00:14:28,649 --> 00:14:30,590 Excel, which I I think is really good. 405 00:14:30,970 --> 00:14:32,909 But, definitely, some of the extensibility 406 00:14:33,289 --> 00:14:36,110 pieces, like Copilot actions and Copilot agents, 407 00:14:36,514 --> 00:14:39,154 like, no brainers. Like, I think once people 408 00:14:39,154 --> 00:14:41,075 use them, as long as you're licensed for 409 00:14:41,075 --> 00:14:41,575 it, 410 00:14:41,955 --> 00:14:44,294 you're you're you're gonna be good and 411 00:14:44,754 --> 00:14:45,735 ready to go 412 00:14:46,035 --> 00:14:47,174 in in that lens. 413 00:14:51,019 --> 00:14:53,100 Do you feel overwhelmed by trying to manage 414 00:14:53,100 --> 00:14:54,080 your Office 365 415 00:14:54,460 --> 00:14:57,500 environment? Are you facing unexpected issues that disrupt 416 00:14:57,500 --> 00:15:00,220 your company's productivity? Intelligink is here to help. 417 00:15:00,220 --> 00:15:01,740 Much like you take your car to the 418 00:15:01,740 --> 00:15:04,220 mechanic that has specialized knowledge on how to 419 00:15:04,220 --> 00:15:06,935 best keep your car running, Intelligent helps you 420 00:15:06,935 --> 00:15:09,735 with your Microsoft cloud environment because that's their 421 00:15:09,735 --> 00:15:10,235 expertise. 422 00:15:10,615 --> 00:15:12,855 Intelligent keeps up with the latest updates in 423 00:15:12,855 --> 00:15:15,095 the Microsoft cloud to help keep your business 424 00:15:15,095 --> 00:15:17,254 running smoothly and ahead of the curve. Whether 425 00:15:17,254 --> 00:15:19,335 you are a small organization with just a 426 00:15:19,335 --> 00:15:21,690 few users, up to an organization of several 427 00:15:21,690 --> 00:15:24,490 thousand employees, they want to partner with you 428 00:15:24,490 --> 00:15:27,870 to implement and administer your Microsoft Cloud technology. 429 00:15:28,649 --> 00:15:30,110 Visit them at inteligink.com/podcast. 430 00:15:32,330 --> 00:15:33,470 That's intel 431 00:15:35,945 --> 00:15:36,445 ligink.com/podcast 432 00:15:39,545 --> 00:15:41,625 for more information or to schedule a 30 433 00:15:41,625 --> 00:15:43,725 minute call to get started with them today. 434 00:15:43,945 --> 00:15:47,305 Remember, Intelligink focuses on the Microsoft cloud, so 435 00:15:47,305 --> 00:15:48,840 you can focus on your business. 436 00:15:51,240 --> 00:15:52,759 We kinda make fun of Copilot and that 437 00:15:52,759 --> 00:15:55,740 it's all Copilot, but it does feel like 438 00:15:55,879 --> 00:15:58,379 Copilot this year was not so much, 439 00:15:58,840 --> 00:16:01,820 here's Copilot and coming out with a 440 00:16:02,605 --> 00:16:05,825 Microsoft competitor to the other AI engines out 441 00:16:06,045 --> 00:16:07,024 there. But more, 442 00:16:07,804 --> 00:16:10,445 here's all the different things we're doing in 443 00:16:10,445 --> 00:16:10,945 Copilot 444 00:16:11,404 --> 00:16:13,485 to to avoid whether it's extending it to 445 00:16:13,485 --> 00:16:15,665 data or just extending it to different 446 00:16:16,125 --> 00:16:16,945 use cases. 447 00:16:17,325 --> 00:16:20,329 It's more than just here's Copilot. It's here's 448 00:16:20,329 --> 00:16:23,389 how you can actually use Copilot to 449 00:16:23,929 --> 00:16:25,149 improve your 450 00:16:25,529 --> 00:16:26,029 work. 451 00:16:26,569 --> 00:16:27,309 And improve 452 00:16:27,769 --> 00:16:30,350 what you're doing. Like you said, Copilot actions. 453 00:16:30,730 --> 00:16:32,809 There was some stuff around Copilot for Outlook 454 00:16:32,809 --> 00:16:35,264 that's interesting. There's a button already that lets 455 00:16:35,264 --> 00:16:37,024 you, like, respond to an email and schedule 456 00:16:37,024 --> 00:16:37,605 a meeting. 457 00:16:37,985 --> 00:16:40,144 But they also talked about more around using 458 00:16:40,144 --> 00:16:41,824 Copilot to be able to schedule 1 on 459 00:16:41,824 --> 00:16:43,044 ones or 460 00:16:43,745 --> 00:16:44,245 to 461 00:16:45,105 --> 00:16:47,529 create agendas. And it would be interesting to, 462 00:16:47,529 --> 00:16:49,529 like, see if you could combine something like 463 00:16:49,529 --> 00:16:52,990 Copilot actions with some of the, Outlook stuff 464 00:16:53,129 --> 00:16:55,769 where you now have a regular prompt to 465 00:16:55,769 --> 00:16:57,769 go schedule 1 on ones and build an 466 00:16:57,769 --> 00:17:00,965 agenda based on the last week. And all 467 00:17:00,965 --> 00:17:03,785 of this is kinda automatically happening in Copilot 468 00:17:04,085 --> 00:17:06,644 behind the scenes. The other interesting one I 469 00:17:06,644 --> 00:17:10,664 saw going to the team stuff. Presentations, screen, 470 00:17:11,125 --> 00:17:14,289 capture, reasoning over that. But also the ability 471 00:17:14,349 --> 00:17:16,369 to reason over files 472 00:17:16,829 --> 00:17:17,329 shared 473 00:17:17,630 --> 00:17:20,109 in chat. Yes. So if somebody throws a 474 00:17:20,109 --> 00:17:22,349 word document out there or I don't know 475 00:17:22,349 --> 00:17:24,369 if it would extend out to URLs 476 00:17:25,304 --> 00:17:27,565 yet. I didn't read enough about it. But 477 00:17:27,704 --> 00:17:29,384 now someone throws a word document out there, 478 00:17:29,384 --> 00:17:31,625 and you don't wanna necessarily open it and 479 00:17:31,625 --> 00:17:33,865 have to summarize it. You can actually ask 480 00:17:33,865 --> 00:17:35,865 Copilot in the meeting, give me the key 481 00:17:35,865 --> 00:17:38,044 points from this document that was just shared 482 00:17:38,105 --> 00:17:40,650 without ever opening it, and it'll spit back 483 00:17:40,650 --> 00:17:42,809 that summarization of the word document. So maybe 484 00:17:42,809 --> 00:17:44,809 not summaries in word that are super intriguing, 485 00:17:44,809 --> 00:17:46,970 but that type of stuff where you can 486 00:17:46,970 --> 00:17:49,130 summarize the document shared in the chat without 487 00:17:49,130 --> 00:17:50,650 ever having to open it or look at 488 00:17:50,650 --> 00:17:53,115 it, I can see where that would be 489 00:17:53,115 --> 00:17:54,634 useful. I share a lot of links and 490 00:17:54,634 --> 00:17:56,335 documents and chats during the meeting, 491 00:17:57,115 --> 00:17:59,775 and that type of functionality that's coming, 492 00:18:00,154 --> 00:18:01,855 I'm really excited to 493 00:18:02,234 --> 00:18:04,234 start trying out and getting my hands on 494 00:18:04,234 --> 00:18:05,835 and playing with. I think you're gonna start 495 00:18:05,835 --> 00:18:06,494 to see 496 00:18:06,954 --> 00:18:07,454 more, 497 00:18:08,119 --> 00:18:09,500 and they had a term for it, 498 00:18:09,880 --> 00:18:12,460 agentic types types of things coming. 499 00:18:12,920 --> 00:18:13,420 So, 500 00:18:13,799 --> 00:18:14,779 you know, you have 501 00:18:15,080 --> 00:18:17,420 things like Copilot agents, which are ultimately 502 00:18:18,039 --> 00:18:20,184 a a wrapper for Copilot Studio. So you 503 00:18:20,184 --> 00:18:22,265 could absolutely go into Copilot Studio and build 504 00:18:22,265 --> 00:18:24,184 one of these things, but that might not 505 00:18:24,184 --> 00:18:26,105 be, like, your jam or your jelly, and 506 00:18:26,105 --> 00:18:27,464 maybe you're Right. That next next Well, in 507 00:18:27,464 --> 00:18:29,865 Copilot Studio, there's certain licensing to build some 508 00:18:29,865 --> 00:18:31,404 of your own in Copilot Studio. 509 00:18:31,785 --> 00:18:33,799 Right? Like, I know agents is different than 510 00:18:33,799 --> 00:18:35,320 if you're gonna go build a bunch of 511 00:18:35,320 --> 00:18:37,400 stuff in Copilot Studio. So it is a 512 00:18:37,400 --> 00:18:39,720 little bit different, and I I think one 513 00:18:39,720 --> 00:18:41,820 is, like, I tend to view, like, Copilot 514 00:18:41,880 --> 00:18:44,039 agents or at least the creation of, like, 515 00:18:44,039 --> 00:18:46,359 a custom Copilot agent Yep. To be, like, 516 00:18:46,359 --> 00:18:49,215 part of that m 365 stack. Right. And 517 00:18:49,215 --> 00:18:50,975 I look at things like Copilot Studio as 518 00:18:50,975 --> 00:18:54,195 more, like, the power grounded in the Azure 519 00:18:54,494 --> 00:18:56,255 stack and and and kind of that pillar 520 00:18:56,255 --> 00:18:58,035 that sits over there. But, 521 00:18:58,335 --> 00:19:01,075 like, to be clear, like, the agentic capabilities 522 00:19:02,015 --> 00:19:02,515 are 523 00:19:02,830 --> 00:19:03,330 coming 524 00:19:03,789 --> 00:19:06,450 from Copilot studio. Like, it's not the Copilot 525 00:19:06,509 --> 00:19:08,130 agent front end. I had that. 526 00:19:08,750 --> 00:19:10,590 It's the back end with that thing. Yes. 527 00:19:10,590 --> 00:19:12,990 So now, like, when we talk about, like, 528 00:19:12,990 --> 00:19:13,970 agentic capabilities, 529 00:19:14,670 --> 00:19:16,585 that could be things like, you know, I 530 00:19:16,585 --> 00:19:18,424 think, eventually, that gets to the point where 531 00:19:18,424 --> 00:19:20,505 it can click buttons on your screen. It's 532 00:19:20,505 --> 00:19:22,265 not there today, but I think that's where 533 00:19:22,265 --> 00:19:24,505 they go, especially That'll be interesting. Especially where, 534 00:19:24,505 --> 00:19:26,904 like, Claude has gone, like, with Sonic and 535 00:19:26,904 --> 00:19:29,225 and and Claude 35. Like, they announced, like, 536 00:19:29,225 --> 00:19:29,725 their 537 00:19:30,309 --> 00:19:31,049 new computer 538 00:19:31,590 --> 00:19:33,590 model a couple weeks ago. So I think 539 00:19:33,590 --> 00:19:35,269 that's where some of this stuff goes, and 540 00:19:35,269 --> 00:19:36,549 I don't know what that does to Power 541 00:19:36,549 --> 00:19:38,390 Automate or other tools that are out there 542 00:19:38,390 --> 00:19:38,890 today. 543 00:19:39,430 --> 00:19:39,930 But, 544 00:19:40,309 --> 00:19:42,090 you know, it's it's gonna come, but 545 00:19:42,424 --> 00:19:45,964 there's also Agenta capabilities in that you can 546 00:19:46,105 --> 00:19:46,605 string 547 00:19:47,384 --> 00:19:49,005 multiple things together. 548 00:19:49,544 --> 00:19:50,744 So I don't have a good example of, 549 00:19:50,744 --> 00:19:52,345 like, a Copilot engine that does this, but 550 00:19:52,345 --> 00:19:53,724 I saw it in another session 551 00:19:54,265 --> 00:19:55,484 while I was here at Ignite, 552 00:19:55,940 --> 00:19:56,440 And 553 00:19:57,220 --> 00:19:58,119 that was around 554 00:19:59,299 --> 00:20:00,359 was around PowerToys. 555 00:20:00,980 --> 00:20:01,960 And PowerToys 556 00:20:02,819 --> 00:20:03,960 has a, 557 00:20:04,500 --> 00:20:06,660 capability that's being built into it that's gonna 558 00:20:06,660 --> 00:20:08,980 allow you to basically pump in, like, an 559 00:20:08,980 --> 00:20:09,480 open 560 00:20:10,005 --> 00:20:11,945 an open AI or a chat JPT 561 00:20:12,325 --> 00:20:13,224 API key, 562 00:20:13,525 --> 00:20:15,625 and then use that in the background to 563 00:20:15,684 --> 00:20:16,184 do, 564 00:20:17,045 --> 00:20:19,445 agentic type things. So one of the things 565 00:20:19,445 --> 00:20:21,684 that's gonna be coming in PowerToys is the 566 00:20:21,684 --> 00:20:23,865 ability to, say, take a screenshot, 567 00:20:24,200 --> 00:20:26,299 and that screenshot could be in another language, 568 00:20:26,680 --> 00:20:29,960 and you can have it translate it for 569 00:20:29,960 --> 00:20:32,859 you. Like, hey. Translate this screenshot to text. 570 00:20:33,000 --> 00:20:34,359 And then the other way you could do 571 00:20:34,359 --> 00:20:35,980 is you could put text on your clipboard 572 00:20:36,484 --> 00:20:38,484 and like, in a foreign language. Yep. And 573 00:20:38,484 --> 00:20:41,125 you could say, translate this text and save 574 00:20:41,125 --> 00:20:42,345 it as a text document 575 00:20:42,725 --> 00:20:43,225 in 576 00:20:43,605 --> 00:20:44,105 my 577 00:20:44,404 --> 00:20:46,644 current folder. Right? Okay. That I'm working kind 578 00:20:46,644 --> 00:20:48,025 of thing. Or 579 00:20:48,340 --> 00:20:50,820 you could string all those capabilities together, and 580 00:20:50,820 --> 00:20:52,420 you could just ask the AI. You could 581 00:20:52,420 --> 00:20:52,920 say, 582 00:20:53,539 --> 00:20:54,840 AI, take the screenshot, 583 00:20:55,460 --> 00:20:56,600 translate the screenshot, 584 00:20:57,140 --> 00:20:59,720 and save the text of that translated 585 00:21:00,420 --> 00:21:00,920 thing 586 00:21:01,224 --> 00:21:03,565 as a text file in my current folder. 587 00:21:04,024 --> 00:21:06,744 So the the agentic capability is really being 588 00:21:06,744 --> 00:21:09,464 able to tie all those things together in 589 00:21:09,464 --> 00:21:12,345 an autonomous way versus you having to do 590 00:21:12,345 --> 00:21:14,044 it as, like, a set of discrete steps. 591 00:21:14,264 --> 00:21:15,704 So is there power in doing it in 592 00:21:15,704 --> 00:21:17,779 the discrete steps? Absolutely. I think of that 593 00:21:17,859 --> 00:21:18,900 I think that's the way a lot of 594 00:21:18,900 --> 00:21:20,579 folks are gonna approach it in the beginning. 595 00:21:20,579 --> 00:21:22,740 Yeah. But as this opens up and as 596 00:21:22,740 --> 00:21:24,119 the world of connectors 597 00:21:24,500 --> 00:21:25,480 and those capabilities 598 00:21:25,940 --> 00:21:27,480 kind of come come along, 599 00:21:27,779 --> 00:21:30,065 I think then it starts to get super 600 00:21:30,284 --> 00:21:32,444 interesting. Right? So, like, earlier, you know, we 601 00:21:32,444 --> 00:21:33,984 talked through the example of 602 00:21:34,684 --> 00:21:36,845 just being able to, like, maybe compare your 603 00:21:36,845 --> 00:21:39,964 sales numbers to released features or things like 604 00:21:39,964 --> 00:21:43,005 that. What if you're on the marketing side 605 00:21:43,005 --> 00:21:45,179 and you have other stats that are out 606 00:21:45,179 --> 00:21:46,559 there in the marketing engine, 607 00:21:46,859 --> 00:21:48,700 and you just happen to be an Adobe 608 00:21:48,700 --> 00:21:50,619 marketing customer? Well, how do you get at 609 00:21:50,619 --> 00:21:51,200 that data? 610 00:21:51,500 --> 00:21:52,940 You know, I think that can be a 611 00:21:52,940 --> 00:21:54,779 little rough because sometimes you need an API 612 00:21:54,779 --> 00:21:56,539 or another things to talk to it. Well, 613 00:21:56,539 --> 00:21:58,139 there's also a bunch of, like, 3rd party 614 00:21:58,139 --> 00:22:00,855 agents. So now you can potentially string agents 615 00:22:00,855 --> 00:22:03,414 together because you can at mention agents in 616 00:22:03,414 --> 00:22:04,075 your prompts. 617 00:22:04,375 --> 00:22:06,214 So you can say at this agent, do 618 00:22:06,214 --> 00:22:08,294 this, and then you guys can mention agent. 619 00:22:08,375 --> 00:22:10,214 I think you're eventually, you're gonna have the 620 00:22:10,214 --> 00:22:13,115 capability to just string all those things together. 621 00:22:13,490 --> 00:22:15,570 And then maybe you're building agents based on 622 00:22:15,570 --> 00:22:18,150 agents, and it starts to get really weird 623 00:22:18,210 --> 00:22:20,070 really fast. But, 624 00:22:21,250 --> 00:22:23,890 you know, arguably, there's some some good stuff 625 00:22:23,890 --> 00:22:25,250 in there. Yeah. I think the thing folks 626 00:22:25,250 --> 00:22:26,529 need to keep in mind is, like, it's 627 00:22:26,529 --> 00:22:28,545 still in, like, the very early days. Like, 628 00:22:28,705 --> 00:22:30,465 everybody is still in a land grab here. 629 00:22:30,465 --> 00:22:32,865 Like I said, like, Claude, couple weeks ago, 630 00:22:32,865 --> 00:22:35,585 just announced the Agentech capabilities. Like, click a 631 00:22:35,585 --> 00:22:37,585 button on my screen and and do those 632 00:22:37,585 --> 00:22:40,305 kinds of things. I think, eventually, Open AI 633 00:22:40,305 --> 00:22:42,225 Open AI has signaled their intent to get 634 00:22:42,225 --> 00:22:44,859 there. You know, when Open AI gets there, 635 00:22:44,859 --> 00:22:47,675 Microsoft gets there, or Microsoft does it on 636 00:22:47,675 --> 00:22:50,059 its own. All these companies do. Mistral does 637 00:22:50,059 --> 00:22:52,619 it. Everybody's going to do it, and it's 638 00:22:52,619 --> 00:22:54,880 gonna open up this, like, kinda 639 00:22:55,294 --> 00:22:56,974 new world of stuff. Right? Like, we don't 640 00:22:56,974 --> 00:22:59,615 necessarily know what people are going to do 641 00:22:59,615 --> 00:23:01,294 with it, and I think that's a little 642 00:23:01,294 --> 00:23:03,214 rough. And and and you can tell that 643 00:23:03,214 --> 00:23:05,294 by the positioning of some of the other 644 00:23:05,294 --> 00:23:06,434 things that were announced. 645 00:23:06,974 --> 00:23:09,460 So one of the funny ones to me, 646 00:23:09,519 --> 00:23:10,259 not funny 647 00:23:10,640 --> 00:23:12,799 but funny, like, weird, was how do we 648 00:23:12,799 --> 00:23:15,519 measure the ROI of Copilot and all the 649 00:23:15,519 --> 00:23:18,000 agents that we've built? Right? So you need 650 00:23:18,000 --> 00:23:20,160 you need you need analytics to do that. 651 00:23:20,160 --> 00:23:21,140 So you would think 652 00:23:21,875 --> 00:23:24,615 analytics for Copilot would be like, which users 653 00:23:24,674 --> 00:23:25,494 in my organization 654 00:23:26,115 --> 00:23:27,494 are using Copilot? 655 00:23:27,954 --> 00:23:29,794 How often are they using it? What's the 656 00:23:29,794 --> 00:23:31,794 data that they're using it against? And that's 657 00:23:31,794 --> 00:23:34,034 one part of it, but that doesn't actually 658 00:23:34,034 --> 00:23:36,299 tell you the ROI of Copilot. That just 659 00:23:36,299 --> 00:23:37,900 tells you how much people are using it. 660 00:23:37,900 --> 00:23:39,980 It doesn't tell you, like, how good it 661 00:23:39,980 --> 00:23:42,779 was. So one of the things with some 662 00:23:42,779 --> 00:23:44,480 of these things, like analytics, 663 00:23:45,019 --> 00:23:47,339 is it's very early days of analytics where 664 00:23:47,339 --> 00:23:49,179 they're doing things and and you you can 665 00:23:49,179 --> 00:23:50,875 see this, like you know, I was kind 666 00:23:50,875 --> 00:23:52,474 of paying attention while I was walking across 667 00:23:52,474 --> 00:23:54,954 the Xflow floor too. There's some companies that 668 00:23:54,954 --> 00:23:56,894 are also doing this analytics capability 669 00:23:57,355 --> 00:24:00,075 where they are presenting analytics in the form 670 00:24:00,075 --> 00:24:00,575 of, 671 00:24:01,194 --> 00:24:03,434 kind of like a a secure score kind 672 00:24:03,434 --> 00:24:05,399 of thing. Tell me how good I'm doing 673 00:24:05,399 --> 00:24:07,819 against other companies that are in my segment. 674 00:24:07,960 --> 00:24:10,200 How much are they using AI? And then 675 00:24:10,200 --> 00:24:12,200 maybe you have a measure to say, like, 676 00:24:12,200 --> 00:24:13,659 oh, is that company growing? 677 00:24:14,279 --> 00:24:15,500 Is it slowing down? 678 00:24:15,960 --> 00:24:18,200 Is is it actually an accelerator in that 679 00:24:18,200 --> 00:24:20,224 business? We had dinner tonight, Scott. So I 680 00:24:20,224 --> 00:24:22,384 was getting phone calls and text messages about 681 00:24:22,384 --> 00:24:24,625 dinner here. Okay. So I was just making 682 00:24:24,625 --> 00:24:25,845 sure we're still 683 00:24:26,464 --> 00:24:27,284 doing okay. 684 00:24:27,825 --> 00:24:29,984 So one thing, you mentioned translations. I'm curious 685 00:24:29,984 --> 00:24:31,345 what your thought was on this one, since 686 00:24:31,345 --> 00:24:34,289 you mentioned doing the whole translation thing. The 687 00:24:34,529 --> 00:24:35,029 Teams 688 00:24:35,330 --> 00:24:35,830 live 689 00:24:36,850 --> 00:24:38,950 translations of a different language 690 00:24:39,650 --> 00:24:42,869 on a call, and not only live translations 691 00:24:43,170 --> 00:24:45,009 where I could be presenting and it would 692 00:24:45,009 --> 00:24:47,490 be live translating into another language for other 693 00:24:47,490 --> 00:24:49,964 attendees on the Teams call, It would also 694 00:24:49,964 --> 00:24:51,184 make that live translation 695 00:24:51,644 --> 00:24:54,545 sound like it was actually That's an option. 696 00:24:54,765 --> 00:24:56,125 You don't have to You don't have to 697 00:24:56,125 --> 00:24:58,065 do that, but it was Wait with everybody. 698 00:24:58,444 --> 00:25:00,384 Some people are like, that's just kinda creepy 699 00:25:00,845 --> 00:25:02,684 of it sounding like you in a different 700 00:25:02,684 --> 00:25:05,769 language. But that was another one where it's 701 00:25:05,990 --> 00:25:08,170 again, I think moving into practical application. 702 00:25:08,630 --> 00:25:09,769 Because I've been on 703 00:25:10,150 --> 00:25:11,049 calls before 704 00:25:11,430 --> 00:25:11,930 and, 705 00:25:13,589 --> 00:25:14,809 training and 706 00:25:15,269 --> 00:25:18,230 people have turned on captions. Because I'm teaching 707 00:25:18,230 --> 00:25:19,289 people over in 708 00:25:19,644 --> 00:25:22,444 APAC or over in Europe that English isn't 709 00:25:22,444 --> 00:25:24,865 necessarily their first language and they prefer 710 00:25:25,484 --> 00:25:25,984 to 711 00:25:26,365 --> 00:25:28,125 speak or read in their native language or 712 00:25:28,125 --> 00:25:29,964 it helps them to read it in English 713 00:25:29,964 --> 00:25:31,345 versus just hearing it. 714 00:25:31,769 --> 00:25:33,690 But I think that would that's one that's 715 00:25:33,690 --> 00:25:36,890 really powerful. Whether it's global companies and some 716 00:25:36,890 --> 00:25:38,809 of the people I was talking to were 717 00:25:38,809 --> 00:25:40,330 in that same boat. They're like, you know 718 00:25:40,330 --> 00:25:42,910 when I'm regularly on calls with people from 719 00:25:43,210 --> 00:25:45,630 China or from Japan and 720 00:25:46,214 --> 00:25:48,294 they actually have to have translators on the 721 00:25:48,294 --> 00:25:51,255 call. That can slow communication down quite a 722 00:25:51,255 --> 00:25:52,474 bit and make it challenging. 723 00:25:52,855 --> 00:25:55,174 Where I think this really has the potential 724 00:25:55,174 --> 00:25:58,154 to be nice for global companies, for training, 725 00:25:58,454 --> 00:25:58,954 to 726 00:25:59,440 --> 00:26:02,340 help that be delivered in people's native languages 727 00:26:02,400 --> 00:26:03,539 and help people communicate 728 00:26:04,000 --> 00:26:05,920 better on these Teams meetings? Once you get 729 00:26:05,920 --> 00:26:08,820 over the creep factor, it's an inclusivity thing. 730 00:26:10,320 --> 00:26:13,200 If, generally speaking, folks are more comfortable talking 731 00:26:13,200 --> 00:26:14,500 in their native language, 732 00:26:14,984 --> 00:26:16,765 unless they've been, like, multilingual, 733 00:26:17,464 --> 00:26:19,464 you know, from from early days kinds of 734 00:26:19,464 --> 00:26:20,204 things. So, 735 00:26:20,744 --> 00:26:22,825 you know, I I work for a global 736 00:26:22,825 --> 00:26:25,065 company. Like, there are definitely times where I 737 00:26:25,065 --> 00:26:25,964 am on the phone 738 00:26:26,424 --> 00:26:28,845 with folks in America, 739 00:26:29,384 --> 00:26:29,819 Europe, 740 00:26:31,099 --> 00:26:31,599 India, 741 00:26:32,059 --> 00:26:34,460 and China at the same time. And it's 742 00:26:34,460 --> 00:26:35,440 a lot of accents, 743 00:26:35,819 --> 00:26:37,359 it's a lot of 744 00:26:37,819 --> 00:26:39,440 it's a lot of active listening, 745 00:26:39,899 --> 00:26:42,299 and active listening can be kind of tired. 746 00:26:42,299 --> 00:26:44,404 If I'm on a phone call at 10 747 00:26:44,404 --> 00:26:46,005 PM my time because I wanted to talk 748 00:26:46,005 --> 00:26:48,164 to somebody in Shanghai and I've got somebody 749 00:26:48,164 --> 00:26:49,924 in Europe on the phone, well, 10 PM 750 00:26:49,924 --> 00:26:52,484 for me is, like, 4 AM for most 751 00:26:52,484 --> 00:26:54,404 of my European employees. They don't like being 752 00:26:54,404 --> 00:26:55,224 up that early. 753 00:26:55,684 --> 00:26:58,025 You know, it's it's getting to be 754 00:26:58,470 --> 00:27:01,029 just weird times all around for for everybody 755 00:27:01,029 --> 00:27:02,490 on that call. So, 756 00:27:02,869 --> 00:27:04,390 you know, I think most folks just wanna 757 00:27:04,390 --> 00:27:06,009 go through that in a comfortable experience. 758 00:27:06,549 --> 00:27:09,529 I can totally see the value of that. 759 00:27:10,150 --> 00:27:12,444 Folks are hopefully get get over the creep 760 00:27:12,444 --> 00:27:14,365 factor. Like, I would very much look forward 761 00:27:14,365 --> 00:27:15,825 to it. I would rather have 762 00:27:16,924 --> 00:27:18,464 a native Mandarin speaker 763 00:27:18,845 --> 00:27:23,184 be speaking native Mandarin rather than trying to 764 00:27:23,730 --> 00:27:25,910 speak English sometimes Yes. Especially 765 00:27:26,450 --> 00:27:29,170 in the tech space or I think any 766 00:27:29,170 --> 00:27:31,730 kind of acronym heavy thing. You could be 767 00:27:31,730 --> 00:27:32,230 in 768 00:27:32,529 --> 00:27:33,029 logistics. 769 00:27:33,410 --> 00:27:35,809 You could be in health care. You could 770 00:27:35,809 --> 00:27:38,704 be in finance. Like, there's so many just 771 00:27:38,924 --> 00:27:41,244 jobs out there that you get lost in 772 00:27:41,244 --> 00:27:44,765 the jumble of the the actual, like, language 773 00:27:44,765 --> 00:27:45,505 of the company, 774 00:27:45,805 --> 00:27:47,884 let alone human language and all the constructs 775 00:27:47,884 --> 00:27:49,244 and things that come along with it. So 776 00:27:49,244 --> 00:27:50,684 I think if it provides that measure of 777 00:27:50,684 --> 00:27:52,204 comfort and gets folks to where they need 778 00:27:52,204 --> 00:27:55,210 to be, I'd I'd be happy to do 779 00:27:55,210 --> 00:27:57,930 it. It's kinda comes down to how well 780 00:27:57,930 --> 00:28:00,509 it works. Right? So so I worry about 781 00:28:00,890 --> 00:28:02,109 things like 782 00:28:02,490 --> 00:28:05,769 I I often speak in, like, riddles because 783 00:28:05,769 --> 00:28:08,515 I'll just use little quips or things like 784 00:28:08,515 --> 00:28:10,035 that. Or, like, we're we're in the South. 785 00:28:10,035 --> 00:28:11,875 Right? You and I live in Florida. People 786 00:28:11,875 --> 00:28:14,595 say y'all. Or all y'all. Or all y'all. 787 00:28:14,595 --> 00:28:17,335 Yeah. So how is that gonna translate into 788 00:28:17,474 --> 00:28:18,775 Mandarin or Japanese? 789 00:28:19,234 --> 00:28:20,214 I don't know. 790 00:28:20,740 --> 00:28:23,400 You know, TBD, how things like that goes. 791 00:28:23,460 --> 00:28:25,319 Or do I have to be more intentional 792 00:28:25,380 --> 00:28:27,880 as a speaker and kinda keep things grounded? 793 00:28:28,099 --> 00:28:30,500 And maybe that's, like, it absolutely is something 794 00:28:30,500 --> 00:28:32,179 I should probably do. Right. Maybe that's a 795 00:28:32,179 --> 00:28:33,460 good thing, that it would force you to 796 00:28:33,460 --> 00:28:34,759 be a little bit more 797 00:28:35,234 --> 00:28:37,154 focused in what you said and not use 798 00:28:37,154 --> 00:28:37,654 those 799 00:28:38,194 --> 00:28:40,674 the slang that we tend to use or 800 00:28:40,674 --> 00:28:41,174 the 801 00:28:41,875 --> 00:28:44,994 weird catch phrases or different things like that 802 00:28:44,994 --> 00:28:47,234 of okay. Let's be intentional about what we're 803 00:28:47,234 --> 00:28:49,819 saying. So the translator works, which is probably 804 00:28:49,819 --> 00:28:52,799 something we should do anyways. It's all empowering 805 00:28:53,019 --> 00:28:53,519 stuff. 806 00:28:54,059 --> 00:28:56,559 You know, the thing that struck me about 807 00:28:56,940 --> 00:28:58,319 the keynote today 808 00:28:58,700 --> 00:28:59,200 is 809 00:28:59,659 --> 00:29:01,279 it was very 810 00:29:01,579 --> 00:29:02,799 end user focused. 811 00:29:03,384 --> 00:29:05,085 I I think, you 812 00:29:05,384 --> 00:29:07,404 know, my meta comment on 813 00:29:07,785 --> 00:29:09,544 what I saw at the keynote and and 814 00:29:09,544 --> 00:29:11,804 really what I've seen at Ignite so far 815 00:29:12,105 --> 00:29:12,605 is 816 00:29:12,904 --> 00:29:15,544 the days of this being the IT Pro 817 00:29:15,544 --> 00:29:16,765 conference from Microsoft 818 00:29:17,269 --> 00:29:19,509 are well behind us. Right. Like, there's been 819 00:29:19,509 --> 00:29:21,750 this general sense that it's more a kind 820 00:29:21,750 --> 00:29:23,750 of marketing engine, at least, for the last 821 00:29:23,750 --> 00:29:24,490 couple of years. 822 00:29:24,950 --> 00:29:26,950 This year really, like, sealed it for me. 823 00:29:26,950 --> 00:29:27,990 I think if you go out and look 824 00:29:27,990 --> 00:29:30,375 at the session catalog, there are, like, hundreds 825 00:29:30,375 --> 00:29:31,195 of sessions 826 00:29:31,735 --> 00:29:34,934 on Copilot this, AI this. There there's not 827 00:29:34,934 --> 00:29:37,335 really anything out there about how to manage 828 00:29:37,335 --> 00:29:39,815 Exchange online. There's how to manage Exchange online 829 00:29:39,815 --> 00:29:40,555 with Copilot, 830 00:29:40,934 --> 00:29:42,855 but there's not the down in the weeds 831 00:29:42,855 --> 00:29:45,320 things about, oh, I wanted to build this 832 00:29:45,320 --> 00:29:48,200 custom experience using the Graph API, or I 833 00:29:48,200 --> 00:29:50,460 wanted to build this custom experience using 834 00:29:51,080 --> 00:29:52,299 Exchange Web Services, 835 00:29:52,840 --> 00:29:56,059 or I wanted to interact as an admin 836 00:29:56,440 --> 00:29:59,105 and, you know, do x, y, zed, whatever 837 00:29:59,244 --> 00:30:01,505 it happens to be. That that stuff just 838 00:30:01,565 --> 00:30:04,125 wasn't there. So it's all end user facing 839 00:30:04,125 --> 00:30:05,184 things. I do 840 00:30:05,484 --> 00:30:08,285 kinda wonder and worry kinda long term what 841 00:30:08,285 --> 00:30:10,204 that means. Maybe that means AI is gonna 842 00:30:10,204 --> 00:30:11,804 replace all our jobs. So 843 00:30:12,444 --> 00:30:14,304 No. Maybe that's the thing. But 844 00:30:14,710 --> 00:30:16,630 it's it's interesting to see the direction it 845 00:30:16,630 --> 00:30:17,130 goes. 846 00:30:17,670 --> 00:30:18,950 There's a lot of 847 00:30:19,590 --> 00:30:21,269 I I genuinely think there's a lot of 848 00:30:21,269 --> 00:30:23,750 goodness there, but I don't know that it 849 00:30:23,750 --> 00:30:25,910 was, like, the goodness that I was looking 850 00:30:25,910 --> 00:30:28,309 for. I I kinda wanted to walk in 851 00:30:28,309 --> 00:30:30,285 and be wowed with a set of 852 00:30:30,765 --> 00:30:33,164 capabilities that would, like, help me accelerate as 853 00:30:33,164 --> 00:30:34,144 an IT pro. 854 00:30:34,525 --> 00:30:36,045 You know? And and those things are out 855 00:30:36,045 --> 00:30:38,365 there. Right? Like, I I think AI shell 856 00:30:38,365 --> 00:30:40,205 is one of those things that was recently 857 00:30:40,205 --> 00:30:40,705 announced. 858 00:30:41,164 --> 00:30:43,984 There's a lot of goodness coming inside of 859 00:30:44,365 --> 00:30:45,585 Copilot for GitHub. 860 00:30:46,240 --> 00:30:48,559 You know, totally applicable to non developers as 861 00:30:48,559 --> 00:30:50,240 well. Like, it'll totally help you write a 862 00:30:50,240 --> 00:30:51,940 PowerShell script when you need it to. 863 00:30:52,319 --> 00:30:54,559 Some of the code capabilities that are coming 864 00:30:54,559 --> 00:30:55,059 to 865 00:30:55,839 --> 00:30:56,740 GitHub Copilot 866 00:30:57,919 --> 00:31:00,640 and Copilot in general and being able to 867 00:31:00,640 --> 00:31:03,514 reason over code, like, those those are legitimately 868 00:31:03,815 --> 00:31:05,095 good things. So when I say code, I 869 00:31:05,095 --> 00:31:06,615 mean, like, could be like a bash script 870 00:31:06,615 --> 00:31:09,095 or IT pro code is what you're saying. 871 00:31:09,095 --> 00:31:10,534 Or, like, you know, we've talked in the 872 00:31:10,534 --> 00:31:12,774 past, like, interacting with REST APIs and things 873 00:31:12,774 --> 00:31:14,294 like that, I think, tends to be something. 874 00:31:14,294 --> 00:31:16,179 Like, everybody know needs to know how to 875 00:31:16,179 --> 00:31:18,099 fire off an HTTP request and maybe do, 876 00:31:18,099 --> 00:31:19,779 like, a git or a put or things 877 00:31:19,779 --> 00:31:20,279 like 878 00:31:21,059 --> 00:31:22,980 that. You know? So it's a little weird 879 00:31:22,980 --> 00:31:24,980 that, like, that stuff isn't there because that 880 00:31:24,980 --> 00:31:26,339 stuff would have been there in, like, the 881 00:31:26,339 --> 00:31:27,045 hero days. 882 00:31:27,605 --> 00:31:29,525 Right. I think of what people think back 883 00:31:29,525 --> 00:31:33,205 to, like, when Ignite was the IT pro 884 00:31:33,205 --> 00:31:33,705 conference 885 00:31:34,884 --> 00:31:37,205 and, you know, TechEd before that and and 886 00:31:37,205 --> 00:31:38,965 things like that. Do you think some of 887 00:31:38,965 --> 00:31:40,880 it, though and then we should wrap up 888 00:31:40,880 --> 00:31:42,480 because we do have to go to dinner. 889 00:31:42,480 --> 00:31:44,000 But do you think some of it is 890 00:31:44,000 --> 00:31:46,480 even the advent of the cloud and that's 891 00:31:47,200 --> 00:31:48,880 some of that stuff is still there, but 892 00:31:48,880 --> 00:31:51,919 in some respects the IT pro's job has 893 00:31:51,919 --> 00:31:54,924 changed. Because I remember, like you mentioned TechEd 894 00:31:54,924 --> 00:31:56,625 or even some of the SharePoint conferences, 895 00:31:57,244 --> 00:31:59,664 where you were getting 400 level sessions 896 00:32:00,044 --> 00:32:00,544 on 897 00:32:00,924 --> 00:32:03,724 how SharePoint stored content and databases and how 898 00:32:03,724 --> 00:32:05,585 to optimize your SQL databases 899 00:32:06,285 --> 00:32:06,785 for 900 00:32:07,440 --> 00:32:09,759 SharePoint data storage. I remember, like, a Spence 901 00:32:09,759 --> 00:32:11,700 Harbar 400 level session on 902 00:32:12,000 --> 00:32:13,139 all the intricacies 903 00:32:13,440 --> 00:32:15,519 of how the user profile service worked in 904 00:32:15,519 --> 00:32:16,019 SharePoint. 905 00:32:17,039 --> 00:32:18,500 As an IT pro, 906 00:32:19,039 --> 00:32:22,404 that type of work, just it's there in 907 00:32:22,404 --> 00:32:24,244 some companies. There are some companies I just 908 00:32:24,244 --> 00:32:28,005 did a SharePoint on prem installation upgrade, like, 909 00:32:28,005 --> 00:32:29,684 the last couple months. What are the last 910 00:32:29,684 --> 00:32:31,605 ones? Sticking with it. But is it truly 911 00:32:31,605 --> 00:32:33,384 that there's maybe not as much 912 00:32:33,990 --> 00:32:35,849 400 level content that applies 913 00:32:36,630 --> 00:32:37,130 to 914 00:32:37,670 --> 00:32:39,829 the broader level of people? Because I know 915 00:32:39,829 --> 00:32:41,990 my IT pro job has changed. I'm not 916 00:32:41,990 --> 00:32:43,910 in the weeds on servers. I'm still doing 917 00:32:43,910 --> 00:32:46,970 stuff with security, with conditional access, with Intune. 918 00:32:47,029 --> 00:32:50,855 Troubleshooting that, it's different. And I there's definitely 919 00:32:50,994 --> 00:32:52,934 not that level of content 920 00:32:53,474 --> 00:32:57,014 here that there probably could be about managing 921 00:32:57,154 --> 00:32:59,095 devices. I'm curious to 922 00:32:59,954 --> 00:33:01,474 go into some of the sessions and read 923 00:33:01,474 --> 00:33:03,075 through some of the blog posts, because there 924 00:33:03,075 --> 00:33:04,054 have been some 925 00:33:04,650 --> 00:33:07,070 things that have caught my eye around particularly 926 00:33:07,450 --> 00:33:08,509 security and Copilot. 927 00:33:08,890 --> 00:33:10,490 But I do think the IT pros job 928 00:33:10,490 --> 00:33:12,970 has changed, which may also have led to 929 00:33:12,970 --> 00:33:14,330 some of this. I think some of it's 930 00:33:14,330 --> 00:33:17,494 self fulfilling prophecy. Right? Like, that that kind 931 00:33:17,494 --> 00:33:18,554 of glue in the middle 932 00:33:18,855 --> 00:33:21,335 is just not talked about anymore, but it 933 00:33:21,335 --> 00:33:22,154 still exists. 934 00:33:22,615 --> 00:33:24,934 Like, if you're gonna go out and I 935 00:33:24,934 --> 00:33:26,375 I and I think the keynote today was 936 00:33:26,375 --> 00:33:28,294 a good example of that. It talked about 937 00:33:28,294 --> 00:33:30,315 the front end with users and Copilot, 938 00:33:30,649 --> 00:33:32,409 and it talked about the back end with 939 00:33:32,409 --> 00:33:35,929 things like Azure AI search and Cosmos DB 940 00:33:35,929 --> 00:33:38,409 and the developer experience. Yep. It didn't talk 941 00:33:38,409 --> 00:33:40,669 about how to bridge that gap. 942 00:33:40,970 --> 00:33:42,089 So somebody needs to 943 00:33:42,809 --> 00:33:44,730 before the end user can consume it up 944 00:33:44,730 --> 00:33:46,944 here, somebody needs to go and provision that 945 00:33:46,944 --> 00:33:49,505 infrastructure. And that's still a step that needs 946 00:33:49,505 --> 00:33:51,825 to happen. And it it's very strange to 947 00:33:51,825 --> 00:33:54,224 me that those things are kind of cut 948 00:33:54,224 --> 00:33:56,384 out of the experience. Right? Like, I would 949 00:33:56,384 --> 00:33:59,284 think something like AI Shell and the ability 950 00:33:59,345 --> 00:34:00,164 to leverage 951 00:34:00,869 --> 00:34:01,369 Azure, 952 00:34:01,910 --> 00:34:04,109 Copilot for Azure, Azure Copilot, whatever they call 953 00:34:04,109 --> 00:34:06,549 it Whatever. To leverage and and integrate that 954 00:34:06,549 --> 00:34:08,550 in because it's part of that experience. Right? 955 00:34:08,550 --> 00:34:10,469 It completes the story. You can't tell me 956 00:34:10,469 --> 00:34:11,289 about the 957 00:34:11,590 --> 00:34:13,130 beginning and the end, 958 00:34:13,954 --> 00:34:16,114 or, you know, like, the the end and 959 00:34:16,114 --> 00:34:17,875 the middle without giving me, like, how did 960 00:34:17,875 --> 00:34:19,474 how did all this stuff come to fruition 961 00:34:19,474 --> 00:34:19,974 and 962 00:34:20,914 --> 00:34:22,994 and and where did it spin up along 963 00:34:22,994 --> 00:34:24,835 the way? So I think we talk a 964 00:34:24,835 --> 00:34:26,835 lot about, like, inner loop and outer loop 965 00:34:26,835 --> 00:34:29,369 and developer life cycles and things like that, 966 00:34:29,530 --> 00:34:32,010 But IT pros are largely, like, left out 967 00:34:32,010 --> 00:34:33,610 of that equation. Yeah. Well, and I think 968 00:34:33,610 --> 00:34:35,530 it probably does exist more on the Azure 969 00:34:35,530 --> 00:34:37,530 side, to your point. It definitely exists more 970 00:34:37,530 --> 00:34:39,230 on the Azure side than maybe the M365 971 00:34:39,690 --> 00:34:41,769 side because you do have all the Azure 972 00:34:41,769 --> 00:34:43,450 in front. How do you get that to 973 00:34:43,450 --> 00:34:44,190 end users? 974 00:34:45,114 --> 00:34:46,555 So but we have a lot more stuff. 975 00:34:46,555 --> 00:34:47,755 We have a lot more stuff from the 976 00:34:47,755 --> 00:34:49,755 keynote than we actually got to, Scott. Surprise, 977 00:34:49,755 --> 00:34:51,434 surprise. We had a bunch of notes and 978 00:34:51,434 --> 00:34:52,635 we only got to a fraction of them. 979 00:34:52,635 --> 00:34:54,315 You let me talk about Copilot after you 980 00:34:54,315 --> 00:34:55,775 said you weren't. So we're good. 981 00:34:56,394 --> 00:34:58,315 It happens. Every once in a while, I 982 00:34:58,315 --> 00:35:00,900 just let you loose to talk about what 983 00:35:00,900 --> 00:35:03,219 you're feeling passionate about on that given day. 984 00:35:03,219 --> 00:35:04,659 But we do have stuff like, I did 985 00:35:04,659 --> 00:35:07,159 an interview today with someone from Microsoft about 986 00:35:07,300 --> 00:35:09,059 a new device Microsoft is coming out with 987 00:35:09,059 --> 00:35:11,059 a Microsoft 365 link. We have a bunch 988 00:35:11,059 --> 00:35:13,219 of other Windows 365. Windows 365. I said 989 00:35:13,219 --> 00:35:14,465 it wrong. Windows 990 00:35:14,765 --> 00:35:17,005 365 link. There will be that. We might 991 00:35:17,005 --> 00:35:19,644 have to do a few Ignite recordings while 992 00:35:19,644 --> 00:35:21,325 we're here and talk about some of the 993 00:35:21,325 --> 00:35:24,045 other keynote stuff we have and we might 994 00:35:24,045 --> 00:35:25,885 line up some other interviews with people over 995 00:35:25,885 --> 00:35:27,809 here. Yeah. Make it work. Now it's time 996 00:35:27,809 --> 00:35:29,730 for dinner, Scott. I am looking forward to 997 00:35:29,730 --> 00:35:32,309 this steak. Sounds good. Let's do it. Alright. 998 00:35:32,449 --> 00:35:34,230 Well, thanks, Scott. We'll talk to you later. 999 00:35:36,210 --> 00:35:38,449 If you enjoyed the podcast, go leave us 1000 00:35:38,449 --> 00:35:40,690 a 5 star rating in iTunes. It helps 1001 00:35:40,690 --> 00:35:42,494 to get the word out so more IT 1002 00:35:42,494 --> 00:35:45,234 pros can learn about Office 365 and Azure. 1003 00:35:45,775 --> 00:35:47,375 If you have any questions you want us 1004 00:35:47,375 --> 00:35:49,614 to address on the show, or feedback about 1005 00:35:49,614 --> 00:35:51,934 the show, feel free to reach out via 1006 00:35:51,934 --> 00:35:55,214 our website, Twitter, or Facebook. Thanks again for 1007 00:35:55,214 --> 00:35:56,835 listening, and have a great day.

Digital Dispatch Podcast Podcast Artwork Image

Microsoft Cloud IT Pro Podcast

Ben Stegink, Scott Hoag

On the MS Cloud IT Pro Podcast, Scott and Ben discuss the Microsoft Cloud with a focus on IT Pros. They'll discuss the latest in Microsoft 365 and Office 365 News, Azure news and talk about their experiences with managing the Microsoft Cloud as well as interview industry experts on various cloud technology. They'll cover things such as SharePoint, Exchange, Microsoft Teams, PowerShell, Azure, Azure AD, Security, Networking, Storage, and the many other technologies and products that have made their way into the Microsoft 365 suite and Azure. To stay up-to-date on the latest in Microsoft Cloud news and gain some valuable knowledge as you deploy it within your own organization, make sure to tune in every week! Find out more at msclouditpropodcast.com.

Contact Show