Episode 391 – Remote Desktop and Application Delivery with Kamal Srinivasan from Parallels

December 19, 2024

Episode Transcript

Welcome to Episode 391 of the Microsoft Cloud IT Pro Podcast. In this episode, Scott sits down with Kamal Srinivasan from Parallels to talk how you can think about delivering applications and desktops to your users in post-Citrix world. As the traditional “Citrix” model faces disruption, we explore how remote work, hybrid scenarios, and cloud-based computing are redefining how organizations deliver applications and desktops to end users.

Key topics include:

The shift away from static, on-prem desktops to dynamic, cloud-based compute.
How to optimize app delivery by building on top of Microsoft’s Azure Virtual Desktop (AVD) platform.
Bridging the gap between legacy systems and cloud-based solutions, enabling businesses to roll out remote desktop solutions like AVD and Parallels RAS gradually while scaling down on-prem infrastructure.
The changing role of IT admins in supporting a workforce that operates anywhere, anytime.

Listen in and learn how your organization can streamline operations and empower your workforce with flexible, efficient application and desktop delivery.

Like what you hear and want to support the show? Check out our membership options.

Show Notes

About the sponsors

Would you like to become the irreplaceable Microsoft 365 resource for your organization? Let us know!

See full episode transcriptTranscript is autogenerated by AI

