1 00:00:03,600 --> 00:00:06,480 Welcome to episode 424 2 00:00:06,480 --> 00:00:09,059 of the Microsoft Cloud IT Pro podcast, 3 00:00:09,359 --> 00:00:12,500 recorded live 02/09/2026. 4 00:00:12,639 --> 00:00:14,880 This is a show about Microsoft three sixty 5 00:00:14,880 --> 00:00:15,074 five 6 00:00:17,234 --> 00:00:17,377 five and Azure from the perspective of IT 7 00:00:17,377 --> 00:00:19,314 pros and end users, where we discuss a 8 00:00:19,314 --> 00:00:21,714 topic or recent news and how it relates 9 00:00:21,714 --> 00:00:24,515 to you. In this episode, Ben and Scott 10 00:00:24,515 --> 00:00:26,675 get back together again with a plan for 11 00:00:26,675 --> 00:00:29,640 one topic that suddenly goes awry with the 12 00:00:29,640 --> 00:00:32,679 recent announcement of the new Microsoft three sixty 13 00:00:32,679 --> 00:00:35,559 five e seven plan. So instead of talking 14 00:00:35,559 --> 00:00:39,159 about GPOs and configuration policies, we postpone that 15 00:00:39,159 --> 00:00:41,384 for a future episode and dive into the 16 00:00:41,384 --> 00:00:43,465 world of the up and coming e seven 17 00:00:43,465 --> 00:00:43,965 plan, 18 00:00:44,344 --> 00:00:46,924 what's included in this plan, and our perception 19 00:00:46,984 --> 00:00:49,545 of its value. With this announcement and the 20 00:00:49,545 --> 00:00:52,265 inclusion of Microsoft three sixty five Copilot in 21 00:00:52,265 --> 00:00:55,359 the e seven plan, we also discuss some 22 00:00:55,359 --> 00:00:57,520 of the new features coming to Microsoft three 23 00:00:57,520 --> 00:01:00,739 sixty five Copilot wave three that were announced 24 00:01:00,799 --> 00:01:04,000 at the same time. So let's talk about 25 00:01:04,000 --> 00:01:06,420 Microsoft three sixty five e seven. 26 00:01:08,795 --> 00:01:10,554 We should talk about e seven. I wanna 27 00:01:10,554 --> 00:01:12,155 open with this, and maybe this is a 28 00:01:12,155 --> 00:01:13,515 little bit of a different way to go 29 00:01:13,515 --> 00:01:15,754 with this. Okay. I'm gonna start maybe not 30 00:01:15,754 --> 00:01:16,734 from the 31 00:01:17,435 --> 00:01:17,935 hero 32 00:01:18,394 --> 00:01:20,894 entry point, which would be like a raw, 33 00:01:20,954 --> 00:01:23,854 like, super, here's the user value of this 34 00:01:24,020 --> 00:01:26,340 to you Yep. But rather from the partner 35 00:01:26,340 --> 00:01:29,000 angle. So I always think it's interesting how 36 00:01:29,459 --> 00:01:32,040 Microsoft interacts with partners. There's a 37 00:01:32,340 --> 00:01:35,140 massive partner ecosystem, and they very much rely 38 00:01:35,140 --> 00:01:35,880 on partners 39 00:01:36,995 --> 00:01:39,655 to co sell and upsell opportunities 40 00:01:39,954 --> 00:01:43,334 to customers. Like, everybody wins. Microsoft makes money, 41 00:01:43,394 --> 00:01:46,454 partners make money, and customers get the functionality 42 00:01:46,674 --> 00:01:47,894 that they're looking for 43 00:01:48,194 --> 00:01:51,234 all for the same price along the way. 44 00:01:51,234 --> 00:01:53,479 So I'm gonna start with the partner blog 45 00:01:53,479 --> 00:01:54,920 and just read you a couple of things. 46 00:01:54,920 --> 00:01:57,879 So Microsoft three sixty five is the frontier 47 00:01:57,879 --> 00:02:00,840 suite designed for a human led agent operated 48 00:02:00,840 --> 00:02:04,299 enterprise turning human intent into AI action 49 00:02:04,674 --> 00:02:08,034 that functions securely and at scale. To accomplish 50 00:02:08,034 --> 00:02:11,395 this, Microsoft three sixty five e seven includes 51 00:02:11,395 --> 00:02:14,754 access to Microsoft agent three sixty five, which 52 00:02:14,754 --> 00:02:17,955 is the control plane to govern and scale 53 00:02:17,955 --> 00:02:20,110 agents. Okay. Yeah. Like you said, here's an 54 00:02:20,110 --> 00:02:21,549 e seven. It's got some new stuff in 55 00:02:21,549 --> 00:02:22,689 it primarily 56 00:02:23,150 --> 00:02:25,250 and including access to AI 57 00:02:25,789 --> 00:02:28,829 experiences and Microsoft Agent three sixty five. All 58 00:02:28,829 --> 00:02:30,209 all good. Now 59 00:02:31,025 --> 00:02:33,665 here's the thing. So starting on 04/01/2026, 60 00:02:33,665 --> 00:02:36,485 to accelerate Microsoft three sixty five e five 61 00:02:37,185 --> 00:02:40,004 to Microsoft three sixty five e seven upsell 62 00:02:40,145 --> 00:02:42,724 and Agent three sixty five adoption, Copilot 63 00:02:43,025 --> 00:02:46,020 plus Power Accelerate are going to include agent 64 00:02:46,020 --> 00:02:49,319 three sixty five across immersion briefings, envisioning, 65 00:02:49,699 --> 00:02:51,159 and proof of concept engagements, 66 00:02:51,460 --> 00:02:52,759 as well as deployment 67 00:02:53,139 --> 00:02:53,639 accelerators. 68 00:02:54,259 --> 00:02:55,939 And all of these things are now gonna 69 00:02:55,939 --> 00:02:58,199 be included as eligible workloads for 70 00:02:58,665 --> 00:03:01,705 core tier one strategic product accelerators and growth 71 00:03:01,705 --> 00:03:04,365 levers for cloud solution providers. 72 00:03:04,824 --> 00:03:05,324 So 73 00:03:05,705 --> 00:03:07,705 prepare thyself. Even if you didn't know what 74 00:03:07,705 --> 00:03:09,305 an e seven was or know that it's 75 00:03:09,305 --> 00:03:12,205 coming, you are about to know as your 76 00:03:12,750 --> 00:03:14,610 resellers. You're in this boat yourself 77 00:03:15,069 --> 00:03:17,069 saying, hey. Yep. Out there working in the 78 00:03:17,069 --> 00:03:17,969 partner ecosystem 79 00:03:18,349 --> 00:03:19,569 and selling to customers. 80 00:03:20,030 --> 00:03:20,849 If you were 81 00:03:21,150 --> 00:03:23,889 getting tired of hearing about AI, guess what? 82 00:03:24,270 --> 00:03:24,770 You're 83 00:03:25,550 --> 00:03:26,590 not gonna be able to take a nap 84 00:03:26,590 --> 00:03:29,344 anytime soon. I have a couple of issues. 85 00:03:29,805 --> 00:03:31,485 I'm gonna take issue with a couple of 86 00:03:31,485 --> 00:03:33,104 things in here. One, 87 00:03:33,485 --> 00:03:36,844 Microsoft three sixty five e seven bundles, Microsoft 88 00:03:36,844 --> 00:03:39,164 three sixty five e five, Microsoft three sixty 89 00:03:39,164 --> 00:03:39,905 five Copilot, 90 00:03:40,500 --> 00:03:43,539 EntraSweet, and Agent three sixty five. Yes. That 91 00:03:43,539 --> 00:03:44,199 is true. 92 00:03:44,500 --> 00:03:45,000 However, 93 00:03:46,019 --> 00:03:46,519 EntraSweet 94 00:03:46,819 --> 00:03:49,139 was already announced that it was going to 95 00:03:49,139 --> 00:03:49,879 be included 96 00:03:50,259 --> 00:03:50,759 with 97 00:03:51,060 --> 00:03:52,659 e five. Dev hole is always in the 98 00:03:52,659 --> 00:03:53,159 details. 99 00:03:54,099 --> 00:03:54,599 Yes. 100 00:03:54,974 --> 00:03:57,294 Technically, that's true. You're getting EntraSweet with an 101 00:03:57,294 --> 00:03:58,735 e seven, but you were getting it already 102 00:03:58,735 --> 00:04:00,814 with an e five. So it's not that's 103 00:04:00,814 --> 00:04:02,995 not a value add for the e seven. 104 00:04:03,055 --> 00:04:05,775 It's really Microsoft three sixty five Copilot and 105 00:04:05,775 --> 00:04:07,860 Agent three sixty five is the way I 106 00:04:07,860 --> 00:04:09,699 would phrase it because everybody that's already on 107 00:04:09,699 --> 00:04:10,919 e five gets EntraSweet. 108 00:04:11,300 --> 00:04:12,819 That being said, this is not a bad 109 00:04:12,819 --> 00:04:13,319 deal 110 00:04:13,620 --> 00:04:14,360 if you 111 00:04:14,819 --> 00:04:15,800 are interested 112 00:04:16,100 --> 00:04:19,160 if you're gonna use Copilot. E fives also, 113 00:04:19,699 --> 00:04:20,759 like, July, 114 00:04:21,205 --> 00:04:21,705 Sometime, 115 00:04:22,324 --> 00:04:24,324 July. E five is going up to $60 116 00:04:24,324 --> 00:04:27,365 a month. Copilot's already $30 a month. There's 117 00:04:27,365 --> 00:04:30,324 your $90 a month. Agent ID is essentially 118 00:04:30,324 --> 00:04:33,205 costing you $9 a month. This is also 119 00:04:33,205 --> 00:04:34,965 an add on. This is the part that 120 00:04:34,965 --> 00:04:36,709 surprised me. Agent 121 00:04:37,009 --> 00:04:37,509 ID 122 00:04:37,889 --> 00:04:40,209 or agent ID. Agent ID is not it. 123 00:04:40,209 --> 00:04:41,750 Agent $3.65 124 00:04:42,050 --> 00:04:43,410 is a $15 125 00:04:43,410 --> 00:04:44,629 a month add on. 126 00:04:45,170 --> 00:04:46,470 That to me, 127 00:04:46,850 --> 00:04:48,850 I'm maybe there's gonna be some more stuff 128 00:04:48,850 --> 00:04:50,574 that comes out in the next month. I 129 00:04:50,574 --> 00:04:52,754 have a hard time digesting that 130 00:04:53,375 --> 00:04:55,474 based on what I've seen comparing 131 00:04:56,254 --> 00:04:58,414 a normal tenant versus a tenant with agent 132 00:04:58,414 --> 00:04:59,214 365 133 00:04:59,214 --> 00:05:00,814 because I do have it on in preview 134 00:05:00,814 --> 00:05:02,894 in mind. That was actually on a call 135 00:05:02,894 --> 00:05:04,920 with a client this morning, and we were 136 00:05:04,920 --> 00:05:06,680 talking about that. We pulled up our two 137 00:05:06,680 --> 00:05:09,800 admin centers together, like admin.microsoft.com, 138 00:05:09,800 --> 00:05:10,779 and we're comparing 139 00:05:11,399 --> 00:05:13,800 what he had versus what I had because, 140 00:05:13,800 --> 00:05:15,959 frankly, I kind of forgot what it looked 141 00:05:15,959 --> 00:05:19,480 like before Agent $380 142 00:05:19,480 --> 00:05:21,064 a month, I was struggling 143 00:05:21,764 --> 00:05:24,164 with the cost of this. Again, maybe there's 144 00:05:24,164 --> 00:05:25,225 more features coming, 145 00:05:25,604 --> 00:05:27,285 but it looked like to me it was 146 00:05:27,285 --> 00:05:30,185 really just a lot of data and reporting 147 00:05:30,324 --> 00:05:32,879 that's an Agent three sixty five, a few 148 00:05:32,879 --> 00:05:34,720 governance things that are in there, but you 149 00:05:34,720 --> 00:05:36,899 already have some of it in just normal 150 00:05:37,040 --> 00:05:40,639 Microsoft three sixty five. So it'll be interesting 151 00:05:40,639 --> 00:05:41,939 to see where that goes. 152 00:05:42,399 --> 00:05:44,720 The other thing with this that I have 153 00:05:44,720 --> 00:05:47,615 not been able to figure out is, does 154 00:05:47,615 --> 00:05:49,235 Agent three sixty five 155 00:05:49,535 --> 00:05:52,514 have to be licensed for every user 156 00:05:53,214 --> 00:05:54,274 that is 157 00:05:55,055 --> 00:05:56,514 touching an agent 158 00:05:56,894 --> 00:05:59,694 that's managed or governed by Agent three sixty 159 00:05:59,694 --> 00:06:01,800 five, or does it only have to be 160 00:06:01,800 --> 00:06:02,300 licensed 161 00:06:02,600 --> 00:06:03,500 by those 162 00:06:04,439 --> 00:06:05,979 admins that are using 163 00:06:06,759 --> 00:06:08,699 Agent three sixty five on the administrative 164 00:06:09,000 --> 00:06:11,879 side? Because Agent three sixty five is really 165 00:06:11,879 --> 00:06:12,620 a governance 166 00:06:13,115 --> 00:06:15,995 construct Very much so. Not really an end 167 00:06:15,995 --> 00:06:17,134 user focused thing. 168 00:06:17,514 --> 00:06:19,935 Some of the licensing gets phrased where 169 00:06:20,314 --> 00:06:22,014 every user that benefits 170 00:06:22,395 --> 00:06:24,715 from this service has to be licensed for 171 00:06:24,715 --> 00:06:27,159 it, which would push this to everybody. There's 172 00:06:27,159 --> 00:06:29,180 other ones that are, like, only the people 173 00:06:29,240 --> 00:06:31,339 actually doing the config, the administration. 174 00:06:32,199 --> 00:06:33,800 That type of stuff have to be licensed 175 00:06:33,800 --> 00:06:35,879 for it. And I haven't been able to 176 00:06:35,879 --> 00:06:38,634 decipher which boat this falls into where do 177 00:06:38,634 --> 00:06:40,314 you end up with e sevens for admins 178 00:06:40,314 --> 00:06:43,295 and e fives plus Copilot for everybody else, 179 00:06:43,435 --> 00:06:43,935 or 180 00:06:44,395 --> 00:06:46,955 how is this gonna shake out? Because $15 181 00:06:46,955 --> 00:06:49,115 a month for a client or client customer 182 00:06:49,274 --> 00:06:51,709 I have customers that are 8,000 employees. 183 00:06:52,649 --> 00:06:55,949 That's not an insignificant amount of money. Yeah. 184 00:06:57,689 --> 00:07:00,169 I wasn't able to parse it myself either. 185 00:07:00,169 --> 00:07:02,889 So like you said, per user, per maybe, 186 00:07:02,889 --> 00:07:05,245 like, number of agents, like, a particular user 187 00:07:05,245 --> 00:07:06,865 consumes. Because if you look across, 188 00:07:07,165 --> 00:07:09,805 I think, any large enterprise, you're probably gonna 189 00:07:09,805 --> 00:07:11,884 have folks who use these things even if 190 00:07:11,884 --> 00:07:13,904 they're licensed for them and those who don't, 191 00:07:14,125 --> 00:07:17,024 and you're gonna have varying levels of consumption 192 00:07:17,084 --> 00:07:19,099 there. So I know, like, across 193 00:07:19,479 --> 00:07:21,159 the folks that I work with, I'll start 194 00:07:21,159 --> 00:07:23,740 with, like, kind of like my hyperlocal team, 195 00:07:23,800 --> 00:07:25,019 a lot of us use 196 00:07:25,800 --> 00:07:27,500 things like WorkIQ. 197 00:07:28,039 --> 00:07:29,099 We use M365 198 00:07:29,800 --> 00:07:31,740 Copilot with lots of 199 00:07:32,074 --> 00:07:34,634 modes in there. Like, I have access to 200 00:07:34,634 --> 00:07:36,634 both when I use, like, the researcher agent, 201 00:07:36,634 --> 00:07:38,955 I have built access to GPT five and 202 00:07:38,955 --> 00:07:39,455 Claude. 203 00:07:40,235 --> 00:07:42,555 We're all in this mode of kinda trying 204 00:07:42,555 --> 00:07:44,654 to sometimes, I think, emulate 205 00:07:45,300 --> 00:07:48,180 other features that exist in other properties. So, 206 00:07:48,180 --> 00:07:50,339 like, one of the interesting things here is 207 00:07:50,339 --> 00:07:53,959 Copilot Cowork, which is built on anthropics 208 00:07:54,419 --> 00:07:57,220 or Claude Cowork. Okay. So Claude Cowork is 209 00:07:57,220 --> 00:07:59,300 really cool. I'm actually kind of excited to 210 00:07:59,300 --> 00:08:01,185 see that and have that. But if I'm 211 00:08:01,185 --> 00:08:03,904 using Claude Cowork, is that, like, one thing 212 00:08:03,904 --> 00:08:05,824 that I'm using, or is that all the 213 00:08:05,824 --> 00:08:08,704 underlying subtasks and sub agents that I push 214 00:08:08,704 --> 00:08:11,664 out? Because, like, hey. In Claude Cowork, I 215 00:08:11,664 --> 00:08:13,930 can do things like go into this folder 216 00:08:13,930 --> 00:08:16,089 on my desktop and re and read the 217 00:08:16,089 --> 00:08:18,810 contents of these PDFs and rename them all 218 00:08:18,810 --> 00:08:20,649 in this format, blah blah blah. And it 219 00:08:20,649 --> 00:08:21,689 can touch out and it can do that. 220 00:08:21,689 --> 00:08:22,649 And I can have it spider out and 221 00:08:22,649 --> 00:08:24,490 do all sorts of weird things. I'm wondering 222 00:08:24,490 --> 00:08:26,009 if m three sixty five co works and 223 00:08:26,009 --> 00:08:27,764 do the same thing, but then then, you 224 00:08:27,764 --> 00:08:30,264 know, I become a heavy consumer of agentic 225 00:08:30,404 --> 00:08:30,904 experiences 226 00:08:31,205 --> 00:08:32,884 where the person who's sitting next to me 227 00:08:32,884 --> 00:08:35,125 who maybe doesn't need these things realize them, 228 00:08:35,125 --> 00:08:37,605 that value is not inflicted upon them to 229 00:08:37,605 --> 00:08:39,144 go ahead and pick them up. 230 00:08:39,684 --> 00:08:41,519 Like, are you gonna have to license them 231 00:08:41,519 --> 00:08:43,040 and have them come through just because they're 232 00:08:43,040 --> 00:08:45,040 part of the organization and because they opened 233 00:08:45,040 --> 00:08:47,840 up Microsoft three sixty five Copilot once? I 234 00:08:47,840 --> 00:08:49,519 don't know. But we'll see. It's gonna be 235 00:08:49,519 --> 00:08:50,980 a really weird time at TrueUp 236 00:08:51,920 --> 00:08:53,924 when these things come through. Yeah. I 237 00:08:54,404 --> 00:08:57,365 missed the Copilot co work that's coming as 238 00:08:57,365 --> 00:09:00,105 I was reading through these too. That'll be 239 00:09:00,964 --> 00:09:03,365 interesting because that, yeah, brings in some of 240 00:09:03,365 --> 00:09:04,904 the multi step tasks. 241 00:09:05,445 --> 00:09:07,845 I'm still waiting. I don't see anything about 242 00:09:07,845 --> 00:09:09,205 it in here. I should look for this 243 00:09:09,205 --> 00:09:11,180 article or or look through here. Chat and 244 00:09:11,180 --> 00:09:13,660 Copilot, agents and chat. MC I was looking 245 00:09:13,660 --> 00:09:15,500 for MCPs to see if there was any 246 00:09:15,500 --> 00:09:18,379 updates in MCPs, and it's only mentioned once 247 00:09:18,379 --> 00:09:19,120 in here. 248 00:09:19,660 --> 00:09:21,040 Where it's chat and Copilot, 249 00:09:21,420 --> 00:09:23,740 agents for Word, Excel, PowerPoint, Outlook, let you 250 00:09:23,740 --> 00:09:26,294 move into app native work with agents in 251 00:09:26,294 --> 00:09:29,095 Copilot supporting open standards like agent SDK and 252 00:09:29,095 --> 00:09:31,654 MCP apps. Agents and Copilot. I mean, you 253 00:09:31,654 --> 00:09:33,975 can kind of already do MCPs and agents. 254 00:09:33,975 --> 00:09:35,495 Well, you can do agents. You can't do 255 00:09:35,495 --> 00:09:37,815 MCPs and Copilot. Can't you do like, if 256 00:09:37,815 --> 00:09:39,035 you go build an agent 257 00:09:39,379 --> 00:09:41,720 in Studio, you can incorporate MCPs? 258 00:09:42,100 --> 00:09:43,460 If I build it in Studio, but I 259 00:09:43,460 --> 00:09:45,940 think that's a very different experience because then 260 00:09:45,940 --> 00:09:48,259 we're talking then we're talking about Copilot Studio, 261 00:09:48,259 --> 00:09:50,259 not m three sixty five Copilot, not to 262 00:09:50,259 --> 00:09:52,580 be confused with Microsoft Copilot. We got a 263 00:09:52,580 --> 00:09:54,200 lot of Copilots here. Like, 264 00:09:54,665 --> 00:09:56,985 it's it's Oprah has handed them Planes only 265 00:09:56,985 --> 00:09:59,225 have one Copilot. Why do we need, like, 266 00:09:59,225 --> 00:10:02,264 20 Copilots for working? Because more agents, more 267 00:10:02,264 --> 00:10:04,264 money, I guess. We'll see where that goes. 268 00:10:04,264 --> 00:10:06,184 I'm still like, I would really like to 269 00:10:06,184 --> 00:10:09,200 see both OpenAI with Chat GPT on the 270 00:10:09,200 --> 00:10:10,340 desktop and 271 00:10:10,799 --> 00:10:11,299 Microsoft. 272 00:10:11,600 --> 00:10:13,779 They'll bring in the ability to integrate 273 00:10:14,559 --> 00:10:15,059 MCPs 274 00:10:15,679 --> 00:10:17,679 with the native chat experiences. I think that 275 00:10:17,679 --> 00:10:19,840 would be a big win and low hanging 276 00:10:19,840 --> 00:10:22,980 fruit, especially if you're doing things like 277 00:10:23,414 --> 00:10:24,634 Claude Cowork style 278 00:10:25,014 --> 00:10:27,815 now with Copilot Cowork. Like, that would be 279 00:10:27,815 --> 00:10:30,615 a really powerful thing. Not just go read 280 00:10:30,615 --> 00:10:32,455 all these PDFs and renaming them in this 281 00:10:32,455 --> 00:10:35,195 format, but maybe go read all these PDFs, 282 00:10:35,720 --> 00:10:37,800 rename them in this format. And then once 283 00:10:37,800 --> 00:10:39,960 you've done that, create an inventory of them 284 00:10:39,960 --> 00:10:42,059 and go create a Power BI report 285 00:10:42,440 --> 00:10:42,940 or 286 00:10:43,320 --> 00:10:44,460 go and 287 00:10:44,920 --> 00:10:47,580 update this system over here with this information, 288 00:10:47,879 --> 00:10:48,379 you 289 00:10:48,680 --> 00:10:51,004 know, depending on the the connectivity and things 290 00:10:51,004 --> 00:10:52,524 that are out there and available to you, 291 00:10:52,524 --> 00:10:54,365 or heck, just to, like, be able to 292 00:10:54,365 --> 00:10:58,365 extend the the capabilities of these LLM driven 293 00:10:58,365 --> 00:11:00,945 experiences. We think about, like, remote MCPs 294 00:11:01,325 --> 00:11:03,245 and things like you and I, like, in 295 00:11:03,245 --> 00:11:05,730 our day to day, both use the Microsoft 296 00:11:05,789 --> 00:11:08,429 Learn MCP server and have that integrated in. 297 00:11:08,429 --> 00:11:10,350 Like, hey. It's there. It's available. I would 298 00:11:10,350 --> 00:11:12,509 love to have that in just a native 299 00:11:12,509 --> 00:11:15,309 Copilot chat and be able to augment things, 300 00:11:15,309 --> 00:11:15,809 like, 301 00:11:16,190 --> 00:11:18,334 in my worlds. Hey. If I'm writing 302 00:11:18,955 --> 00:11:21,214 a a product requirements document like a PRD, 303 00:11:21,434 --> 00:11:22,714 it would be super cool if I could 304 00:11:22,714 --> 00:11:25,914 not only have that PRD, like, evaluate it 305 00:11:25,914 --> 00:11:28,475 for tone and grammar and correctness and things 306 00:11:28,475 --> 00:11:30,235 like that. Wouldn't it be, like, nifty if 307 00:11:30,235 --> 00:11:32,334 I could bounce a PRD across 308 00:11:32,759 --> 00:11:35,559 and up against, like, public documentation to see 309 00:11:35,559 --> 00:11:37,080 maybe where I'm right, where I'm wrong, where 310 00:11:37,080 --> 00:11:39,480 I'm breaking something, especially if I'm thinking about 311 00:11:39,480 --> 00:11:41,960 an ideating experience that builds on top of 312 00:11:41,960 --> 00:11:45,100 existing functionality or constructs? Like, today, 313 00:11:45,424 --> 00:11:47,184 I can do that, but I have to 314 00:11:47,184 --> 00:11:49,504 build a custom experience to do it or 315 00:11:49,504 --> 00:11:50,944 rely on somebody else to build me a 316 00:11:50,944 --> 00:11:52,544 custom experience to do it. It'd be kinda 317 00:11:52,544 --> 00:11:54,564 cool if that stuff was just, like, their 318 00:11:54,704 --> 00:11:56,704 native baked in ready to go. So I 319 00:11:56,704 --> 00:11:58,509 think there's the it's all to say there's 320 00:11:58,509 --> 00:12:00,110 a lot more integration points that they can 321 00:12:00,110 --> 00:12:01,970 do with m three sixty five Copilot 322 00:12:02,350 --> 00:12:05,309 and the desktop experience of it and just 323 00:12:05,309 --> 00:12:07,389 the declarative agents. And I think they could 324 00:12:07,389 --> 00:12:08,769 open up a whole ecosystem 325 00:12:09,230 --> 00:12:12,764 of consumption, like, just raw consumption. If they've 326 00:12:13,004 --> 00:12:15,245 Oh, yeah. If that's what the game is, 327 00:12:15,245 --> 00:12:18,465 raw consumption and being able to offer customers 328 00:12:18,524 --> 00:12:19,345 these experiences 329 00:12:19,725 --> 00:12:22,445 at their expense, like, hey. We're paying for 330 00:12:22,445 --> 00:12:24,384 licensing, potentially add ons, 331 00:12:24,820 --> 00:12:27,299 Even without, like, opportunities to expand into, like, 332 00:12:27,299 --> 00:12:29,700 PAYGo or, like, burst pricing, should I go 333 00:12:29,700 --> 00:12:31,799 beyond a certain limit or should my organization? 334 00:12:31,860 --> 00:12:33,940 Like, I think there's a lot of runway 335 00:12:33,940 --> 00:12:36,740 there to just introduce experiences. So, like, this 336 00:12:36,740 --> 00:12:38,579 starts to open it up a little bit, 337 00:12:38,579 --> 00:12:40,455 but I don't know. Like you, I was 338 00:12:40,455 --> 00:12:42,875 looking maybe for, like, different things and different 339 00:12:42,934 --> 00:12:45,355 enablers in there for getting it going. 340 00:12:51,014 --> 00:12:53,340 This episode is brought to you by Trusted 341 00:12:53,340 --> 00:12:56,299 Tech. If you're managing Microsoft three sixty five, 342 00:12:56,299 --> 00:12:59,419 you already know licensing isn't simple. E three 343 00:12:59,419 --> 00:13:01,500 versus e five, the brand new e seven 344 00:13:01,500 --> 00:13:05,179 licenses, Copilot security bundles, and with price changes 345 00:13:05,179 --> 00:13:07,125 coming in July 2026, 346 00:13:07,284 --> 00:13:10,085 the stakes are getting higher. Trusted Tech helps 347 00:13:10,085 --> 00:13:12,644 IT leaders make sense of their Microsoft three 348 00:13:12,644 --> 00:13:15,544 sixty five environment with a free licensing consultation. 349 00:13:16,004 --> 00:13:18,804 Their engineers analyze what you're licensed for and 350 00:13:18,804 --> 00:13:21,205 what you're actually using and where you can 351 00:13:21,205 --> 00:13:21,705 optimize, 352 00:13:22,070 --> 00:13:25,350 whether that means consolidating security tools, preparing for 353 00:13:25,350 --> 00:13:29,509 copilot, or eliminating wasted spend. Plus, they offer 354 00:13:29,509 --> 00:13:32,789 proactive and reactive support, which has been awarded 355 00:13:32,789 --> 00:13:35,850 yet another solution partner designation from Microsoft 356 00:13:36,389 --> 00:13:37,850 for support services. 357 00:13:38,285 --> 00:13:40,625 If you want a clear, data backed plan 358 00:13:40,764 --> 00:13:43,004 that has helped over 7,500 359 00:13:43,004 --> 00:13:43,504 subscribing 360 00:13:43,805 --> 00:13:46,605 customers save up to 20% on Microsoft three 361 00:13:46,605 --> 00:13:56,230 sixty five before your next renewal, visit trustedtech.team/mscloudprom365 362 00:13:56,230 --> 00:13:58,250 and schedule your free consultation 363 00:13:58,629 --> 00:13:59,129 today. 364 00:14:04,235 --> 00:14:06,235 We're getting away a little bit from our 365 00:14:06,235 --> 00:14:08,894 e seven, but if I was gonna give 366 00:14:09,195 --> 00:14:11,195 say what you will about responses. Right? Like, 367 00:14:11,195 --> 00:14:13,355 we could talk all day about our Chad 368 00:14:13,355 --> 00:14:16,555 GPT's response is better, our Claude's response is 369 00:14:16,555 --> 00:14:19,139 better, Copilot better, all of that. Just from 370 00:14:19,139 --> 00:14:19,879 a pure 371 00:14:20,419 --> 00:14:23,460 technology enablement perspective, if I was gonna give 372 00:14:23,460 --> 00:14:25,379 one area where I feel like Copilot is 373 00:14:25,379 --> 00:14:27,240 falling way behind, it's 374 00:14:27,620 --> 00:14:30,980 that right there. The easy integration of MCP 375 00:14:30,980 --> 00:14:32,120 servers and allowing 376 00:14:32,659 --> 00:14:33,399 end users. 377 00:14:33,779 --> 00:14:35,355 And, again, I get you still would need 378 00:14:35,355 --> 00:14:38,315 some governance controls in place because enterprises don't 379 00:14:38,315 --> 00:14:40,235 want their users just going out connecting to 380 00:14:40,235 --> 00:14:42,634 any MCP server. But, hey, Agent three sixty 381 00:14:42,634 --> 00:14:44,394 five is there. You can build that control 382 00:14:44,394 --> 00:14:46,154 plane. Like like, the ability to build that 383 00:14:46,154 --> 00:14:48,875 exists within the ecosystem. Figuring out how to 384 00:14:48,875 --> 00:14:49,375 integrate 385 00:14:49,779 --> 00:14:52,360 MCP servers into Microsoft three sixty five chat, 386 00:14:52,419 --> 00:14:54,580 that is one of it's not the only, 387 00:14:54,580 --> 00:14:56,740 but it's the number one re one of 388 00:14:56,740 --> 00:14:58,360 the top reasons I will 389 00:14:58,740 --> 00:15:01,299 flip over to Claude from Microsoft three sixty 390 00:15:01,299 --> 00:15:03,375 five is because of I have up to, 391 00:15:03,375 --> 00:15:05,774 like, 11 or 12 MCP servers now. Control 392 00:15:05,774 --> 00:15:08,835 plane governance idea for Microsoft is 393 00:15:09,294 --> 00:15:11,695 build a control plane and build the capability 394 00:15:11,695 --> 00:15:13,615 to put MCPs in m three sixty five 395 00:15:13,615 --> 00:15:14,115 Copilot. 396 00:15:14,549 --> 00:15:16,549 Leave it, like, so it's wide open and 397 00:15:16,549 --> 00:15:18,950 it can be locked down, and enterprises can 398 00:15:18,950 --> 00:15:19,769 push MCPs 399 00:15:20,149 --> 00:15:22,330 to certain, like, business organizations 400 00:15:22,710 --> 00:15:23,690 with known configurations. 401 00:15:24,389 --> 00:15:26,870 So like you said, given the operational control, 402 00:15:26,870 --> 00:15:29,545 like, oh, hey. You can play with the, 403 00:15:29,764 --> 00:15:31,545 I don't know, you can play with 404 00:15:31,924 --> 00:15:34,804 the Azure MCP server, which has hundreds of 405 00:15:34,804 --> 00:15:37,524 tools in it, but only people in this 406 00:15:37,524 --> 00:15:40,485 division or this business team or with this 407 00:15:40,485 --> 00:15:41,304 set of responsibilities 408 00:15:41,684 --> 00:15:43,580 get it, and we're gonna preconfigure it for 409 00:15:43,580 --> 00:15:46,700 you. So authentication's gonna be locked in, all 410 00:15:46,700 --> 00:15:48,700 those kinds of things. Or I can't think 411 00:15:48,700 --> 00:15:50,139 of a good example off my head, but, 412 00:15:50,139 --> 00:15:51,980 like, the Kusto MCP, you can configure a 413 00:15:51,980 --> 00:15:53,980 bunch of, like, Kusto MCP servers in it. 414 00:15:53,980 --> 00:15:55,500 Same thing. Like, I'm gonna push this down 415 00:15:55,500 --> 00:15:57,254 to you, and you're only gonna be allowed 416 00:15:57,254 --> 00:15:59,894 to connect to these Kusto servers, not these 417 00:15:59,894 --> 00:16:02,054 other ones through these kinds of things. Right. 418 00:16:02,054 --> 00:16:03,495 And I think if Microsoft was to do 419 00:16:03,495 --> 00:16:04,955 that, it would actually probably 420 00:16:05,335 --> 00:16:07,995 do some interesting things in the MCP ecosystem. 421 00:16:08,455 --> 00:16:10,375 I wonder if it would actually lead to, 422 00:16:10,375 --> 00:16:12,554 like, a collaboration opportunity with Anthropic 423 00:16:12,860 --> 00:16:16,060 to bring in, like, additional operational controls or, 424 00:16:16,060 --> 00:16:17,040 like, extensions 425 00:16:17,500 --> 00:16:19,580 to that protocol to be able to make 426 00:16:19,580 --> 00:16:21,420 those things Yeah. A little bit easier. You 427 00:16:21,420 --> 00:16:23,180 know what else this would help with? We 428 00:16:23,180 --> 00:16:24,954 may have talked about this before too. We 429 00:16:24,954 --> 00:16:27,274 would not need 20 or 30 or 40 430 00:16:27,274 --> 00:16:30,414 Copilots. We would have one Copilot with MCPs. 431 00:16:30,954 --> 00:16:33,514 And then Azure Storage, you can go build 432 00:16:33,514 --> 00:16:35,914 your MCP. Security team, you go build an 433 00:16:35,914 --> 00:16:38,634 MCP. Sentinel, you go build an MCP. Let's 434 00:16:38,634 --> 00:16:39,534 not reinvent 435 00:16:40,059 --> 00:16:40,559 Copilot 436 00:16:41,019 --> 00:16:43,980 50 times. Let's create one Copilot, make it 437 00:16:43,980 --> 00:16:46,000 extensible, governable, manageable, 438 00:16:46,379 --> 00:16:46,879 configurable 439 00:16:47,660 --> 00:16:50,139 from an MCP perspective, and let all these 440 00:16:50,139 --> 00:16:52,139 different teams build MCP servers that you tie 441 00:16:52,139 --> 00:16:54,384 into your Copilot. Scott, we should go work 442 00:16:54,384 --> 00:16:55,205 for Microsoft, 443 00:16:55,745 --> 00:16:57,825 go fix this, and then quit six months 444 00:16:57,825 --> 00:16:59,384 later. Have you seen that meme? There's lots 445 00:16:59,384 --> 00:17:00,705 of things that I would like to do. 446 00:17:00,705 --> 00:17:02,545 And as a PM at Microsoft, I can 447 00:17:02,545 --> 00:17:04,144 tell you it's not that easy. I wish 448 00:17:04,144 --> 00:17:06,190 it was. Like, I I would love to 449 00:17:06,190 --> 00:17:08,109 wave my magic wand in a couple of 450 00:17:08,109 --> 00:17:10,589 these areas. And it's easy to Do all 451 00:17:10,589 --> 00:17:12,829 the things. Armchair design on it, but it 452 00:17:12,829 --> 00:17:14,529 does leave interesting opportunities 453 00:17:14,829 --> 00:17:16,049 to kind of continue 454 00:17:16,349 --> 00:17:19,149 to extend it out. I do wonder, like, 455 00:17:19,149 --> 00:17:21,335 as this kind of keeps coming, so you 456 00:17:21,335 --> 00:17:22,875 think about things like WorkIQ, 457 00:17:23,254 --> 00:17:26,315 Agent three sixty five, Copilot integrations 458 00:17:26,774 --> 00:17:29,894 within the Office Suite, like Excel, Word, things 459 00:17:29,894 --> 00:17:32,294 like that. Is this where it stops or 460 00:17:32,294 --> 00:17:34,140 is this, like, the start to some of 461 00:17:34,140 --> 00:17:37,500 these licensing experiences? So, like, is m three 462 00:17:37,500 --> 00:17:40,859 sixty five E seven kinda like the stopping 463 00:17:40,859 --> 00:17:42,619 point or then do you still get a 464 00:17:42,619 --> 00:17:44,539 bunch of add ons and other things in 465 00:17:44,539 --> 00:17:45,440 it? Because, 466 00:17:45,820 --> 00:17:47,259 I mean, if you think about it, like 467 00:17:47,259 --> 00:17:47,759 OpenAI, 468 00:17:48,460 --> 00:17:48,960 Claude, 469 00:17:49,355 --> 00:17:53,134 they're charging $200 a month for their professional 470 00:17:53,195 --> 00:17:55,355 ones, and those are just for access to 471 00:17:55,355 --> 00:17:57,674 the LLMs and the underlying functionality, like these 472 00:17:57,674 --> 00:17:59,835 agentic experiences, things like that, really, in, like, 473 00:17:59,835 --> 00:18:02,075 Microsoft land. You're getting the Office Suite. You're 474 00:18:02,075 --> 00:18:05,210 getting all the identity, all the governance, all 475 00:18:05,210 --> 00:18:08,390 the management that comes from Entra and Intune, 476 00:18:08,609 --> 00:18:09,109 SharePoint, 477 00:18:09,410 --> 00:18:12,470 Exchange, these different things. Like, it still feels 478 00:18:12,690 --> 00:18:13,190 like 479 00:18:13,490 --> 00:18:15,250 there's other room in there too. Like, I 480 00:18:15,250 --> 00:18:17,575 wouldn't be surprised if this is kinda the 481 00:18:17,575 --> 00:18:18,555 end versus 482 00:18:19,015 --> 00:18:20,455 the start. You don't think they're gonna keep 483 00:18:20,455 --> 00:18:21,815 going with an e nine? I don't think 484 00:18:21,815 --> 00:18:23,914 this is the end of the licensing conundrum. 485 00:18:24,055 --> 00:18:26,215 Like, it will not stop at $99 a 486 00:18:26,215 --> 00:18:29,035 month. It won't stop. No. 100%. 487 00:18:29,095 --> 00:18:30,855 It'll keep going up. And I was 488 00:18:31,369 --> 00:18:32,890 again, I was talking to a client about 489 00:18:32,890 --> 00:18:35,529 this morning, and I was surprised they were 490 00:18:35,529 --> 00:18:36,029 not 491 00:18:36,730 --> 00:18:38,570 like, they saw this, and they were not, 492 00:18:38,570 --> 00:18:40,250 oh, no. There's no way we're doing that. 493 00:18:40,250 --> 00:18:43,049 It was a we're already paying $60 for 494 00:18:43,049 --> 00:18:44,670 e five and 30 for Copilot, 495 00:18:45,289 --> 00:18:45,789 and 496 00:18:46,170 --> 00:18:46,670 this 497 00:18:47,284 --> 00:18:50,244 governance question comes up more and more with 498 00:18:50,244 --> 00:18:52,724 everybody creating agents and the ability to create 499 00:18:52,724 --> 00:18:55,125 agents is this $99 500 00:18:55,125 --> 00:18:57,065 a month does not feel 501 00:18:57,684 --> 00:19:00,080 unreasonable for what you get. Again, I would 502 00:19:00,080 --> 00:19:02,019 like to see a little bit more 503 00:19:02,640 --> 00:19:03,140 functionality 504 00:19:03,599 --> 00:19:04,259 come out 505 00:19:04,640 --> 00:19:07,039 in Agent three sixty five, and it's still 506 00:19:07,039 --> 00:19:09,840 in preview. It we very well may see 507 00:19:09,840 --> 00:19:11,700 that particular product 508 00:19:12,080 --> 00:19:14,320 to continue to evolve or even in the 509 00:19:14,320 --> 00:19:17,414 next, what? It's March. We have March, April. 510 00:19:17,414 --> 00:19:19,255 We have two more months. There may be 511 00:19:19,255 --> 00:19:20,934 some stuff they're working on that's gonna pop 512 00:19:20,934 --> 00:19:22,535 up in there in the next couple months 513 00:19:22,535 --> 00:19:24,875 that really help because they do say 514 00:19:25,174 --> 00:19:27,414 Agent three sixty five. There's a we'll put 515 00:19:27,414 --> 00:19:28,695 the link in the show notes. There's a 516 00:19:28,695 --> 00:19:30,400 nice table they have in there where you're 517 00:19:30,400 --> 00:19:33,200 getting observe, monitor, and manage agents in real 518 00:19:33,200 --> 00:19:36,079 time. You're getting governed agents through their life 519 00:19:36,079 --> 00:19:36,579 cycle, 520 00:19:36,880 --> 00:19:39,200 and you're getting secure and protect all agents 521 00:19:39,200 --> 00:19:42,000 across your enterprise with Agent three sixty five. 522 00:19:42,000 --> 00:19:43,460 Those are kind of the three 523 00:19:43,845 --> 00:19:44,585 things you're 524 00:19:45,125 --> 00:19:47,365 getting with that particular product. And then, again, 525 00:19:47,365 --> 00:19:49,285 they throw in that chart, the Entra Suite 526 00:19:49,285 --> 00:19:51,125 for $12 a month and say, oh, look. 527 00:19:51,125 --> 00:19:52,244 It's only 99. 528 00:19:52,244 --> 00:19:53,924 If you're listening to this, ignore the Entra 529 00:19:53,924 --> 00:19:55,845 Suite. It's gonna be bundled in the $60 530 00:19:55,845 --> 00:19:58,690 one anyways. It's devils in the details there. 531 00:19:58,690 --> 00:20:01,089 You mentioned kinda talking about this maybe with 532 00:20:01,089 --> 00:20:02,309 a couple customers. 533 00:20:02,690 --> 00:20:03,349 I was 534 00:20:03,890 --> 00:20:05,990 maybe a little bit surprised by 535 00:20:06,450 --> 00:20:08,450 the phrasing or positioning of this. Like, I 536 00:20:08,450 --> 00:20:09,750 could have seen this as 537 00:20:10,065 --> 00:20:12,865 Microsoft three sixty five e seven, like, the 538 00:20:12,865 --> 00:20:15,424 ultimate enterprise suite or whatever it happened to 539 00:20:15,424 --> 00:20:18,304 be. And it was it's being framed as 540 00:20:18,304 --> 00:20:20,464 the frontier workers suite. So when I think 541 00:20:20,464 --> 00:20:23,410 about, like, the phrasing of Frontier in AI 542 00:20:23,410 --> 00:20:26,789 land, primarily, that's been positioned around the Frontier 543 00:20:26,850 --> 00:20:30,289 AI companies, the Frontier models like chat g 544 00:20:30,289 --> 00:20:32,150 p like OpenAI training 545 00:20:32,609 --> 00:20:33,830 GPT and 546 00:20:34,369 --> 00:20:36,815 Anthropic training Claude, things like that. Like, there's 547 00:20:36,815 --> 00:20:37,795 only a handful 548 00:20:38,255 --> 00:20:41,375 of frontier models out there and frontier model 549 00:20:41,375 --> 00:20:43,055 trainers. I kinda looked at that. I was 550 00:20:43,055 --> 00:20:45,215 like, oh, is this targeted just at those 551 00:20:45,215 --> 00:20:47,055 companies? Like, that was weird to me in 552 00:20:47,055 --> 00:20:49,579 my head. And I guess it's being positioned 553 00:20:49,579 --> 00:20:50,399 as companies 554 00:20:50,779 --> 00:20:54,240 on the frontier of consumption of AI experiences, 555 00:20:54,539 --> 00:20:57,579 which is also an interesting way to kind 556 00:20:57,579 --> 00:20:58,079 of 557 00:20:58,380 --> 00:20:59,980 frame it. I don't know. If you put 558 00:20:59,980 --> 00:21:01,179 it out there and buy it for yourselves, 559 00:21:01,179 --> 00:21:03,734 like, do you consider yourself on the cutting 560 00:21:03,734 --> 00:21:06,295 edge, or do you just consider yourself, like, 561 00:21:06,295 --> 00:21:08,555 hey. Like you said, it's easy to rationalize 562 00:21:08,694 --> 00:21:10,375 the pricing for these things if I'm already 563 00:21:10,375 --> 00:21:13,095 paying 60 here, 90 here, 10 here kinda 564 00:21:13,095 --> 00:21:14,934 thing. You get to the price pretty quick. 565 00:21:14,934 --> 00:21:17,179 I didn't think too much about the phrasing 566 00:21:17,179 --> 00:21:19,339 of it. I kinda glanced at it. I 567 00:21:19,339 --> 00:21:20,799 saw the frontier transformations. 568 00:21:21,740 --> 00:21:23,819 As you're talking about it, I think it 569 00:21:23,819 --> 00:21:24,319 is 570 00:21:24,700 --> 00:21:25,200 absolutely 571 00:21:26,539 --> 00:21:29,339 confusing for a couple reasons. One, what you 572 00:21:29,339 --> 00:21:32,240 said. They say in this article, frontier transformation 573 00:21:32,460 --> 00:21:34,595 starts with a simple idea. AI must do 574 00:21:34,595 --> 00:21:37,154 more than optimize what already exists, unlocking new 575 00:21:37,154 --> 00:21:39,875 levels of creativity, innovation, and growth. So I 576 00:21:39,875 --> 00:21:42,595 think in here, they're maybe thinking about it 577 00:21:42,595 --> 00:21:43,734 as unlocking 578 00:21:44,755 --> 00:21:45,414 the next 579 00:21:46,274 --> 00:21:48,960 level of AI in a company. But to 580 00:21:48,960 --> 00:21:51,279 me, it also gets confusing is have you 581 00:21:51,279 --> 00:21:54,240 seen that in Copilot, you also have the 582 00:21:54,240 --> 00:21:54,740 Frontier 583 00:21:55,200 --> 00:21:55,700 program 584 00:21:56,000 --> 00:21:56,659 in Copilot, 585 00:21:57,200 --> 00:21:58,419 which is essentially 586 00:21:58,720 --> 00:22:00,579 the beta preview 587 00:22:01,394 --> 00:22:01,894 features 588 00:22:02,355 --> 00:22:04,375 of Copilot. So when they come out 589 00:22:04,994 --> 00:22:08,295 with different agents or different innovations within Copilot, 590 00:22:08,674 --> 00:22:11,394 it goes from, like, I guess, maybe private 591 00:22:11,394 --> 00:22:13,974 preview, whatever comes before public availability, 592 00:22:14,595 --> 00:22:16,695 then it comes to the Frontier program. 593 00:22:17,000 --> 00:22:19,480 So if you can go, like, get signed 594 00:22:19,480 --> 00:22:21,960 up for the Frontier experiences, which is just 595 00:22:21,960 --> 00:22:23,820 a fancy way of saying beta experiences 596 00:22:24,440 --> 00:22:26,920 for preview. I think about it as like 597 00:22:26,920 --> 00:22:29,160 the old TAP programs, like technology. I think 598 00:22:29,160 --> 00:22:30,539 technology access previews 599 00:22:30,984 --> 00:22:32,984 was what those were. Yeah. Only I don't 600 00:22:32,984 --> 00:22:34,984 know that this is NDA as like the 601 00:22:34,984 --> 00:22:37,065 TAP stuff was. I think it's a little 602 00:22:37,065 --> 00:22:39,784 bit more accessible to the public, but that 603 00:22:39,784 --> 00:22:42,105 phrasing confuses me when I start when you 604 00:22:42,105 --> 00:22:44,365 start thinking about powering Frontier transformation. 605 00:22:45,039 --> 00:22:47,519 I think they're thinking about Frontier the same 606 00:22:47,519 --> 00:22:49,119 way in both of those as being kind 607 00:22:49,119 --> 00:22:51,299 of on the cutting edge, the leading edge, 608 00:22:51,680 --> 00:22:52,980 pushing everything forward, 609 00:22:53,279 --> 00:22:56,160 but it's still two different kind of programs 610 00:22:56,160 --> 00:22:57,220 where I think the terminology, 611 00:22:57,680 --> 00:22:59,515 it just gets confusing? I mean, I can 612 00:22:59,515 --> 00:23:01,755 put the mental mapping together, but it was 613 00:23:01,755 --> 00:23:04,154 a little interesting. Right? Like, if I'm if 614 00:23:04,154 --> 00:23:06,394 I'm the purchasing decision maker and I don't 615 00:23:06,394 --> 00:23:09,134 know what frontier models are, 616 00:23:09,595 --> 00:23:12,269 and I think that's just general phrasing of 617 00:23:12,330 --> 00:23:14,809 frontier versus early access and some of the 618 00:23:14,809 --> 00:23:16,570 other things that have been out there in 619 00:23:16,570 --> 00:23:18,170 the ecosystem for a long time. And maybe 620 00:23:18,170 --> 00:23:19,609 I'm just being like old man yells at 621 00:23:19,609 --> 00:23:21,289 cloud, right? I've got my gray hair and 622 00:23:21,289 --> 00:23:24,029 I'm curmudgeon, but it is a weird 623 00:23:24,330 --> 00:23:24,910 kind of 624 00:23:25,275 --> 00:23:26,715 positioning. I can see where it gets some, 625 00:23:26,715 --> 00:23:28,955 but I also wonder. We'll see where it 626 00:23:28,955 --> 00:23:31,195 goes. I'd be interested in hearing anecdotes as 627 00:23:31,195 --> 00:23:33,055 you're out there talking to more customers 628 00:23:33,434 --> 00:23:35,055 and seeing some of that stuff. 629 00:23:38,394 --> 00:23:40,634 Do you feel overwhelmed by trying to manage 630 00:23:40,634 --> 00:23:42,849 your Office three sixty five environment? Are you 631 00:23:42,849 --> 00:23:46,150 facing unexpected issues that disrupt your company's productivity? 632 00:23:46,450 --> 00:23:48,369 Intelligink is here to help. Much like you 633 00:23:48,369 --> 00:23:50,289 take your car to the mechanic that has 634 00:23:50,289 --> 00:23:52,369 specialized knowledge on how to best keep your 635 00:23:52,369 --> 00:23:53,025 car running, 636 00:23:53,424 --> 00:23:56,224 Intelligink helps you with your Microsoft cloud environment 637 00:23:56,224 --> 00:23:57,684 because that's their expertise. 638 00:23:58,065 --> 00:24:00,384 Intelligink keeps up with the latest updates in 639 00:24:00,384 --> 00:24:02,545 the Microsoft cloud to help keep your business 640 00:24:02,545 --> 00:24:04,785 running smoothly and ahead of the curve. Whether 641 00:24:04,785 --> 00:24:06,865 you are a small organization with just a 642 00:24:06,865 --> 00:24:09,179 few users up to an organization of several 643 00:24:09,179 --> 00:24:10,319 thousand employees, 644 00:24:10,619 --> 00:24:12,619 they want to partner with you to implement 645 00:24:12,619 --> 00:24:15,359 and administer your Microsoft cloud technology. 646 00:24:16,139 --> 00:24:19,599 Visit them at inteliginc.com/podcast. 647 00:24:19,899 --> 00:24:26,565 That's intelligink.com/podcast 648 00:24:26,944 --> 00:24:29,105 for more information or to schedule a thirty 649 00:24:29,105 --> 00:24:31,204 minute call to get started with them today. 650 00:24:31,424 --> 00:24:34,784 Remember, Intelligink focuses on the Microsoft cloud so 651 00:24:34,784 --> 00:24:36,480 you can focus on your business. 652 00:24:38,720 --> 00:24:40,559 I'll definitely keep you updated as I talk 653 00:24:40,559 --> 00:24:42,000 to people about it and see what people 654 00:24:42,000 --> 00:24:44,099 are saying about the Frontier 655 00:24:45,039 --> 00:24:45,539 transformation 656 00:24:46,000 --> 00:24:47,859 or the powering Frontier transformation, 657 00:24:48,160 --> 00:24:50,515 the new e seven licenses. I don't think 658 00:24:50,515 --> 00:24:52,595 there was anything else really in that article, 659 00:24:52,595 --> 00:24:55,414 multimodel intelligence, agent three sixty five. 660 00:24:56,115 --> 00:24:57,734 Yeah. The Frontier suite. 661 00:24:58,115 --> 00:24:59,554 Available May 1. I don't know. I think 662 00:24:59,554 --> 00:25:01,234 we mentioned that. That's when you'll be able 663 00:25:01,234 --> 00:25:02,990 to go get it, go buy it. But 664 00:25:02,990 --> 00:25:04,670 this kind of is all bundled in wave 665 00:25:04,670 --> 00:25:05,650 three. So 666 00:25:05,950 --> 00:25:07,950 I would also even if you're not interested 667 00:25:07,950 --> 00:25:09,950 in e seven, go read these articles that 668 00:25:09,950 --> 00:25:11,549 we'll post in here because it does talk 669 00:25:11,549 --> 00:25:14,830 about, like, wave three of Copilot and, like, 670 00:25:14,830 --> 00:25:17,234 the Copilot co work that you mentioned is 671 00:25:17,234 --> 00:25:19,414 not necessarily an e seven 672 00:25:19,795 --> 00:25:21,474 aspect to it. E seven was just kind 673 00:25:21,474 --> 00:25:24,295 of bundled in this article that talks about 674 00:25:24,434 --> 00:25:27,075 all the Wave three improvements to Microsoft three 675 00:25:27,075 --> 00:25:29,795 sixty five Copilot. I think there's some exciting 676 00:25:29,795 --> 00:25:31,795 things in there, and then there's also just 677 00:25:31,795 --> 00:25:34,640 the general churn and kind of pace that 678 00:25:34,640 --> 00:25:36,240 we're in right now. So one of the 679 00:25:36,240 --> 00:25:38,660 things that kinda got to me was 680 00:25:39,359 --> 00:25:40,960 and, you know, this is again, like, old 681 00:25:40,960 --> 00:25:43,119 maniels at cloud kinda thing, but it's still 682 00:25:43,119 --> 00:25:44,960 thinking back. And I don't think enterprises have 683 00:25:44,960 --> 00:25:46,559 changed this much where you still have to 684 00:25:46,559 --> 00:25:49,315 do, like, enterprise training programs, get people up 685 00:25:49,315 --> 00:25:51,015 to speed on here's 686 00:25:51,394 --> 00:25:54,294 Word, here's Excel. You hire a new, like, 687 00:25:54,355 --> 00:25:57,315 frontline worker, things like that. They kinda continue 688 00:25:57,315 --> 00:25:58,994 to play around with the names of things 689 00:25:58,994 --> 00:26:01,840 there. So if you look at Copilot within 690 00:26:02,460 --> 00:26:04,940 Word, Excel, PowerPoint, things like that, they've been 691 00:26:04,940 --> 00:26:07,340 on this journey of, like, Copilot there to 692 00:26:07,340 --> 00:26:09,820 Copilot agents, and now they're just kinda, like, 693 00:26:09,820 --> 00:26:10,559 built in. 694 00:26:10,940 --> 00:26:12,700 And that freeze and goes. And that all 695 00:26:12,700 --> 00:26:15,500 happened over the course of not too long. 696 00:26:15,500 --> 00:26:17,894 Like, you're not talking, like, a decade to 697 00:26:17,894 --> 00:26:20,134 get there. You're talking, like, a year to 698 00:26:20,134 --> 00:26:20,714 two years 699 00:26:21,015 --> 00:26:23,414 and potentially less time as that stuff turns 700 00:26:23,414 --> 00:26:25,654 around. That kinda struck me was, yes. You 701 00:26:25,654 --> 00:26:27,734 can go and empower your organizations with these 702 00:26:27,734 --> 00:26:29,335 things. Like, maybe you do. But I do 703 00:26:29,335 --> 00:26:31,595 wonder about, like, the human lift 704 00:26:32,029 --> 00:26:33,890 to get people to really understand 705 00:26:34,509 --> 00:26:37,549 these tools and how they work and, frankly, 706 00:26:37,549 --> 00:26:39,630 where the rough edges are versus, like, the 707 00:26:39,630 --> 00:26:42,909 real value within any given business. I think 708 00:26:42,909 --> 00:26:45,309 that's gonna still take some time to shake 709 00:26:45,309 --> 00:26:47,535 out. It was also interesting to see, and 710 00:26:47,535 --> 00:26:49,934 this is interesting given, like, the current climate 711 00:26:49,934 --> 00:26:51,695 in The US and things that are going 712 00:26:51,695 --> 00:26:53,394 on, some of the call outs 713 00:26:53,695 --> 00:26:54,195 and 714 00:26:54,575 --> 00:26:56,575 some of the additional work that they're doing 715 00:26:56,575 --> 00:26:58,595 to integrate Claude into 716 00:26:59,375 --> 00:27:01,330 more and more of the stack. So if 717 00:27:01,330 --> 00:27:03,330 you're an m three 65 customer today at 718 00:27:03,330 --> 00:27:05,410 a tenant level, you can kinda choose if 719 00:27:05,410 --> 00:27:08,930 you have access to anthropic models within within 720 00:27:08,930 --> 00:27:11,250 your tenant and within your deployments. So that's 721 00:27:11,250 --> 00:27:12,466 been there for a while. That that operational 722 00:27:12,466 --> 00:27:13,275 control, it's been 723 00:27:17,434 --> 00:27:19,994 interesting things wave three bought was or is 724 00:27:19,994 --> 00:27:23,295 bringing is claw just available in mainline chat. 725 00:27:23,434 --> 00:27:24,955 So, you know, if you've been following the 726 00:27:24,955 --> 00:27:26,315 news I saw that. So if you've been 727 00:27:26,315 --> 00:27:27,839 following the news in The United States, 728 00:27:28,240 --> 00:27:32,079 anthropic was declared a supply chain risk by 729 00:27:32,079 --> 00:27:33,539 the Department of Defense. 730 00:27:34,240 --> 00:27:38,019 And that has, like, downstream impacts of anthropic 731 00:27:38,240 --> 00:27:40,799 being able to be consumed within not only 732 00:27:40,799 --> 00:27:42,965 the Department of Defense, but also, like, broader 733 00:27:42,965 --> 00:27:45,144 US government and defense contractors 734 00:27:45,845 --> 00:27:48,965 and all sorts of things. Interesting that continues 735 00:27:48,965 --> 00:27:52,025 to, like, kinda steam ahead at least in 736 00:27:52,485 --> 00:27:53,545 regular Copilot. 737 00:27:54,005 --> 00:27:55,605 Now don't get me wrong. I'm very glad 738 00:27:55,605 --> 00:27:57,850 to see it there. I think the anthropic 739 00:27:57,910 --> 00:27:59,830 models are we talked about this. So if 740 00:27:59,830 --> 00:28:01,509 you're gonna spend $20 a month on on 741 00:28:01,509 --> 00:28:04,230 some AI thing, go by Claude. That's probably 742 00:28:04,230 --> 00:28:06,250 the best one. Does all the MCP integrations, 743 00:28:06,309 --> 00:28:08,870 but, also, the responses are very well tuned 744 00:28:08,870 --> 00:28:11,350 for, like, enterprise and business in a way 745 00:28:11,350 --> 00:28:12,525 that ChatGPT 746 00:28:13,065 --> 00:28:16,025 is not, and by extension, Copilot running the 747 00:28:16,025 --> 00:28:18,825 ChatGPT models is not as well. So I'm 748 00:28:18,825 --> 00:28:21,464 very excited to see Claude coming. Like, this 749 00:28:21,464 --> 00:28:23,144 makes me wanna go and just kinda keep, 750 00:28:23,144 --> 00:28:25,509 like, opening and closing the chat, the Microsoft 751 00:28:25,509 --> 00:28:27,269 three sixty five app and seeing if it 752 00:28:27,269 --> 00:28:28,089 becomes available 753 00:28:28,710 --> 00:28:29,690 a little earlier 754 00:28:30,069 --> 00:28:32,230 in the tenant that I play along with. 755 00:28:32,230 --> 00:28:33,750 So having that the other thing I don't 756 00:28:33,750 --> 00:28:35,829 know, having that model choice is, like, really 757 00:28:35,829 --> 00:28:37,589 cool to me. I do wonder about that 758 00:28:37,589 --> 00:28:39,269 for users, though. Like, are you gonna re 759 00:28:39,349 --> 00:28:42,784 really teach your people in finance, like, hey. 760 00:28:42,784 --> 00:28:44,865 When you're working with this Excel workbook, make 761 00:28:44,865 --> 00:28:46,464 sure you flip it to Claude. When you're 762 00:28:46,464 --> 00:28:48,704 working over here on this Word document, make 763 00:28:48,704 --> 00:28:50,144 sure you flip it to OpenAI. Oh, when 764 00:28:50,144 --> 00:28:51,504 you're working over here, make sure you not 765 00:28:51,504 --> 00:28:53,264 only flip it to OpenAI, but flip it 766 00:28:53,264 --> 00:28:54,390 to this model. Like, I don't know if 767 00:28:54,390 --> 00:28:55,990 it's gonna get that far, but that was 768 00:28:55,990 --> 00:28:56,490 always 769 00:28:56,789 --> 00:28:59,070 a little bit of friction and consumption of 770 00:28:59,190 --> 00:29:01,590 and kinda being able to pick up some 771 00:29:01,590 --> 00:29:04,950 of those things. So we shall see where 772 00:29:04,950 --> 00:29:06,009 this one goes. 773 00:29:06,325 --> 00:29:07,605 I imagine you're gonna go and buy this 774 00:29:07,605 --> 00:29:08,965 stuff and get hands on with it, so 775 00:29:08,965 --> 00:29:10,965 I'll get lots of Ben feedback on it. 776 00:29:10,965 --> 00:29:12,244 Yeah. I'll go buy it. I'll have to 777 00:29:12,244 --> 00:29:15,144 go redo my licensing and cancel some 778 00:29:15,445 --> 00:29:18,085 and buy other ones and sort through all 779 00:29:18,085 --> 00:29:21,809 that mess. You talk about model switching, I 780 00:29:22,029 --> 00:29:24,750 bet it's not gonna it's gonna depend on 781 00:29:24,750 --> 00:29:27,569 your users. But I don't maybe not business. 782 00:29:27,630 --> 00:29:29,809 I'm so used to in any 783 00:29:30,429 --> 00:29:32,450 AI tool, whether it's Cloud or ChatGPT, 784 00:29:33,069 --> 00:29:34,929 of being able to go pick which 785 00:29:35,365 --> 00:29:37,125 Visual Studio code for that matter, being able 786 00:29:37,125 --> 00:29:38,884 to pitch pick which model I wanna use 787 00:29:38,884 --> 00:29:40,884 and do all of that, I feel like 788 00:29:40,884 --> 00:29:43,944 that's going to become just a normal 789 00:29:44,484 --> 00:29:45,845 thing. I think you and I are the 790 00:29:45,845 --> 00:29:46,345 outliers. 791 00:29:46,724 --> 00:29:48,024 We would be atypical 792 00:29:48,484 --> 00:29:48,984 to 793 00:29:49,450 --> 00:29:52,650 a general frontline worker that that that's out 794 00:29:52,650 --> 00:29:54,650 there and running through things. And not even 795 00:29:54,650 --> 00:29:56,910 frontline workers. I think workers across 796 00:29:57,450 --> 00:29:58,990 the, really, the nontechnical 797 00:29:59,369 --> 00:30:01,950 divisions within our organization. So if you're in 798 00:30:02,730 --> 00:30:03,789 HR, finance, 799 00:30:04,825 --> 00:30:07,144 legal, things like that, I think you'll be 800 00:30:07,144 --> 00:30:09,144 able to guide customers to a certain point, 801 00:30:09,144 --> 00:30:11,384 but there's a bunch of mental overhead and 802 00:30:11,384 --> 00:30:13,465 friction kind of along the way there. And 803 00:30:13,465 --> 00:30:15,065 you even saw that in the kind of 804 00:30:15,065 --> 00:30:17,305 commercial models and releases over time. Right? There 805 00:30:17,305 --> 00:30:18,904 was a period of time where they didn't 806 00:30:18,904 --> 00:30:21,200 refer to, like, even OpenAI with ChatGPT 807 00:30:21,579 --> 00:30:23,579 where they started referring to things like the 808 00:30:23,579 --> 00:30:26,460 model names. I remember when ChatGPT five launched 809 00:30:26,460 --> 00:30:27,679 and it was strawberry 810 00:30:28,299 --> 00:30:30,539 and they had, like, cuter code names to 811 00:30:30,539 --> 00:30:32,160 them so you didn't have to decipher 812 00:30:32,539 --> 00:30:35,234 the numbers and the codes and things behind 813 00:30:35,234 --> 00:30:37,394 it. I think that is a general friction 814 00:30:37,394 --> 00:30:39,394 point. I hope that improves. Like, a lot 815 00:30:39,394 --> 00:30:41,174 of these, like, agentic experiences 816 00:30:41,554 --> 00:30:44,754 are kinda getting better at directing into certain 817 00:30:44,754 --> 00:30:46,994 models. And I've also seen companies, and I 818 00:30:46,994 --> 00:30:48,359 don't know how this will work in m 819 00:30:48,359 --> 00:30:51,259 three sixty five Copilot land, but certainly within, 820 00:30:51,480 --> 00:30:52,619 like, custom applications, 821 00:30:53,320 --> 00:30:55,400 there's a lot of companies that are kind 822 00:30:55,400 --> 00:30:58,779 of spinning up around the LLM proxy interface. 823 00:30:59,000 --> 00:31:00,759 So, like, go ahead and route all your 824 00:31:00,759 --> 00:31:03,160 requests to me, and I'll help you choose 825 00:31:03,160 --> 00:31:05,875 the best model based on the intentionality 826 00:31:06,575 --> 00:31:08,414 of your request. So there's a little bit 827 00:31:08,414 --> 00:31:10,174 of overhead there, right, to evaluate the prompt 828 00:31:10,174 --> 00:31:11,855 the user sent in and whatever, but could 829 00:31:11,855 --> 00:31:13,855 potentially save you a whole bunch of money 830 00:31:13,855 --> 00:31:15,775 when you're talking about executing some of these 831 00:31:15,775 --> 00:31:17,259 models. I need to go figure out how 832 00:31:17,259 --> 00:31:18,700 to get Claude to show I still don't 833 00:31:18,700 --> 00:31:21,500 have Claude in any of my m three 834 00:31:21,500 --> 00:31:22,480 sixty five. 835 00:31:23,099 --> 00:31:24,960 Like, Researcher doesn't have Claude 836 00:31:25,259 --> 00:31:26,940 by chat. I only have it in Researcher 837 00:31:26,940 --> 00:31:28,460 today. I'm looking forward to getting it in 838 00:31:28,460 --> 00:31:29,980 chat, though, if this is coming. See, I 839 00:31:29,980 --> 00:31:31,945 want it in chat too. I'm kinda surprised 840 00:31:31,945 --> 00:31:33,545 I don't see it in Researcher yet. Maybe 841 00:31:33,545 --> 00:31:34,984 I'm gonna have to go make sure I 842 00:31:34,984 --> 00:31:37,244 actually have all my settings set 843 00:31:37,545 --> 00:31:38,045 properly 844 00:31:38,345 --> 00:31:40,285 for You might have blocked it. Copilot. 845 00:31:40,585 --> 00:31:43,465 Maybe. I have a tendency to fiddle. Or 846 00:31:43,465 --> 00:31:45,190 you gotta make sure your play your tenant's 847 00:31:45,190 --> 00:31:46,470 in a place where you're allowed to have 848 00:31:46,470 --> 00:31:48,150 it. So I made this mistake at work. 849 00:31:48,150 --> 00:31:50,150 I was showing I was showing some folks 850 00:31:50,150 --> 00:31:52,549 researcher with Claude and, like, how much more 851 00:31:52,549 --> 00:31:54,390 I liked it, and they happen to be 852 00:31:54,390 --> 00:31:57,269 over in Germany where due to kinda local 853 00:31:57,269 --> 00:31:58,789 laws, they're not allowed to have it. It's 854 00:31:58,789 --> 00:32:00,904 been locked out and done due to the 855 00:32:00,904 --> 00:32:03,865 worker council over there. That's another interesting thing 856 00:32:03,865 --> 00:32:05,545 I think to think about too is depending 857 00:32:05,545 --> 00:32:07,944 on your business, are you national, international, all 858 00:32:07,944 --> 00:32:10,345 those things? Can you can you float it? 859 00:32:10,345 --> 00:32:11,785 Like, is it actually are you gonna be 860 00:32:11,785 --> 00:32:13,785 able to give a consistent experience to your 861 00:32:13,785 --> 00:32:17,000 users? Scott, I just clicked in my settings 862 00:32:17,059 --> 00:32:19,380 in my chat in, like, my m three 863 00:32:19,380 --> 00:32:21,539 sixty five Copilot app in chat. I went 864 00:32:21,539 --> 00:32:23,380 to settings, and I had an update. So 865 00:32:23,380 --> 00:32:25,539 I clicked the update button, and now in 866 00:32:25,539 --> 00:32:27,859 my chat, I can choose between Claude Sonnet 867 00:32:27,859 --> 00:32:29,779 and GPT. There you go. Look at that. 868 00:32:29,779 --> 00:32:31,154 It's just an update away from you. I 869 00:32:31,154 --> 00:32:32,674 don't have it in Researcher yet, but I 870 00:32:32,674 --> 00:32:34,454 do have it in chat. Go figure. 871 00:32:34,835 --> 00:32:36,355 I wonder if I did something and blocked 872 00:32:36,355 --> 00:32:38,194 it in Researcher. Who knows? You gotta dive 873 00:32:38,194 --> 00:32:40,674 to, like, the seventh level of the admin 874 00:32:40,674 --> 00:32:43,234 center to figure figure out the operational control 875 00:32:43,234 --> 00:32:44,674 all the way down there at the bottom. 876 00:32:44,674 --> 00:32:45,575 Yeah. Apparently. 877 00:32:46,009 --> 00:32:47,529 I have this bad habit of fiddling with 878 00:32:47,529 --> 00:32:50,009 my tenant to figure stuff out, and then 879 00:32:50,009 --> 00:32:52,090 I forget that I fiddled with it and 880 00:32:52,090 --> 00:32:53,769 something doesn't work, and it's really my own 881 00:32:53,769 --> 00:32:54,970 fault. Look at that. We were gonna talk 882 00:32:54,970 --> 00:32:56,890 about GPU and Intune today. We spent the 883 00:32:56,890 --> 00:32:57,869 whole time on 884 00:32:58,345 --> 00:33:00,505 e e sevens and everything that's coming there. 885 00:33:00,505 --> 00:33:02,505 So I'm kinda curious for folks that are 886 00:33:02,505 --> 00:33:03,865 out there and listening, like, give us a 887 00:33:03,865 --> 00:33:05,005 ping on LinkedIn, 888 00:33:05,544 --> 00:33:08,585 on the podcast account, or give Ben and 889 00:33:08,585 --> 00:33:11,369 I a tag. Like, if you're thinking about 890 00:33:11,369 --> 00:33:14,089 adopting the e seven or not adopting it 891 00:33:14,089 --> 00:33:16,589 or kind of what's interesting to you 892 00:33:16,890 --> 00:33:18,809 as a consumer there. I think there's a 893 00:33:18,809 --> 00:33:21,849 bunch of interesting ways to kind of to 894 00:33:21,849 --> 00:33:25,150 kinda go with this one for customers. 100%. 895 00:33:25,365 --> 00:33:26,884 And we'll have to come back to GPOs 896 00:33:26,884 --> 00:33:28,565 and Intune at another time. Well, we got 897 00:33:28,565 --> 00:33:30,565 all the notes and everything for it. So 898 00:33:30,565 --> 00:33:31,944 I think Yeah. Exactly. 899 00:33:32,404 --> 00:33:35,444 Next time. Alright. Well, thanks, Scott. Appreciate it. 900 00:33:35,444 --> 00:33:37,605 Enjoy your day. Yeah. Like you said, let 901 00:33:37,605 --> 00:33:39,045 us know your thoughts on e seven. Look 902 00:33:39,045 --> 00:33:40,724 forward to hearing from people. Thanks, Ben. Thanks, 903 00:33:40,724 --> 00:33:41,339 Scott. Talk to you 904 00:33:43,419 --> 00:33:45,279 next time. If you enjoyed the podcast, 905 00:33:45,579 --> 00:33:47,179 go leave us a five star rating in 906 00:33:47,179 --> 00:33:49,259 iTunes. It helps to get the word out 907 00:33:49,259 --> 00:33:51,419 so more IT pros can learn about Office 908 00:33:51,419 --> 00:33:52,880 three sixty five and Azure. 909 00:33:53,419 --> 00:33:55,019 If you have any questions you want us 910 00:33:55,019 --> 00:33:57,234 to address on the show, or feedback about 911 00:33:57,234 --> 00:33:59,634 the show, feel free to reach out via 912 00:33:59,634 --> 00:34:02,835 our website, Twitter, or Facebook. Thanks again for 913 00:34:02,835 --> 00:34:04,455 listening, and have a great day.