Episode 362 – The Flustration of Microsoft Ignite

November 30, 2023

Episode Transcript

In Episode 362, Ben and Scott get sidetracked with some of the announcements coming out of Microsoft Ignite.

It’s also the season of giving and we’re raising money for Girls Who Code. Donate today at https://give.girlswhocode.com/msclouditpro!

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

Show Notes

About the sponsors

Intelligink utilizes their skill and passion for the Microsoft cloud to empower their customers with the freedom to focus on their core business. They partner with them to implement and administer their cloud technology deployments and solutions. Visit Intelligink.com for more info.

See full episode transcriptTranscript is autogenerated by AI

1 00:00:03,325 --> 00:00:05,895 - Welcome to episode 362 2 00:00:05,895 --> 00:00:08,095 of the Microsoft Cloud IT Pro Podcast 3 00:00:08,695 --> 00:00:11,495 recorded live on November 17th, 2023. 4 00:00:11,805 --> 00:00:14,175 This is a show about Microsoft 365 5 00:00:14,175 --> 00:00:16,295 and Azure from the perspective of it pros 6 00:00:16,295 --> 00:00:19,655 and end users where we discuss a topic or recent news 7 00:00:19,675 --> 00:00:20,855 and how it relates to you. 8 00:00:21,205 --> 00:00:23,095 Finally, we have our news episode 9 00:00:23,095 --> 00:00:25,895 where we discuss news from Microsoft Ignite. 10 00:00:26,355 --> 00:00:29,015 We do actually discuss a little of the AI news, 11 00:00:29,115 --> 00:00:30,735 but also some interesting news 12 00:00:30,735 --> 00:00:33,415 around pausing virtual machines, updates 13 00:00:33,475 --> 00:00:37,055 to virtual machine scale sets, web application firewalls, 14 00:00:37,355 --> 00:00:40,815 the new Microsoft planner as well as SharePoint Premium. 15 00:00:43,305 --> 00:00:45,415 Today we'll talk Scott. Today we'll 16 00:00:45,415 --> 00:00:46,415 - Talk, what do you wanna talk about? 17 00:00:46,415 --> 00:00:48,975 We'll talk Ignite conferences, stuff and things. 18 00:00:49,205 --> 00:00:52,095 - Okay. Ignite News, copilot ai. Next topic. 19 00:00:52,145 --> 00:00:53,975 We're done with our Ignite News. You just 20 00:00:54,355 --> 00:00:58,295 - Summed up the entire M 365 admin session, 21 00:00:58,895 --> 00:01:00,815 , which I hopped into. 22 00:01:00,975 --> 00:01:02,095 I wanted to see if there were some 23 00:01:02,095 --> 00:01:03,175 new things in admin centers. 24 00:01:03,485 --> 00:01:06,175 What have I missed? And it was all about co-pilot. 25 00:01:06,255 --> 00:01:09,135 Co-pilot, not how co-pilot could help you as an admin. 26 00:01:09,955 --> 00:01:13,015 Not even how to get ready for co-pilot. 27 00:01:13,015 --> 00:01:14,695 It was just about co-pilot. 28 00:01:14,845 --> 00:01:16,655 - Okay. Now that we talked about Ignite News, 29 00:01:16,655 --> 00:01:17,655 what else should we talk about? 30 00:01:17,865 --> 00:01:20,015 There was actually other stuff, so there was, 31 00:01:20,265 --> 00:01:22,535 maybe we should ask co-pilot what we should talk about. 32 00:01:22,805 --> 00:01:26,615 What was the biggest news from Ignite now 33 00:01:26,615 --> 00:01:29,975 that Bing Chat has been renamed to Co-Pilot . 34 00:01:30,485 --> 00:01:33,895 Okay. The biggest news from Microsoft Ignite 2023 was the 35 00:01:33,895 --> 00:01:35,695 unveiling of several new AI products 36 00:01:36,115 --> 00:01:38,935 and expansions, including Microsoft Co-pilot for services. 37 00:01:39,235 --> 00:01:41,775 The, I have no idea, how do you pronounce their new chips? 38 00:01:41,835 --> 00:01:45,215 The Maya MEA AI chips. 39 00:01:45,445 --> 00:01:46,735 - It's not pronounced Maya, 40 00:01:46,875 --> 00:01:48,935 but I can't pull off the other 41 00:01:48,935 --> 00:01:50,215 pronunciation off the top of my head. 42 00:01:50,215 --> 00:01:51,815 It's been a hot minute since I looked at 43 00:01:51,815 --> 00:01:52,815 - It. 44 00:01:52,815 --> 00:01:54,135 Co-Pilot studio. Yeah. 45 00:01:54,295 --> 00:01:56,975 Sentinel Defender, XDR, all of the other stuff. 46 00:01:57,315 --> 00:01:58,855 It was a lot of co-pilot, 47 00:01:58,955 --> 00:02:02,935 but I will say I did happen to see some other stuff that, 48 00:02:03,445 --> 00:02:07,495 I'll be honest, given all of the co-pilot requirements 49 00:02:07,835 --> 00:02:11,455 and barriers to entry to get into someone like me, 50 00:02:12,055 --> 00:02:16,815 I have a little bit of co-pilot AI burnout, , 51 00:02:17,235 --> 00:02:19,455 and it was affecting a little 52 00:02:19,455 --> 00:02:20,455 - Bit of envy. 53 00:02:20,455 --> 00:02:22,655 - I don't know if it's envy or just I'm tired of 54 00:02:23,715 --> 00:02:25,535 the marketing push for it 55 00:02:25,715 --> 00:02:29,455 and even the push from Microsoft to 56 00:02:30,005 --> 00:02:32,415 different partners, different MVPs to 57 00:02:33,245 --> 00:02:34,695 essentially evangelize it. 58 00:02:34,915 --> 00:02:37,935 But yet I can't do anything with it. Hmm. 59 00:02:37,985 --> 00:02:41,735 Maybe it's envy that I'm masking with disinterest 60 00:02:41,915 --> 00:02:46,255 or maybe it's just like flat out burnout from hearing 61 00:02:46,715 --> 00:02:49,055 all about all this co-pilot stuff. 62 00:02:49,395 --> 00:02:51,815 And I feel like, here's the other thing 63 00:02:51,885 --> 00:02:55,535 that I've run into is I look at things like Loop 64 00:02:55,955 --> 00:02:58,455 and I'm trying to think what else this happened with. 65 00:02:58,655 --> 00:03:00,605 I mean copilot to a certain extent. 66 00:03:01,085 --> 00:03:02,725 'cause when was Copilot first announced? 67 00:03:02,745 --> 00:03:06,885 Was it first announced at last year's Ignite 68 00:03:06,905 --> 00:03:08,005 or was it build? 69 00:03:08,445 --> 00:03:12,165 - I believe it's been less than a year. I think it 70 00:03:12,165 --> 00:03:13,565 - Was like, has it been less than a year? It was 71 00:03:13,805 --> 00:03:16,445 - November 21st, 22nd. 72 00:03:16,445 --> 00:03:21,005 2022. So almost exactly a year, which is okay. 73 00:03:21,445 --> 00:03:22,485 Interesting. If you think about it. 74 00:03:22,625 --> 00:03:24,605 So we've been just indu, 75 00:03:25,635 --> 00:03:27,645 like all this news thrown out about inundated. 76 00:03:27,645 --> 00:03:29,805 Inundated, yes. With all these things. 77 00:03:30,585 --> 00:03:34,685 And it is interesting to think about it from the perspective 78 00:03:35,265 --> 00:03:37,885 of when's the last time 79 00:03:39,085 --> 00:03:41,045 Microsoft announced something 80 00:03:41,425 --> 00:03:45,765 and got it to GA in less than a year, across any 81 00:03:45,765 --> 00:03:48,845 of its kind of modern cloud stack, 82 00:03:49,025 --> 00:03:52,405 be it SaaS services in M 365 83 00:03:52,505 --> 00:03:55,245 or new services in M 365 Azure. 84 00:03:55,905 --> 00:03:57,605 I'm the proud owner of an Azure feature 85 00:03:57,605 --> 00:03:59,925 that's been in public preview for almost two years now. 86 00:04:00,245 --> 00:04:01,885 , like I might say, proud owner, 87 00:04:02,025 --> 00:04:03,165 not exactly the proud owner. 88 00:04:03,355 --> 00:04:05,205 Some stuff's been out there kicking around for a long time 89 00:04:05,785 --> 00:04:10,565 and co-pilot is a rapid thing. 90 00:04:10,835 --> 00:04:13,205 Like it's interesting to just disconnect from 91 00:04:13,785 --> 00:04:15,365 did you get the news you wanted at Ignite 92 00:04:15,365 --> 00:04:17,605 or did you get the types of content you wanted to Ignite 93 00:04:17,605 --> 00:04:18,725 to just step back 94 00:04:18,725 --> 00:04:20,285 and say, huh, , 95 00:04:20,435 --> 00:04:22,285 there's some interesting velocity here. 96 00:04:22,805 --> 00:04:24,845 I don't know if it's the right product, right time, 97 00:04:24,855 --> 00:04:26,165 right fit, all those kinds of things. 98 00:04:26,165 --> 00:04:27,325 But the velocity in and of itself 99 00:04:27,325 --> 00:04:28,805 is an interesting story to me. Yeah. 100 00:04:29,145 --> 00:04:32,605 - And I guess from that perspective of velocity 101 00:04:32,785 --> 00:04:34,125 of copilot compared 102 00:04:34,125 --> 00:04:36,405 to Loop is absolutely super fast. 103 00:04:36,405 --> 00:04:38,085 Like I think the velocity of Loop was, 104 00:04:38,085 --> 00:04:39,565 it was announced two years 105 00:04:40,185 --> 00:04:43,845 before we actually started to see some of the previews. 106 00:04:44,105 --> 00:04:47,805 But even then, I think after the last few ignites 107 00:04:47,865 --> 00:04:49,965 and some of that, I mean 108 00:04:49,965 --> 00:04:51,845 that velocity is still announcing something 109 00:04:51,845 --> 00:04:54,965 and it not coming out for almost a year afterwards 110 00:04:55,465 --> 00:04:57,365 to me these days feels really slow. 111 00:04:57,745 --> 00:05:02,005 And I think that's part of maybe my, oh, maybe some 112 00:05:02,005 --> 00:05:03,365 of my burnout or the disconnect 113 00:05:03,365 --> 00:05:07,205 or just lacking the excitement as it's like, yay, ignite, 114 00:05:07,295 --> 00:05:08,805 let's go watch all the sessions. 115 00:05:08,945 --> 00:05:12,765 But every session you watch seems to be talking about stuff 116 00:05:12,835 --> 00:05:15,765 that you can't really do yet. 117 00:05:16,205 --> 00:05:18,085 , again, co-pilot and Loop. 118 00:05:18,185 --> 00:05:21,485 And there were some that were announced like I think some 119 00:05:21,485 --> 00:05:25,045 of the Azure or the co-pilot studio stuff maybe you can 120 00:05:25,655 --> 00:05:27,405 start doing stuff with. 121 00:05:27,465 --> 00:05:30,165 And there were some public preview things that came out. 122 00:05:30,665 --> 00:05:32,205 But I think it's, I don't get 123 00:05:32,205 --> 00:05:33,765 that excitement about watching it day one 124 00:05:33,765 --> 00:05:36,165 because I'm like, I can go read the blog post like two 125 00:05:36,165 --> 00:05:38,565 or three days later and I'm not gonna be missing anything 126 00:05:38,565 --> 00:05:40,765 because nothing they announced is like a rush 127 00:05:40,785 --> 00:05:41,845 and go try it anymore. 128 00:05:42,225 --> 00:05:43,485 Or I don't know. 129 00:05:43,585 --> 00:05:46,765 I'm trying to figure out like why was that excitement? 130 00:05:47,005 --> 00:05:48,125 I just didn't have that excitement 131 00:05:48,125 --> 00:05:49,805 for Ignite this year that I normally have. 132 00:05:50,065 --> 00:05:53,125 Or maybe it's that I miss the in-person, the big conference. 133 00:05:53,285 --> 00:05:56,165 I miss what Ignite used to be and this just isn't the same. 134 00:05:56,525 --> 00:05:59,845 - I think you need to pick and choose your moments 135 00:05:59,945 --> 00:06:01,525 and your battles with stuff like this. 136 00:06:02,085 --> 00:06:06,365 I think I've resigned myself to the fact that the days 137 00:06:06,585 --> 00:06:10,125 of kind of deep technical conferences, which are the, 138 00:06:10,135 --> 00:06:12,285 don't get me wrong, like those are the things that I, 139 00:06:12,645 --> 00:06:14,085 I absolutely opine for. 140 00:06:14,435 --> 00:06:18,125 Like those don't necessarily exist anymore. 141 00:06:18,525 --> 00:06:21,245 I, I was watching did an internal watch party 142 00:06:21,425 --> 00:06:24,245 for at least the day two keynote from Guthrie. 143 00:06:24,485 --> 00:06:26,205 'cause that one focuses on Azure 144 00:06:26,945 --> 00:06:30,725 and most of us were paying attention to the chat just to see 145 00:06:31,195 --> 00:06:34,285 what sediment was and what people were thinking. 146 00:06:35,025 --> 00:06:38,885 And I was kind of blown away that even some 147 00:06:38,885 --> 00:06:40,765 of the folks on our side were like, 148 00:06:41,185 --> 00:06:44,365 why are people in the chat saying that Ignite sucks 149 00:06:44,385 --> 00:06:46,165 and it's not a technical conference anymore? 150 00:06:46,625 --> 00:06:48,285 Why are people in the chat annoyed 151 00:06:48,995 --> 00:06:51,005 that they say they're spending thousands 152 00:06:51,005 --> 00:06:53,405 of dollars in a conference where they can't learn anything? 153 00:06:53,525 --> 00:06:58,325 I was like, well my, I think not so naive take is many 154 00:06:58,325 --> 00:07:00,085 of these things and it's not just Ignite. 155 00:07:00,365 --> 00:07:03,045 I, I think AWS like reinvent is uh, 156 00:07:03,155 --> 00:07:05,205 very much getting this same kinda reputation. 157 00:07:05,655 --> 00:07:07,165 These big conferences that used 158 00:07:07,165 --> 00:07:10,365 to be about technical enablement are now really 159 00:07:11,235 --> 00:07:13,125 like sales motions, right? 160 00:07:13,505 --> 00:07:16,085 To get people going, which means they don't have 161 00:07:16,085 --> 00:07:18,645 to be technical and they probably shouldn't be, 162 00:07:18,785 --> 00:07:20,045 but they're still being pitched that way. 163 00:07:20,625 --> 00:07:22,365 But they are really marketing 164 00:07:22,585 --> 00:07:25,165 and architecture driven kinds of things. 165 00:07:25,545 --> 00:07:28,165 So if you go and you're an admin, like I was trying 166 00:07:28,165 --> 00:07:29,525 to put myself in the seat 167 00:07:29,525 --> 00:07:31,605 of oh I've got a 200 person company 168 00:07:32,145 --> 00:07:34,965 and I'm taking $6,000 outta the budget 169 00:07:35,065 --> 00:07:37,445 to send my my my one loan admin off to Ignite. 170 00:07:37,605 --> 00:07:38,925 'cause they're gonna learn all these great things 171 00:07:39,265 --> 00:07:41,125 and they're gonna gimme this great writeup when they 172 00:07:41,125 --> 00:07:42,245 come back about all of it. 173 00:07:42,385 --> 00:07:44,685 You're probably gonna get a pretty dissing disappointing 174 00:07:44,715 --> 00:07:46,525 writeup and you're not gonna think there's a lot 175 00:07:46,525 --> 00:07:50,125 of ROI there because that person like first time going, 176 00:07:50,315 --> 00:07:53,005 they would've gone through the motions of Ooh, 177 00:07:53,105 --> 00:07:54,165 here's the book of news 178 00:07:54,185 --> 00:07:55,805 and I'm gonna go to this, 179 00:07:55,805 --> 00:07:57,485 what's new session and this what's new session? 180 00:07:57,505 --> 00:07:58,765 Or I'm gonna go to this round table 181 00:07:59,345 --> 00:08:00,925 or I'm gonna go to this keynote kind of thing. 182 00:08:00,925 --> 00:08:04,565 And that's where you're exposed to all the marketing 183 00:08:04,945 --> 00:08:06,725 and market architecture stuff. 184 00:08:06,835 --> 00:08:09,845 Like you have to pick and choose your battles and 185 00:08:09,865 --> 00:08:13,765 and do that double click and go down a level which more 186 00:08:13,765 --> 00:08:16,405 and more I'm finding to be go to the keynotes 187 00:08:16,585 --> 00:08:20,285 and go to the What's new sessions and then everything else. 188 00:08:20,835 --> 00:08:25,045 Like you're not getting like a deep dive show off demo 189 00:08:25,225 --> 00:08:26,325 for actually how to do it. 190 00:08:26,905 --> 00:08:29,565 So if you don't get that out of it, like why not just go 191 00:08:29,565 --> 00:08:31,965 to those sessions and then wait for the docs to land 192 00:08:32,065 --> 00:08:34,165 and then go check out the docs and 193 00:08:34,185 --> 00:08:36,205 and do it yourself and and go on that way. 194 00:08:36,425 --> 00:08:38,285 So I did that with a lot of stuff this year like 195 00:08:38,285 --> 00:08:39,765 like the co-pilot stuff. 196 00:08:40,185 --> 00:08:42,245 Not inherently interesting to me 197 00:08:42,745 --> 00:08:45,045 but there was some really cool stuff that was announced 198 00:08:45,225 --> 00:08:49,445 around virtual machines both in kind of scale 199 00:08:50,155 --> 00:08:51,285 also in availability. 200 00:08:51,515 --> 00:08:55,645 Like you can do things like hibernate your virtual machines 201 00:08:55,745 --> 00:08:59,125 now there's been a big push into 202 00:09:00,295 --> 00:09:02,125 zonal availability across Microsoft. 203 00:09:02,145 --> 00:09:04,365 So now you can do things like you can take VMs 204 00:09:04,365 --> 00:09:07,445 and a scale set like we talked about VMSS flex 205 00:09:07,565 --> 00:09:08,685 a while ago, a couple months ago. 206 00:09:08,705 --> 00:09:10,685 Yep. So you can take VMs in those scale sets, 207 00:09:10,865 --> 00:09:11,925 you can realign them 208 00:09:11,945 --> 00:09:15,285 to different availability zones all without your application 209 00:09:15,285 --> 00:09:17,085 having to go offline. 210 00:09:17,455 --> 00:09:21,165 There is some nifty stuff that's out there. 211 00:09:21,305 --> 00:09:23,405 And I think some of like even the more interesting stuff, 212 00:09:23,425 --> 00:09:24,805 at least to me in my day-to-Day, 213 00:09:25,465 --> 00:09:27,925 it was actually announced pre Ignite in 214 00:09:27,925 --> 00:09:31,205 that big dump of news a couple weeks ago while they try 215 00:09:31,205 --> 00:09:32,205 and clear the decks 216 00:09:32,305 --> 00:09:35,605 before everything actually lands on that side. 217 00:09:35,805 --> 00:09:36,805 - I don't know that I really want 218 00:09:36,805 --> 00:09:37,645 to go into the copilot 219 00:09:37,645 --> 00:09:38,885 stuff 'cause there's just so much there. 220 00:09:39,245 --> 00:09:40,645 I mean we could touch on some of it 221 00:09:40,745 --> 00:09:44,565 but if you did have to pick something, was there 222 00:09:45,145 --> 00:09:49,045 an announcement that you were interested in 223 00:09:49,045 --> 00:09:52,645 that interested you that you saw from Ignite? 224 00:09:52,785 --> 00:09:54,765 - At Ignite specifically, like I said it was some 225 00:09:54,765 --> 00:09:55,925 of the virtual machine stuff. 226 00:09:56,035 --> 00:09:59,685 There's a push into greater perf 227 00:09:59,785 --> 00:10:01,085 and scale on compute. 228 00:10:01,585 --> 00:10:04,485 So there's things like Azure Boost, I think 229 00:10:04,545 --> 00:10:06,445 that's all a big win. 230 00:10:06,515 --> 00:10:08,925 Like being able to drive up 231 00:10:08,925 --> 00:10:12,845 to 200 gigabits a second from a client VM 232 00:10:13,665 --> 00:10:15,365 is an awesome capability. 233 00:10:15,675 --> 00:10:17,885 Does everybody need it? Absolutely not. 234 00:10:18,425 --> 00:10:19,805 At the same time, does everybody need 235 00:10:19,805 --> 00:10:22,725 to drive 650,000 IOPS from a single VM ? 236 00:10:22,945 --> 00:10:24,085 Eh, probably not. 237 00:10:24,705 --> 00:10:27,125 But I work with the kind of customers that do. 238 00:10:27,785 --> 00:10:32,325 So that's all like that is genuine tech enablement for 239 00:10:33,105 --> 00:10:36,605 the kinds of things that I work on over there. 240 00:10:36,985 --> 00:10:38,725 And admittedly I'm a little bit close to it. 241 00:10:39,115 --> 00:10:40,245 Like we have a new service 242 00:10:40,275 --> 00:10:42,165 that we just launched in Storage Actions, 243 00:10:42,655 --> 00:10:45,165 which is a serverless compute offering 244 00:10:45,435 --> 00:10:47,525 that sits parallel to storage. 245 00:10:47,595 --> 00:10:49,245 Like it's its own resource provider 246 00:10:49,785 --> 00:10:51,525 but it's a purpose-built service 247 00:10:51,825 --> 00:10:54,685 for manipulating blobs objects. 248 00:10:55,025 --> 00:10:57,485 So blob and ad tion two at scale 249 00:10:57,585 --> 00:10:58,965 and customer storage accounts. 250 00:10:58,985 --> 00:11:02,845 So things like doing like massive set blob tier operations 251 00:11:02,845 --> 00:11:04,685 where in the past you would add a scripted out 252 00:11:04,805 --> 00:11:07,605 or go build an application and pick up one of our SDKs. 253 00:11:07,605 --> 00:11:11,765 Like that stuff's all out in the ether and available now. 254 00:11:12,225 --> 00:11:15,445 And then the other interesting one is a week 255 00:11:15,505 --> 00:11:17,205 before announcement kind of thing, 256 00:11:17,785 --> 00:11:21,925 but it's something that I've been really looking for a while 257 00:11:22,545 --> 00:11:26,285 is they finally added rate limit rules to App gateway 258 00:11:26,905 --> 00:11:30,325 and the web application firewall in app gateway . 259 00:11:31,025 --> 00:11:33,125 So for me, this is really cool 260 00:11:33,485 --> 00:11:36,045 'cause I work in fundamentally a space where we do nothing 261 00:11:36,145 --> 00:11:39,725 but work on API surface with our customers all day 262 00:11:39,725 --> 00:11:41,685 and we try and teach 'em the API service 263 00:11:42,065 --> 00:11:44,165 and then we have to teach 'em perf and scale 264 00:11:44,225 --> 00:11:45,365 and everything that goes in it. 265 00:11:45,585 --> 00:11:47,725 And you don't always have the operational controls you want 266 00:11:47,725 --> 00:11:50,965 as a customer there, but now like tools like that, 267 00:11:50,965 --> 00:11:53,325 like rate limiting in a web application firewall, 268 00:11:53,795 --> 00:11:56,405 well it's not ideal to have to inject like a proxy service 269 00:11:56,545 --> 00:11:57,965 or something that sits in the middle. 270 00:11:58,665 --> 00:12:00,525 It still provides a level 271 00:12:00,545 --> 00:12:02,485 of flexibility in application design 272 00:12:03,035 --> 00:12:06,085 that I think folks will appreciate. 273 00:12:06,465 --> 00:12:08,765 And some of that stuff like the web application firewall 274 00:12:08,765 --> 00:12:12,805 thing like that was a GA announcement so it's Ooh cool, 275 00:12:13,005 --> 00:12:15,485 I can just take that to my customers today and 276 00:12:15,585 --> 00:12:17,765 and it's all ready to go and and it all works 277 00:12:17,865 --> 00:12:19,085 and does what it needs to do. 278 00:12:19,315 --> 00:12:22,725 - Nice. I definitely did not pay as close of attention to 279 00:12:23,315 --> 00:12:26,485 some of that type of stuff as you probably did. 280 00:12:26,545 --> 00:12:29,485 But I did see a couple, some of those come through. 281 00:12:29,745 --> 00:12:32,125 - One last really cool one that that I'll give you. 282 00:12:32,125 --> 00:12:35,645 Alright, this one is like wow, I would've loved 283 00:12:35,665 --> 00:12:38,885 to have had this five years ago thing when I was working 284 00:12:39,285 --> 00:12:40,405 actively with compute customers. 285 00:12:40,665 --> 00:12:44,525 So it's another VMSS feature and it is attach 286 00:12:44,585 --> 00:12:47,725 and detach of virtual machines 287 00:12:48,265 --> 00:12:50,805 within virtual machine scale sets. 288 00:12:50,985 --> 00:12:52,245 - Oh I did see that one. 289 00:12:52,425 --> 00:12:55,045 - Yes. So one of the big problems that I always had 290 00:12:55,045 --> 00:12:59,125 with VMSS is if you had to take a machine down, 291 00:12:59,595 --> 00:13:02,605 like you had to do like a scale down operation 292 00:13:02,625 --> 00:13:05,125 to take something out 'cause it was misbehaving your 293 00:13:05,235 --> 00:13:07,605 opportunity to really capture 294 00:13:07,825 --> 00:13:11,565 and play with that machine was limited to a certain degree. 295 00:13:11,835 --> 00:13:14,525 Yeah, there were things you could do, go capture logs, 296 00:13:15,025 --> 00:13:16,925 do memory dumps or whatever you had to do. 297 00:13:17,115 --> 00:13:18,965 Then you had to go through and do all that analysis. 298 00:13:18,965 --> 00:13:21,645 Like I'm a firm believer in if it's running 299 00:13:21,645 --> 00:13:23,925 and you can capture it at the time it's running like 300 00:13:23,925 --> 00:13:25,605 with an actual reproducible event, 301 00:13:25,785 --> 00:13:28,765 you're way better off than you are having 302 00:13:28,765 --> 00:13:30,725 to go down those other kinds of paths. 303 00:13:31,185 --> 00:13:32,885 So what attach 304 00:13:32,885 --> 00:13:36,045 and detach does, so this is something that works with, 305 00:13:36,655 --> 00:13:40,445 again, virtual machine scale sets VMSS flex I believe 306 00:13:41,245 --> 00:13:42,645 specifically is what it does. 307 00:13:43,145 --> 00:13:45,685 But it lets you take a single VM 308 00:13:46,065 --> 00:13:47,965 and you can either move a VM 309 00:13:48,585 --> 00:13:51,245 or you can detach a vm. 310 00:13:51,345 --> 00:13:54,045 So you attach detach from okay an 311 00:13:54,565 --> 00:13:58,285 existing virtual machine scale set all with no downtime. 312 00:13:58,625 --> 00:14:01,365 So say you had a scale set that sits out there 313 00:14:01,825 --> 00:14:04,565 and you need to inject like a new virtual machin 314 00:14:04,565 --> 00:14:06,885 as a sidecar for logging or something like that. 315 00:14:07,505 --> 00:14:09,525 You can just boom, go ahead and stand. 316 00:14:09,625 --> 00:14:10,645 You can stand up 317 00:14:10,785 --> 00:14:14,285 and configure that entire VM outside in isolation 318 00:14:14,665 --> 00:14:16,085 and then just go ahead and shift it 319 00:14:16,085 --> 00:14:17,325 into your scale set when it's ready. 320 00:14:17,755 --> 00:14:19,965 That earlier one earlier one earlier, 321 00:14:20,385 --> 00:14:22,605 the earlier one earlier, you can tell my brain's really 322 00:14:22,605 --> 00:14:25,205 fried this week about being able 323 00:14:25,205 --> 00:14:28,925 to do things like detach so great that you were scaled out 324 00:14:28,945 --> 00:14:31,205 to five VMs in your VM scale set. 325 00:14:31,865 --> 00:14:33,765 One is misbehaving and you really want to see 326 00:14:33,765 --> 00:14:35,285 what it's doing and why it's misbehaving 327 00:14:35,545 --> 00:14:36,565 but obviously you don't wanna do 328 00:14:36,565 --> 00:14:38,885 that while it's in the scale set 'cause you need to continue 329 00:14:38,885 --> 00:14:40,605 to surface customer traffic and 330 00:14:40,605 --> 00:14:41,605 and all those kinds of things. 331 00:14:41,975 --> 00:14:43,125 Great. You just go ahead 332 00:14:43,345 --> 00:14:46,885 and uh, pull it out of that existing skillset. 333 00:14:47,075 --> 00:14:51,925 Like it's super easy to do all arm API driven kind of stuff. 334 00:14:51,925 --> 00:14:55,325 So the rest APIs there, CLI, PowerShell, all 335 00:14:55,325 --> 00:14:58,365 that stuff really slick like it just works. 336 00:14:58,555 --> 00:15:00,405 - Yeah, the public preview of how to do this, 337 00:15:00,635 --> 00:15:03,245 it's like you get the VM and you get the scale set 338 00:15:03,385 --> 00:15:06,125 and you just update it and that's all there is to it. 339 00:15:06,125 --> 00:15:10,645 It's what four lines of PowerShell to add it 340 00:15:10,645 --> 00:15:13,445 to the skillset and then two lines to remove it from. 341 00:15:13,665 --> 00:15:16,005 So yeah, it's not at all complex, 342 00:15:16,035 --> 00:15:17,245 hard to do anything like that. 343 00:15:17,495 --> 00:15:19,445 Super straightforward and simple and 344 00:15:19,445 --> 00:15:20,805 - Public docs are out there for it. 345 00:15:20,805 --> 00:15:21,885 So it's in preview today. 346 00:15:21,955 --> 00:15:23,725 Preview is not for production, 347 00:15:23,955 --> 00:15:25,365 blah blah blah, that kind of stuff. 348 00:15:26,025 --> 00:15:27,965 But if this is something you've been looking 349 00:15:28,025 --> 00:15:29,685 for, it just works. 350 00:15:30,065 --> 00:15:31,685 And I think it's another interesting one 351 00:15:31,685 --> 00:15:36,565 because we talked in the past when we talked about VMSS 352 00:15:36,715 --> 00:15:39,765 flex, we talked about it as this new way 353 00:15:39,825 --> 00:15:41,925 to think about virtual machine scale sets 354 00:15:42,225 --> 00:15:45,525 and how orchestration mode could potentially impact 355 00:15:45,525 --> 00:15:46,605 some of the things you're doing. 356 00:15:47,315 --> 00:15:50,045 This is only available with VMSS flex. 357 00:15:50,825 --> 00:15:53,605 So I think it goes more to a little bit of 358 00:15:53,605 --> 00:15:55,645 that writing on the wall that like hey, 359 00:15:55,645 --> 00:15:56,925 there's no reason not 360 00:15:56,925 --> 00:15:59,685 to use VMSS flex over just straight 361 00:15:59,685 --> 00:16:01,085 virtual machine scale sets. 362 00:16:01,275 --> 00:16:02,685 Like you get all the additive benefits 363 00:16:02,685 --> 00:16:05,845 of scale sets plus the flexibility of flex 364 00:16:06,425 --> 00:16:09,365 and sorry that one was purposeful to go ahead 365 00:16:09,365 --> 00:16:13,045 and be able to make these things really start 366 00:16:13,045 --> 00:16:14,325 to work for you. 367 00:16:14,695 --> 00:16:16,445 Which I think is important. 368 00:16:16,555 --> 00:16:18,445 There's a ton of friction in the cloud in 369 00:16:18,445 --> 00:16:19,685 general and there still is. 370 00:16:20,065 --> 00:16:23,125 So the more that these things just work the way you would 371 00:16:23,125 --> 00:16:26,085 expect them to, the easier life is for everybody. 372 00:16:26,305 --> 00:16:28,405 - Yep, a hundred percent. 373 00:16:29,025 --> 00:16:33,485 So I have one Scott, this is going to go down as one 374 00:16:33,485 --> 00:16:36,365 of those that could end up frustrating me Going back 375 00:16:36,365 --> 00:16:38,005 to all the reasons I talked about before, 376 00:16:38,385 --> 00:16:40,765 but I think we've talked about this 377 00:16:40,765 --> 00:16:45,445 before in my flu frustration, frustration is a new word. 378 00:16:45,515 --> 00:16:47,245 It's a combination of getting me flustered 379 00:16:47,245 --> 00:16:50,765 and frustrated with planner and task management 380 00:16:50,945 --> 00:16:53,325 and that I feel like there's a million different places 381 00:16:53,705 --> 00:16:56,525 to do it and no uniformity. 382 00:16:56,595 --> 00:16:58,365 This is either going to be really good 383 00:16:58,625 --> 00:17:00,165 or completely fall apart. 384 00:17:00,785 --> 00:17:03,925 But there is a new Microsoft planner, 385 00:17:04,165 --> 00:17:06,445 a unified experience bringing together to-dos tasks, 386 00:17:06,535 --> 00:17:07,565 plans and projects. 387 00:17:08,195 --> 00:17:09,925 There's AI stuff in here naturally 388 00:17:09,925 --> 00:17:13,645 because what would be ignite without AI stuff, 389 00:17:14,305 --> 00:17:17,485 but if you go past all the AI stuff, 390 00:17:17,715 --> 00:17:22,005 this is an effort to start trying 391 00:17:22,105 --> 00:17:26,165 to combine everything together in some sort of fashion. 392 00:17:26,565 --> 00:17:27,845 I don't know how it's gonna turn out 393 00:17:28,145 --> 00:17:33,045 but in November of 2023, so this month we are going 394 00:17:33,105 --> 00:17:35,245 to have tasks 395 00:17:35,945 --> 00:17:39,165 by planner in todo in teams is gonna be renamed to planner. 396 00:17:39,505 --> 00:17:42,365 So not a big change there, it's just getting renamed as task 397 00:17:42,385 --> 00:17:44,445 by planner and to do to planner spring. 398 00:17:44,505 --> 00:17:45,725 The new planner app in teams 399 00:17:45,745 --> 00:17:46,965 is gonna be generally available. 400 00:17:47,585 --> 00:17:50,565 And this is another interesting aspect 401 00:17:50,565 --> 00:17:54,685 of this Microsoft project for the web will be renamed 402 00:17:54,685 --> 00:17:58,445 to planner and then later in 2024 these timeframes get 403 00:17:58,465 --> 00:18:01,565 vaguer and vaguer more and more vague as you go. 404 00:18:01,595 --> 00:18:05,045 Like we go from November to spring to just later in 2024. 405 00:18:05,385 --> 00:18:07,405 So could be summer, fall, winter, 406 00:18:07,945 --> 00:18:09,965 we don't know the web experience 407 00:18:09,965 --> 00:18:11,725 of the new planner will be generally available 408 00:18:12,565 --> 00:18:14,565 Features one Love and Microsoft project 409 00:18:14,745 --> 00:18:18,005 for the web will be available and the new planner app 410 00:18:18,005 --> 00:18:20,205 and teams and the new planner web app, 411 00:18:20,495 --> 00:18:22,205 again they say they're combining everything. 412 00:18:22,265 --> 00:18:25,005 To me this sounds a lot like to-do may still exist 413 00:18:25,265 --> 00:18:27,885 but it's really a combination of bringing planner 414 00:18:27,985 --> 00:18:31,685 and project for the web together into this new planner. 415 00:18:32,065 --> 00:18:34,445 And I get the aspect of having 416 00:18:34,465 --> 00:18:36,325 to do is still a separate app like 417 00:18:36,425 --> 00:18:39,565 to do is my task management, it's tasks assigned to me. 418 00:18:39,625 --> 00:18:42,045 My tasks that I add into like personal tasks 419 00:18:42,225 --> 00:18:45,765 or some of that todo is let's bring all my tasks together 420 00:18:45,765 --> 00:18:47,525 where Planner is a little bit more 421 00:18:48,275 --> 00:18:50,525 team task management oriented. 422 00:18:50,785 --> 00:18:52,885 But my biggest frustration was there was still a lot 423 00:18:52,885 --> 00:18:54,605 of stuff missing from planner. 424 00:18:54,995 --> 00:18:57,725 Like the aspect that I couldn't just get a holistic view 425 00:18:57,725 --> 00:18:59,005 of all the tasks and planner 426 00:18:59,225 --> 00:19:03,245 or say here's the five plans that I'm the manager of. 427 00:19:03,315 --> 00:19:05,765 Show me all of the tasks across all 428 00:19:05,765 --> 00:19:08,085 of my team members for these plans. 429 00:19:08,915 --> 00:19:12,445 This is where it's just me hoping that as they redo this 430 00:19:12,445 --> 00:19:13,445 and maybe bring some 431 00:19:13,445 --> 00:19:16,645 of the project management stuff from project into planner, 432 00:19:16,955 --> 00:19:21,285 that planner will actually get a lot better when it comes to 433 00:19:21,445 --> 00:19:22,685 that enterprise work management 434 00:19:22,685 --> 00:19:24,005 because I felt like they rolled it out 435 00:19:24,025 --> 00:19:27,605 and it's languished in my opinion over the last year or two. 436 00:19:27,605 --> 00:19:29,565 Nobody's really made a ton of updates to it. 437 00:19:29,565 --> 00:19:31,125 There's been little stuff here and there 438 00:19:31,625 --> 00:19:34,645 but it feels like there hasn't been any real investment in 439 00:19:34,645 --> 00:19:36,725 it or improvement to some 440 00:19:36,725 --> 00:19:38,805 of these features we all are missing. 441 00:19:39,155 --> 00:19:40,605 Hopefully we'll see some of that. 442 00:19:40,865 --> 00:19:43,645 But this is gonna be again, one of those that 443 00:19:43,745 --> 00:19:44,765 to really see the benefit. 444 00:19:44,965 --> 00:19:46,445 I think it's gonna be like six months, 445 00:19:46,515 --> 00:19:49,045 nine months down the road it'll be one to watch. 446 00:19:49,465 --> 00:19:51,845 And let me tell you, any cha time I have a chance 447 00:19:51,865 --> 00:19:55,645 to provide some feedback on what I think should be in here. 448 00:19:55,885 --> 00:19:56,885 I will absolutely do it 449 00:19:56,885 --> 00:20:00,365 because I mean at Microsoft 365 I would love 450 00:20:00,365 --> 00:20:02,845 to use Planner over Jira work management. 451 00:20:02,845 --> 00:20:03,845 We've talked about it. That's 452 00:20:03,845 --> 00:20:06,885 what I use right now is just from a pure work management 453 00:20:06,885 --> 00:20:08,285 perspective it has 454 00:20:08,425 --> 00:20:10,605 so much more functionality than Planner does. 455 00:20:10,785 --> 00:20:12,045 - 100% - . 456 00:20:12,345 --> 00:20:16,285 I'm hoping that we'll see some updates, some changes come 457 00:20:16,285 --> 00:20:18,085 with this, but that is one 458 00:20:18,085 --> 00:20:21,285 that was not necessarily AI driven outta the conference 459 00:20:21,395 --> 00:20:24,765 that I am going to keep an eye on 460 00:20:24,765 --> 00:20:27,205 because I would love to bring that in. 461 00:20:27,455 --> 00:20:29,445 There are some things in planet Earth that I really like, 462 00:20:29,445 --> 00:20:32,685 like being able to time to a team, being able to do some 463 00:20:32,685 --> 00:20:35,485 of the document attachment stuff, some of that, 464 00:20:35,915 --> 00:20:38,685 that it just works better natively with some 465 00:20:38,685 --> 00:20:40,445 of the other Microsoft 365 stuff. 466 00:20:40,665 --> 00:20:43,965 So we, we will see this 467 00:20:43,965 --> 00:20:44,965 - One's hard for me. 468 00:20:44,965 --> 00:20:48,645 So my problem with planner isn't necessarily planner 469 00:20:49,155 --> 00:20:51,525 it's planner in the disparate nature of it, right? 470 00:20:51,525 --> 00:20:54,005 Like like there's no cohesion at all 471 00:20:54,225 --> 00:20:56,125 to all the various to-do services. 472 00:20:56,355 --> 00:20:59,845 Like the plans that you make in plans are not the same 473 00:20:59,865 --> 00:21:03,365 as the like a task list in SharePoint which are not the same 474 00:21:03,365 --> 00:21:06,005 as your flagged items in Outlook, 475 00:21:06,535 --> 00:21:09,365 which are definitely not the same as project. 476 00:21:09,675 --> 00:21:11,205 There's varying levels of things there 477 00:21:11,465 --> 00:21:13,125 and that's not the worst thing in the world, right? 478 00:21:13,125 --> 00:21:14,405 Like right tool for the right job. 479 00:21:14,785 --> 00:21:16,725 The problem is there's a whole bunch of tools 480 00:21:17,145 --> 00:21:18,645 and it's not always clear like 481 00:21:18,645 --> 00:21:20,485 what the right one is And this 482 00:21:20,485 --> 00:21:21,765 doesn't seem to solve that problem. 483 00:21:21,955 --> 00:21:25,805 Like if I read between the lines on this blog post, 484 00:21:26,155 --> 00:21:28,525 this is all the same services on the backend 485 00:21:29,345 --> 00:21:31,885 and a fancy new ui 486 00:21:32,145 --> 00:21:33,005 - New front end. Yeah 487 00:21:33,355 --> 00:21:35,325 - Like we've put a, we've put a new proxy on it 488 00:21:35,385 --> 00:21:37,725 but we haven't fixed the underlying problem of 489 00:21:38,365 --> 00:21:39,965 I flag an email and Outlook 490 00:21:40,345 --> 00:21:42,765 and I have a task in a SharePoint list. 491 00:21:42,915 --> 00:21:44,725 Like how do those two things 492 00:21:45,325 --> 00:21:46,805 actually come together and play? 493 00:21:47,315 --> 00:21:50,205 Like in my head, if you're striving for simplification, 494 00:21:50,755 --> 00:21:52,285 like one path is you do it like this, 495 00:21:52,285 --> 00:21:53,885 you put everything in a unified UI 496 00:21:54,145 --> 00:21:55,565 and then you live with the disparate nature. 497 00:21:55,665 --> 00:21:58,285 The other thing is you make this the surface 498 00:21:59,065 --> 00:22:01,245 and the container for tasks 499 00:22:01,905 --> 00:22:03,325 and for all these different things 500 00:22:03,465 --> 00:22:05,845 and then those other services start to consume them. 501 00:22:06,345 --> 00:22:09,405 So rather than having five disparate services pulled 502 00:22:09,565 --> 00:22:12,525 together under one banner, what if you had one banner 503 00:22:12,555 --> 00:22:15,005 that was then just consumed by those services 504 00:22:15,395 --> 00:22:16,565 that could that go the other way? 505 00:22:16,565 --> 00:22:18,765 It makes sense and I don't get the sense from this 506 00:22:18,765 --> 00:22:20,445 that this fixes 507 00:22:21,715 --> 00:22:22,715 - That problem. 508 00:22:23,225 --> 00:22:25,725 - At least some of my underlying frustrations there 509 00:22:25,825 --> 00:22:26,845 and there's a whole lot of like 510 00:22:26,945 --> 00:22:28,165 me personally in there, right? 511 00:22:28,165 --> 00:22:29,925 Just having to flip through all these different tools 512 00:22:29,925 --> 00:22:32,005 throughout the day and everything else like there 513 00:22:32,005 --> 00:22:33,725 because there becomes a point with all this stuff, right? 514 00:22:33,965 --> 00:22:35,525 I think like SharePoint files 515 00:22:35,545 --> 00:22:38,885 and teams generally works until it doesn't work. 516 00:22:39,325 --> 00:22:40,405 'cause you need to go over to SharePoint 517 00:22:40,405 --> 00:22:42,205 and do something 518 00:22:42,465 --> 00:22:44,565 and it's like this in so many places, right? 519 00:22:44,705 --> 00:22:45,925 You eventually hit that wall 520 00:22:45,925 --> 00:22:48,285 where it's like oh that doesn't do that thing. 521 00:22:48,385 --> 00:22:50,965 So now I guess I just go to the canonical service 522 00:22:50,995 --> 00:22:52,005 that actually hosts it. 523 00:22:52,145 --> 00:22:53,165 And that's really only helpful 524 00:22:53,165 --> 00:22:55,405 to you even if you know the canonical services there, 525 00:22:55,405 --> 00:22:58,165 which I don't think many users do. 526 00:22:58,235 --> 00:23:01,125 Like it's not always clear the other way to hop out for 527 00:23:01,125 --> 00:23:02,125 - That. 528 00:23:02,125 --> 00:23:04,725 Yeah and I think that's to where I'm waiting to see 529 00:23:05,235 --> 00:23:07,085 what happens with planner because I'm with you. 530 00:23:07,155 --> 00:23:10,365 Like we should just get rid of the ability to do task lists 531 00:23:10,625 --> 00:23:13,005 and SharePoint and if you want a task list 532 00:23:13,005 --> 00:23:16,325 and SharePoint put in planner, like why do we need boards 533 00:23:16,325 --> 00:23:17,325 and a SharePoint list? 534 00:23:17,465 --> 00:23:19,245 Why do we need, and I get different tools 535 00:23:19,305 --> 00:23:21,045 for different people, they all like different things 536 00:23:21,625 --> 00:23:24,405 but it does create a lot of confusion. 537 00:23:24,705 --> 00:23:27,645 And to your point about Outlook, that's been one 538 00:23:27,645 --> 00:23:29,045 of my biggest gripes with Planner 539 00:23:29,185 --> 00:23:32,165 for years is like you said, you can flag one in Outlook, 540 00:23:32,555 --> 00:23:34,525 flag an email and Outlook and it goes to do, 541 00:23:34,745 --> 00:23:37,445 but it doesn't help me give that task to somebody else 542 00:23:37,515 --> 00:23:38,725 that needs to handle that thing. 543 00:23:38,725 --> 00:23:40,045 That came in via my email 544 00:23:40,425 --> 00:23:43,445 and there was, I don't know if it was un user voice, 545 00:23:43,525 --> 00:23:46,125 I found it in tight community like two and a half years ago. 546 00:23:46,155 --> 00:23:47,525 Someone asked for, 547 00:23:47,665 --> 00:23:50,805 Hey can we add an Outlook email to a planner task? 548 00:23:50,875 --> 00:23:53,605 Like we need an add-in And this is one thing that Jira 549 00:23:53,605 --> 00:23:54,805 - Does be Simple thing, right? 550 00:23:54,905 --> 00:23:55,905 - Add to planner. 551 00:23:55,905 --> 00:23:58,605 And it was like there was a response from Microsoft 552 00:23:58,605 --> 00:24:00,805 that said we're working on it two and a half years ago 553 00:24:01,265 --> 00:24:03,125 and here we are again. 554 00:24:03,125 --> 00:24:05,845 Fingers crossed that maybe they fix some of that. 555 00:24:05,985 --> 00:24:08,085 And this is giving it new life. 556 00:24:08,465 --> 00:24:09,845 If it's similar to what you said 557 00:24:09,845 --> 00:24:13,245 and it's just a new UI on top 558 00:24:13,245 --> 00:24:14,925 of three different services 559 00:24:15,065 --> 00:24:18,925 and there's no really new functionality like adding tasks 560 00:24:18,925 --> 00:24:21,445 from Outlook or some of that, 561 00:24:21,755 --> 00:24:23,405 then I'm gonna be disappointed. I 562 00:24:23,405 --> 00:24:25,285 - Don't know but uh, like just reading and 563 00:24:25,295 --> 00:24:27,085 - Right and I don't either 564 00:24:27,355 --> 00:24:28,725 - From what I know of the way things work 565 00:24:28,745 --> 00:24:29,885 and reading between the lines 566 00:24:29,985 --> 00:24:31,485 and reading that blog posts like 567 00:24:31,485 --> 00:24:34,645 that seems like a new coat of paint. 568 00:24:34,735 --> 00:24:36,005 Maybe not lipstick on a pig 569 00:24:36,065 --> 00:24:41,045 but it's you, you're masking over some of the, some 570 00:24:41,125 --> 00:24:43,405 of the underlying things that exist there, 571 00:24:43,775 --> 00:24:47,205 which could actually be like the more problematic area. 572 00:24:47,635 --> 00:24:50,125 Like just that bigger rock that you wanna go up 573 00:24:50,145 --> 00:24:51,685 and turn over and 574 00:24:51,745 --> 00:24:54,525 and see what you can make happen. I don't know on 575 00:24:54,525 --> 00:24:55,005 - That side. Yes I 576 00:24:55,005 --> 00:24:56,005 - Don't. 577 00:24:56,005 --> 00:24:57,245 I got another one just while we got a little bit of time. 578 00:25:01,265 --> 00:25:02,885 - Do you feel overwhelmed by trying 579 00:25:02,885 --> 00:25:05,165 to manage your Office 365 environment? 580 00:25:05,305 --> 00:25:07,045 Are you facing unexpected issues 581 00:25:07,045 --> 00:25:08,925 that disrupt your company's productivity? 582 00:25:08,955 --> 00:25:11,725 Intelligent is here to help much like you take your car 583 00:25:11,725 --> 00:25:14,165 to the mechanic that has specialized knowledge on how 584 00:25:14,165 --> 00:25:17,125 to best keep your car running Intelligent helps you 585 00:25:17,125 --> 00:25:18,925 with your Microsoft Cloud environment 586 00:25:18,925 --> 00:25:20,525 because that's their expertise. 587 00:25:20,675 --> 00:25:21,965 Intelligent keeps up 588 00:25:21,965 --> 00:25:24,005 with the latest updates on the Microsoft Cloud 589 00:25:24,025 --> 00:25:25,485 to help keep your business running 590 00:25:25,805 --> 00:25:27,005 smoothly and ahead of the curve. 591 00:25:27,035 --> 00:25:28,965 Whether you are a small organization 592 00:25:28,965 --> 00:25:31,325 with just a few users up to an organization 593 00:25:31,325 --> 00:25:34,445 of several thousand employees, they want to partner with you 594 00:25:34,465 --> 00:25:38,165 to implement and administer your Microsoft Cloud technology, 595 00:25:38,735 --> 00:25:42,125 visit them at intelligent.com/podcast. 596 00:25:42,625 --> 00:25:47,045 That's I-N-T-E-L-L-I-G-I-N 597 00:25:47,125 --> 00:25:49,125 k.com/podcast. 598 00:25:49,745 --> 00:25:52,125 For more information or to schedule a 30 minute call 599 00:25:52,125 --> 00:25:53,405 to get started with them today. 600 00:25:54,365 --> 00:25:57,205 Remember Intelligent focuses on the Microsoft cloud 601 00:25:57,345 --> 00:25:59,165 so you can focus on your business. 602 00:26:01,905 --> 00:26:04,485 - So this one really confused me. 603 00:26:04,485 --> 00:26:06,645 You're gonna have to help me out here 604 00:26:06,865 --> 00:26:09,325 and deal with the stupidity. 605 00:26:09,325 --> 00:26:10,645 That is Scott sometimes. 606 00:26:11,425 --> 00:26:14,285 So SharePoint premium was announced. 607 00:26:14,425 --> 00:26:15,965 - Oh we're jumping down to this one, 608 00:26:16,095 --> 00:26:18,045 - We're gonna do this one 'cause you have a limited amount 609 00:26:18,045 --> 00:26:19,525 of time which means you can't rant 610 00:26:19,665 --> 00:26:20,765 and I can get you worked up 611 00:26:20,765 --> 00:26:22,125 before your next meeting . 612 00:26:22,125 --> 00:26:25,565 So SharePoint Premium, what the heck is SharePoint Premium? 613 00:26:25,885 --> 00:26:27,325 'cause SharePoint's already a premium product. 614 00:26:27,485 --> 00:26:28,605 I already pay money for it. Good 615 00:26:28,805 --> 00:26:29,805 - Question. 616 00:26:29,805 --> 00:26:30,245 I don't know . 617 00:26:31,385 --> 00:26:34,005 - Oh I thought you were gonna be ready for, it's your show. 618 00:26:34,005 --> 00:26:36,525 These are your notes, your links come on. 619 00:26:36,625 --> 00:26:41,005 - No I am not ready for this. So, well I threw 'em out here. 620 00:26:41,825 --> 00:26:45,405 Here's the best I can figure 621 00:26:46,185 --> 00:26:49,925 is it's SharePoint copilot if you want my 622 00:26:50,555 --> 00:26:54,765 general overall honest opinion on SharePoint premium. 623 00:26:55,245 --> 00:26:59,965 I have not read this but this deals a lot more from what I 624 00:27:00,695 --> 00:27:05,285 understand with the culmination of 625 00:27:05,285 --> 00:27:08,765 what they actually announced back in May at the SharePoint 626 00:27:08,765 --> 00:27:12,205 conference where it was starting 627 00:27:12,265 --> 00:27:17,045 to tie in some of the being able to use AI to help 628 00:27:17,235 --> 00:27:18,525 with . 629 00:27:18,915 --> 00:27:21,605 This is where it all gets weird to be able to help 630 00:27:21,605 --> 00:27:23,125 with the content in SharePoint. 631 00:27:23,465 --> 00:27:25,325 So you've talked about like you write your 632 00:27:25,325 --> 00:27:26,885 newsletters in SharePoint, right? 633 00:27:26,885 --> 00:27:28,565 Mm-Hmm . And you were excited about the whole 634 00:27:28,885 --> 00:27:31,605 functionality of now I can 635 00:27:32,135 --> 00:27:33,365 write those newsletters in 636 00:27:33,365 --> 00:27:34,405 SharePoint, send 'em out as emails. 637 00:27:34,425 --> 00:27:39,005 All of that I think based on my understanding is some 638 00:27:39,005 --> 00:27:43,605 of this SharePoint premium stuff is now you can leverage AI 639 00:27:43,945 --> 00:27:47,285 to help you write those newsletters to help you format 'em 640 00:27:47,285 --> 00:27:50,645 to help you bring content together, bring those types 641 00:27:50,705 --> 00:27:55,205 of things into SharePoint, not to be confused with 642 00:27:55,205 --> 00:27:58,085 what you are gonna be able to do in co-pilot. 643 00:27:58,355 --> 00:28:00,725 Some of the, I don't know if it's in here, I need to look 644 00:28:00,725 --> 00:28:03,445 through this article 'cause this is a long article. 645 00:28:03,915 --> 00:28:05,885 Make sure the right information is shared sensitive 646 00:28:05,885 --> 00:28:07,685 information doesn't accidentally overshared 647 00:28:08,225 --> 00:28:10,485 and exposed in search or co-pilot. 648 00:28:10,865 --> 00:28:14,045 So there's a little bit of this go by SharePoint premium 649 00:28:14,145 --> 00:28:15,725 to help you get ready for co-pilot 650 00:28:15,755 --> 00:28:18,805 because SharePoint premium is also gonna extend some 651 00:28:18,805 --> 00:28:22,325 of the traditional IT controls around governance, 652 00:28:22,955 --> 00:28:24,005 auto tagging. 653 00:28:24,765 --> 00:28:27,765 I saw some, this just gets weird Scott 654 00:28:28,205 --> 00:28:30,725 'cause then I saw some stuff about co-pilot for topics. 655 00:28:31,025 --> 00:28:35,405 But topics is technically still a SharePoint ish feature 656 00:28:35,825 --> 00:28:38,285 but I don't know that SharePoint premium gives you co-pilot 657 00:28:38,285 --> 00:28:39,485 and topics or if co-pilot 658 00:28:39,485 --> 00:28:42,485 and topics is Microsoft 365 co-pilot. 659 00:28:43,225 --> 00:28:47,605 The lines blurred here for me some in terms of 660 00:28:48,635 --> 00:28:50,685 what exactly this is. 661 00:28:51,365 --> 00:28:53,525 I think there's some security stuff in here. 662 00:28:53,805 --> 00:28:57,405 I think there's some additional insights around 663 00:28:58,425 --> 00:29:00,245 how people interact with your content, 664 00:29:00,555 --> 00:29:03,805 what people are viewing with your content, some of 665 00:29:03,805 --> 00:29:04,845 that type of stuff too. 666 00:29:05,185 --> 00:29:06,405 But it's interesting then 667 00:29:06,565 --> 00:29:08,285 'cause as you go down in this article 668 00:29:08,285 --> 00:29:09,805 where they talk about SharePoint premium, 669 00:29:09,875 --> 00:29:14,285 they start talking about Microsoft 365 backup and archive. 670 00:29:14,425 --> 00:29:15,565 And this may just be, 671 00:29:16,505 --> 00:29:18,845 see this says introducing SharePoint premium, the future 672 00:29:18,845 --> 00:29:20,645 of AI powered content management. 673 00:29:20,905 --> 00:29:23,485 So that kinda sums it up. It's AI powered. 674 00:29:23,705 --> 00:29:25,205 But when they talk about backup 675 00:29:25,265 --> 00:29:28,565 and archive, that is not SharePoint premium. 676 00:29:29,025 --> 00:29:31,965 That's starting to get into the pay-as-you-go services 677 00:29:32,105 --> 00:29:34,725 and stuff for Microsoft Syntex. 678 00:29:34,745 --> 00:29:36,605 So this article is a little deceiving 679 00:29:36,605 --> 00:29:37,965 and that some of the things mentioned here, 680 00:29:38,105 --> 00:29:40,765 no it's not necessarily Syntex is getting 681 00:29:40,765 --> 00:29:41,765 - Rolled into premium. 682 00:29:41,995 --> 00:29:43,605 Okay, I have a different take than you. 683 00:29:43,825 --> 00:29:47,445 So and maybe this is based on past life kinds of things. 684 00:29:47,985 --> 00:29:51,005 So if I'm reading between the lines on this one, 685 00:29:51,435 --> 00:29:54,605 this is Microsoft making a little bit of a play 686 00:29:54,985 --> 00:29:57,325 to actually turn SharePoint 687 00:29:57,695 --> 00:29:59,325 after how many years 688 00:30:00,235 --> 00:30:03,245 into a proper document management service 689 00:30:03,905 --> 00:30:05,525 or a content management service. 690 00:30:05,665 --> 00:30:06,685 So if you think about, 691 00:30:07,325 --> 00:30:09,645 I don't know if you've ever done customer work on top 692 00:30:09,645 --> 00:30:12,885 of things like OpenText or laser fee 693 00:30:13,385 --> 00:30:16,885 or Highland like OnBase, anything like that. 694 00:30:17,755 --> 00:30:21,005 Like every organization I've worked in that has those tools, 695 00:30:21,515 --> 00:30:23,045 they also have SharePoint 696 00:30:23,265 --> 00:30:25,325 and it's been always just a major pain. 697 00:30:25,405 --> 00:30:26,645 A major contentious thing. 698 00:30:27,105 --> 00:30:28,405 So I look at a lot of the things 699 00:30:28,405 --> 00:30:31,125 that are coming in here like built-in document viewers, 700 00:30:31,145 --> 00:30:35,765 native e-signatures and signing better metadata and movement 701 00:30:35,905 --> 00:30:38,765 and security controls, stuff like 702 00:30:39,115 --> 00:30:43,685 that is all playing around in the content service 703 00:30:44,405 --> 00:30:47,485 platform space where there's already some big kind 704 00:30:47,485 --> 00:30:49,125 of players and I wonder if 705 00:30:49,365 --> 00:30:50,725 Microsoft can finally make it work. 706 00:30:51,245 --> 00:30:54,285 'cause every job that I had, like when I used to, I I used, 707 00:30:54,445 --> 00:30:55,725 I worked in a couple law firms. 708 00:30:55,895 --> 00:30:58,965 Every single law firm I worked in had some form 709 00:30:59,305 --> 00:31:00,685 of Laserfiche going on. 710 00:31:00,685 --> 00:31:03,285 Like I learned to love to hate it kind of thing. 711 00:31:03,485 --> 00:31:06,245 'cause you had to, and again those organizations also had 712 00:31:06,655 --> 00:31:09,325 SharePoint and full on Office stack 713 00:31:09,625 --> 00:31:11,125 and all the things that come with them. 714 00:31:11,355 --> 00:31:12,965 There's a whole world of stuff out there 715 00:31:12,965 --> 00:31:14,485 that isn't done in SharePoint 716 00:31:14,925 --> 00:31:16,965 'cause Microsoft was never interested in it. 717 00:31:17,305 --> 00:31:19,565 And some of this stuff is they've finally run 718 00:31:19,565 --> 00:31:20,725 out of other things to build. 719 00:31:21,065 --> 00:31:23,285 So now they can go after some of the established stuff. 720 00:31:23,645 --> 00:31:24,965 - I kinda get that. 721 00:31:25,145 --> 00:31:27,525 But they also talk about SharePoint premium. 722 00:31:28,165 --> 00:31:29,685 I put this in the Discord chat too. 723 00:31:29,825 --> 00:31:31,565 Our advanced content management 724 00:31:31,585 --> 00:31:34,285 and experience platform for next evolution of syntax. 725 00:31:34,635 --> 00:31:36,605 Okay I that's where it's coming from. 726 00:31:36,605 --> 00:31:40,005 The syntax SharePoint Premium brings AI automation added 727 00:31:40,325 --> 00:31:42,725 security to content experience processing and governance. 728 00:31:42,895 --> 00:31:45,725 SharePoint premium will be transitioning services already 729 00:31:45,725 --> 00:31:48,365 part of syntax including SharePoint Advance Management 730 00:31:48,505 --> 00:31:50,205 to join SharePoint services. 731 00:31:50,585 --> 00:31:52,365 So I get all of this, this is all coming. 732 00:31:52,545 --> 00:31:54,285 So that's where you're getting it from is 733 00:31:54,285 --> 00:31:55,805 that's all gonna be in SharePoint premium. 734 00:31:56,515 --> 00:31:59,925 Then my next question is, is given this is another sku, 735 00:32:00,585 --> 00:32:03,965 are you gonna have to pay for SharePoint premium 736 00:32:04,465 --> 00:32:09,325 or is SharePoint Premium the umbrella that all 737 00:32:09,565 --> 00:32:11,085 of these services sit under? 738 00:32:11,275 --> 00:32:14,205 Because the next link that you'll see down is the, 739 00:32:14,715 --> 00:32:18,845 essentially all of this stuff that we're talking about 740 00:32:19,505 --> 00:32:21,565 is transitioning to a pay-as-you-go services 741 00:32:21,665 --> 00:32:23,485 and it's still labeled pay-as-you-go services 742 00:32:23,625 --> 00:32:24,805 and pricing for syntax. 743 00:32:25,025 --> 00:32:28,485 So pre-built document processing has a price per 744 00:32:28,485 --> 00:32:30,125 transaction structure. 745 00:32:30,285 --> 00:32:33,085 Freeform document processing has a price per transaction, 746 00:32:33,405 --> 00:32:36,925 unstructured document processing, content assembly, 747 00:32:37,175 --> 00:32:40,885 image tagging, taxonomy tagging, e-signatures, 748 00:32:41,435 --> 00:32:46,325 typical character recognition, OCR, Microsoft 365 archive 749 00:32:46,325 --> 00:32:49,565 and Microsoft 365 backup are all 750 00:32:50,145 --> 00:32:54,605 priced based on transactions or in the case of backup 751 00:32:54,705 --> 00:32:58,405 and archive are based on the amount 752 00:32:58,405 --> 00:32:59,405 of storage you're consuming. 753 00:32:59,905 --> 00:33:02,845 So is premium just a skew you light up 754 00:33:02,845 --> 00:33:06,925 and tie a credit card to so that all of this stuff is 755 00:33:07,035 --> 00:33:08,765 what SharePoint Premium is? 756 00:33:08,995 --> 00:33:10,685 - Good question one. 757 00:33:10,705 --> 00:33:13,925 Has the office team ever really rationalized licensing in a 758 00:33:13,925 --> 00:33:16,005 way that that makes sense? 759 00:33:16,605 --> 00:33:19,525 I don't know that they have 760 00:33:20,035 --> 00:33:21,285 ever done some of those things. 761 00:33:21,425 --> 00:33:26,325 So licensing aside, it's funny if you go so to 762 00:33:26,345 --> 00:33:28,285 to your point like that quote 763 00:33:28,665 --> 00:33:31,885 of SharePoint Premium is an advanced content management 764 00:33:31,885 --> 00:33:32,885 experience platform. 765 00:33:33,625 --> 00:33:36,525 It brings AI automation added security 766 00:33:36,625 --> 00:33:39,845 to your content experiences, processing and governance. 767 00:33:40,175 --> 00:33:42,885 Great. The rest of it's all about just transitioning right 768 00:33:42,885 --> 00:33:43,925 from existing services. 769 00:33:44,505 --> 00:33:47,805 So if I go and read like OnBase from Highland 770 00:33:48,405 --> 00:33:50,725 Highland's OnBase platform automates your processes, 771 00:33:51,075 --> 00:33:52,685 manages your important business content 772 00:33:52,985 --> 00:33:55,805 and works with your other applications to provide users 773 00:33:55,875 --> 00:33:59,205 with a complete view of the right information when 774 00:33:59,425 --> 00:34:00,765 and where they need it. 775 00:34:00,945 --> 00:34:03,765 OnBase gives you visibility into the statuses of processes, 776 00:34:04,045 --> 00:34:06,045 documents and information and automates 777 00:34:06,045 --> 00:34:08,365 and supports retention requirements. 778 00:34:08,755 --> 00:34:11,565 This allows you to transform your internal processes 779 00:34:11,685 --> 00:34:15,165 and customer experience, reduce your opt uh, operating costs 780 00:34:15,385 --> 00:34:16,965 and minimize risk. 781 00:34:17,185 --> 00:34:18,485 Sounds pretty darn familiar. 782 00:34:19,005 --> 00:34:22,725 like basically one for one, they're coming over 783 00:34:22,725 --> 00:34:25,405 to this space so they're, they're finally trying 784 00:34:25,425 --> 00:34:29,965 to bolt office into a proper content platform. 785 00:34:30,425 --> 00:34:32,045 I'm gonna get my popcorn out for this one 786 00:34:32,245 --> 00:34:33,645 'cause it'll get interesting really fast. 787 00:34:33,865 --> 00:34:35,445 - So now I'm even more confused 788 00:34:35,965 --> 00:34:38,485 'cause you keep reading in the article under availability. 789 00:34:38,745 --> 00:34:39,845 If you're following along 790 00:34:39,985 --> 00:34:42,165 and you want to go read this availability, 791 00:34:42,575 --> 00:34:43,725 we're bringing SharePoint, 792 00:34:43,905 --> 00:34:45,525 I'm reading these a little bit out of order 793 00:34:45,825 --> 00:34:47,205 but it's all under availability. 794 00:34:47,775 --> 00:34:49,245 We're bringing SharePoint premium 795 00:34:49,425 --> 00:34:52,165 to broad availability in the first half of 2024. 796 00:34:52,505 --> 00:34:54,245 So next seven months, 797 00:34:55,155 --> 00:34:57,685 both SharePoint premium seat licenses. 798 00:34:57,945 --> 00:34:59,765 So there is gonna be a seat license for this 799 00:35:00,145 --> 00:35:01,725 and Pego services. 800 00:35:01,825 --> 00:35:03,765 mm-Hmm can be used independently 801 00:35:04,025 --> 00:35:06,405 and combined to meet your business requirements. 802 00:35:06,705 --> 00:35:09,605 So it sounds like there is gonna be some aspect 803 00:35:09,605 --> 00:35:13,085 of SharePoint premium that isn't syntax 804 00:35:13,425 --> 00:35:17,165 or is there some of those syntax like topics 805 00:35:17,545 --> 00:35:21,285 for instance I think technically falls under syntax 806 00:35:21,665 --> 00:35:25,045 but I thought they transitioned all of syntax out of uh, 807 00:35:25,225 --> 00:35:28,325 per user model into a PEGO model. 808 00:35:28,355 --> 00:35:30,365 They have not but now it sounds isn't 809 00:35:30,365 --> 00:35:32,245 it all out of Pego yet? Nope. Are you sure? 810 00:35:32,305 --> 00:35:36,805 - Yep. Positive. So , this is another sneaky one. 811 00:35:37,225 --> 00:35:41,405 So if you go to the adoption hub, so you go 812 00:35:41,405 --> 00:35:44,605 to SharePoint premium [email protected] Yep. 813 00:35:44,905 --> 00:35:48,085 The overview of SharePoint premium link 814 00:35:48,635 --> 00:35:51,925 that leans you directly on the overview 815 00:35:51,925 --> 00:35:53,525 of Microsoft Syntax article 816 00:35:54,125 --> 00:35:56,205 straight up like you're just going there 817 00:35:56,825 --> 00:35:59,965 and then you can dive into syntax stuff from there. 818 00:36:00,215 --> 00:36:03,765 Where lysing for syntax is both pay 819 00:36:03,765 --> 00:36:05,685 as you go per user licensing 820 00:36:06,105 --> 00:36:09,965 and then the per use stuff as well that comes in it. 821 00:36:10,265 --> 00:36:13,725 So one would think just from the way it's all wired up 822 00:36:13,725 --> 00:36:17,605 today, the syntax documentation just gets rebranded. 823 00:36:17,605 --> 00:36:19,005 Like they do a mass rename , 824 00:36:19,075 --> 00:36:23,125 they call it SharePoint premium and then they pull archive 825 00:36:23,265 --> 00:36:24,565 and back up underneath those 826 00:36:24,745 --> 00:36:27,565 and then hopefully customers have access to those 827 00:36:27,705 --> 00:36:32,685 as pego services without the need to consume some type 828 00:36:32,725 --> 00:36:35,245 of like per user license and SharePoint premium as well. 829 00:36:35,345 --> 00:36:36,405 But that clarity is not there 830 00:36:36,625 --> 00:36:38,405 - But that doesn't so 831 00:36:38,805 --> 00:36:40,925 'cause it talks about SharePoint premium becoming probably 832 00:36:40,925 --> 00:36:43,005 available next year, which means there's certain stuff 833 00:36:43,005 --> 00:36:45,165 that's obviously not there yet. 834 00:36:45,185 --> 00:36:47,125 - Backup and archive aren't there today. You 835 00:36:47,125 --> 00:36:48,805 - Think those are the only two nor 836 00:36:48,805 --> 00:36:51,805 - Are some of the content services stuff, right? 837 00:36:52,305 --> 00:36:53,485 If they actually wanna make a play 838 00:36:53,485 --> 00:36:54,885 as a content services platform, 839 00:36:55,145 --> 00:36:59,485 having things like a built-in content viewer critical like 840 00:36:59,485 --> 00:37:00,725 that doesn't exist for all forms 841 00:37:00,785 --> 00:37:02,005 of content in SharePoint today. 842 00:37:02,185 --> 00:37:04,445 Having things like e-signatures 843 00:37:04,665 --> 00:37:06,525 and like verified metadata movement, all that stuff 844 00:37:07,075 --> 00:37:08,765 doesn't exist in SharePoint today. 845 00:37:09,145 --> 00:37:11,965 That's the stuff that's to come and and be bolted in. 846 00:37:12,065 --> 00:37:14,925 But Synt syntax is there. You can go do syntax. 847 00:37:15,145 --> 00:37:16,565 - Syntax is there right 848 00:37:16,825 --> 00:37:17,825 - Now. 849 00:37:17,825 --> 00:37:20,005 You can go do M 365 backup archive like 850 00:37:20,115 --> 00:37:21,645 that stuff's all kicking out in preview. 851 00:37:22,105 --> 00:37:23,485 That's all out there as well. 852 00:37:24,045 --> 00:37:25,245 Actually E-signatures are there too 853 00:37:25,445 --> 00:37:27,605 'cause you can do e-signatures in in syntax. 854 00:37:27,715 --> 00:37:29,365 - E-signature is there too. Yeah, 855 00:37:29,545 --> 00:37:33,645 - So there's a good portion of it that already does exist, 856 00:37:33,895 --> 00:37:34,895 - Right? 857 00:37:34,895 --> 00:37:35,925 Well 'cause that's under availability 858 00:37:36,665 --> 00:37:39,045 before it says we'll bring all of this broadly available. 859 00:37:39,105 --> 00:37:41,685 The first half of 2024 it says you can start using 860 00:37:41,685 --> 00:37:42,725 SharePoint premium today. 861 00:37:42,875 --> 00:37:45,165 Like you can start using SharePoint premium today 862 00:37:45,465 --> 00:37:47,405 and we're bringing SharePoint premium 863 00:37:47,505 --> 00:37:49,125 to broad availability in the first half 864 00:37:49,125 --> 00:37:51,965 of 2024 are both under availability. 865 00:37:52,305 --> 00:37:55,005 So it's like sort of there but not really there 866 00:37:55,065 --> 00:37:56,125 and lead it up to you. 867 00:37:56,125 --> 00:37:58,845 And then it does lists like content processing 868 00:37:59,195 --> 00:38:00,285 - More to come - . 869 00:38:00,515 --> 00:38:03,365 Yeah. Is there content assembly, OCR E-signature, 870 00:38:03,785 --> 00:38:05,205 all the pego stuff. 871 00:38:05,345 --> 00:38:06,925 You can also purchase governance 872 00:38:07,065 --> 00:38:09,085 for the SharePoint advanced management. 873 00:38:09,635 --> 00:38:11,805 Then it lists services under the syntax brand 874 00:38:11,805 --> 00:38:14,485 that are moving to the premium brand in 2024. 875 00:38:14,905 --> 00:38:16,445 So maybe that's some of it is, 876 00:38:16,835 --> 00:38:18,605 it's broadly available in the first half 877 00:38:18,605 --> 00:38:22,925 of 2024 when syntax gets officially renamed to premium. 878 00:38:23,345 --> 00:38:26,485 And that article you sent does break it out 879 00:38:26,785 --> 00:38:30,245 as all those pego things at the top under syntax. 880 00:38:30,705 --> 00:38:33,365 And then it does have some other features listed 881 00:38:33,555 --> 00:38:36,605 that maybe these are under premium that aren't PayGo like 882 00:38:37,115 --> 00:38:41,125 annotations content query, which is 883 00:38:41,845 --> 00:38:44,525 metadata based queries on SharePoint document libraries. 884 00:38:44,565 --> 00:38:47,085 I thought that was search but you can do it with search. 885 00:38:47,085 --> 00:38:50,125 You've been able to do it in search based on content queries 886 00:38:50,125 --> 00:38:53,645 with metadata since 2007 Days of SharePoint. 887 00:38:53,645 --> 00:38:55,085 - Nevermind that it's new now. 888 00:38:55,205 --> 00:38:57,285 - I mean it's been content query forever, right? 889 00:38:57,285 --> 00:38:59,845 SharePoint search it used literally was called like you 890 00:38:59,845 --> 00:39:02,005 could go create content query rules in your SharePoint 891 00:39:02,005 --> 00:39:05,765 search in SharePoint 2007 but that's neither here nor there. 892 00:39:05,765 --> 00:39:08,365 - Listen, you're dating yourself now. Yeah I 893 00:39:08,365 --> 00:39:09,365 - Am. 894 00:39:09,365 --> 00:39:12,485 Margin and extract PDFs, processing rules, 895 00:39:13,465 --> 00:39:14,925 simple rule driven actions 896 00:39:14,925 --> 00:39:16,845 and document libraries based on metadata. 897 00:39:16,955 --> 00:39:18,165 Okay, let's go create a flow 898 00:39:18,165 --> 00:39:19,405 and power automate 899 00:39:19,475 --> 00:39:22,205 that processes my content based on metadata. 900 00:39:22,575 --> 00:39:24,965 Maybe it gets made simpler, I don't know. 901 00:39:24,985 --> 00:39:27,165 But that's just new skin on features that already exist. 902 00:39:28,365 --> 00:39:32,245 Solution accelerators, site templates, 903 00:39:32,725 --> 00:39:35,805 solution accelerators, new term SharePoint site templates 904 00:39:35,805 --> 00:39:37,845 for Microsoft syntax are pre-built, ready to deploy 905 00:39:37,845 --> 00:39:40,285 and customizable use these templates 906 00:39:40,315 --> 00:39:42,165 otherwise known as solution accelerators. 907 00:39:42,435 --> 00:39:45,445 Tending appliance like I don't know, I don't, it's 908 00:39:45,445 --> 00:39:46,565 so con I'm confused. 909 00:39:46,895 --> 00:39:49,685 How's that? I have read the articles a little bit 910 00:39:49,905 --> 00:39:52,965 but there's a lot of stuff in here that, oh 911 00:39:53,885 --> 00:39:56,805 I don't know all the SharePoint premium stuff other than 912 00:39:56,805 --> 00:39:58,725 maybe merge and extract PDFs. 913 00:39:58,985 --> 00:40:01,325 Sounds like stuff that you can already do. 914 00:40:01,695 --> 00:40:04,365 Maybe annotations and then all the other stuff Sounds like 915 00:40:04,955 --> 00:40:07,205 pego stuff that's already there under syntax. We've come 916 00:40:07,205 --> 00:40:08,205 - Full circle. 917 00:40:08,205 --> 00:40:10,685 We started at Ignite is a marketing 918 00:40:10,685 --> 00:40:11,965 and architecture conference 919 00:40:12,665 --> 00:40:15,085 and we have come all the way back around 920 00:40:15,225 --> 00:40:17,325 to marketing and architecture 921 00:40:17,685 --> 00:40:18,685 - . 922 00:40:18,685 --> 00:40:20,165 Yes. Which by the way e-signatures 923 00:40:20,165 --> 00:40:21,925 and SharePoint maybe it's nice 'cause it's built in 924 00:40:21,925 --> 00:40:23,125 and it's only pay per go but 925 00:40:23,275 --> 00:40:25,085 that seems really expensive to me. 926 00:40:25,385 --> 00:40:26,525 Did you see the price on that? 927 00:40:26,845 --> 00:40:30,765 - I would encourage you to go look at the pricing for some 928 00:40:30,765 --> 00:40:33,525 of the other products in this space that do similar things 929 00:40:34,025 --> 00:40:35,485 and tell me if you think they're cheap. 930 00:40:35,715 --> 00:40:38,565 It's been a hot minute since I've worked on a Highland 931 00:40:39,305 --> 00:40:41,965 but it like was not cheap 10 years ago. 932 00:40:42,445 --> 00:40:44,325 , I doubt it's gotten any cheaper. Maybe 933 00:40:44,385 --> 00:40:49,085 - The advantages is that you are paying per signature 934 00:40:49,715 --> 00:40:51,405 request for a transaction. 935 00:40:51,715 --> 00:40:53,765 I've been a, I don't do a lot of e-signatures. 936 00:40:53,765 --> 00:40:56,445 I've been on a free plan a DocuSign for 10 years 937 00:40:57,115 --> 00:40:59,005 that does more than enough e-signatures 938 00:40:59,025 --> 00:41:00,845 for me and I've never paid for it. Well 939 00:41:01,005 --> 00:41:02,485 - Remember the intent here isn't to compete 940 00:41:02,485 --> 00:41:06,645 with DocuSign DocuSign's, its its own little beast. 941 00:41:07,025 --> 00:41:09,125 So this doesn't have to be DocuSign, but 942 00:41:09,125 --> 00:41:11,925 - For e-signature, no, but e-signature. 943 00:41:12,645 --> 00:41:13,805 I mean your standard plan. 944 00:41:14,285 --> 00:41:16,525 I don't, I get that maybe it's some 945 00:41:16,525 --> 00:41:17,845 of the other stuff obviously isn't, 946 00:41:17,845 --> 00:41:19,805 but I feel like e-signature, you're really competing 947 00:41:19,805 --> 00:41:21,445 with DocuSign in Adobe. 948 00:41:21,465 --> 00:41:23,125 You're not, there's a bunch of other ones 949 00:41:23,125 --> 00:41:24,245 that are way more expensive 950 00:41:24,745 --> 00:41:29,485 - In this world of content platform systems. 951 00:41:30,155 --> 00:41:31,925 Yeah, there are other options. 952 00:41:32,355 --> 00:41:34,765 They cost the same if not more 953 00:41:35,585 --> 00:41:39,605 and Microsoft potentially tries to eat their lunch 954 00:41:39,875 --> 00:41:43,165 because if you think about it for somebody like an OnBase 955 00:41:43,225 --> 00:41:45,645 or a Laser FE or something like that to integrate 956 00:41:45,645 --> 00:41:47,845 with SharePoint, they're stuck at the API surface. 957 00:41:48,395 --> 00:41:50,485 I'll give you like a good example. If you go to a law firm 958 00:41:50,545 --> 00:41:54,565 and that law firm uses Laserfiche today, all of their emails 959 00:41:55,365 --> 00:41:58,405 actually get ingested in there as documents in that system. 960 00:41:58,785 --> 00:42:01,805 So like your email gets a document ID every single email you 961 00:42:01,805 --> 00:42:04,525 send every single document you write every single version of 962 00:42:04,525 --> 00:42:06,125 that document like they all get captured 963 00:42:06,265 --> 00:42:07,925 and go through this workflow and do these things. 964 00:42:08,385 --> 00:42:10,605 So if you think about the friction for those vendors 965 00:42:10,785 --> 00:42:12,605 to integrate in the office ecosystem, 966 00:42:13,325 --> 00:42:15,405 Microsoft definitely has an advantage here in 967 00:42:15,405 --> 00:42:17,885 that they can see the APIs as they're coming. 968 00:42:18,075 --> 00:42:22,005 They can potentially influence the design decisions 969 00:42:22,025 --> 00:42:26,085 and how those APIs are built now all to their advantage 970 00:42:26,385 --> 00:42:29,005 for what's arguably a pretty tightly 971 00:42:29,005 --> 00:42:30,205 integrated system already. 972 00:42:30,945 --> 00:42:32,965 And yeah, you just tack these things on here. 973 00:42:33,425 --> 00:42:36,085 If this costs the same exact amount of money 974 00:42:36,145 --> 00:42:37,645 as an existing content platform 975 00:42:37,905 --> 00:42:41,045 and somebody builds a migration engine for it, you'd be 976 00:42:41,635 --> 00:42:44,005 hard pressed as a customer not to make that argument as 977 00:42:44,005 --> 00:42:46,365 to like why you just wouldn't do this. Why 978 00:42:46,365 --> 00:42:48,405 - You just, I get that from a, 979 00:42:48,505 --> 00:42:52,365 if you're looking at the holistic content processing, 980 00:42:52,645 --> 00:42:54,005 I guess I have enough clients 981 00:42:54,005 --> 00:42:56,645 that aren't doing maybe the holistic content processing 982 00:42:56,645 --> 00:42:58,965 that are just like we need signatures on contracts 983 00:42:59,105 --> 00:43:00,105 - And your clients. 984 00:43:00,105 --> 00:43:03,205 So in that case, but your clients are not thinking about let 985 00:43:03,205 --> 00:43:05,525 me go buy the most premium of the premium service. 986 00:43:05,635 --> 00:43:08,445 They're saying I need to do signatures on the country. 987 00:43:08,525 --> 00:43:09,525 - I just need to do a signature, 988 00:43:09,525 --> 00:43:13,005 - I need to do metadata movement in this single list over 989 00:43:13,005 --> 00:43:14,925 here from this thing not right. 990 00:43:14,935 --> 00:43:15,965 Every single document 991 00:43:15,965 --> 00:43:19,445 that goes into my environment needs a unique document id. 992 00:43:19,445 --> 00:43:20,725 Every single version needs 993 00:43:20,725 --> 00:43:22,525 to be versioned under that same document. 994 00:43:22,985 --> 00:43:26,085 And it all needs to have these set pieces of metadata 995 00:43:26,465 --> 00:43:29,445 that's a totally different class of business problems, 996 00:43:29,845 --> 00:43:33,045 regulatory kind of things that you have to go and solve for. 997 00:43:33,225 --> 00:43:36,605 - So, and that's where you see Docu 998 00:43:36,625 --> 00:43:38,725 or SharePoint Premium is trying 999 00:43:38,745 --> 00:43:42,765 to wiggle their way into its more that's space 1000 00:43:43,065 --> 00:43:45,685 or those types of customers that it might be trying 1001 00:43:45,705 --> 00:43:46,725 to appeal to. 1002 00:43:46,925 --> 00:43:48,925 - I think so. Like I read all this and I look at it 1003 00:43:49,185 --> 00:43:52,725 and the way it composes, I would've personally killed 1004 00:43:52,785 --> 00:43:56,645 for this a long time ago back when I was, 1005 00:43:56,645 --> 00:43:58,485 but a lowly SharePoint developer. 1006 00:43:58,945 --> 00:44:01,045 And I worked for 1007 00:44:01,645 --> 00:44:04,605 a couple really big law firms like top 10 in in, 1008 00:44:04,605 --> 00:44:06,965 in the world by like size revenue, things like that 1009 00:44:07,225 --> 00:44:08,845 as a SharePoint developer in those places. 1010 00:44:08,955 --> 00:44:11,005 Like I would've killed for things like this 1011 00:44:11,465 --> 00:44:14,925 and to have access to this rather than the mishmash of stuff 1012 00:44:15,235 --> 00:44:16,685 that came along with other, the 1013 00:44:16,685 --> 00:44:17,685 - Stuff you put together. 1014 00:44:17,685 --> 00:44:18,765 - Content services. Yeah. Got 1015 00:44:18,765 --> 00:44:19,765 - It. 1016 00:44:19,765 --> 00:44:20,885 See, and I have not, I will say 1017 00:44:20,885 --> 00:44:24,405 that is one area from a massive law firm like that. 1018 00:44:24,645 --> 00:44:28,645 I have not had a ton of experience so I would not be able 1019 00:44:28,645 --> 00:44:31,205 to adequately talk to how well this works. 1020 00:44:31,205 --> 00:44:32,565 Maybe you should come back to the SharePoint 1021 00:44:32,565 --> 00:44:34,245 world now that you have this Scott. No 1022 00:44:34,685 --> 00:44:36,685 - , no. 1023 00:44:37,025 --> 00:44:38,645 Not gonna happen. I'm gonna, I'm gonna stick 1024 00:44:38,665 --> 00:44:42,005 to my crazy world of APIs 1025 00:44:42,005 --> 00:44:43,765 and SDKs and live that life. 1026 00:44:43,875 --> 00:44:46,045 - Alright, well we should probably wrap this up. 1027 00:44:46,285 --> 00:44:48,685 'cause like you said, I do have a meeting now 1028 00:44:48,685 --> 00:44:49,885 that you got me all worked up. 1029 00:44:49,915 --> 00:44:52,365 Yeah, I know. I do have some other Ignite stuff we can talk 1030 00:44:52,365 --> 00:44:53,645 about in some future episodes. 1031 00:44:53,785 --> 00:44:54,565 All right. There were some 1032 00:44:54,805 --> 00:44:56,165 interesting security announcements too. 1033 00:44:56,175 --> 00:44:57,885 We'll leave you with that. Some interesting 1034 00:44:58,455 --> 00:45:00,965 stuff in the Microsoft Defender landscape. 1035 00:45:01,405 --> 00:45:03,725 - XDR. Yeah, we'll come back and talk about that one. Yeah. 1036 00:45:04,285 --> 00:45:06,325 - , you mean what happened to 365 1037 00:45:07,005 --> 00:45:08,565 tease everybody with that. 1038 00:45:08,565 --> 00:45:10,965 Alright, sounds good. Well thanks Scott. Yep. Thanks Ben. 1039 00:45:10,965 --> 00:45:13,285 Go enjoy your weekend. We are recording this shortly 1040 00:45:13,285 --> 00:45:15,485 before Thanksgiving, so anybody here, 1041 00:45:15,795 --> 00:45:16,805 well you won't hear this 1042 00:45:16,805 --> 00:45:19,045 before Thanksgiving, so enjoy your Thanksgiving. 1043 00:45:19,095 --> 00:45:21,485 Scott, anybody in the US that hears this afterwards, 1044 00:45:21,725 --> 00:45:22,925 I hope you enjoyed your Thanksgiving. 1045 00:45:23,625 --> 00:45:27,485 And don't forget Thanksgiving, December holidays, 1046 00:45:27,665 --> 00:45:30,525 all the next few months trying to continue 1047 00:45:30,545 --> 00:45:32,845 to do our fundraiser with Girls Who Code. 1048 00:45:32,845 --> 00:45:36,205 So there will be a link in the show notes for that to try to 1049 00:45:36,945 --> 00:45:41,485 top what we were able to get last year 1050 00:45:41,505 --> 00:45:43,645 or what people donated last year to Girls Who Code. 1051 00:45:43,645 --> 00:45:46,125 See if we can do a little better this year. Indeed. 1052 00:45:46,225 --> 00:45:49,405 Go check that out and we will talk to you next week. Great, 1053 00:45:49,405 --> 00:45:50,405 - Thanks Ben. 1054 00:45:52,265 --> 00:45:53,405 - If you enjoyed the podcast, 1055 00:45:53,905 --> 00:45:55,965 go leave us a five star rating in iTunes. 1056 00:45:56,185 --> 00:45:57,525 It helps to get the word out 1057 00:45:57,545 --> 00:46:00,765 so more IT Pros can learn about Office 365 and Azure. 1058 00:46:01,545 --> 00:46:04,365 If you have any questions you want us to address on the show 1059 00:46:04,505 --> 00:46:06,925 or feedback about the show, feel free 1060 00:46:06,945 --> 00:46:10,045 to reach out via our website, Twitter, or Facebook. 1061 00:46:10,305 --> 00:46:12,405 Thanks again for listening and have a great day.

Digital Dispatch Podcast Podcast Artwork Image

Microsoft Cloud IT Pro Podcast

Ben Stegink, Scott Hoag

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

Contact Show