1 00:00:03,439 --> 00:00:04,580 Welcome to episode 2 00:00:05,120 --> 00:00:08,179 391 of the Microsoft Cloud IT Pro podcast, 3 00:00:08,639 --> 00:00:11,380 recorded live from Microsoft Ignite 2024. 4 00:00:12,240 --> 00:00:14,984 This is a show about Microsoft 365 and 5 00:00:15,384 --> 00:00:17,385 Azure from the perspective of IT pros and 6 00:00:17,385 --> 00:00:19,704 end users, where we discuss a topic or 7 00:00:19,704 --> 00:00:21,964 recent news and how it relates to you. 8 00:00:22,344 --> 00:00:24,265 In this episode, it's time for Scott to 9 00:00:24,265 --> 00:00:26,344 do an interview as he sits down with 10 00:00:26,344 --> 00:00:27,484 Kamal from Parallels 11 00:00:28,029 --> 00:00:30,289 to discuss how you can think about delivering 12 00:00:30,349 --> 00:00:32,770 applications and desktops to your users 13 00:00:33,229 --> 00:00:36,210 as the traditional Citrix model faces disruption. 14 00:00:36,829 --> 00:00:39,869 In the interview, we explore remote work, hybrid 15 00:00:39,869 --> 00:00:41,890 scenarios, and cloud based computing. 16 00:00:42,245 --> 00:00:44,085 So let's sit down and listen to the 17 00:00:44,085 --> 00:00:44,585 interview. 18 00:00:46,565 --> 00:00:48,825 I'm at Ignite with Kamal Srinivasan. 19 00:00:49,365 --> 00:00:52,585 He is from Parallels, and we're gonna have 20 00:00:52,804 --> 00:00:54,104 a conversation about 21 00:00:54,539 --> 00:00:57,359 all things virtual desktops and client delivery 22 00:00:57,739 --> 00:00:59,439 and remote apps and, 23 00:01:00,219 --> 00:01:02,399 generally, how to think of things in 24 00:01:02,780 --> 00:01:04,459 context of some of the new announcements that 25 00:01:04,459 --> 00:01:06,619 we've had at Ignite this week, potentially with 26 00:01:06,619 --> 00:01:07,439 Windows 365 27 00:01:07,819 --> 00:01:10,634 link and Cloud PCs, and hopefully help everybody 28 00:01:10,634 --> 00:01:13,034 out there figure out the best path forward 29 00:01:13,034 --> 00:01:14,974 and and how to how to rationalize, 30 00:01:15,674 --> 00:01:17,914 how to move through things. So, Kamal, thanks 31 00:01:17,914 --> 00:01:20,474 for joining us. Why don't you quickly introduce 32 00:01:20,474 --> 00:01:21,674 yourself, and then we'll go ahead and get 33 00:01:21,674 --> 00:01:23,994 into it. Super excited. Thanks for having me 34 00:01:23,994 --> 00:01:24,814 on the podcast. 35 00:01:25,210 --> 00:01:26,969 This is definitely an exciting time. I mean, 36 00:01:26,969 --> 00:01:29,049 like, we're gonna talk something which is not 37 00:01:29,049 --> 00:01:30,430 AI agent and Copilot. 38 00:01:30,730 --> 00:01:32,109 Thank you. Thank you. 39 00:01:32,569 --> 00:01:35,370 But the real problems that customers and the 40 00:01:35,370 --> 00:01:38,385 administrators are facing today. Right? I'm Kamal. I'm 41 00:01:38,385 --> 00:01:41,344 based in Seattle. I've been running I'm head 42 00:01:41,344 --> 00:01:42,725 of product for Palos, 43 00:01:43,185 --> 00:01:44,245 and, definitely 44 00:01:44,545 --> 00:01:46,885 been around this industry for quite some time, 45 00:01:47,105 --> 00:01:50,305 ex Microsoft, ex Oracle Cloud. Super excited to 46 00:01:50,305 --> 00:01:51,605 be here. Awesome. 47 00:01:52,259 --> 00:01:54,599 So maybe we can start with 48 00:01:55,299 --> 00:01:58,979 Windows 365 Links. So Windows 365 Link was 49 00:01:58,979 --> 00:02:00,759 announced earlier this week. 50 00:02:01,140 --> 00:02:01,799 A very 51 00:02:02,259 --> 00:02:04,034 different take on a thin client, 52 00:02:04,355 --> 00:02:06,215 locked down with a custom OS. 53 00:02:06,835 --> 00:02:08,835 Don't have to maintain an OS. Don't really 54 00:02:08,835 --> 00:02:10,594 need to maintain a client, but I need 55 00:02:10,594 --> 00:02:14,135 to log in specifically to a cloud PC 56 00:02:14,515 --> 00:02:15,015 and 57 00:02:15,395 --> 00:02:17,254 a Windows 365 desktop. 58 00:02:17,689 --> 00:02:19,530 From what I know, not even Azure Virtual 59 00:02:19,530 --> 00:02:21,530 Desktop or or some of the other things 60 00:02:21,530 --> 00:02:23,770 that are out there today. So how should 61 00:02:23,770 --> 00:02:25,310 customers think about 62 00:02:25,770 --> 00:02:29,069 virtual desktops and thin clients today and ultimately 63 00:02:29,129 --> 00:02:29,629 delivering 64 00:02:30,165 --> 00:02:31,944 potentially desktops and 65 00:02:32,564 --> 00:02:35,125 applications back. I think Microsoft's kind of put 66 00:02:35,125 --> 00:02:36,564 a foot down and said, we have some 67 00:02:36,564 --> 00:02:39,685 opinions about this, and we potentially drive OEMs 68 00:02:39,685 --> 00:02:41,044 this way. But I wonder based on your 69 00:02:41,044 --> 00:02:43,444 experience in the market, how do folks generally 70 00:02:43,444 --> 00:02:45,205 think about things, and how should they maybe 71 00:02:45,205 --> 00:02:47,319 be thinking about things in their considerations 72 00:02:47,699 --> 00:02:48,199 with 73 00:02:48,659 --> 00:02:51,479 Citrix out there? You're on the parallel side. 74 00:02:51,620 --> 00:02:55,159 RAS does both application delivery and virtual desktop 75 00:02:55,219 --> 00:02:58,514 delivery. We've got Lync, and, you know, we 76 00:02:58,514 --> 00:03:00,514 still have the Windows app that's hanging out 77 00:03:00,514 --> 00:03:03,074 there and connect to this whole ecosystem as 78 00:03:03,074 --> 00:03:04,754 well. And and it is a big push. 79 00:03:04,754 --> 00:03:06,134 So how should customers 80 00:03:06,914 --> 00:03:09,074 think about that and and approach that? And 81 00:03:09,074 --> 00:03:09,574 especially 82 00:03:09,954 --> 00:03:11,875 administrators who kinda have to sit down and 83 00:03:11,875 --> 00:03:14,319 think about not just, hey, my organization has 84 00:03:14,319 --> 00:03:16,159 to go out and buy this, but then 85 00:03:16,159 --> 00:03:18,480 I need to love and care and feed 86 00:03:18,480 --> 00:03:20,879 it and grow it and maintain it. Yeah. 87 00:03:20,879 --> 00:03:23,280 Definitely. I think, like, look, the first thing 88 00:03:23,280 --> 00:03:25,784 first is we live in a post Citrix 89 00:03:25,784 --> 00:03:28,344 world. Right? Citrix was there in the last 90 00:03:28,344 --> 00:03:31,784 20 years, 30 years, dealing how applications and 91 00:03:31,784 --> 00:03:35,004 desktops were delivered, and the industry was following 92 00:03:35,144 --> 00:03:37,884 in the same paths. And if not anything, 93 00:03:37,944 --> 00:03:39,849 everything that you said means that like, hey, 94 00:03:39,849 --> 00:03:41,150 we are getting disrupted 95 00:03:41,450 --> 00:03:44,330 in how desktops and applications, right? In general, 96 00:03:44,330 --> 00:03:45,469 the end user computing 97 00:03:45,930 --> 00:03:48,730 industry is getting disrupted for this new world, 98 00:03:48,730 --> 00:03:50,909 which is like in a post cloud world 99 00:03:51,129 --> 00:03:51,950 where developers, 100 00:03:52,490 --> 00:03:53,469 knowledge workers, 101 00:03:54,235 --> 00:03:57,194 office workers, contractors are all working differently. It 102 00:03:57,194 --> 00:03:59,615 is not the same assumptions that you made 103 00:03:59,835 --> 00:04:02,075 in the last 20 years, where people came 104 00:04:02,075 --> 00:04:04,474 in, they logged in at certain times, they 105 00:04:04,474 --> 00:04:07,169 logged off at certain times. You're even like 106 00:04:07,169 --> 00:04:09,650 network bandwidth. You could like map out and 107 00:04:09,650 --> 00:04:11,590 say like, for many years, 108 00:04:11,889 --> 00:04:13,569 I used to work in networking where you 109 00:04:13,569 --> 00:04:15,810 could map out and see the cycles of 110 00:04:15,810 --> 00:04:16,310 productivity 111 00:04:16,930 --> 00:04:18,389 mapping to network bandwidth. 112 00:04:18,805 --> 00:04:21,204 So that maps to corporate network, right, like 113 00:04:21,204 --> 00:04:21,704 usage 114 00:04:22,324 --> 00:04:24,564 over a period of a day. And those 115 00:04:24,564 --> 00:04:26,805 assumptions are getting disrupted because of the fact 116 00:04:26,805 --> 00:04:28,884 that, like, how people have started working. So 117 00:04:28,884 --> 00:04:31,865 which means naturally, the applications they are accessing 118 00:04:32,324 --> 00:04:34,504 and the desktops they are accessing has changed. 119 00:04:34,699 --> 00:04:36,300 In this, all of this, when you said 120 00:04:36,300 --> 00:04:38,779 about Windows 3 65, the most interesting thing 121 00:04:38,779 --> 00:04:40,939 about this is I'm a developer. I used 122 00:04:40,939 --> 00:04:43,019 to be a developer. I'm like, then went 123 00:04:43,019 --> 00:04:45,259 into product. One of the big things was, 124 00:04:45,259 --> 00:04:46,000 if you remember, 125 00:04:46,379 --> 00:04:48,375 we all used to have a developer box 126 00:04:48,615 --> 00:04:50,615 sitting there, right? I still have a dev 127 00:04:50,615 --> 00:04:52,055 box. We still have a dev box. We 128 00:04:52,055 --> 00:04:53,735 still end up having a dev box in 129 00:04:53,735 --> 00:04:56,214 all honesty. But like, there is a period 130 00:04:56,214 --> 00:04:58,134 of time, maybe 5 years, 10 years from 131 00:04:58,134 --> 00:05:00,855 now, maybe that assumption may not exist with 132 00:05:00,855 --> 00:05:03,120 this Windows 3 65 leg. You have a 133 00:05:03,120 --> 00:05:05,360 simple kind of a box that sits on 134 00:05:05,360 --> 00:05:06,819 my desk, very clean, 135 00:05:07,199 --> 00:05:08,500 looks super empty, 136 00:05:08,879 --> 00:05:11,060 but my developer box sits in the cloud, 137 00:05:11,120 --> 00:05:13,600 right, with all this powerful capability that I 138 00:05:13,600 --> 00:05:16,259 can, whether I need GPUs, I need accessibility, 139 00:05:16,725 --> 00:05:19,605 Who knows, liquid cooled GPUs. Like everything that, 140 00:05:19,605 --> 00:05:21,145 like, you need as a developer 141 00:05:21,764 --> 00:05:23,384 to build, test, deploy 142 00:05:23,925 --> 00:05:26,084 might not come from under your desk, but 143 00:05:26,084 --> 00:05:29,125 actually from somewhere else. And what is more 144 00:05:29,125 --> 00:05:31,139 interesting is that, like, that means that, like, 145 00:05:31,379 --> 00:05:33,620 your ability to go from what you need 146 00:05:33,620 --> 00:05:35,460 this week versus next week. I don't need 147 00:05:35,460 --> 00:05:37,699 to wait for somebody to approve, somebody to 148 00:05:37,699 --> 00:05:39,639 go through this supply chain painful 149 00:05:40,180 --> 00:05:43,000 process. Somebody's handled all that. As an administrator, 150 00:05:43,379 --> 00:05:46,064 that means, hey, I've simplified, right? Because admins 151 00:05:46,064 --> 00:05:48,865 and developers never were friends for many, many 152 00:05:48,865 --> 00:05:49,365 years. 153 00:05:49,904 --> 00:05:53,125 So, like, this means the administrator is becoming 154 00:05:53,185 --> 00:05:54,964 actually like a friend of this 155 00:05:55,264 --> 00:05:57,745 developer population by saying that, like, hey, you 156 00:05:57,745 --> 00:05:59,400 want this? You've got it. Right? And I've 157 00:05:59,400 --> 00:06:01,240 got an ability to manage it. So that 158 00:06:01,240 --> 00:06:03,480 to me is super empowering on both sides 159 00:06:03,480 --> 00:06:05,000 of the aisle. If you look at how 160 00:06:05,000 --> 00:06:07,720 Windows 3 65 link is going to probably 161 00:06:07,720 --> 00:06:09,960 head in that direction. It's a disruption for 162 00:06:09,960 --> 00:06:12,040 this end user computing industry. Right? Because I'm 163 00:06:12,040 --> 00:06:13,100 not giving static 164 00:06:13,400 --> 00:06:13,900 desktops 165 00:06:14,444 --> 00:06:15,824 with a VDI session 166 00:06:16,284 --> 00:06:19,004 back to this end user, but instead making 167 00:06:19,004 --> 00:06:22,125 this more dynamic as the need arises for 168 00:06:22,125 --> 00:06:23,324 the day or the week. I think it's 169 00:06:23,324 --> 00:06:25,824 very interesting where it's gone with connectivity 170 00:06:26,604 --> 00:06:27,504 and authentication. 171 00:06:28,204 --> 00:06:29,324 So, like, when I said I have a 172 00:06:29,324 --> 00:06:29,824 DevBox, 173 00:06:30,180 --> 00:06:31,479 my Dev Box is virtual. 174 00:06:31,779 --> 00:06:33,779 So I certainly have my laptop that I 175 00:06:33,779 --> 00:06:35,800 walk around and things just like that. But 176 00:06:36,180 --> 00:06:39,379 my day to day job laptop has 16 177 00:06:39,379 --> 00:06:41,379 gigs of RAM, and it's not necessarily doing 178 00:06:41,379 --> 00:06:42,899 the things that I need it to do. 179 00:06:42,899 --> 00:06:44,875 So I usually log into that, and then 180 00:06:44,875 --> 00:06:46,014 I log in to 181 00:06:46,314 --> 00:06:49,194 my mini core 128 gig of RAM dev 182 00:06:49,194 --> 00:06:51,675 box, and that's where I spend most of 183 00:06:51,675 --> 00:06:54,074 my day. And it's been interesting to watch 184 00:06:54,074 --> 00:06:54,574 the 185 00:06:54,875 --> 00:06:55,375 evolution 186 00:06:56,074 --> 00:06:57,134 of optimizations 187 00:06:57,514 --> 00:06:59,250 on the stacks. So we've had kind of 188 00:06:59,250 --> 00:07:02,129 RDP out there for a long time. Video 189 00:07:02,129 --> 00:07:04,930 delivery has often been, like, my bottleneck. So 190 00:07:04,930 --> 00:07:06,529 I'm a product manager. I spend a lot 191 00:07:06,529 --> 00:07:08,689 of time on calls with customers and, you 192 00:07:08,689 --> 00:07:10,850 know, various members of my team, and that 193 00:07:10,850 --> 00:07:13,509 means teams, camera, and I'm a remote employee. 194 00:07:13,764 --> 00:07:15,625 Audio and video are important to me. 195 00:07:16,085 --> 00:07:19,285 And, you know, optimizations with MMR and some 196 00:07:19,285 --> 00:07:21,525 of those things, MMR, MRR, I always get 197 00:07:21,525 --> 00:07:23,925 my acronyms screwed up. You know, those have 198 00:07:23,925 --> 00:07:26,485 been super disruptive for, like, me just as 199 00:07:26,485 --> 00:07:29,819 an individual and an information worker that's that's 200 00:07:29,819 --> 00:07:30,959 out there in the workforce. 201 00:07:31,339 --> 00:07:32,939 Yeah. Like, one of the things that you 202 00:07:32,939 --> 00:07:35,419 see in the what is very empowering the 203 00:07:35,419 --> 00:07:37,339 ZUC industry is for a while, you see 204 00:07:37,339 --> 00:07:40,060 was end user computing was definitely, like, a 205 00:07:40,060 --> 00:07:42,699 capped set of time. Right? Which is, like, 206 00:07:42,699 --> 00:07:45,724 you had, like, a certain amount of pie 207 00:07:45,944 --> 00:07:48,344 of what this looks like, and you were 208 00:07:48,425 --> 00:07:51,004 every vendor was trying to operate within that. 209 00:07:51,144 --> 00:07:54,104 What with the disruptions that's happening has changed 210 00:07:54,104 --> 00:07:55,784 is that like now the pie looks much 211 00:07:55,784 --> 00:07:58,185 bigger. The reason has become the fact that 212 00:07:58,185 --> 00:07:58,379 like now you've got greenfield opportunities to deploy 213 00:07:58,379 --> 00:07:58,419 for new use cases and new ways of 214 00:07:58,425 --> 00:07:59,404 for the 215 00:08:05,729 --> 00:08:06,229 developer, 216 00:08:06,529 --> 00:08:08,229 administrator to knowledge maker, 217 00:08:08,529 --> 00:08:11,410 administrator to a contractor, right? We have this 218 00:08:11,410 --> 00:08:13,750 customer who is right moving off Citrix, 219 00:08:14,164 --> 00:08:16,664 and they're dispersing their workload to the edge, 220 00:08:16,805 --> 00:08:19,544 and they're dispersing their workload to the server 221 00:08:19,764 --> 00:08:21,625 and to the cloud. So there's ability 222 00:08:22,004 --> 00:08:24,824 to take an existing workload from a Citrix 223 00:08:24,884 --> 00:08:26,724 environment and be able to say, hey, I'm 224 00:08:26,724 --> 00:08:28,964 actually gonna give a population of the use 225 00:08:28,964 --> 00:08:30,620 case to run on the laptops. 226 00:08:31,079 --> 00:08:33,559 But I'm managing that workload. I'm managing that 227 00:08:33,559 --> 00:08:35,019 application on the desktop, 228 00:08:35,480 --> 00:08:37,879 and I've got ability to do golden image, 229 00:08:37,879 --> 00:08:38,700 batch management, 230 00:08:39,080 --> 00:08:41,320 VM controls, everything. And then I can do 231 00:08:41,320 --> 00:08:43,254 the same thing on the server for certain 232 00:08:43,254 --> 00:08:45,735 other use cases and population, and I can 233 00:08:45,735 --> 00:08:47,334 do the same thing from the cloud for 234 00:08:47,334 --> 00:08:49,894 certain other use cases and population. So this 235 00:08:49,894 --> 00:08:51,595 ability to span this 236 00:08:51,894 --> 00:08:55,120 desktop server cloud is becoming real. I have 237 00:08:55,120 --> 00:08:57,839 another customer who has come because of the 238 00:08:57,839 --> 00:09:00,079 simple reason that, like, hey, GPUs are shot. 239 00:09:00,079 --> 00:09:03,120 Everybody's fighting for GPUs in the cloud. My 240 00:09:03,120 --> 00:09:06,079 supply chain, I cannot get GPUs to deploy 241 00:09:06,079 --> 00:09:08,079 in my data center. What do I do? 242 00:09:08,079 --> 00:09:10,535 I have all these M series machines that 243 00:09:10,535 --> 00:09:13,254 these user population is sitting with. Let me 244 00:09:13,254 --> 00:09:15,735 go give them and enable them these VMs 245 00:09:15,735 --> 00:09:17,815 there. I can manage it, and let me 246 00:09:17,815 --> 00:09:20,134 do it. Right? Mhmm. So that's been a 247 00:09:20,295 --> 00:09:23,195 now this administrator can really look at the 248 00:09:23,490 --> 00:09:26,309 constraints they have. Don't have to force artificially 249 00:09:26,529 --> 00:09:27,269 the user 250 00:09:27,649 --> 00:09:30,129 to come to an environment, although there were 251 00:09:30,129 --> 00:09:32,529 these constraints, but instead do, hey, you want 252 00:09:32,529 --> 00:09:34,529 these things? I can really deliver it there. 253 00:09:34,529 --> 00:09:36,450 I think that's what is very empowering, and 254 00:09:36,450 --> 00:09:38,595 that's why, like, I'm super interested in seeing 255 00:09:38,595 --> 00:09:40,054 how Windows 365 256 00:09:40,434 --> 00:09:42,514 link is taken by the rest of the 257 00:09:42,514 --> 00:09:45,254 thin client industry or in general hardware OEMs, 258 00:09:45,315 --> 00:09:47,975 right? And seeing, oh, maybe there's a new 259 00:09:48,035 --> 00:09:50,559 market and a new way to look at 260 00:09:50,559 --> 00:09:52,500 this entire spectrum of EOC. 261 00:09:56,159 --> 00:09:58,240 Do you feel overwhelmed by trying to manage 262 00:09:58,240 --> 00:10:01,539 your Office 365 environment? Are you facing unexpected 263 00:10:01,679 --> 00:10:03,860 issues that disrupt your company's productivity? 264 00:10:04,304 --> 00:10:06,065 Intelligink is here to help. Much like you 265 00:10:06,065 --> 00:10:07,985 take your car to the mechanic that has 266 00:10:07,985 --> 00:10:10,065 specialized knowledge on how to best keep your 267 00:10:10,065 --> 00:10:13,125 car running, Intelligink helps you with your Microsoft 268 00:10:13,184 --> 00:10:15,365 cloud environment because that's their expertise. 269 00:10:15,745 --> 00:10:18,039 Intelligink keeps up with the latest updates in 270 00:10:18,039 --> 00:10:20,279 the Microsoft cloud to help keep your business 271 00:10:20,279 --> 00:10:22,519 running smoothly and ahead of the curve. Whether 272 00:10:22,519 --> 00:10:24,519 you are a small organization with just a 273 00:10:24,519 --> 00:10:27,000 few users up to an organization of several 274 00:10:27,000 --> 00:10:29,720 1000 employees, they want to partner with you 275 00:10:29,720 --> 00:10:33,100 to implement and administer your Microsoft cloud technology. 276 00:10:33,855 --> 00:10:35,315 Visit them at inteliginc.com/podcast. 277 00:10:37,535 --> 00:10:38,674 That's intelligink.com/podcast 278 00:10:44,735 --> 00:10:46,815 for more information or to schedule a 30 279 00:10:46,815 --> 00:10:48,809 minute call to get started with them today. 280 00:10:49,190 --> 00:10:52,549 Remember, IntelliJunk focuses on the Microsoft cloud, so 281 00:10:52,549 --> 00:10:54,329 you can focus on your business. 282 00:10:56,470 --> 00:10:58,950 I think the intent to OEM that device 283 00:10:58,950 --> 00:11:01,190 is very interesting. It kinda follows the model 284 00:11:01,190 --> 00:11:03,475 that Microsoft has done in other things like 285 00:11:03,475 --> 00:11:06,915 Surface to compute and Copilot Plus PCs. You 286 00:11:06,915 --> 00:11:08,915 know, they tend to lead the way with 287 00:11:08,915 --> 00:11:09,415 maybe 288 00:11:09,875 --> 00:11:12,195 designs around Surface and things like that. But 289 00:11:12,195 --> 00:11:14,434 then the architectures are open and and the 290 00:11:14,434 --> 00:11:16,860 rest of the ecosystem that's out there with 291 00:11:16,860 --> 00:11:19,740 partners and vendors can can adopt it and 292 00:11:19,740 --> 00:11:21,339 and push it through. I think it's also 293 00:11:21,339 --> 00:11:22,480 a a great observation 294 00:11:22,860 --> 00:11:23,360 that 295 00:11:23,899 --> 00:11:26,700 from an administrator side, we can kind of 296 00:11:26,700 --> 00:11:29,634 chase the functionality that our users need versus 297 00:11:29,634 --> 00:11:32,355 making our users chase it. So I go 298 00:11:32,355 --> 00:11:35,154 from having to say, oh, I've got Scott 299 00:11:35,154 --> 00:11:36,995 over there, and he's complaining that his laptop 300 00:11:36,995 --> 00:11:38,995 is too slow. And Yeah. You know, I 301 00:11:38,995 --> 00:11:40,514 better get go buy him a laptop with 302 00:11:40,514 --> 00:11:42,690 64 gigs of RAM. And then 2 months 303 00:11:42,690 --> 00:11:45,090 later, I'm back complaining again. And, well, now 304 00:11:45,090 --> 00:11:47,090 I gotta get you a desktop, and I've 305 00:11:47,090 --> 00:11:49,330 just had this proliferation of hardware in my 306 00:11:49,330 --> 00:11:49,830 depot 307 00:11:50,290 --> 00:11:52,230 that then I've gotta hand back out. But 308 00:11:52,290 --> 00:11:54,769 if I can chase the compute around the 309 00:11:54,769 --> 00:11:56,945 world, and that's acceptable within my org, and 310 00:11:56,945 --> 00:11:59,264 there's always gonna be geo boundaries and constraints 311 00:11:59,264 --> 00:12:01,605 there. But it does give you some fungibility 312 00:12:01,824 --> 00:12:02,565 and flexibility 313 00:12:03,184 --> 00:12:05,345 to figure out what's the kind of best 314 00:12:05,345 --> 00:12:07,904 delivery method for the compute, and then what's 315 00:12:07,904 --> 00:12:10,589 the best method to deliver that to on 316 00:12:10,589 --> 00:12:13,230 the end user side. Right. And look, this 317 00:12:13,230 --> 00:12:15,710 application, this is where the application part of 318 00:12:15,710 --> 00:12:17,809 it comes to. Right? Like, which is like 319 00:12:17,870 --> 00:12:18,610 the administrator 320 00:12:19,149 --> 00:12:21,389 earlier, like desktop. Hey, give a desktop, be 321 00:12:21,389 --> 00:12:23,654 done. Right? Let me manage the desktop. And 322 00:12:23,654 --> 00:12:25,095 that way I don't have to deal with 323 00:12:25,095 --> 00:12:26,934 what the user is trying to do within 324 00:12:26,934 --> 00:12:29,654 that, like, because I'm managing the box around 325 00:12:29,654 --> 00:12:31,975 that. But I think more and more, the 326 00:12:31,975 --> 00:12:34,695 users have become much more savvy. They pick 327 00:12:34,695 --> 00:12:35,195 applications, 328 00:12:35,654 --> 00:12:36,794 not like desktops. 329 00:12:37,100 --> 00:12:39,340 So which means now this box, hey, where 330 00:12:39,340 --> 00:12:41,340 is this box? It's not at the desktop 331 00:12:41,340 --> 00:12:43,420 because now my application might come from the 332 00:12:43,420 --> 00:12:45,820 cloud. My application might come from a different 333 00:12:45,820 --> 00:12:48,220 geo. Now what? Like the box gets very 334 00:12:48,220 --> 00:12:50,425 hard for the administrators to put. I think 335 00:12:50,425 --> 00:12:53,465 this is where application delivery gets very interesting. 336 00:12:53,465 --> 00:12:56,205 Right? Like I've spent like time, like healthcare 337 00:12:56,345 --> 00:12:58,825 happens to be a big market and focus 338 00:12:58,825 --> 00:12:59,805 for parallels. 339 00:13:00,264 --> 00:13:02,285 Oh, I I think things like Windows 365 340 00:13:02,425 --> 00:13:03,960 link you're going to take off in 341 00:13:04,360 --> 00:13:07,399 That's right. That's the canonical use case. Because 342 00:13:07,399 --> 00:13:09,639 if you look at it, for the many, 343 00:13:09,639 --> 00:13:12,279 many years, like, this was a very on 344 00:13:12,279 --> 00:13:12,779 premise, 345 00:13:13,559 --> 00:13:16,360 sitting off, like, a certain desktop. The application 346 00:13:16,440 --> 00:13:18,040 we know, like, 1 or 2 vendors in 347 00:13:18,040 --> 00:13:20,414 this space, right, who take on. And they 348 00:13:20,414 --> 00:13:22,975 were always delivered in a certain way. But 349 00:13:22,975 --> 00:13:25,875 now with this all these disruptions of application 350 00:13:26,014 --> 00:13:28,654 delivery, not desktop, means that, like, hey, you 351 00:13:28,654 --> 00:13:30,274 can go into an environment. 352 00:13:30,735 --> 00:13:33,615 You want this application to be delivered the 353 00:13:33,615 --> 00:13:35,909 point we're talking about desktop versus server versus 354 00:13:36,149 --> 00:13:39,049 cloud, you've got the flexibility within a hospital 355 00:13:39,110 --> 00:13:39,610 network 356 00:13:39,990 --> 00:13:42,490 to go deliver the application in certain ways 357 00:13:42,549 --> 00:13:45,190 to certain population of users, a different way 358 00:13:45,190 --> 00:13:46,889 to a different population of users, 359 00:13:47,190 --> 00:13:49,029 and be able to manage all that. Right? 360 00:13:49,029 --> 00:13:49,101 That platform concept where, like, now the security 361 00:13:49,101 --> 00:13:50,615 and the postures, platform concept 362 00:13:50,995 --> 00:13:53,575 where, like, now the security and the postures 363 00:13:53,634 --> 00:13:56,514 that you have, the identity and the management 364 00:13:56,514 --> 00:13:58,754 that you have, the integrations with, like, a 365 00:13:58,754 --> 00:14:01,235 number of these devices, peripheral devices that you 366 00:14:01,235 --> 00:14:04,529 have, are all now spanning this platform, 367 00:14:05,070 --> 00:14:08,029 not a certain solution delivered from a certain 368 00:14:08,029 --> 00:14:11,009 place. Right? Yeah. I think that's also 369 00:14:11,389 --> 00:14:13,149 super interesting. One of the things that was 370 00:14:13,149 --> 00:14:15,389 always hard for me to rationalize, like, back 371 00:14:15,389 --> 00:14:17,625 when I lived this life, was things like 372 00:14:17,784 --> 00:14:20,745 single user versus multi user sessions in some 373 00:14:20,745 --> 00:14:22,745 of the pools. And when I think about, 374 00:14:22,745 --> 00:14:25,865 like, the things that customers are doing, they 375 00:14:25,865 --> 00:14:28,764 tend to be more and more application specific. 376 00:14:28,985 --> 00:14:30,825 Like, you know, we have video editors out 377 00:14:30,825 --> 00:14:32,620 there who are gonna wanna be in a 378 00:14:32,620 --> 00:14:35,500 certain editing workflow. So if I'm working for 379 00:14:35,500 --> 00:14:37,740 Disney and Pixar, I've got a whole bunch 380 00:14:37,740 --> 00:14:40,620 of folks out there who are just sitting 381 00:14:40,620 --> 00:14:43,740 around waiting for rendering engines. Yeah. So give 382 00:14:43,740 --> 00:14:46,184 me access to GPU and rendering engine. Well, 383 00:14:46,345 --> 00:14:49,485 maybe in some cases, that's a single session 384 00:14:49,544 --> 00:14:51,884 or I can do, like, multi session for 385 00:14:51,945 --> 00:14:54,345 delivering, like, Word as a client down or 386 00:14:54,345 --> 00:14:56,664 or things like that. Do you see it 387 00:14:56,664 --> 00:14:59,325 kind of application delivery continuing 388 00:14:59,705 --> 00:15:00,205 to 389 00:15:00,730 --> 00:15:02,370 play a part here. I I I think 390 00:15:02,370 --> 00:15:04,090 it was very interesting. And I I can't 391 00:15:04,090 --> 00:15:06,649 tell if it's early days with things like 392 00:15:06,649 --> 00:15:09,129 Microsoft leaning into Lync and saying, well, it's 393 00:15:09,129 --> 00:15:12,410 desktops today. Maybe it's applications tomorrow. But when 394 00:15:12,410 --> 00:15:13,450 I look out there and I think about, 395 00:15:13,450 --> 00:15:15,754 like, remote app, remote app's been kicking around 396 00:15:15,815 --> 00:15:17,254 for For a while. A long time now. 397 00:15:17,254 --> 00:15:19,815 For a while. But there's other vendors out 398 00:15:19,815 --> 00:15:22,055 there that can do remote app delivery better 399 00:15:22,055 --> 00:15:23,575 than Microsoft can do with remote app. So 400 00:15:23,575 --> 00:15:24,615 I don't I don't think it's an area 401 00:15:24,615 --> 00:15:27,654 that they've necessarily, like, invested heavily in. Like, 402 00:15:27,654 --> 00:15:28,955 it's a product in the portfolio. 403 00:15:29,330 --> 00:15:31,409 But do you see it being more desktop 404 00:15:31,409 --> 00:15:31,909 delivery, 405 00:15:32,210 --> 00:15:33,509 application delivery, 406 00:15:33,889 --> 00:15:35,570 or is it really gonna be like a 407 00:15:35,570 --> 00:15:37,730 blended world of both where, you know, I 408 00:15:37,730 --> 00:15:39,009 can have my cake and eat it too 409 00:15:39,009 --> 00:15:41,330 as a user? Sure. Look. I mean, like, 410 00:15:41,330 --> 00:15:43,429 Microsoft is great in building platforms. 411 00:15:43,975 --> 00:15:46,215 Right? Like, we all know I've been part 412 00:15:46,215 --> 00:15:48,695 of Microsoft and, like, the it's not news 413 00:15:48,695 --> 00:15:50,455 to any of your listeners that, like, hey. 414 00:15:50,455 --> 00:15:51,914 They're great in building platforms. 415 00:15:52,215 --> 00:15:53,995 They leave room for partners, 416 00:15:54,375 --> 00:15:54,875 vendors, 417 00:15:55,335 --> 00:15:57,629 ecosystem to innovate on top. The same thing 418 00:15:57,629 --> 00:16:00,009 applies here too. They're like, when we look 419 00:16:00,009 --> 00:16:02,269 at it, like as an example, within parallels, 420 00:16:02,329 --> 00:16:04,250 we work very well on top of ABD. 421 00:16:04,250 --> 00:16:05,230 We have a solution 422 00:16:05,610 --> 00:16:08,409 that is offering similar to ABD. You might 423 00:16:08,409 --> 00:16:09,929 look on that and say like, hey, you 424 00:16:09,929 --> 00:16:12,110 guys offer a solution at ABD. That's not 425 00:16:12,329 --> 00:16:14,165 true. And they act like, we work on 426 00:16:14,165 --> 00:16:16,884 AVD because we see customers coming off Citrix, 427 00:16:16,884 --> 00:16:18,965 coming to AVD. How can we add value 428 00:16:18,965 --> 00:16:20,485 on top of AVDs? We are very good 429 00:16:20,485 --> 00:16:22,725 at application delivery. We sit on top of 430 00:16:22,725 --> 00:16:25,785 AVD, optimize the heck out of application delivery. 431 00:16:25,940 --> 00:16:27,860 AVD is very good at delivering these multi 432 00:16:27,860 --> 00:16:29,980 session desktops. It's a great compute host. Team 433 00:16:30,019 --> 00:16:31,699 So you leverage it as a compute host. 434 00:16:31,699 --> 00:16:33,700 We leverage as this host, and like on 435 00:16:33,700 --> 00:16:35,539 top of it, we are able to optimize 436 00:16:35,539 --> 00:16:38,679 for printing, optimize for file access, optimize for 437 00:16:39,065 --> 00:16:42,424 accessibility for networking, for certain things, accessibility for 438 00:16:42,424 --> 00:16:44,825 peripheral devices, right? Like some of these things 439 00:16:44,825 --> 00:16:48,024 that certain applications that we've optimized to deliver 440 00:16:48,024 --> 00:16:49,784 from a server, we've done that same thing 441 00:16:49,784 --> 00:16:51,705 for ABD. And the other thing is the 442 00:16:51,705 --> 00:16:54,024 hybrid, right? Not everything is going to run 443 00:16:54,024 --> 00:16:55,839 on the cloud. So if we think about 444 00:16:55,839 --> 00:16:57,539 AVD or Windows 3 65, 445 00:16:58,079 --> 00:16:59,679 one of the things is that like today, 446 00:16:59,679 --> 00:17:02,079 if I'm delivering, let's say, a desktop, I 447 00:17:02,079 --> 00:17:05,679 can move a desktop, maybe, right? But there's 448 00:17:05,679 --> 00:17:07,679 also the hybrid scenario where like, how do 449 00:17:07,679 --> 00:17:10,065 I get something running on premise to go? 450 00:17:10,144 --> 00:17:12,065 I can't just shut off my data center 451 00:17:12,065 --> 00:17:14,464 in 1 week, 1 month, 1 year. It 452 00:17:14,464 --> 00:17:16,544 takes time. Right? You've got, like, the tile 453 00:17:16,544 --> 00:17:18,144 space. You're paying for the tile space. It 454 00:17:18,144 --> 00:17:19,605 goes for a certain depreciation. 455 00:17:20,065 --> 00:17:21,825 So you need to move this over time. 456 00:17:21,825 --> 00:17:23,700 When you move this over time, you can't, 457 00:17:23,700 --> 00:17:26,039 like, come at the time of renewal 458 00:17:26,339 --> 00:17:27,779 and say that, like, hey, I'm going to 459 00:17:27,779 --> 00:17:30,500 evaluate, do a POC, turn on AVD or 460 00:17:30,500 --> 00:17:32,259 Windows 3 60 5 in a month. It's 461 00:17:32,259 --> 00:17:34,019 it's hard to snap your fingers and go 462 00:17:34,019 --> 00:17:36,339 from capex to opex and So it's very 463 00:17:36,339 --> 00:17:38,365 hard for different, like, product, 464 00:17:38,825 --> 00:17:39,325 application, 465 00:17:39,705 --> 00:17:42,825 user, security, finance perspective, right? It's very hard 466 00:17:42,825 --> 00:17:44,205 for an admin, CSO, 467 00:17:44,664 --> 00:17:46,345 CFO to CI to I and turn this 468 00:17:46,345 --> 00:17:47,705 on. But what you can do is, you 469 00:17:47,705 --> 00:17:49,305 can do this over time. This is where, 470 00:17:49,305 --> 00:17:50,539 like, a hybrid solution, 471 00:17:50,920 --> 00:17:51,740 and that's what 472 00:17:52,120 --> 00:17:54,600 people like parallels. Like, we do this very 473 00:17:54,600 --> 00:17:57,000 well. We have, like, large customers spanning from 474 00:17:57,000 --> 00:17:59,160 Europe to America where, like, even here at 475 00:17:59,160 --> 00:18:01,320 Ignite, they come, hey, I wanna go to 476 00:18:01,320 --> 00:18:03,480 AVD. Great, you're on top of AVD. Give 477 00:18:03,480 --> 00:18:05,855 me a way today that I can start 478 00:18:05,855 --> 00:18:07,934 using it. We optimize costs on top of 479 00:18:07,934 --> 00:18:10,174 AVD. We do manageability on top of AVD. 480 00:18:10,174 --> 00:18:12,434 Guess what? The licensing is the same mechanism. 481 00:18:12,494 --> 00:18:14,275 All you gotta do is Azure subscription, 482 00:18:14,575 --> 00:18:15,634 no change in licensing, 483 00:18:15,934 --> 00:18:17,775 and you're now running on top. This is 484 00:18:17,775 --> 00:18:19,775 great, right? Because this kind of a hybrid 485 00:18:19,775 --> 00:18:21,809 pathway means that, like, Windows 486 00:18:22,349 --> 00:18:23,330 365, AVD 487 00:18:23,710 --> 00:18:26,750 adoption will increase over time, but I can 488 00:18:26,750 --> 00:18:29,950 keep reducing the footprint on premise, right? I 489 00:18:29,950 --> 00:18:33,194 think this is where like vendors and like 490 00:18:33,434 --> 00:18:35,514 customers need to look and evaluate as to, 491 00:18:35,514 --> 00:18:37,595 like, how do I do this transition over 492 00:18:37,595 --> 00:18:40,335 time? How do I look for application delivery 493 00:18:40,875 --> 00:18:43,274 when I come here and not just a 494 00:18:43,274 --> 00:18:45,940 raw infrastructure and expect like, oh, it's not 495 00:18:45,940 --> 00:18:48,100 a binary thing that like, hey, Windows 3 496 00:18:48,100 --> 00:18:50,259 65 works or not. Right? Of course, it 497 00:18:50,259 --> 00:18:52,340 may not work because you had deployed this 498 00:18:52,340 --> 00:18:54,580 for 10, 15, 5 years. And if you 499 00:18:54,580 --> 00:18:56,820 come here, like, maybe you don't find like 500 00:18:56,820 --> 00:18:57,320 50%, 501 00:18:57,875 --> 00:18:59,795 Maybe you don't find 80%. Maybe you don't 502 00:18:59,795 --> 00:19:02,115 find 20%. But the last 20% is also 503 00:19:02,115 --> 00:19:03,955 very hard because it's very custom to your 504 00:19:03,955 --> 00:19:06,275 environment. Now we don't find it. It's not 505 00:19:06,275 --> 00:19:08,755 like it's not gonna work. It's because, like, 506 00:19:08,755 --> 00:19:10,674 you need to work to make that fit 507 00:19:10,674 --> 00:19:12,674 in. It's always the devil's in the details. 508 00:19:12,674 --> 00:19:15,080 It's not like, can we do it? It's 509 00:19:15,080 --> 00:19:16,279 how long is it gonna take us to 510 00:19:16,279 --> 00:19:17,960 do it and how much money is it 511 00:19:17,960 --> 00:19:20,120 gonna take us to get there? So I 512 00:19:20,120 --> 00:19:21,660 think there's kinda 2 interesting 513 00:19:22,120 --> 00:19:24,039 things there to kind of maybe close this 514 00:19:24,039 --> 00:19:25,100 out. So you mentioned 515 00:19:25,559 --> 00:19:27,884 value add capabilities on top, and and I 516 00:19:27,884 --> 00:19:30,845 think that's important to consider. So things like 517 00:19:30,845 --> 00:19:31,904 universal print 518 00:19:32,205 --> 00:19:34,125 and how do I consider, like, print in 519 00:19:34,125 --> 00:19:36,365 a remote app delivery world versus Yeah. The 520 00:19:36,365 --> 00:19:39,244 desktop world become important. So so there's those 521 00:19:39,244 --> 00:19:41,619 kinds of things. And then you also mentioned, 522 00:19:41,759 --> 00:19:43,599 and and I think it's important. Like, not 523 00:19:43,599 --> 00:19:45,279 a lot of customers think about it, but 524 00:19:45,279 --> 00:19:48,899 they probably should, especially enterprise customers on commitments. 525 00:19:49,440 --> 00:19:53,039 The ability to leverage their existing commitments with 526 00:19:53,039 --> 00:19:55,855 Microsoft, like, as a platform provider. So, you 527 00:19:55,855 --> 00:19:58,274 know, Microsoft for years years has had enterprise 528 00:19:58,414 --> 00:20:01,134 agreements. Now we're all on Macs for Azure 529 00:20:01,134 --> 00:20:02,974 and, you know, these commitments to consume and 530 00:20:02,974 --> 00:20:04,835 things like that. So I think the ability 531 00:20:04,974 --> 00:20:05,474 to 532 00:20:05,934 --> 00:20:09,054 have solutions both from Microsoft and, like you 533 00:20:09,054 --> 00:20:11,000 said, from partners who can help, I was 534 00:20:11,080 --> 00:20:12,680 I think it's 4. I would say, like, 535 00:20:12,680 --> 00:20:14,279 fill in the gaps. I think it is 536 00:20:14,279 --> 00:20:16,360 value add and and augmentation really at the 537 00:20:16,360 --> 00:20:17,880 end of the day. But being able to 538 00:20:17,880 --> 00:20:20,059 kinda consume from those same buckets 539 00:20:20,360 --> 00:20:23,214 is also super empowering for customers. That's right. 540 00:20:23,375 --> 00:20:24,654 You you know, it's one thing to go 541 00:20:24,654 --> 00:20:26,414 to your CFO and say, hey. We need 542 00:20:26,414 --> 00:20:28,734 to cut a new cut a new invoice 543 00:20:28,734 --> 00:20:30,575 here and and get a new PO out 544 00:20:30,575 --> 00:20:32,974 the door with a new vendor, or I'm 545 00:20:32,974 --> 00:20:34,034 in the same ecosystem. 546 00:20:34,335 --> 00:20:35,954 It's the same billing model. 547 00:20:36,460 --> 00:20:38,860 It can be cost optimized in similar ways 548 00:20:38,860 --> 00:20:40,779 to the tools I'm already using today. I 549 00:20:40,779 --> 00:20:43,660 think the Azure transactable marketplace is like a 550 00:20:43,660 --> 00:20:45,660 great thing for this. Right? It's cool, but 551 00:20:45,660 --> 00:20:47,180 I wish more people went in there. There's 552 00:20:47,180 --> 00:20:49,100 there's so much stuff. Customers come to me 553 00:20:49,100 --> 00:20:50,414 and they say, how do I do this? 554 00:20:50,494 --> 00:20:52,494 Yeah. And I look sometimes and I go, 555 00:20:52,494 --> 00:20:55,055 you know, there's there's there's the path and 556 00:20:55,055 --> 00:20:56,654 I can put you on a path, but 557 00:20:56,654 --> 00:20:58,595 I'll give you the smorgasbord of options. 558 00:20:58,975 --> 00:21:00,894 And sometimes it's the easy way. And so 559 00:21:00,975 --> 00:21:03,615 It's not just customers. Even for partners. Right? 560 00:21:03,615 --> 00:21:06,410 Like, that is, like, the three way capability 561 00:21:06,470 --> 00:21:07,210 of transaction 562 00:21:07,509 --> 00:21:10,470 and, like, how service providers can actually transact 563 00:21:10,470 --> 00:21:12,950 through this is super empowering because we've now 564 00:21:12,950 --> 00:21:14,490 lit up on Azure Marketplace. 565 00:21:14,789 --> 00:21:16,549 That's been, like, the best thing because, like, 566 00:21:16,549 --> 00:21:18,150 they can to your point on the map 567 00:21:18,150 --> 00:21:18,650 consumption, 568 00:21:19,224 --> 00:21:21,704 the partner offers can go out. We can 569 00:21:21,704 --> 00:21:23,804 set up certain things for these service providers 570 00:21:23,865 --> 00:21:26,024 or even resellers, and they can, like, transact 571 00:21:26,024 --> 00:21:26,524 directly 572 00:21:26,825 --> 00:21:28,664 with the customer. So which means the customer, 573 00:21:28,664 --> 00:21:30,585 to your point, can go to the CFO 574 00:21:30,585 --> 00:21:33,099 and say, hey. We're already on Microsoft ecosystem. 575 00:21:33,399 --> 00:21:34,919 Here's all I'm doing. Right? So when I 576 00:21:34,919 --> 00:21:37,720 switch from Citrix to this solution, whether it 577 00:21:37,720 --> 00:21:40,679 is AVD, Windows 365, with Parallels, it's an 578 00:21:40,679 --> 00:21:42,919 easy sell. For the CFO, yeah, it's part 579 00:21:42,919 --> 00:21:45,399 of the Microsoft consumption. I'm right here. I 580 00:21:45,399 --> 00:21:48,115 haven't changed the partner, Right? The service provider 581 00:21:48,115 --> 00:21:50,214 or the reseller. I haven't changed the Microsoft 582 00:21:50,434 --> 00:21:52,434 set of, like, consumption credits, and it makes 583 00:21:52,434 --> 00:21:54,375 it easy. Yeah. And you still have supportability 584 00:21:54,515 --> 00:21:56,355 as well. You still have supportability. Both sides 585 00:21:56,355 --> 00:21:57,954 of the stack. So, yeah, I think I 586 00:21:57,954 --> 00:22:00,134 think it is an interesting kind of virtuous 587 00:22:00,275 --> 00:22:02,730 ecosystem that can Agree. That can build it 588 00:22:02,730 --> 00:22:04,970 self out there. So closing thoughts, you've been 589 00:22:04,970 --> 00:22:06,970 here at Ignite all week. What's kind of 590 00:22:06,970 --> 00:22:09,609 your most exciting thing in this space? I 591 00:22:09,609 --> 00:22:11,849 think like, look, we started with this joking 592 00:22:11,849 --> 00:22:13,549 thing on AI agent Copilot, 593 00:22:14,169 --> 00:22:14,669 but 594 00:22:15,055 --> 00:22:16,894 one of the things that I see very 595 00:22:16,894 --> 00:22:19,555 empowering with some of this AI is like, 596 00:22:19,695 --> 00:22:22,414 not necessarily the, the earlier version used to 597 00:22:22,414 --> 00:22:25,934 be like automation by API contracts. Right? What 598 00:22:25,934 --> 00:22:27,775 is super interesting is to see is like, 599 00:22:27,775 --> 00:22:29,634 what is the agent contracts 600 00:22:30,289 --> 00:22:33,329 between different tasks look like? Right? If I 601 00:22:33,329 --> 00:22:35,029 can, like, today codify, 602 00:22:35,490 --> 00:22:38,289 tomorrow maybe there's learning tasks that may evolve 603 00:22:38,289 --> 00:22:41,109 as the agent frameworks and AI itself evolve. 604 00:22:41,250 --> 00:22:43,750 But as I look at a fast forwarded 605 00:22:43,890 --> 00:22:44,390 nature, 606 00:22:44,964 --> 00:22:46,964 administrators need to take a look at how 607 00:22:46,964 --> 00:22:47,865 can I leverage 608 00:22:48,325 --> 00:22:49,224 these frameworks 609 00:22:49,684 --> 00:22:51,684 in a way that is going to be 610 00:22:51,684 --> 00:22:53,924 more productive for me, right? They should not 611 00:22:53,924 --> 00:22:55,224 be afraid to embrace. 612 00:22:55,684 --> 00:22:57,924 So within these frameworks, one of the things 613 00:22:57,924 --> 00:23:00,339 like Microsoft is doing well is this Copilot 614 00:23:00,339 --> 00:23:01,480 as a user interface. 615 00:23:01,859 --> 00:23:03,940 It's yet to be proven. Like, there's lots 616 00:23:03,940 --> 00:23:06,180 of things to be there. Definitely early days. 617 00:23:06,180 --> 00:23:09,539 Early days. Maybe early innings. But it's worth 618 00:23:09,539 --> 00:23:11,755 looking from the aspect that, like, hey, how 619 00:23:11,755 --> 00:23:14,075 can me as an administrator, me as a 620 00:23:14,075 --> 00:23:16,414 vendor, plug into this Copilot ecosystem 621 00:23:16,875 --> 00:23:18,255 to give this codified 622 00:23:18,794 --> 00:23:21,515 task list that can talk to each other, 623 00:23:21,515 --> 00:23:23,694 right? Even if these are simple tasks, 624 00:23:24,210 --> 00:23:25,190 finding networking 625 00:23:25,490 --> 00:23:26,710 and finding EUC 626 00:23:27,169 --> 00:23:29,650 VDI issues and making sure, like, hey, this 627 00:23:29,650 --> 00:23:31,490 goes into a unified place for me to 628 00:23:31,490 --> 00:23:33,809 do one. It's a simple thing. Yeah. But 629 00:23:33,809 --> 00:23:35,429 but that's my, takeaway 630 00:23:35,809 --> 00:23:37,250 that, hey, we need to go do some 631 00:23:37,250 --> 00:23:38,710 of these codified tasks. 632 00:23:39,089 --> 00:23:40,904 Alright. That's that's excellent. Well, thank you very 633 00:23:40,904 --> 00:23:42,904 much for the conversation today. I do appreciate 634 00:23:42,904 --> 00:23:44,664 it. Thank you. Thanks for having me on 635 00:23:44,664 --> 00:23:46,204 the podcast. I'm looking forward to Gary. 636 00:23:48,984 --> 00:23:51,224 If you enjoyed the podcast, go leave us 637 00:23:51,224 --> 00:23:53,464 a 5 star rating in iTunes. It helps 638 00:23:53,464 --> 00:23:55,269 to get the word out so more IT 639 00:23:55,269 --> 00:23:58,009 pros can learn about Office 365 and Azure. 640 00:23:58,549 --> 00:24:00,230 If you have any questions you want us 641 00:24:00,230 --> 00:24:02,309 to address on the show, or feedback about 642 00:24:02,309 --> 00:24:02,970 the show, 643 00:24:03,269 --> 00:24:05,450 feel free to reach out via our website, 644 00:24:05,589 --> 00:24:08,549 Twitter, or Facebook. Thanks again for listening, and 645 00:24:08,549 --> 00:24:09,609 have a great day.

Digital Dispatch Podcast Podcast Artwork Image

Microsoft Cloud IT Pro Podcast

Ben Stegink, Scott Hoag

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

Contact Show