Episode 400 – Microsoft 365 Copilot Declarative Agents and Copilot Studio Agent Builder

April 24, 2025

Episode Transcript

Welcome to Episode 400 of the Microsoft Cloud IT Pro Podcast. In this episode, Ben and Scott explore how IT professionals and developers can leverage Microsoft 365 Copilot’s declarative agents and the Copilot Studio Agent Builder to enhance productivity and streamline workflows within their organizations. Declarative agents allow you to define specific tasks and workflows, enabling Copilot to assist users more effectively. With the Copilot Studio Agent Builder, creating these agents becomes a streamlined process, even for those with minimal coding experience. Listen and learn how to build, deploy, and manage these agents, licensing considerations, and best practices to maximize their impact in your organization.

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,600 --> 00:00:06,399 Welcome to our four hundredth episode of the 2 00:00:06,399 --> 00:00:08,740 Microsoft Cloud IT Pro podcast 3 00:00:09,039 --> 00:00:12,339 recorded live 04/21/2025. 4 00:00:12,559 --> 00:00:14,925 This is a show about Microsoft three sixty 5 00:00:14,925 --> 00:00:17,085 five and Azure from the perspective of IT 6 00:00:17,085 --> 00:00:19,164 pros and end users, where we discuss a 7 00:00:19,164 --> 00:00:21,644 topic or recent news and how it relates 8 00:00:21,644 --> 00:00:22,225 to you. 9 00:00:22,685 --> 00:00:26,144 This week, after eight years and 400 episodes, 10 00:00:26,285 --> 00:00:28,570 Ben and Scott thought about doing something special 11 00:00:28,570 --> 00:00:31,710 to celebrate this four hundredth episode, but instead 12 00:00:31,769 --> 00:00:33,789 just decided to talk more about Copilot. 13 00:00:34,489 --> 00:00:38,009 This time, discussing getting started with declarative agents 14 00:00:38,009 --> 00:00:41,795 in Copilot Studio Agent Builder. They discuss everything 15 00:00:41,795 --> 00:00:44,434 from getting started building agents to how you 16 00:00:44,434 --> 00:00:47,254 might use them to licensing and costs. 17 00:00:47,634 --> 00:00:50,375 Hope you enjoy episode number 400. 18 00:00:52,674 --> 00:00:54,134 How was your weekend, Scott? 19 00:00:54,770 --> 00:00:56,469 My weekend? Oh, it was 20 00:00:56,929 --> 00:00:58,850 a a a quiet stay at home weekend. 21 00:00:58,850 --> 00:01:00,469 I've still got a little bit of my 22 00:01:00,530 --> 00:01:02,929 radio voice here as I get over my 23 00:01:02,929 --> 00:01:05,489 my first spring cold or whatever is going 24 00:01:05,489 --> 00:01:07,250 around. I've been getting over one for, like, 25 00:01:07,250 --> 00:01:09,984 two weeks. So since I don't have my 26 00:01:09,984 --> 00:01:12,625 notes up yet and they do not appear 27 00:01:12,625 --> 00:01:14,465 to want to come up, what are we 28 00:01:14,465 --> 00:01:16,465 gonna talk about today, Scott? What are you 29 00:01:16,465 --> 00:01:18,224 gonna talk about today? Well, I try to 30 00:01:18,224 --> 00:01:19,744 get my notes to load. What am I 31 00:01:19,744 --> 00:01:21,364 gonna talk about today? Sure. Let's 32 00:01:22,060 --> 00:01:24,859 let's have the guy who has no voice 33 00:01:24,859 --> 00:01:26,379 be the one who talks a bunch of 34 00:01:27,500 --> 00:01:29,359 well, today, we are going to 35 00:01:29,739 --> 00:01:30,239 talk 36 00:01:30,540 --> 00:01:31,040 about 37 00:01:33,099 --> 00:01:34,959 no code declarative agents 38 00:01:35,644 --> 00:01:38,704 and Copilot Studio Agent Builder, 39 00:01:39,244 --> 00:01:41,084 if that's not a mouthful for you. But 40 00:01:41,084 --> 00:01:41,584 effectively, 41 00:01:42,204 --> 00:01:44,064 the little Copilot agents 42 00:01:44,444 --> 00:01:47,584 that you can take and build for yourself 43 00:01:47,884 --> 00:01:48,944 inside of Copilot 44 00:01:49,450 --> 00:01:50,670 in a nice little 45 00:01:51,290 --> 00:01:53,549 next next next GUI. Perfect. 46 00:01:54,090 --> 00:01:56,329 Sounds good. And now my notes are coming 47 00:01:56,329 --> 00:01:58,650 back to me. I'm well, in my head. 48 00:01:58,650 --> 00:02:00,890 In my head, I have notes. So this 49 00:02:00,890 --> 00:02:03,034 is something I've started playing with a little 50 00:02:03,034 --> 00:02:05,034 bit. I've actually had clients start asking about 51 00:02:05,034 --> 00:02:06,254 this too. So 52 00:02:06,555 --> 00:02:09,034 this could be an interesting topic because even 53 00:02:09,194 --> 00:02:10,894 I spent a bunch of time even deciphering 54 00:02:10,955 --> 00:02:13,675 licensing around this. Like, even licensing around this 55 00:02:13,675 --> 00:02:16,430 seems goofy to me. So I wanna build 56 00:02:16,430 --> 00:02:18,909 an agent with no code. Where should I 57 00:02:18,909 --> 00:02:21,310 start? Should we start with licensing, or should 58 00:02:21,310 --> 00:02:23,069 we start with just how to start building 59 00:02:23,069 --> 00:02:25,790 it? Why don't we start with how to 60 00:02:25,790 --> 00:02:28,110 start building it, and then we can get 61 00:02:28,110 --> 00:02:28,610 into 62 00:02:29,645 --> 00:02:31,025 a little bit about licensing 63 00:02:31,485 --> 00:02:33,885 and things like that as as we go 64 00:02:33,885 --> 00:02:35,025 along. Sounds 65 00:02:35,485 --> 00:02:35,985 good. 66 00:02:36,284 --> 00:02:38,444 So starting to build it, there's a website. 67 00:02:38,444 --> 00:02:39,885 So there's a couple ways, I guess, you 68 00:02:39,885 --> 00:02:42,305 could start building this, can't you? There is 69 00:02:43,139 --> 00:02:46,340 in Teams now or in Copilot, I guess 70 00:02:46,340 --> 00:02:48,919 it's actually in the Copilot app, you have 71 00:02:49,299 --> 00:02:49,799 agents 72 00:02:50,180 --> 00:02:51,000 in the upper 73 00:02:51,459 --> 00:02:53,860 right hand corner, and it looks like there's 74 00:02:53,860 --> 00:02:56,439 already a few agents in there, potentially, 75 00:02:56,739 --> 00:02:59,115 depending on what you set up, but you 76 00:02:59,115 --> 00:03:00,955 also have a button up there to just 77 00:03:00,955 --> 00:03:03,354 click on build an agent. It turns out 78 00:03:03,354 --> 00:03:05,514 that you've probably been interacting with these in 79 00:03:05,514 --> 00:03:08,074 some way, shape, or form, and you just 80 00:03:08,074 --> 00:03:09,775 might not have noticed. So 81 00:03:10,155 --> 00:03:13,240 there's things like a prompt coach. So you 82 00:03:13,240 --> 00:03:15,240 you wanna get better at writing prompts, you 83 00:03:15,240 --> 00:03:17,000 can go down that path and work with 84 00:03:17,000 --> 00:03:17,500 those. 85 00:03:17,960 --> 00:03:19,900 There's a generic writing coach. 86 00:03:20,360 --> 00:03:22,139 There's all sorts of just 87 00:03:22,520 --> 00:03:23,740 built in agents 88 00:03:24,040 --> 00:03:25,099 that are 89 00:03:25,639 --> 00:03:27,560 ready to ready to go for you should 90 00:03:27,560 --> 00:03:30,014 you want to use them. And then you 91 00:03:30,014 --> 00:03:31,935 can build out your own agents on top 92 00:03:31,935 --> 00:03:35,155 of those and leverage the connectors within 93 00:03:35,694 --> 00:03:36,834 your organization. 94 00:03:37,215 --> 00:03:37,715 So 95 00:03:38,254 --> 00:03:39,794 why would you want to 96 00:03:40,175 --> 00:03:42,574 build your own agent? Well, like, there there's 97 00:03:42,574 --> 00:03:44,094 a whole bunch of things that you can 98 00:03:44,094 --> 00:03:44,550 do 99 00:03:45,030 --> 00:03:47,990 within even, like, our world and and our 100 00:03:47,990 --> 00:03:49,909 roles and and the things that happen. So 101 00:03:49,909 --> 00:03:51,610 for you, I could think about maybe, 102 00:03:52,069 --> 00:03:54,330 hey. I would like to build the 103 00:03:55,030 --> 00:03:58,330 the the the project knowledge bot for IntelliJunk, 104 00:03:58,775 --> 00:04:00,875 and you wanna point it at maybe your 105 00:04:01,335 --> 00:04:01,835 document 106 00:04:02,135 --> 00:04:02,635 repository 107 00:04:03,015 --> 00:04:05,915 for where you've done things like your SAUs 108 00:04:06,375 --> 00:04:08,855 or you have artifacts from deliveries, things like 109 00:04:08,855 --> 00:04:11,254 that. Like, teach me about past things and 110 00:04:11,254 --> 00:04:13,269 help me make this next one better. You 111 00:04:13,269 --> 00:04:15,689 could also build probably a pretty good, like, 112 00:04:15,830 --> 00:04:18,169 SAU bot, like a statement of work agent 113 00:04:18,389 --> 00:04:20,550 based on statements work and things like that 114 00:04:20,550 --> 00:04:23,029 that are out there. I've been taking these 115 00:04:23,029 --> 00:04:24,089 and building these. 116 00:04:24,470 --> 00:04:27,610 So part of my role involves working with 117 00:04:27,834 --> 00:04:29,454 products that are released on GitHub, 118 00:04:29,914 --> 00:04:31,995 and all the code lives on GitHub, the 119 00:04:31,995 --> 00:04:35,034 releases, the wikis for these things. So I've 120 00:04:35,034 --> 00:04:37,354 been using them within my organization where the 121 00:04:37,354 --> 00:04:39,995 GitHub connector is turned on to point directly 122 00:04:39,995 --> 00:04:40,735 at Git repos 123 00:04:41,115 --> 00:04:42,574 and get insights on 124 00:04:43,220 --> 00:04:44,360 not only the 125 00:04:44,740 --> 00:04:47,060 the repos themselves, but also the the code 126 00:04:47,060 --> 00:04:48,199 within those repos. 127 00:04:48,579 --> 00:04:50,500 So I'll give you an example. We have 128 00:04:50,500 --> 00:04:51,000 a 129 00:04:51,379 --> 00:04:54,259 product that gets distributed to customers. It gets 130 00:04:54,259 --> 00:04:56,899 compiled and and pushed out. That product has 131 00:04:56,899 --> 00:04:57,959 a bunch of 132 00:04:58,745 --> 00:05:01,625 hidden flags inside of it. And those hidden 133 00:05:01,625 --> 00:05:03,305 flags are they're they're sitting there in the 134 00:05:03,305 --> 00:05:04,264 code if you know where they are, but 135 00:05:04,264 --> 00:05:06,425 I don't always remember, like, which file to 136 00:05:06,425 --> 00:05:08,105 go into at which time to look up 137 00:05:08,105 --> 00:05:08,845 which code. 138 00:05:09,225 --> 00:05:09,725 So 139 00:05:10,504 --> 00:05:13,949 enter my little my little product helper agent 140 00:05:14,029 --> 00:05:16,350 that can tell me those things. And then 141 00:05:16,350 --> 00:05:18,930 it can also maybe be augmented with documentation 142 00:05:19,230 --> 00:05:21,250 from internal wikis, SharePoint, 143 00:05:21,949 --> 00:05:23,650 things like that as well. So 144 00:05:24,590 --> 00:05:27,410 these become powerful little helpers 145 00:05:28,125 --> 00:05:30,845 against your knowledge bases. So you can effectively 146 00:05:30,845 --> 00:05:33,404 think about it as a or the way 147 00:05:33,404 --> 00:05:35,805 I think about it is a very quick 148 00:05:35,805 --> 00:05:36,305 onboarding, 149 00:05:36,764 --> 00:05:37,745 no code flow 150 00:05:38,365 --> 00:05:40,305 to be able to 151 00:05:41,165 --> 00:05:41,665 leverage 152 00:05:42,240 --> 00:05:44,100 RAG, retrieval augmented generation. 153 00:05:44,560 --> 00:05:47,519 So RAG with my own documentation, my own 154 00:05:47,519 --> 00:05:50,399 code basis, things like that, to ground these 155 00:05:50,399 --> 00:05:50,899 models 156 00:05:51,199 --> 00:05:54,399 and further refine the responses before they spit 157 00:05:54,399 --> 00:05:55,935 some stuff back over the fence to me. 158 00:05:55,935 --> 00:05:57,615 Me. Yeah. And I think even the part 159 00:05:57,615 --> 00:05:59,454 you brought up there about, like, looking at 160 00:05:59,454 --> 00:06:00,595 GitHub is 161 00:06:01,454 --> 00:06:02,995 it's also a way to 162 00:06:03,375 --> 00:06:04,995 bring in some of that additional 163 00:06:06,014 --> 00:06:06,514 context 164 00:06:07,055 --> 00:06:07,555 or 165 00:06:08,495 --> 00:06:10,915 refine these Copilot agents or build these agents 166 00:06:11,134 --> 00:06:13,399 to look at other data sources. Like, as 167 00:06:13,399 --> 00:06:15,800 you go into these Copilot agents, it's not 168 00:06:15,800 --> 00:06:18,699 just I wanna go look at this specific 169 00:06:19,080 --> 00:06:20,939 SharePoint site or 170 00:06:21,480 --> 00:06:22,379 look at 171 00:06:22,759 --> 00:06:23,500 this specific, 172 00:06:23,879 --> 00:06:26,120 I guess, context for the Microsoft three sixty 173 00:06:26,120 --> 00:06:28,535 five. It's go pull in data from 174 00:06:28,995 --> 00:06:30,615 GitHub. Let's go look 175 00:06:30,995 --> 00:06:33,555 at Confluence wikis. Let's go look at Trello 176 00:06:33,555 --> 00:06:35,495 boards. Let's go look at a SQL database. 177 00:06:35,954 --> 00:06:38,914 There's lots of other date or this allows 178 00:06:38,914 --> 00:06:41,850 you to build these agents that are not 179 00:06:41,850 --> 00:06:44,250 only just specific, but also pull in data 180 00:06:44,250 --> 00:06:46,110 from a lot of other data sources 181 00:06:46,410 --> 00:06:46,910 to, 182 00:06:47,449 --> 00:06:49,709 help with these Copilot responses, these 183 00:06:50,009 --> 00:06:50,509 conversations 184 00:06:50,889 --> 00:06:51,949 you have with Copilot. 185 00:06:52,329 --> 00:06:52,829 Yes. 186 00:06:53,129 --> 00:06:53,629 So 187 00:06:54,089 --> 00:06:55,930 I I I think, like, there there's a 188 00:06:55,930 --> 00:06:56,750 world where 189 00:06:57,194 --> 00:06:58,875 some of this stuff can get more complicated, 190 00:06:58,875 --> 00:07:00,894 and you can go down a path of 191 00:07:01,274 --> 00:07:01,774 needing 192 00:07:03,034 --> 00:07:04,654 to actually build an agent 193 00:07:05,274 --> 00:07:07,034 and do some code around it. And then 194 00:07:07,034 --> 00:07:07,935 there is the 195 00:07:08,634 --> 00:07:10,414 Copilot agent studio 196 00:07:10,954 --> 00:07:12,254 experience, which is 197 00:07:12,699 --> 00:07:15,819 zero code, super easy to onboard. So you're 198 00:07:15,819 --> 00:07:17,680 kinda getting out of the world of those 199 00:07:18,300 --> 00:07:18,959 more traditional 200 00:07:19,500 --> 00:07:20,399 language bots 201 00:07:20,939 --> 00:07:23,979 that are gonna require some measure of I 202 00:07:23,979 --> 00:07:25,819 don't wanna say, like, extensive coding, but they're 203 00:07:25,819 --> 00:07:27,360 gonna require some knowledge 204 00:07:27,664 --> 00:07:29,745 and things to get in there versus these 205 00:07:29,745 --> 00:07:31,044 things, which are 206 00:07:32,064 --> 00:07:34,144 declarative. Like, you just go in and and 207 00:07:34,144 --> 00:07:35,845 and declare what you want 208 00:07:36,224 --> 00:07:39,264 via the Copilot agent studio, and then it 209 00:07:39,264 --> 00:07:39,764 effectively 210 00:07:40,224 --> 00:07:42,919 ends up in this what you define is 211 00:07:42,919 --> 00:07:45,019 what you get kind kind of 212 00:07:45,319 --> 00:07:47,560 bot that that's out there. The other cool 213 00:07:47,560 --> 00:07:48,779 thing is because 214 00:07:49,240 --> 00:07:51,000 it's all built on top of m three 215 00:07:51,000 --> 00:07:52,060 sixty five Copilot, 216 00:07:52,519 --> 00:07:54,519 if you think about things that you might 217 00:07:54,519 --> 00:07:55,019 want 218 00:07:55,454 --> 00:07:55,954 in 219 00:07:56,495 --> 00:07:57,214 a workflow 220 00:07:58,095 --> 00:07:59,694 so let's take, like, kinda like one of 221 00:07:59,694 --> 00:08:02,254 the easier examples. So employee onboarding. So when 222 00:08:02,254 --> 00:08:04,915 I do a new hire for an employee, 223 00:08:05,214 --> 00:08:07,854 there's typically a slew of documents that employees 224 00:08:07,854 --> 00:08:09,900 need to sign when they come in, like 225 00:08:09,900 --> 00:08:11,819 get this going, get this going, get this 226 00:08:11,819 --> 00:08:13,040 going kinds of things. 227 00:08:13,340 --> 00:08:16,379 There's probably also, like, security groups they need 228 00:08:16,379 --> 00:08:18,560 to sign up for. There might be 229 00:08:18,939 --> 00:08:20,779 meeting series that they need to be a 230 00:08:20,779 --> 00:08:23,115 part of, like an all hands, things like 231 00:08:23,115 --> 00:08:25,355 that. So you could build an agent that 232 00:08:25,355 --> 00:08:27,535 has those assets inside of it, 233 00:08:27,915 --> 00:08:30,654 like, point it to your HR onboarding documents, 234 00:08:31,274 --> 00:08:33,434 have a baked prompt in there, a system 235 00:08:33,434 --> 00:08:35,754 prompt that you've already worked on, and and 236 00:08:35,754 --> 00:08:37,759 you've kind of gotten to where it needs 237 00:08:37,759 --> 00:08:40,159 to be. And you could do that across 238 00:08:40,159 --> 00:08:41,839 a series of system prompts that are baked 239 00:08:41,839 --> 00:08:44,559 into that agent and augmented with the data 240 00:08:44,559 --> 00:08:46,720 that you need for your onboarding process, and 241 00:08:46,720 --> 00:08:49,519 you could just make that employee onboarding super 242 00:08:49,519 --> 00:08:50,980 easy to do right there. 243 00:08:51,304 --> 00:08:52,904 And then if there's even things that you 244 00:08:52,904 --> 00:08:54,284 wanna do outside 245 00:08:54,745 --> 00:08:55,565 of just 246 00:08:56,024 --> 00:08:59,865 retrieval augmented generation, like, with documents that are 247 00:08:59,865 --> 00:09:02,424 sitting, like, in SharePoint or, like, my example 248 00:09:02,424 --> 00:09:04,679 would, like, GitHub, things like that, Because this 249 00:09:04,679 --> 00:09:06,919 is m three sixty five Copilot, and it's 250 00:09:06,919 --> 00:09:09,240 connected to the rest of your data sources, 251 00:09:09,240 --> 00:09:09,740 like, 252 00:09:10,120 --> 00:09:12,620 if if I'm chatting with that agent, that's 253 00:09:12,919 --> 00:09:14,860 my team's chats, that's 254 00:09:15,240 --> 00:09:17,924 my mail sitting in my mailbox kinda thing. 255 00:09:17,924 --> 00:09:19,924 You can also bake those system prompts so 256 00:09:19,924 --> 00:09:22,245 that they further go out and spider and 257 00:09:22,245 --> 00:09:25,764 get information from those sources as well. So 258 00:09:25,764 --> 00:09:28,404 not just go get the HR doc, but 259 00:09:28,485 --> 00:09:30,804 or go get the blah blah blah project 260 00:09:30,804 --> 00:09:32,559 start doc, but maybe go back through my 261 00:09:32,559 --> 00:09:34,240 mail and look at the last five projects 262 00:09:34,240 --> 00:09:36,419 I did and help me write up my, 263 00:09:37,120 --> 00:09:39,759 introduction for this one kinda thing. Absolutely. And 264 00:09:39,759 --> 00:09:41,860 as you're going to build these, like, there's 265 00:09:42,080 --> 00:09:43,759 a few different steps once you go in 266 00:09:43,759 --> 00:09:46,485 here to build these agents. So we've kinda 267 00:09:46,485 --> 00:09:48,324 talked about, like, what you can do with 268 00:09:48,324 --> 00:09:50,884 them. I think the fascinating part is when 269 00:09:50,884 --> 00:09:52,964 you go in to build these agents, like, 270 00:09:52,964 --> 00:09:54,804 you click on that. Like you said, you 271 00:09:54,804 --> 00:09:57,924 go to the the agent builder, and the 272 00:09:57,924 --> 00:09:59,944 first thing you do is you actually use 273 00:10:00,080 --> 00:10:02,240 Copilot to try to build the agent. Like, 274 00:10:02,240 --> 00:10:03,539 it'll ask you, 275 00:10:03,840 --> 00:10:05,360 what do you wanna do with this agent? 276 00:10:05,360 --> 00:10:07,379 What are you trying to accomplish with this? 277 00:10:07,440 --> 00:10:09,840 And you can just type in what you 278 00:10:09,840 --> 00:10:12,399 wanna build to get started building these agents. 279 00:10:12,399 --> 00:10:15,200 So you'll actually see the system agents in 280 00:10:15,200 --> 00:10:17,774 there, So, like, that prompt coach, things like 281 00:10:17,774 --> 00:10:19,214 that. So you can get a sense not 282 00:10:19,214 --> 00:10:21,294 for, like, how those are built if you're 283 00:10:21,294 --> 00:10:23,554 looking for a little bit of information there. 284 00:10:23,695 --> 00:10:25,294 The the docs are pretty good here as 285 00:10:25,294 --> 00:10:28,014 well about kinda giving grounding and and what 286 00:10:28,014 --> 00:10:30,575 each of the options are that are available 287 00:10:30,575 --> 00:10:32,419 to you. But it is kind of just 288 00:10:32,419 --> 00:10:34,679 as easy, like, licensing aside. 289 00:10:35,379 --> 00:10:37,139 Once you've got the ability to create these 290 00:10:37,139 --> 00:10:39,860 things, it's literally just go to Copilot, and 291 00:10:39,860 --> 00:10:42,980 that could be Copilot the app, the m 292 00:10:42,980 --> 00:10:44,980 m three sixty five Copilot, whatever the business 293 00:10:44,980 --> 00:10:46,674 one is. Like, it's pinned to your desktop 294 00:10:46,735 --> 00:10:48,034 automatically in most cases, 295 00:10:48,495 --> 00:10:50,014 you've got that one, or you can just 296 00:10:50,014 --> 00:10:51,875 go to office.com/shop. 297 00:10:52,174 --> 00:10:52,674 And 298 00:10:53,455 --> 00:10:54,735 right up there in the upper right, like 299 00:10:54,735 --> 00:10:56,894 you said, you've got your list of kinda 300 00:10:56,894 --> 00:10:58,910 system agents, and then you can just go 301 00:10:58,910 --> 00:11:01,950 ahead and build a new agent right on 302 00:11:01,950 --> 00:11:03,230 top of that. So you just go ahead 303 00:11:03,230 --> 00:11:07,009 and click create agent, and then you're kinda 304 00:11:07,070 --> 00:11:08,129 off to the races 305 00:11:08,669 --> 00:11:10,910 from there. So it it's it's meant to 306 00:11:10,910 --> 00:11:11,410 be 307 00:11:11,845 --> 00:11:12,345 super 308 00:11:12,804 --> 00:11:15,445 quick. Like so so that agent builder is 309 00:11:15,445 --> 00:11:17,044 there to kinda show you the template, show 310 00:11:17,044 --> 00:11:18,884 you what can be done, get you through 311 00:11:18,884 --> 00:11:20,184 that creation process 312 00:11:20,884 --> 00:11:21,705 pretty quickly, 313 00:11:22,164 --> 00:11:25,285 and then get you to publish and then 314 00:11:25,285 --> 00:11:27,610 maybe come back and and make updates and 315 00:11:27,610 --> 00:11:29,370 refine and things like that as you go. 316 00:11:29,370 --> 00:11:31,690 Yeah. And those different things. So once you 317 00:11:31,690 --> 00:11:33,450 do that, you get your agent built or 318 00:11:33,450 --> 00:11:35,209 as a process of building it, if you 319 00:11:35,209 --> 00:11:36,589 wanna add different things, 320 00:11:36,889 --> 00:11:38,570 it is. It's going in, giving it a 321 00:11:38,570 --> 00:11:40,485 name. Like you said, this could be the 322 00:11:40,485 --> 00:11:42,904 internal knowledge base. This could be 323 00:11:43,284 --> 00:11:44,264 employee onboarding, 324 00:11:44,725 --> 00:11:46,964 give it a quick description, and then you 325 00:11:46,964 --> 00:11:48,424 can give instructions 326 00:11:48,884 --> 00:11:50,964 for your agent too. So this is, like 327 00:11:50,964 --> 00:11:52,644 you said, how you direct the behavior of 328 00:11:52,644 --> 00:11:55,500 this agent, different tasks, how it's supposed to 329 00:11:55,500 --> 00:11:56,879 complete different tasks, 330 00:11:57,579 --> 00:11:59,759 but all those prompts around 331 00:12:00,379 --> 00:12:01,519 how it builds agents, 332 00:12:01,980 --> 00:12:04,539 and then it gets into that other thing 333 00:12:04,539 --> 00:12:05,600 we said, the knowledge. 334 00:12:05,980 --> 00:12:07,980 Where is this agent gonna start looking for 335 00:12:07,980 --> 00:12:09,679 stuff? Is it gonna look in 336 00:12:10,095 --> 00:12:13,054 SharePoint? Is it gonna look at a public 337 00:12:13,054 --> 00:12:14,654 website? Is it gonna look at a SQL 338 00:12:14,654 --> 00:12:15,154 database? 339 00:12:15,695 --> 00:12:17,794 Adding all those different sources 340 00:12:18,414 --> 00:12:19,475 into your agent, 341 00:12:20,174 --> 00:12:22,495 and then even some starter prompts. So you 342 00:12:22,495 --> 00:12:24,654 can go in and add some number of 343 00:12:24,654 --> 00:12:26,209 starter prompts for your 344 00:12:26,589 --> 00:12:28,049 different users so that 345 00:12:28,589 --> 00:12:30,269 you can help them get started with the 346 00:12:30,269 --> 00:12:32,189 agent, help them figure it out. But it 347 00:12:32,189 --> 00:12:33,649 really is. It's just that GUI 348 00:12:34,029 --> 00:12:35,169 work through the 349 00:12:35,549 --> 00:12:36,049 different 350 00:12:36,509 --> 00:12:38,829 the different steps in it to really refine 351 00:12:38,829 --> 00:12:40,049 that knowledge, instructions, 352 00:12:40,975 --> 00:12:43,695 even capabilities. Is it gonna have a code 353 00:12:43,695 --> 00:12:45,774 interpreter, image generator as a part of it, 354 00:12:45,774 --> 00:12:47,455 and then what those starter prompts are? And 355 00:12:47,455 --> 00:12:49,455 then you just hit publish, and it'll be 356 00:12:49,455 --> 00:12:51,534 there to start using, and then you can 357 00:12:51,534 --> 00:12:53,855 go in and tweak it, refine it, configure 358 00:12:53,855 --> 00:12:55,475 it as you go. Some of that stuff's 359 00:12:55,534 --> 00:12:56,034 relatively 360 00:12:57,110 --> 00:12:58,970 new or it kinda, like, 361 00:12:59,750 --> 00:13:02,149 evergreen SaaS product. Right? It's always changing underneath 362 00:13:02,149 --> 00:13:04,970 you kinda thing. So some of those connectors 363 00:13:05,110 --> 00:13:06,709 that are available like, I noticed, like, in 364 00:13:06,709 --> 00:13:07,449 my organization, 365 00:13:08,149 --> 00:13:10,125 like, on day one, the number of 366 00:13:10,845 --> 00:13:11,664 pre enabled 367 00:13:12,284 --> 00:13:13,664 Microsoft Graph connectors 368 00:13:14,205 --> 00:13:15,424 was pretty 369 00:13:15,884 --> 00:13:17,745 low, like, low to nonexistence. 370 00:13:18,445 --> 00:13:20,764 And now there's a whole bunch of them 371 00:13:20,764 --> 00:13:23,585 in there, things like connecting to ADO, connecting 372 00:13:23,725 --> 00:13:24,225 to 373 00:13:24,940 --> 00:13:27,980 the ServiceNow, connecting to SAP. Like, there's a 374 00:13:27,980 --> 00:13:29,820 whole bunch of them that have just been 375 00:13:29,820 --> 00:13:31,180 added in there, and then some of those 376 00:13:31,180 --> 00:13:32,800 capabilities you talked about. So 377 00:13:33,180 --> 00:13:35,680 code interpreter is an interesting one. 378 00:13:36,139 --> 00:13:36,889 It uses 379 00:13:37,554 --> 00:13:38,054 Python 380 00:13:39,315 --> 00:13:40,215 in the background 381 00:13:41,315 --> 00:13:44,535 to analyze data that's being input by users. 382 00:13:44,835 --> 00:13:46,434 So maybe if you're, like, trying to build 383 00:13:46,434 --> 00:13:48,835 an agent where you're trying to have the 384 00:13:48,835 --> 00:13:50,995 agent help you solve a math problem, things 385 00:13:50,995 --> 00:13:53,529 like that, That's where the the code interpreter 386 00:13:53,590 --> 00:13:56,090 comes into play. And then the image generator, 387 00:13:56,309 --> 00:13:58,789 just image generation one zero one, and I 388 00:13:58,789 --> 00:14:01,190 think the things that folks are probably used 389 00:14:01,190 --> 00:14:03,529 to from from seeing most of these systems. 390 00:14:03,884 --> 00:14:04,845 You do have to keep in the back 391 00:14:04,845 --> 00:14:06,205 of your head that this is all built 392 00:14:06,205 --> 00:14:08,065 on m three sixty five Copilot, 393 00:14:08,605 --> 00:14:12,205 so it's going to kinda behave like m 394 00:14:12,205 --> 00:14:13,424 three sixty five Copilot. 395 00:14:13,884 --> 00:14:15,165 And the reason I call that out is, 396 00:14:15,165 --> 00:14:17,129 like, image generation and, like, 397 00:14:17,610 --> 00:14:18,669 just chat GPT 398 00:14:18,970 --> 00:14:20,570 versus, I don't know, maybe going out and 399 00:14:20,570 --> 00:14:23,230 using, like, stable diffusion OSS versus 400 00:14:23,690 --> 00:14:26,750 mid journey versus Copilot are all very different. 401 00:14:26,970 --> 00:14:28,970 And they all have their kinda baked in 402 00:14:28,970 --> 00:14:30,809 system prompts along the way and and their 403 00:14:30,809 --> 00:14:33,164 own flavors, so you can't override some of 404 00:14:33,164 --> 00:14:35,565 that stuff. Like, I don't know, maybe there's, 405 00:14:35,565 --> 00:14:37,565 like, a prompt injection thing or something. But 406 00:14:37,565 --> 00:14:39,725 for the most part, like, yeah, I'm I'm 407 00:14:39,725 --> 00:14:41,245 not hacking away at these things like that. 408 00:14:41,245 --> 00:14:43,245 So you can't override them. Right? You kinda 409 00:14:43,245 --> 00:14:44,225 live with the outputs 410 00:14:44,684 --> 00:14:46,845 in some cases that those systems give you. 411 00:14:46,845 --> 00:14:49,879 Yeah. And I noticed even with setting up 412 00:14:49,879 --> 00:14:51,879 these connectors to your point of different ones 413 00:14:51,879 --> 00:14:55,080 showing up, even setting them up, I was 414 00:14:55,080 --> 00:14:57,639 working through some of the documentation the other 415 00:14:57,639 --> 00:15:00,360 day, and they're even set up a little 416 00:15:01,024 --> 00:15:02,945 it's interesting how you set them up. Well, 417 00:15:02,945 --> 00:15:03,764 how about that? 418 00:15:04,625 --> 00:15:07,585 It's not necessarily straightforward as I thought. Like, 419 00:15:07,585 --> 00:15:09,904 I can go into mine right now when 420 00:15:09,904 --> 00:15:10,644 I see 421 00:15:11,105 --> 00:15:13,024 just one of those knowledge sources. And I 422 00:15:13,024 --> 00:15:14,465 was going in and trying to figure out 423 00:15:14,465 --> 00:15:16,309 how to add more, and you can, like, 424 00:15:16,309 --> 00:15:18,730 click to add more knowledge sources and you 425 00:15:18,789 --> 00:15:20,629 see them there, but you can't really add 426 00:15:20,629 --> 00:15:22,149 them. It's like you have to go connect 427 00:15:22,149 --> 00:15:24,389 to them first. And you actually have to 428 00:15:24,389 --> 00:15:27,110 go into, like, your Microsoft three sixty five 429 00:15:27,110 --> 00:15:29,690 admin and go into the search settings 430 00:15:30,774 --> 00:15:33,495 in Microsoft three sixty five admin and go 431 00:15:33,495 --> 00:15:35,274 configure these additional 432 00:15:35,815 --> 00:15:36,315 sources 433 00:15:36,695 --> 00:15:39,995 in your Microsoft three sixty five search setting, 434 00:15:40,215 --> 00:15:42,075 and that's where you set up these connectors 435 00:15:42,295 --> 00:15:44,795 that can then be used in Copilot Studio 436 00:15:45,269 --> 00:15:46,730 to add those additional 437 00:15:47,190 --> 00:15:49,750 or that additional context, those additional knowledge sources 438 00:15:49,750 --> 00:15:52,310 to Copilot Studio. So there is a little 439 00:15:52,310 --> 00:15:54,149 bit of that. I mean, that's how it 440 00:15:54,149 --> 00:15:55,830 works under the covers. Right? Like, if you're 441 00:15:55,830 --> 00:15:58,889 gonna exclude something from Copilot using sensitivity labels, 442 00:15:59,105 --> 00:16:01,504 you also exclude it from Microsoft Search. End 443 00:16:01,504 --> 00:16:04,225 of the day, from all this different knowledge 444 00:16:04,225 --> 00:16:06,725 that gets pulled into Copilot, it's very heavily 445 00:16:06,785 --> 00:16:09,504 using the Microsoft three sixty five search under 446 00:16:09,504 --> 00:16:12,465 the covers for everything from connectors to pulling 447 00:16:12,465 --> 00:16:15,000 your Microsoft three sixty five data. Yes. Search 448 00:16:15,000 --> 00:16:17,639 plus. So so it depends. Sometimes it's using 449 00:16:17,639 --> 00:16:18,139 the 450 00:16:18,759 --> 00:16:21,639 existing indices that are already there. Like like, 451 00:16:21,639 --> 00:16:23,559 hey. They're all ready to go. In the 452 00:16:23,559 --> 00:16:24,300 other cases, 453 00:16:24,759 --> 00:16:25,259 it's 454 00:16:25,800 --> 00:16:28,059 let's take, like, a graph connector, for example. 455 00:16:28,424 --> 00:16:30,845 So you go and configure a graph connector 456 00:16:31,065 --> 00:16:31,565 for 457 00:16:32,184 --> 00:16:34,985 for a ADO kinda thing. Part of that 458 00:16:34,985 --> 00:16:37,465 experience of turning that on is actually not 459 00:16:37,465 --> 00:16:40,024 only lighting up the connector, but, like you 460 00:16:40,024 --> 00:16:41,945 said, lighting it up to search, and then 461 00:16:41,945 --> 00:16:44,120 not only lighting it up to search, like, 462 00:16:44,120 --> 00:16:45,720 just from the top level of saying, like, 463 00:16:45,720 --> 00:16:47,879 oh, it's enabled within m three sixty five 464 00:16:47,879 --> 00:16:50,600 search. It's also going so far as to 465 00:16:50,600 --> 00:16:52,059 do things like 466 00:16:52,759 --> 00:16:55,339 enabling your connectors for inline results. 467 00:16:55,639 --> 00:16:57,174 So you're gonna go through, like, your search 468 00:16:57,174 --> 00:16:59,754 verticals and make sure that they're enabled 469 00:17:00,375 --> 00:17:01,975 up up where they need to be that 470 00:17:01,975 --> 00:17:04,535 way. So, like, it is, like, embedded in 471 00:17:04,535 --> 00:17:05,815 there. So I think you do have to 472 00:17:05,815 --> 00:17:07,654 think about it a little holistically if, like, 473 00:17:07,654 --> 00:17:09,450 before you turn this stuff on. Like, you're 474 00:17:09,450 --> 00:17:11,149 not just to your point exposing it to, 475 00:17:12,730 --> 00:17:15,470 Copilot. You're exposing it to search, 476 00:17:15,769 --> 00:17:18,009 and you're kinda built in search experience. But 477 00:17:18,009 --> 00:17:21,369 then it's still security trimmed, all that kind 478 00:17:21,369 --> 00:17:21,674 of 479 00:17:23,674 --> 00:17:24,174 stuff 480 00:17:25,355 --> 00:17:27,914 around me. Do you feel overwhelmed by trying 481 00:17:27,914 --> 00:17:30,174 to manage your Office three sixty five environment? 482 00:17:30,315 --> 00:17:33,035 Are you facing unexpected issues that disrupt your 483 00:17:33,035 --> 00:17:35,835 company's productivity? Intelligink is here to help. Much 484 00:17:35,835 --> 00:17:37,380 like you take your car to the mechanic 485 00:17:37,380 --> 00:17:39,779 that has specialized knowledge on how to best 486 00:17:39,779 --> 00:17:42,420 keep your car running, Intelligink helps you with 487 00:17:42,420 --> 00:17:45,480 your Microsoft cloud environment because that's their expertise. 488 00:17:45,859 --> 00:17:48,180 Intelligink keeps up with the latest updates in 489 00:17:48,180 --> 00:17:50,339 the Microsoft cloud to help keep your business 490 00:17:50,339 --> 00:17:52,644 running smoothly and ahead of the curve. Whether 491 00:17:52,644 --> 00:17:54,644 you are a small organization with just a 492 00:17:54,644 --> 00:17:57,045 few users up to an organization of several 493 00:17:57,045 --> 00:17:58,105 thousand employees, 494 00:17:58,404 --> 00:18:00,404 they want to partner with you to implement 495 00:18:00,404 --> 00:18:03,065 and administer your Microsoft Cloud technology. 496 00:18:03,845 --> 00:18:07,460 Visit them at inteligync.com/podcast. 497 00:18:07,680 --> 00:18:14,420 That's intelligink.com/podcast 498 00:18:14,799 --> 00:18:16,880 for more information or to schedule a thirty 499 00:18:16,880 --> 00:18:18,980 minute call to get started with them today. 500 00:18:19,279 --> 00:18:20,420 Remember, Intelligink 501 00:18:20,744 --> 00:18:23,065 focuses on the Microsoft cloud so you can 502 00:18:23,065 --> 00:18:24,365 focus on your business. 503 00:18:26,505 --> 00:18:28,025 I would say the other interesting thing I 504 00:18:28,025 --> 00:18:29,224 was talking to a client about this the 505 00:18:29,224 --> 00:18:30,664 other day, and they got all excited when 506 00:18:30,664 --> 00:18:33,359 I mentioned public websites as a data source. 507 00:18:33,440 --> 00:18:35,519 This is not just any public website. I 508 00:18:35,519 --> 00:18:38,579 cannot go point this to, like, learn.microsoft.com 509 00:18:38,640 --> 00:18:40,640 and have that be a knowledge source source 510 00:18:40,640 --> 00:18:42,579 for my bot. Like, you have to confirm 511 00:18:42,720 --> 00:18:45,700 this is a website you own, DNS records, 512 00:18:46,204 --> 00:18:48,444 all that good stuff with public websites. That 513 00:18:48,444 --> 00:18:50,444 was a funny example for me because I 514 00:18:50,444 --> 00:18:53,345 can build declarative agents. You can burn learn. 515 00:18:53,404 --> 00:18:54,384 Okay. Yeah. 516 00:18:55,404 --> 00:18:57,005 Look at me. I'm special. I can use 517 00:18:57,005 --> 00:18:57,904 learn.Microsoft 518 00:18:57,964 --> 00:18:59,839 for my agents. Yeah. There we go. 519 00:19:00,140 --> 00:19:02,000 No. I'm not coming up with another example. 520 00:19:02,059 --> 00:19:04,299 But I also know that because I've I've 521 00:19:04,299 --> 00:19:06,380 played with this even with search, like, pointing 522 00:19:06,380 --> 00:19:08,140 the Microsoft three sixty five search to my 523 00:19:08,140 --> 00:19:11,414 own website is there's also limits on search 524 00:19:11,414 --> 00:19:12,855 and how much you can crawl with search 525 00:19:12,855 --> 00:19:14,934 before you have to start paying. So we 526 00:19:14,934 --> 00:19:17,894 haven't talked about licensing Copilot Studio yet, but 527 00:19:17,894 --> 00:19:19,815 I think depending on these agents and how 528 00:19:19,815 --> 00:19:22,154 they interact with search, there could potentially 529 00:19:22,455 --> 00:19:23,515 be some additional 530 00:19:24,375 --> 00:19:25,195 cost considerations 531 00:19:25,495 --> 00:19:26,609 there because 532 00:19:27,230 --> 00:19:29,710 you start running into limits on what search 533 00:19:29,710 --> 00:19:30,529 can actually 534 00:19:30,829 --> 00:19:31,329 go 535 00:19:31,710 --> 00:19:34,750 pull access based on licensing, etcetera, from things 536 00:19:34,750 --> 00:19:37,490 like public websites. So it does start to 537 00:19:37,789 --> 00:19:39,869 kinda run away a little bit, like, once 538 00:19:39,869 --> 00:19:41,889 you start to light up all the 539 00:19:42,485 --> 00:19:44,244 all all all the little options that are 540 00:19:44,244 --> 00:19:46,025 available for you. So 541 00:19:46,325 --> 00:19:47,144 graph connectors, 542 00:19:47,845 --> 00:19:50,485 they do require a license or some kind 543 00:19:50,485 --> 00:19:51,384 of meter usage. 544 00:19:52,325 --> 00:19:54,965 SharePoint, obvious, you gotta have a license to 545 00:19:54,965 --> 00:19:56,985 SharePoint, OneDrive, things like that. 546 00:19:57,390 --> 00:19:59,549 Web search, funny enough, does not require a 547 00:19:59,549 --> 00:20:00,049 license, 548 00:20:00,589 --> 00:20:02,529 but scoped web search does. 549 00:20:02,910 --> 00:20:05,549 So you gotta kinda think through maybe a 550 00:20:05,549 --> 00:20:07,789 little bit of nuance there. And then there's 551 00:20:07,789 --> 00:20:11,150 some things that are outside the agent builder, 552 00:20:11,150 --> 00:20:12,690 but they're available through 553 00:20:13,285 --> 00:20:16,244 Teams and and building declarative agents in Teams. 554 00:20:16,244 --> 00:20:19,285 So things like a Dataverse connector for your 555 00:20:19,285 --> 00:20:20,744 dynamic CRM data, 556 00:20:21,045 --> 00:20:24,085 email people, Teams messages. That that stuff's all 557 00:20:24,085 --> 00:20:25,305 part of the Teams toolkit, 558 00:20:25,684 --> 00:20:28,710 and then that all requires licensing as well. 559 00:20:28,789 --> 00:20:29,289 So 560 00:20:29,669 --> 00:20:31,190 it it it can be, it can be 561 00:20:31,190 --> 00:20:32,470 a thing. So why why don't we talk 562 00:20:32,470 --> 00:20:33,369 through some of 563 00:20:33,829 --> 00:20:34,490 the other 564 00:20:34,869 --> 00:20:37,929 licensing constraints here? Because you mentioned Copilot Studio, 565 00:20:38,470 --> 00:20:40,230 and there there is some stuff to do 566 00:20:40,230 --> 00:20:42,710 there. It's interesting how they license it. And 567 00:20:42,710 --> 00:20:44,644 I don't know that I would say the 568 00:20:44,644 --> 00:20:47,525 documentation is clear. Imagine that. Right? Yeah. I'm 569 00:20:47,525 --> 00:20:51,065 shocked. Yeah. So there's three different ways 570 00:20:51,924 --> 00:20:54,825 based on all the reading through the documentation 571 00:20:54,964 --> 00:20:56,980 and looking at this that I did that 572 00:20:56,980 --> 00:20:59,460 you can license Copilot Studio to go build 573 00:20:59,460 --> 00:21:01,940 these agents. And it's not it's not actually 574 00:21:01,940 --> 00:21:04,339 like you're licensing Copilot Studio. It's more like 575 00:21:04,339 --> 00:21:07,779 you're licensing the interaction of your users with 576 00:21:07,779 --> 00:21:10,279 these agents, but it falls under this Copilot 577 00:21:10,419 --> 00:21:11,559 Studio license 578 00:21:12,099 --> 00:21:14,795 umbrella. So first, you have your pay as 579 00:21:14,795 --> 00:21:16,875 you go option. So I wanna go build 580 00:21:16,875 --> 00:21:18,795 an agent. I want my users to be 581 00:21:18,795 --> 00:21:20,955 able to use it, but I just want 582 00:21:20,955 --> 00:21:23,195 to pay when they use it. And this 583 00:21:23,195 --> 00:21:24,494 is where you go 584 00:21:24,795 --> 00:21:26,720 set up a PayGo connection, 585 00:21:27,179 --> 00:21:28,960 and it is 1¢ 586 00:21:29,500 --> 00:21:30,240 per message 587 00:21:30,859 --> 00:21:31,599 for licensing 588 00:21:31,900 --> 00:21:34,220 or leveraging these agents. And I'm gonna come 589 00:21:34,220 --> 00:21:36,220 back to messages here in a little bit. 590 00:21:36,220 --> 00:21:38,524 Then you can also buy message packs. So 591 00:21:38,524 --> 00:21:40,944 instead of paying on a 592 00:21:41,244 --> 00:21:41,984 per message 593 00:21:42,444 --> 00:21:42,944 basis, 594 00:21:43,565 --> 00:21:45,884 you can go buy a message pack for 595 00:21:45,884 --> 00:21:46,765 $200 596 00:21:46,765 --> 00:21:48,845 per tenant per month. And this essentially gives 597 00:21:48,845 --> 00:21:51,484 you pooled messages. And if I remember right, 598 00:21:51,484 --> 00:21:54,410 I think it's 10,000 599 00:21:54,410 --> 00:21:54,910 messages 600 00:21:55,450 --> 00:21:56,809 no. 25,000 601 00:21:56,809 --> 00:21:57,309 messages 602 00:21:57,690 --> 00:22:00,730 in that $200 plan. So now 200 603 00:22:00,730 --> 00:22:02,730 a month, you're buying 25,000 604 00:22:02,730 --> 00:22:04,910 messages that you can use within your company. 605 00:22:05,049 --> 00:22:07,904 And as users use it, it will deduct 606 00:22:08,144 --> 00:22:08,644 from 607 00:22:08,945 --> 00:22:11,265 this message pool. And then the other way 608 00:22:11,265 --> 00:22:13,904 is you already have Microsoft three sixty five 609 00:22:13,904 --> 00:22:14,404 Copilot, 610 00:22:14,785 --> 00:22:17,285 the $30 per user per month plan, 611 00:22:17,585 --> 00:22:20,884 and then your Copilot Studio is just included 612 00:22:21,025 --> 00:22:22,884 within that $30 613 00:22:22,945 --> 00:22:24,920 per user per month. It's kinda sort of 614 00:22:24,920 --> 00:22:27,319 included. So so some of the limits you're 615 00:22:27,319 --> 00:22:29,559 talking about, like, you're talking about message inclusion. 616 00:22:29,559 --> 00:22:31,799 Yep. PAYGo is PAYGo. Like you mentioned, the 617 00:22:31,799 --> 00:22:34,539 message packs come in 25,000 618 00:22:34,920 --> 00:22:35,420 message 619 00:22:35,880 --> 00:22:36,380 increments 620 00:22:37,115 --> 00:22:39,595 or Copilot Studio with m three sixty five 621 00:22:39,595 --> 00:22:40,815 Copilot unlimited. 622 00:22:41,355 --> 00:22:43,835 But that's just for the messages component. It's 623 00:22:43,835 --> 00:22:45,215 it's a little weird to say 624 00:22:46,394 --> 00:22:48,875 that it comes with everything because the the 625 00:22:48,875 --> 00:22:50,414 one thing that 626 00:22:50,789 --> 00:22:53,049 stands out that Copilot Studio 627 00:22:53,750 --> 00:22:56,630 usage rights when you're using Microsoft three sixty 628 00:22:56,630 --> 00:22:57,369 five Copilot, 629 00:22:57,830 --> 00:22:59,210 oh my gosh. It's a mouthful, 630 00:22:59,670 --> 00:23:02,549 is that you are not allowed to create 631 00:23:02,549 --> 00:23:04,410 and publish your own agents anywhere. 632 00:23:04,744 --> 00:23:06,825 So with that PAYGo and with that message 633 00:23:06,825 --> 00:23:09,244 pack model, you can absolutely create and publish. 634 00:23:09,625 --> 00:23:12,505 But with the Copilot studio usage rights, you 635 00:23:12,505 --> 00:23:15,465 can't publish them anywhere. They're only within your 636 00:23:15,465 --> 00:23:17,545 tenant and your users, that that kind of 637 00:23:17,545 --> 00:23:18,205 thing. So 638 00:23:18,759 --> 00:23:20,119 you you do have to decide, like, what 639 00:23:20,119 --> 00:23:22,200 kind of business you're in and and what 640 00:23:22,200 --> 00:23:24,599 the ultimate, like, intention is for these things 641 00:23:24,599 --> 00:23:26,839 along the way. There's some other things as 642 00:23:26,839 --> 00:23:28,679 well that change around, like, the channels you 643 00:23:28,679 --> 00:23:30,859 can publish in and and stuff like that. 644 00:23:31,000 --> 00:23:33,259 Generally speaking, like, that Copilot 645 00:23:33,855 --> 00:23:36,674 Studio usage rates, because you're already a 646 00:23:37,054 --> 00:23:38,755 Microsoft three sixty five Copilot 647 00:23:39,134 --> 00:23:39,634 subscriber, 648 00:23:40,335 --> 00:23:42,575 that's going to give you, like, your most 649 00:23:42,575 --> 00:23:45,054 bang for your buck across all of these 650 00:23:45,054 --> 00:23:46,654 things that are out there. Well and I 651 00:23:46,654 --> 00:23:48,990 don't think so you mentioned building them in 652 00:23:48,990 --> 00:23:51,950 Copilot Studio. There's a table. We'll link to 653 00:23:51,950 --> 00:23:53,869 this in the show notes. It actually says, 654 00:23:53,869 --> 00:23:56,210 like, create and publish your own agents anywhere. 655 00:23:56,590 --> 00:23:59,549 It's like it's weird because Copilot message packs 656 00:23:59,549 --> 00:24:01,009 and PAYGo, it's included. 657 00:24:01,414 --> 00:24:03,575 Studio, it's not included. But create and publish 658 00:24:03,575 --> 00:24:05,734 your own agents and plugins to extend Microsoft 659 00:24:05,734 --> 00:24:08,875 three sixty five, it's not included with Studio, 660 00:24:09,095 --> 00:24:11,414 PAYGo, or message packs, but it is included 661 00:24:11,414 --> 00:24:14,890 with the $30 a month plan. So they, 662 00:24:14,890 --> 00:24:17,289 like, flip flop. Well, there's an unwritten word 663 00:24:17,289 --> 00:24:19,529 that you have to extend in. So create 664 00:24:19,529 --> 00:24:21,529 and publish your own agents and plugins to 665 00:24:21,529 --> 00:24:23,869 extend Microsoft three sixty five Copilot 666 00:24:24,410 --> 00:24:26,329 in your tenant. Yeah. So it kinda becomes 667 00:24:26,329 --> 00:24:29,345 in your tenant versus multi tenant. Versus anywhere. 668 00:24:29,484 --> 00:24:31,184 Yeah. So, like, if you were a builder 669 00:24:31,484 --> 00:24:33,884 and you wanted to build and deploy an 670 00:24:33,884 --> 00:24:36,605 agent across multiple tenants, then you you might 671 00:24:36,605 --> 00:24:38,224 be in one of the other kinda 672 00:24:38,684 --> 00:24:41,309 one of the other buckets there. So it's 673 00:24:41,309 --> 00:24:43,409 it's weird when they talk about extensibility 674 00:24:43,789 --> 00:24:45,409 that way, but it's really, like, 675 00:24:45,710 --> 00:24:46,210 extensibility 676 00:24:46,829 --> 00:24:48,210 within your tenant 677 00:24:48,669 --> 00:24:50,190 is is the way that I I think 678 00:24:50,190 --> 00:24:52,109 about it in my head. You'll look at 679 00:24:52,109 --> 00:24:53,804 it there. Yeah. And then we talked about 680 00:24:53,804 --> 00:24:56,204 messages. This is the other thing that you 681 00:24:56,204 --> 00:24:57,724 need to be aware of is you may 682 00:24:57,724 --> 00:24:59,105 think messages is 683 00:24:59,404 --> 00:25:02,125 I send the agent a message. I ask 684 00:25:02,125 --> 00:25:04,605 it a question is a message. Kinda like 685 00:25:04,605 --> 00:25:06,284 maybe you'd chat in Teams and you'd send 686 00:25:06,284 --> 00:25:07,265 someone a message. 687 00:25:08,210 --> 00:25:09,029 But different 688 00:25:09,490 --> 00:25:09,990 actions 689 00:25:10,369 --> 00:25:10,869 in 690 00:25:11,250 --> 00:25:11,750 Copilot 691 00:25:12,210 --> 00:25:14,930 count for different messages. It's like another one 692 00:25:14,930 --> 00:25:17,890 of Microsoft's weird, we're gonna use this to 693 00:25:17,890 --> 00:25:20,070 measure your usage without really 694 00:25:20,450 --> 00:25:21,430 making it clear 695 00:25:21,890 --> 00:25:24,214 how that's what that unit is. 696 00:25:24,515 --> 00:25:27,234 So in the billing rate table, and we 697 00:25:27,234 --> 00:25:29,634 can throw this out there, like, a classic 698 00:25:29,634 --> 00:25:32,355 answer is one message. So maybe that's where 699 00:25:32,355 --> 00:25:34,515 this started is I asked Coppola the question, 700 00:25:34,515 --> 00:25:36,515 it gives me a classic answer, that's a 701 00:25:36,515 --> 00:25:38,640 message. But if now I'm doing a generative 702 00:25:39,740 --> 00:25:42,380 answer, it's two messages. If I'm doing an 703 00:25:42,380 --> 00:25:46,380 agent action, it's five messages. If I'm sending 704 00:25:46,380 --> 00:25:47,920 agent flow actions, 705 00:25:48,619 --> 00:25:52,400 it's 13 messages per every 100 actions. 706 00:25:53,015 --> 00:25:55,494 Text and generative AI is a message, but 707 00:25:55,494 --> 00:25:56,394 text and generative 708 00:25:56,774 --> 00:25:57,434 or basic 709 00:25:57,894 --> 00:25:58,394 is 710 00:25:58,855 --> 00:26:00,154 per 10 responses 711 00:26:00,454 --> 00:26:02,774 as one message. But if you're doing text 712 00:26:02,774 --> 00:26:03,434 and generative 713 00:26:03,815 --> 00:26:05,274 AI tools premium, 714 00:26:05,575 --> 00:26:07,755 it's a hundred messages per 10 responses. 715 00:26:08,140 --> 00:26:10,619 So this is, I feel like, definitely a 716 00:26:10,619 --> 00:26:12,539 little bit more of an art than a 717 00:26:12,539 --> 00:26:14,960 science, and you could have some 718 00:26:15,259 --> 00:26:16,240 huge fluctuations, 719 00:26:16,700 --> 00:26:18,559 I would say, in some of this PAYGo 720 00:26:18,940 --> 00:26:21,279 pricing or your message pools 721 00:26:21,794 --> 00:26:22,294 based 722 00:26:23,154 --> 00:26:26,355 on how you're allowing your users to leverage 723 00:26:26,355 --> 00:26:28,914 Copilot within these agents that you build. I 724 00:26:28,914 --> 00:26:31,154 mean, Happy Path is certainly, like, you've picked 725 00:26:31,154 --> 00:26:33,075 up m three sixty five Copilot like you 726 00:26:33,075 --> 00:26:35,169 talked about. Right. The $30 per user per 727 00:26:35,169 --> 00:26:37,569 month or or whatever number that eventually ends 728 00:26:37,569 --> 00:26:38,149 up being. 729 00:26:39,409 --> 00:26:41,569 And and and you've gone down that rabbit 730 00:26:41,569 --> 00:26:44,609 hole, but that's happy path. Like, to your 731 00:26:44,609 --> 00:26:46,615 point, not everybody's in the happy path. And 732 00:26:46,615 --> 00:26:48,315 some of this stuff is a little confusing. 733 00:26:48,375 --> 00:26:50,454 Like, really, when they're talking about messages, they're 734 00:26:50,454 --> 00:26:52,454 talking about tokens. Like, as much as I 735 00:26:52,454 --> 00:26:54,855 hate talking about tokens and context windows with 736 00:26:54,855 --> 00:26:55,355 LLMs, 737 00:26:55,734 --> 00:26:57,734 at least, like, token makes sense to me. 738 00:26:57,734 --> 00:26:59,335 Right? Or you could say, like, fuel up. 739 00:26:59,335 --> 00:27:01,279 Like, hey. I'm I'm going to 740 00:27:01,680 --> 00:27:03,039 in The US, we have, like, Dave and 741 00:27:03,039 --> 00:27:04,799 Buster's, and you're gonna go refill your party 742 00:27:04,799 --> 00:27:06,480 cards so you can go hit more video 743 00:27:06,480 --> 00:27:08,400 games. Same kinda thing. Right? Let let me 744 00:27:08,400 --> 00:27:09,680 go let me go fill up my card 745 00:27:09,680 --> 00:27:11,680 with tokens, and then boom, I'm gonna go 746 00:27:11,680 --> 00:27:12,900 spend 25 747 00:27:13,244 --> 00:27:15,724 tokens to play this game. Or same kinda 748 00:27:15,724 --> 00:27:17,505 thing here. I'm gonna spend one token 749 00:27:18,125 --> 00:27:20,444 to to to generate an answer. I I 750 00:27:20,444 --> 00:27:22,765 think you do have to understand a little 751 00:27:22,765 --> 00:27:23,424 bit about 752 00:27:23,805 --> 00:27:26,605 your patterns for these things and and how 753 00:27:26,605 --> 00:27:28,980 they come across and and plan for them. 754 00:27:29,220 --> 00:27:29,720 So 755 00:27:30,579 --> 00:27:32,579 the the the things here that start to 756 00:27:32,579 --> 00:27:33,240 get you 757 00:27:33,539 --> 00:27:34,839 are the 758 00:27:35,700 --> 00:27:37,779 agent to agent actions. So, like, if you're 759 00:27:37,779 --> 00:27:40,660 autonomously executing agents or you're having one agent 760 00:27:40,660 --> 00:27:42,900 interact with another one, like, great. That's five 761 00:27:42,900 --> 00:27:43,400 tokens. 762 00:27:43,974 --> 00:27:46,794 The other one is the graph grounding stuff. 763 00:27:47,014 --> 00:27:48,075 It can hit you. 764 00:27:48,375 --> 00:27:50,694 So you're saying, okay. Hey. I'm I'm hooked 765 00:27:50,694 --> 00:27:53,494 up to my tenant graph, like Microsoft Graph, 766 00:27:53,494 --> 00:27:56,234 and I've I've turned on these connectors to 767 00:27:56,534 --> 00:27:57,034 extend 768 00:27:57,575 --> 00:28:00,220 Copilot within my tenant. Well, that stuff starts 769 00:28:00,220 --> 00:28:03,019 to get expensive as well. And then from 770 00:28:03,019 --> 00:28:04,940 there, you might actually wanna, like, turn things 771 00:28:04,940 --> 00:28:07,200 off. Like, you might not want to allow 772 00:28:07,259 --> 00:28:10,539 for, like, generative images because of the high 773 00:28:10,539 --> 00:28:13,099 cost and and the tokens associated with them. 774 00:28:13,099 --> 00:28:14,000 Yeah. It is 775 00:28:14,664 --> 00:28:15,164 definitely 776 00:28:15,704 --> 00:28:18,105 something to be careful of, and I would 777 00:28:18,105 --> 00:28:20,505 say I've I've started having conversations too is 778 00:28:20,505 --> 00:28:22,904 looking at how much you expect or where 779 00:28:22,904 --> 00:28:25,464 you start. I would say even the message 780 00:28:25,464 --> 00:28:27,305 packs. I did the math here quick a 781 00:28:27,305 --> 00:28:29,109 minute. If you're buying 25,000 782 00:28:29,109 --> 00:28:30,650 messages for $200, 783 00:28:30,789 --> 00:28:31,930 you're only spending 784 00:28:32,309 --> 00:28:34,089 0.02¢ 785 00:28:34,390 --> 00:28:37,109 per message less. So as opposed to the 786 00:28:37,109 --> 00:28:38,490 PAYGo for 1¢, 787 00:28:38,549 --> 00:28:40,410 if you buy a message pack, you're spending 788 00:28:40,470 --> 00:28:41,589 0.8¢ 789 00:28:41,589 --> 00:28:43,384 per message. I was talking to a client 790 00:28:43,384 --> 00:28:44,924 about this the other day. I'm like, just 791 00:28:44,984 --> 00:28:47,865 start with PayGo. Use PayGo until you hit 792 00:28:47,865 --> 00:28:49,484 essentially $200. 793 00:28:49,704 --> 00:28:51,724 Once if your PayGo is consistently 794 00:28:52,265 --> 00:28:54,744 $200 a month, then maybe you switch to 795 00:28:54,744 --> 00:28:56,825 the message packs, and you essentially pay the 796 00:28:56,825 --> 00:28:58,820 same amount, and you get a few bonus 797 00:28:58,820 --> 00:29:00,740 messages. But I don't know that there's a 798 00:29:00,740 --> 00:29:03,220 lot of benefit to necessarily starting with message 799 00:29:03,220 --> 00:29:05,080 packs unless you're a huge organization, 800 00:29:05,619 --> 00:29:08,359 but you're just gonna blow through messages and 801 00:29:08,420 --> 00:29:10,099 you're like, yeah, we're gonna be spending a 802 00:29:10,099 --> 00:29:12,164 thousand, 2 thousand dollars a month. PAYGo makes 803 00:29:12,164 --> 00:29:13,605 sense. Or like you said, in a happy 804 00:29:13,605 --> 00:29:16,424 world, you're just licensing Microsoft three sixty five, 805 00:29:16,965 --> 00:29:19,445 getting the $30 a month license. Yeah. You'll 806 00:29:19,445 --> 00:29:21,045 look at the cost. Maybe you only have 807 00:29:21,045 --> 00:29:22,825 five or six users in your organization. 808 00:29:23,205 --> 00:29:26,460 Buying six $30 licenses a month is still 809 00:29:26,539 --> 00:29:28,460 still cheaper than $200 a month for message 810 00:29:28,460 --> 00:29:31,500 pack. So really looking at users usage, where 811 00:29:31,500 --> 00:29:33,500 do you wanna start with this when you're 812 00:29:33,500 --> 00:29:35,279 getting into some of that 813 00:29:35,819 --> 00:29:36,799 pricing and 814 00:29:37,179 --> 00:29:38,700 trying some of this stuff out? So you 815 00:29:38,700 --> 00:29:40,319 probably want PayGo there anyway, 816 00:29:40,705 --> 00:29:42,325 at least if you're doing the 817 00:29:42,705 --> 00:29:43,365 the the, 818 00:29:44,225 --> 00:29:45,045 sorry, the 819 00:29:45,424 --> 00:29:46,244 the consumption 820 00:29:46,625 --> 00:29:48,465 or or you're doing kind of the the 821 00:29:48,465 --> 00:29:48,965 bigger 822 00:29:49,424 --> 00:29:51,585 messaging packs that you talked about. Like, hey. 823 00:29:51,585 --> 00:29:52,965 If you buy 25,000, 824 00:29:53,269 --> 00:29:55,750 you're probably gonna wanna PAYGo to bump up 825 00:29:55,750 --> 00:29:57,909 behind it anyway. So you're gonna go and 826 00:29:57,909 --> 00:30:00,329 configure all that stuff on the Azure side. 827 00:30:00,389 --> 00:30:01,990 Like, it's it's it's a little weird the 828 00:30:01,990 --> 00:30:04,230 way it happens too because you end up 829 00:30:04,230 --> 00:30:06,089 taking what's effectively 830 00:30:07,005 --> 00:30:07,505 a 831 00:30:08,365 --> 00:30:10,924 an a linked environment from Power Platform and 832 00:30:10,924 --> 00:30:12,765 bringing that over to Azure, and then that's 833 00:30:12,765 --> 00:30:14,684 your you you end up with this weird 834 00:30:14,684 --> 00:30:16,845 linked billing construct. Like, yeah, you can go 835 00:30:16,845 --> 00:30:18,285 into the Azure portal, and you can see 836 00:30:18,285 --> 00:30:21,320 Copilot Studio, but and your, like, message consumption, 837 00:30:21,320 --> 00:30:22,920 but then there's other stuff going on over 838 00:30:22,920 --> 00:30:23,580 in PowerPlat. 839 00:30:24,120 --> 00:30:25,960 And you have to maintain that connection too. 840 00:30:25,960 --> 00:30:27,559 Like, if you take that connection away, then 841 00:30:27,559 --> 00:30:29,799 the billing relationship is severed. It's it's a 842 00:30:29,799 --> 00:30:31,400 little weird still, the the way it gets 843 00:30:31,400 --> 00:30:33,984 wired up. Anything else? You've been talking. We've 844 00:30:33,984 --> 00:30:35,444 been talking for thirty minutes. 845 00:30:35,744 --> 00:30:37,744 You're getting over your cold. You're starting to 846 00:30:37,744 --> 00:30:39,585 lose your voice, Scott. You still have your 847 00:30:39,585 --> 00:30:42,085 entire week to go. Anything else you wanna 848 00:30:42,224 --> 00:30:44,384 touch on before we wrap up for day 849 00:30:44,384 --> 00:30:46,730 and you wrap up for today, can you 850 00:30:46,730 --> 00:30:48,169 give your voice a little break before you 851 00:30:48,169 --> 00:30:49,609 dive into all your meetings? So I think 852 00:30:49,609 --> 00:30:51,289 a couple of things. Maybe just some, like, 853 00:30:51,289 --> 00:30:54,190 high level tips and tricks and and things 854 00:30:55,129 --> 00:30:57,549 to keep in mind. So one is 855 00:30:57,929 --> 00:30:58,829 design with 856 00:30:59,194 --> 00:31:00,555 when when you're building one of these things, 857 00:31:00,555 --> 00:31:02,075 you kinda have to decide, am I building 858 00:31:02,075 --> 00:31:03,595 it for myself? Am I building it for 859 00:31:03,595 --> 00:31:05,115 my team? Am I building it for a 860 00:31:05,115 --> 00:31:05,934 wider audience? 861 00:31:06,394 --> 00:31:08,394 So as you're going down that path and 862 00:31:08,394 --> 00:31:10,154 you kinda understand your audience and who you're 863 00:31:10,154 --> 00:31:12,474 building for, that'll help you do better grounding 864 00:31:12,474 --> 00:31:13,295 in your instructions, 865 00:31:13,674 --> 00:31:14,494 maybe your 866 00:31:15,150 --> 00:31:16,130 your your preprovided 867 00:31:16,430 --> 00:31:17,809 prompts, things like that. 868 00:31:18,350 --> 00:31:20,670 You do have to think through maintaining your 869 00:31:20,670 --> 00:31:21,490 knowledge sources. 870 00:31:21,789 --> 00:31:23,950 So, obviously, like graph connectors, things like that, 871 00:31:23,950 --> 00:31:25,410 they can be a little bit more evergreen. 872 00:31:25,710 --> 00:31:28,049 But say you had augmented with some documentation 873 00:31:28,190 --> 00:31:29,774 that you dropped in a SharePoint site and 874 00:31:29,774 --> 00:31:32,654 that documentation changes over time, you've gotta remember 875 00:31:32,654 --> 00:31:35,315 to go back and update that documentation, 876 00:31:36,095 --> 00:31:38,095 and keep dropping it in there and landing 877 00:31:38,095 --> 00:31:39,394 it in that place, and potentially 878 00:31:39,934 --> 00:31:40,434 updating 879 00:31:40,815 --> 00:31:41,315 and 880 00:31:42,200 --> 00:31:44,680 refining the prompts within your agent to make 881 00:31:44,680 --> 00:31:46,619 it work with that new data. 882 00:31:47,000 --> 00:31:48,359 The other thing to think about is who 883 00:31:48,359 --> 00:31:50,920 you publish your agents to. So I've I've 884 00:31:50,920 --> 00:31:52,920 seen this, like, at least within, like, the 885 00:31:52,920 --> 00:31:54,680 stuff that I've done, and and, like, I've 886 00:31:54,680 --> 00:31:56,440 built some stuff for myself, some stuff for 887 00:31:56,440 --> 00:31:58,805 our team. And all of a sudden, somebody 888 00:31:58,805 --> 00:31:59,765 will come back to me and they'll say, 889 00:31:59,765 --> 00:32:01,205 like, oh, hey. I was showing off your 890 00:32:01,205 --> 00:32:02,725 blah blah blah to a friend, and and 891 00:32:02,725 --> 00:32:04,244 they wanted access to it. I'm like, well, 892 00:32:04,244 --> 00:32:06,244 they really shouldn't have access to it because 893 00:32:06,244 --> 00:32:07,924 it's our agent. It's, like, for our team, 894 00:32:07,924 --> 00:32:09,445 and it goes around just this subset of 895 00:32:09,445 --> 00:32:11,069 data. Right? Like, back to that, if you 896 00:32:11,069 --> 00:32:13,170 built the statement of work thing for yourself, 897 00:32:13,309 --> 00:32:15,309 you're probably not gonna give that to every 898 00:32:15,309 --> 00:32:17,549 person in your organization. It'll be for you 899 00:32:17,549 --> 00:32:19,549 and a select set of salespeople and things 900 00:32:19,549 --> 00:32:21,710 like that to to to go drive that 901 00:32:21,710 --> 00:32:23,345 through. And then finally, 902 00:32:23,964 --> 00:32:24,704 these are 903 00:32:25,565 --> 00:32:26,065 still 904 00:32:26,365 --> 00:32:26,865 nondeterministic 905 00:32:27,404 --> 00:32:27,904 systems. 906 00:32:28,365 --> 00:32:30,545 They're gonna have wonky answers sometimes. 907 00:32:31,085 --> 00:32:33,244 They're gonna hallucinate. They're they're they're gonna need 908 00:32:33,244 --> 00:32:35,200 refinement, all that kind of stuff. So as 909 00:32:35,200 --> 00:32:37,039 you publish these out, particularly for anything that 910 00:32:37,039 --> 00:32:38,960 you publish that goes beyond the scope of 911 00:32:38,960 --> 00:32:41,440 you, whether that goes to a team of 912 00:32:41,440 --> 00:32:42,820 two, a team of 10, 913 00:32:43,279 --> 00:32:45,539 or your entire company, like, it doesn't matter, 914 00:32:45,600 --> 00:32:48,320 you should be prepared to kinda take feedback 915 00:32:48,320 --> 00:32:51,115 and iterate on that feedback and and republish 916 00:32:51,174 --> 00:32:52,234 these things occasionally 917 00:32:52,775 --> 00:32:54,375 so that they can pick up the new 918 00:32:54,375 --> 00:32:56,694 capabilities. Like, maybe your tenant admin went in 919 00:32:56,694 --> 00:32:58,634 and added a bunch of new graph connectors, 920 00:32:59,255 --> 00:33:02,134 or you're just on that kinda journey of 921 00:33:02,134 --> 00:33:04,779 of continuous improvement with those. Like, I have 922 00:33:04,779 --> 00:33:06,700 found that to be important. Like, you can't 923 00:33:06,700 --> 00:33:09,019 just often do the wrong appeal, set it 924 00:33:09,019 --> 00:33:10,859 and forget it kinda thing. You do have 925 00:33:10,859 --> 00:33:12,880 to kinda come back, care, feed, 926 00:33:13,579 --> 00:33:15,660 water, and and make sure that your garden's 927 00:33:15,660 --> 00:33:19,164 flourishing. % increase or change those instructions. Your 928 00:33:19,164 --> 00:33:20,845 point is data's changing too. You may have 929 00:33:20,845 --> 00:33:22,384 to go update the instructions 930 00:33:23,164 --> 00:33:23,904 to your 931 00:33:24,285 --> 00:33:24,785 agent. 932 00:33:25,164 --> 00:33:27,025 I would say even knowing 933 00:33:28,045 --> 00:33:29,404 you have to know where these agents are 934 00:33:29,404 --> 00:33:31,164 pulling data from because the other thing is 935 00:33:31,164 --> 00:33:33,105 you don't want somebody in your company 936 00:33:33,660 --> 00:33:36,299 to go drop a particular document in a 937 00:33:36,299 --> 00:33:37,200 document library 938 00:33:37,740 --> 00:33:40,619 and a particular SharePoint site, publish a particular 939 00:33:40,619 --> 00:33:41,119 article 940 00:33:41,500 --> 00:33:42,160 in Confluence, 941 00:33:42,460 --> 00:33:44,700 and not realize that there's an agent that's 942 00:33:44,700 --> 00:33:46,460 open to the whole company that's pointing at 943 00:33:46,460 --> 00:33:48,480 this, or there's all that 944 00:33:48,904 --> 00:33:52,585 security compliance governance stuff to think about as 945 00:33:52,585 --> 00:33:54,505 well because now you may have these agents 946 00:33:54,505 --> 00:33:57,865 pointed at very specific spots and allow it 947 00:33:58,505 --> 00:34:01,380 it's like almost allowing your employees to know 948 00:34:01,539 --> 00:34:03,619 where different agents are pulling data from so 949 00:34:03,619 --> 00:34:05,779 they can be cognizant of that as they're 950 00:34:05,779 --> 00:34:07,859 updating data. It is a consideration because one 951 00:34:07,859 --> 00:34:09,219 of the things you can do is you 952 00:34:09,219 --> 00:34:10,980 can take an agent, and because you have 953 00:34:10,980 --> 00:34:13,219 access to the SharePoint site, you can point 954 00:34:13,219 --> 00:34:14,739 it over to that SharePoint site. And I 955 00:34:14,739 --> 00:34:15,559 haven't seen 956 00:34:16,074 --> 00:34:18,394 at least in I don't know. I'd have 957 00:34:18,394 --> 00:34:19,675 to play around with it. I don't know 958 00:34:19,675 --> 00:34:21,195 if everybody that I've shared some of these 959 00:34:21,195 --> 00:34:24,635 things with actually has access to the SharePoint 960 00:34:24,635 --> 00:34:26,954 site or if it's SharePoint or the agent 961 00:34:26,954 --> 00:34:28,315 or like, it's a little weird in my 962 00:34:28,315 --> 00:34:30,235 head, right, for how it all ties together. 963 00:34:30,235 --> 00:34:32,530 I would think at least for SharePoint, it's 964 00:34:32,530 --> 00:34:35,269 going to be using it's gonna respect permissions. 965 00:34:35,329 --> 00:34:37,170 Like, if I have permission to the SharePoint 966 00:34:37,329 --> 00:34:39,329 One would think. One would think. But other 967 00:34:39,329 --> 00:34:41,750 sources, like maybe a SQL database 968 00:34:42,050 --> 00:34:44,449 or a Confluence page or something like that 969 00:34:44,449 --> 00:34:46,275 or, again, you drop it. 970 00:34:46,755 --> 00:34:47,494 Yeah. It's 971 00:34:47,875 --> 00:34:50,835 it's definitely something to be aware of. We'll 972 00:34:50,835 --> 00:34:52,275 leave it at that. I'll have to go 973 00:34:52,275 --> 00:34:54,114 play with that one, Scott, because I'm definitely 974 00:34:54,114 --> 00:34:56,675 making some assumptions there. I am too. But 975 00:34:56,675 --> 00:34:58,949 SharePoint permissions tend to be pretty wide and 976 00:34:59,030 --> 00:35:00,469 open no matter how much you want them 977 00:35:00,469 --> 00:35:01,589 to be locked down. So that's why I 978 00:35:01,589 --> 00:35:02,789 don't know if it's a me thing, if 979 00:35:02,789 --> 00:35:04,150 it's a SharePoint thing, or if it's an 980 00:35:04,150 --> 00:35:05,750 agent thing. Or a combination of all of 981 00:35:05,750 --> 00:35:07,750 those. Yes. Or all of the above, for 982 00:35:07,750 --> 00:35:10,170 sure. We'll throw a bunch of links in 983 00:35:10,309 --> 00:35:11,609 the show notes about 984 00:35:12,094 --> 00:35:14,815 all the licensing stuff, steps for building these, 985 00:35:14,815 --> 00:35:16,034 hooking up different, 986 00:35:16,894 --> 00:35:18,034 different data sources, 987 00:35:18,494 --> 00:35:20,894 all of that. So it would be interesting 988 00:35:20,894 --> 00:35:22,994 too, Scott, to hear how other people have 989 00:35:23,214 --> 00:35:25,679 used agents, what they've built. And I know 990 00:35:25,679 --> 00:35:27,359 I'm starting to build some. Like, I'm working 991 00:35:27,359 --> 00:35:29,760 on building an internal knowledge base one for 992 00:35:29,760 --> 00:35:32,099 me where I can look at different solutions, 993 00:35:32,239 --> 00:35:32,739 documentation, 994 00:35:33,039 --> 00:35:35,119 all of that we've created for clients. But, 995 00:35:35,119 --> 00:35:37,280 yeah, hearing how other people are using agents 996 00:35:37,280 --> 00:35:39,280 as well, reaching out to us on the 997 00:35:39,280 --> 00:35:41,644 socials or any of that and having some 998 00:35:41,644 --> 00:35:44,284 discussion out there on agents and usage around 999 00:35:44,284 --> 00:35:46,605 it. For sure. Awesome. Well, thanks, Scott. Go 1000 00:35:46,605 --> 00:35:48,684 get better. Go drink some more tea. Try 1001 00:35:48,684 --> 00:35:50,125 to let other people talk in all your 1002 00:35:50,125 --> 00:35:52,525 meetings this week, and we will talk to 1003 00:35:52,525 --> 00:35:54,630 you again soon. Alright. Sounds good. Thanks, Beth. 1004 00:35:56,630 --> 00:35:58,869 If you enjoyed the podcast, go leave us 1005 00:35:58,869 --> 00:36:01,109 a five star rating in iTunes. It helps 1006 00:36:01,109 --> 00:36:02,789 to get the word out so more IT 1007 00:36:02,789 --> 00:36:04,869 pros can learn about Office three sixty five 1008 00:36:04,869 --> 00:36:05,609 and Azure. 1009 00:36:06,150 --> 00:36:07,750 If you have any questions you want us 1010 00:36:07,750 --> 00:36:09,989 to address on the show or feedback about 1011 00:36:09,989 --> 00:36:12,304 the show, feel free to reach out via 1012 00:36:12,304 --> 00:36:14,484 our website, Twitter, or Facebook. 1013 00:36:14,784 --> 00:36:16,704 Thanks again for listening, and have a great 1014 00:36:16,704 --> 00:36:17,204 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