Episode 411 – Securing AI with Microsoft Purview: Data Security Posture Management for AI

September 25, 2025

Episode Transcript

Welcome back to another episode of the Microsoft Cloud IT Pro Podcast! In this episode, we dive deep into one of Microsoft Purview’s AI monitoring and protection capabilities: Data Security Posture Management (DSPM) for AI – your secret weapon for monitoring and securing AI usage across your organization.

Your support makes this show possible! Please consider becoming a premium member for access to live shows and more. Check out our membership options.

Show Notes

About the sponsors

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

See full episode transcriptTranscript is autogenerated by AI

1 00:00:03,520 --> 00:00:05,759 Welcome to episode 411 2 00:00:05,759 --> 00:00:08,880 of the Microsoft Cloud IT Pro podcast recorded 3 00:00:08,880 --> 00:00:11,939 live on 09/24/2025. 4 00:00:12,160 --> 00:00:14,400 This is a show about Microsoft three sixty 5 00:00:14,400 --> 00:00:16,605 five and Azure from the perspective of IT 6 00:00:16,605 --> 00:00:18,925 pros and end users, where we discuss a 7 00:00:18,925 --> 00:00:21,244 topic or recent news and how it relates 8 00:00:21,244 --> 00:00:23,964 to you. In this episode, we circle back 9 00:00:23,964 --> 00:00:26,925 to our conversation around preparing for Microsoft three 10 00:00:26,925 --> 00:00:27,984 sixty five Copilot 11 00:00:28,364 --> 00:00:31,339 and, frankly, all AI in a conversation about 12 00:00:31,339 --> 00:00:34,939 data security posture management. We discuss what's available 13 00:00:34,939 --> 00:00:38,320 to you within DSPM for AI and Microsoft 14 00:00:38,380 --> 00:00:40,460 Purview, what you need to do in order 15 00:00:40,460 --> 00:00:42,219 to get started with it, and how you 16 00:00:42,219 --> 00:00:44,905 can leverage this tool within your company to 17 00:00:44,905 --> 00:00:47,625 keep your sensitive data in Microsoft three sixty 18 00:00:47,625 --> 00:00:50,045 five safe and secure from AI. 19 00:00:50,504 --> 00:00:51,644 Let's dive in. 20 00:00:54,104 --> 00:00:57,004 Scott, it feels like forever since we've talked. 21 00:00:57,064 --> 00:00:59,299 I think this might be the longest we've 22 00:00:59,299 --> 00:01:00,840 gone in a while without talking. 23 00:01:02,259 --> 00:01:04,439 Well, that's because you went to a conference, 24 00:01:04,819 --> 00:01:05,319 and 25 00:01:05,620 --> 00:01:07,379 you let Jay and Joy take over the 26 00:01:07,379 --> 00:01:10,519 podcast Saturday. That was a mistake. That's fine. 27 00:01:10,659 --> 00:01:12,659 Nah. It was all good. Oh. Don't you 28 00:01:12,659 --> 00:01:14,019 go back and listen to that one if 29 00:01:14,019 --> 00:01:16,694 they haven't? Joy and Jay take over and 30 00:01:16,694 --> 00:01:18,635 talk change management, episode 31 00:01:19,255 --> 00:01:21,174 four ten Four ten. Of the Microsoft Cloud 32 00:01:21,174 --> 00:01:23,174 IT Pro podcast. Yes. That was a good 33 00:01:23,174 --> 00:01:24,775 one. We need to get you back to 34 00:01:24,775 --> 00:01:25,435 a conference, 35 00:01:26,055 --> 00:01:28,409 Scott. I was at a conference last week. 36 00:01:28,409 --> 00:01:30,250 I was just at a different conference. Which 37 00:01:30,250 --> 00:01:32,409 conference were you at? I was at the 38 00:01:32,409 --> 00:01:34,030 storage developer conference 39 00:01:34,489 --> 00:01:38,329 out in Santa Clara, California. Oh, how are 40 00:01:38,329 --> 00:01:40,189 storage developers these days? 41 00:01:40,655 --> 00:01:43,215 They keep on developing things. I had a 42 00:01:43,215 --> 00:01:46,814 talk on retrieval augmented generation and object storage. 43 00:01:46,814 --> 00:01:49,634 So where does object storage fit into 44 00:01:50,814 --> 00:01:51,314 the 45 00:01:51,694 --> 00:01:54,450 kinda AI pipeline when you think about an 46 00:01:54,530 --> 00:01:55,430 end to end spectrum 47 00:01:55,810 --> 00:01:58,789 of AI training all the way through to 48 00:01:59,250 --> 00:01:59,989 AI inference 49 00:02:00,450 --> 00:02:02,069 and actively, like, serving 50 00:02:02,450 --> 00:02:05,409 these workloads and LLMs and things like that 51 00:02:05,409 --> 00:02:07,090 are on it. But my talk was a 52 00:02:07,090 --> 00:02:09,090 little bit kind of about, like, the three 53 00:02:09,090 --> 00:02:11,114 quarters of the way through the AI pipeline 54 00:02:11,414 --> 00:02:15,014 with fine tuning and retrieval augmented generation. Got 55 00:02:15,014 --> 00:02:16,775 it. Interesting. I was gonna say, because you 56 00:02:16,775 --> 00:02:18,534 probably need storage, like, at every step of 57 00:02:18,534 --> 00:02:21,334 the pipeline. I mean, AI kinda depends on 58 00:02:21,334 --> 00:02:23,334 data a little bit, which kinda depends on 59 00:02:23,334 --> 00:02:23,834 storage. 60 00:02:26,050 --> 00:02:28,610 Yeah. If you're training a foundational model, you 61 00:02:28,610 --> 00:02:31,990 require petabytes and petabytes or exabytes of storage. 62 00:02:32,210 --> 00:02:33,909 If you're just doing fine tuning, 63 00:02:34,530 --> 00:02:36,450 you might be in the petabyte range, or 64 00:02:36,450 --> 00:02:37,889 you could be smaller. You could be down 65 00:02:37,889 --> 00:02:40,894 in the terabyte range and taking a very 66 00:02:40,894 --> 00:02:42,594 specific dataset to 67 00:02:43,215 --> 00:02:45,634 teach a model the new set of skills 68 00:02:46,014 --> 00:02:48,114 along the way. But it turns out that 69 00:02:48,414 --> 00:02:49,715 object storage platforms 70 00:02:50,094 --> 00:02:51,794 are super important 71 00:02:52,659 --> 00:02:55,539 when it comes to retrieval augmented generation as 72 00:02:55,539 --> 00:02:57,219 well, because you've got this thing where you 73 00:02:57,219 --> 00:02:58,520 have to effectively 74 00:02:59,219 --> 00:03:01,699 kinda rather than teaching new skills like you 75 00:03:01,699 --> 00:03:03,539 would fine tuning, you have to teach new 76 00:03:03,539 --> 00:03:05,939 facts. Like, hey. Here's something that is going 77 00:03:05,939 --> 00:03:08,034 to augment your knowledge. So if you think 78 00:03:08,495 --> 00:03:10,655 about, like, Copilot notebook, for example. So we've 79 00:03:10,655 --> 00:03:11,775 talked about those in the past. So you 80 00:03:11,775 --> 00:03:13,215 could go into a Copilot notebook, and you 81 00:03:13,215 --> 00:03:15,534 can put whatever it is, ten, twenty documents 82 00:03:15,534 --> 00:03:18,014 in there. When you put those documents into 83 00:03:18,014 --> 00:03:18,675 the notebook, 84 00:03:19,215 --> 00:03:19,715 Copilot 85 00:03:20,175 --> 00:03:21,394 and the underlying 86 00:03:22,110 --> 00:03:24,189 LOM that's serving the response back to you, 87 00:03:24,189 --> 00:03:26,909 they're not actually reading that document, like, as 88 00:03:26,909 --> 00:03:28,430 a document. Like, they don't open up a 89 00:03:28,430 --> 00:03:30,349 Word document or a PDF and read it 90 00:03:30,349 --> 00:03:33,090 page by page. They have to go ahead 91 00:03:33,150 --> 00:03:33,650 and 92 00:03:34,435 --> 00:03:37,155 generate embeddings. So effectively, they take that PDF 93 00:03:37,155 --> 00:03:39,074 for that Word document, and they turn it 94 00:03:39,074 --> 00:03:41,314 into a bunch of chunks, so and or 95 00:03:41,314 --> 00:03:44,055 embeddings. Those embeddings go to a vector database 96 00:03:44,435 --> 00:03:44,935 and 97 00:03:45,555 --> 00:03:46,055 vectorize, 98 00:03:46,530 --> 00:03:48,229 which means then you need a 99 00:03:48,769 --> 00:03:51,569 a vector search mechanism that can augment the 100 00:03:51,569 --> 00:03:54,049 LLM response. But object storage is kind of 101 00:03:54,049 --> 00:03:55,569 important, or if you think about, like, putting 102 00:03:55,569 --> 00:03:57,729 a new document into a Copilot notebook, something 103 00:03:57,729 --> 00:04:01,030 like that Yep. Because it's gotta be chunked, 104 00:04:01,435 --> 00:04:03,854 and it has to be generated, and embeddings 105 00:04:03,914 --> 00:04:05,754 need to be generated, and those embeddings need 106 00:04:05,754 --> 00:04:07,834 to be pushed over to a vector database. 107 00:04:07,834 --> 00:04:09,834 Well, that means anytime I upload a new 108 00:04:09,834 --> 00:04:11,914 document, if I put a new document or 109 00:04:11,914 --> 00:04:13,754 I take a document out of my Copilot 110 00:04:13,754 --> 00:04:15,810 notebook, anything like that, you actually need to 111 00:04:15,810 --> 00:04:18,529 kinda kick off back end process for data 112 00:04:18,529 --> 00:04:21,089 freshness. So having things like at least in 113 00:04:21,089 --> 00:04:23,250 our platform on the Azure storage side or 114 00:04:23,250 --> 00:04:25,089 the object storage side, we have things like 115 00:04:25,089 --> 00:04:26,470 change feed, which can 116 00:04:27,009 --> 00:04:29,264 be leveraged by these systems to kinda give 117 00:04:29,264 --> 00:04:31,904 them a proactive notification and say, hey. There's 118 00:04:31,904 --> 00:04:34,305 a new object here. Go and run whatever 119 00:04:34,305 --> 00:04:35,985 you need to run on top of this. 120 00:04:35,985 --> 00:04:38,485 For example, maybe you integrate Azure AI search 121 00:04:38,704 --> 00:04:41,024 into your workflow, so you pump a bunch 122 00:04:41,024 --> 00:04:43,990 of documents into a storage account. AI search 123 00:04:43,990 --> 00:04:47,050 can actually respond to the change feed notifications 124 00:04:47,269 --> 00:04:49,370 that are coming out, and it can automatically 125 00:04:49,669 --> 00:04:50,569 do the 126 00:04:51,029 --> 00:04:54,629 chunking, embedding, and store those embeddings in the 127 00:04:54,629 --> 00:04:55,689 vector database 128 00:04:56,235 --> 00:04:58,074 just based on the virtue of having the 129 00:04:58,074 --> 00:05:00,794 ability to notify in, like, a durable ordered 130 00:05:00,794 --> 00:05:03,435 list with something like a change feed along 131 00:05:03,435 --> 00:05:05,834 the way. It's kinda super interesting because I 132 00:05:05,834 --> 00:05:08,394 don't think folks really think about the back 133 00:05:08,394 --> 00:05:10,300 end of these things too much. Right? If 134 00:05:10,300 --> 00:05:12,139 you're playing with a Copilot notebook and you're 135 00:05:12,139 --> 00:05:14,699 putting documents in there, it's all just kinda 136 00:05:14,699 --> 00:05:15,519 like magic 137 00:05:15,979 --> 00:05:17,819 that all of a sudden it can reason 138 00:05:17,819 --> 00:05:21,019 over my document in really near real time. 139 00:05:21,019 --> 00:05:23,759 It doesn't it doesn't take too long to 140 00:05:24,055 --> 00:05:27,654 generate those embeddings, especially with smaller documents and 141 00:05:27,654 --> 00:05:30,454 smaller datasets, which is what most people are 142 00:05:30,454 --> 00:05:33,254 using in things like Copilot notebooks today. But 143 00:05:33,254 --> 00:05:35,014 there's a lot of moving pieces on the 144 00:05:35,014 --> 00:05:37,814 back end to get that all going and 145 00:05:37,814 --> 00:05:39,569 get it to where it needs to be. 146 00:05:39,649 --> 00:05:41,569 Yeah. So anyway, I had a session on 147 00:05:41,569 --> 00:05:43,330 that. That'll be up on YouTube. I'll I 148 00:05:43,330 --> 00:05:45,110 can share it in a couple of months 149 00:05:45,250 --> 00:05:47,910 once once those come out for public consumption. 150 00:05:48,290 --> 00:05:50,149 And then I also spent a couple days 151 00:05:50,210 --> 00:05:52,230 at a a plug fest. 152 00:05:52,610 --> 00:05:53,910 So SNIA 153 00:05:54,370 --> 00:05:55,270 and the broader 154 00:05:55,865 --> 00:05:59,324 storage developer conference, they organize effectively these hackathons 155 00:05:59,545 --> 00:06:01,705 that bring a bunch of vendors together under 156 00:06:01,705 --> 00:06:04,504 NDAs so that we can go and do 157 00:06:04,504 --> 00:06:06,925 interop testing with each other and 158 00:06:07,800 --> 00:06:10,300 kinda do debugging in real time. 159 00:06:10,919 --> 00:06:12,279 So there's a bunch of those plug fests 160 00:06:12,279 --> 00:06:14,379 that's needed hosts. They host one for Swordfish. 161 00:06:14,519 --> 00:06:15,419 They host one 162 00:06:15,720 --> 00:06:18,699 for SMB for, like, vendors to test their 163 00:06:19,079 --> 00:06:20,220 SMB implementations 164 00:06:21,084 --> 00:06:23,084 that might live outside of Windows or things 165 00:06:23,084 --> 00:06:24,365 like that. And then the one that I 166 00:06:24,365 --> 00:06:26,604 did was an object storage plug fest. So 167 00:06:26,604 --> 00:06:29,104 we have focused on, like, restful API surfaces 168 00:06:29,324 --> 00:06:32,764 for object storage vendors of which Microsoft is 169 00:06:32,764 --> 00:06:33,264 one 170 00:06:33,689 --> 00:06:36,490 with Azure storage, and then you've got s 171 00:06:36,490 --> 00:06:39,129 three protocols, which are kind of the elephant 172 00:06:39,129 --> 00:06:41,210 to the room as s three is not 173 00:06:41,210 --> 00:06:43,150 only an s three, but, you know, Google 174 00:06:43,210 --> 00:06:45,050 supports s three as a protocol. And they're 175 00:06:45,050 --> 00:06:47,150 a cloud object storage platform, Alibaba, 176 00:06:48,125 --> 00:06:50,044 Backblaze, and then a whole ton of on 177 00:06:50,044 --> 00:06:52,785 prem vendors, IBM Cloud Object Storage, 178 00:06:53,164 --> 00:06:53,664 Oracle, 179 00:06:54,204 --> 00:06:55,664 both their on prem offering, 180 00:06:56,044 --> 00:06:59,164 OCI as well, and their cloud infrastructure offers 181 00:06:59,164 --> 00:07:01,470 an s three protocol. So spent a couple 182 00:07:01,470 --> 00:07:03,730 days kinda hacking away at that and 183 00:07:04,110 --> 00:07:05,550 then seeing if we can get some of 184 00:07:05,550 --> 00:07:06,370 our products 185 00:07:06,750 --> 00:07:08,850 that we have that talk to s three. 186 00:07:08,910 --> 00:07:10,750 Like, while Azure Storage does not have a 187 00:07:10,750 --> 00:07:13,069 native s three service, we definitely have products 188 00:07:13,069 --> 00:07:14,975 that talk s three, especially 189 00:07:15,354 --> 00:07:17,615 for data management, data movement scenarios. 190 00:07:17,915 --> 00:07:20,014 So things like like AZCopy, 191 00:07:20,475 --> 00:07:20,975 StorageMover, 192 00:07:21,754 --> 00:07:23,134 you pick up one of our SDKs, 193 00:07:23,595 --> 00:07:26,149 we absolutely allow you, and we've got some 194 00:07:26,149 --> 00:07:28,149 great enabling APIs to help you move your 195 00:07:28,149 --> 00:07:30,649 data from S3 over to us. Got it. 196 00:07:30,709 --> 00:07:32,629 Very cool. Well, hopefully we'll get you at 197 00:07:32,629 --> 00:07:35,269 a, at another conference yet this year, Scott, 198 00:07:35,269 --> 00:07:37,610 because we have Ignite coming up 199 00:07:37,910 --> 00:07:39,449 in November, November. 200 00:07:40,274 --> 00:07:43,654 So hopefully doing podcast stuff there again. 201 00:07:44,035 --> 00:07:45,314 I actually have a couple I have one 202 00:07:45,314 --> 00:07:47,254 before that too. I'm going down to Orlando 203 00:07:47,394 --> 00:07:49,654 too. It was dev intersections, 204 00:07:49,955 --> 00:07:52,689 and now they're also doing, like, co locating 205 00:07:52,689 --> 00:07:55,110 dev intersections with cybersecurity intersection 206 00:07:55,490 --> 00:07:58,129 and the Next Gen AI conference. So I 207 00:07:58,129 --> 00:07:59,430 have a couple talks, 208 00:07:59,889 --> 00:08:03,250 presentations Oh, nice. At cybersecurity intersections. And then 209 00:08:03,250 --> 00:08:04,849 I'm actually doing a couple more, two in 210 00:08:04,849 --> 00:08:08,074 December in Dallas at Workplace Ninjas. 211 00:08:08,455 --> 00:08:10,694 So Cool. I've got two more coming up. 212 00:08:10,694 --> 00:08:12,775 Well, three more coming up, hopefully Ignite, and 213 00:08:12,775 --> 00:08:14,214 hopefully we can get you out to Ignite 214 00:08:14,214 --> 00:08:16,455 too. Yeah. We'll see. Pump it out on 215 00:08:16,455 --> 00:08:18,214 the socials. You can always find Ben on 216 00:08:18,214 --> 00:08:20,535 LinkedIn. You can find the podcast on LinkedIn. 217 00:08:20,535 --> 00:08:21,509 Can you find me on LinkedIn as well? 218 00:08:21,910 --> 00:08:23,430 Yeah. I think it's becoming one of our 219 00:08:23,430 --> 00:08:25,210 preferred communication method 220 00:08:25,670 --> 00:08:27,670 mechanisms for the podcast here. I would say 221 00:08:27,670 --> 00:08:29,610 LinkedIn is absolutely becoming 222 00:08:30,389 --> 00:08:31,370 the preferred one. 223 00:08:31,670 --> 00:08:33,509 All of the other ones. This is not 224 00:08:33,509 --> 00:08:35,714 just a any social media. Like, all of 225 00:08:35,714 --> 00:08:37,315 the other ones I have had to turn 226 00:08:37,315 --> 00:08:39,954 into looking at them all as just pure 227 00:08:39,954 --> 00:08:40,454 entertainment. 228 00:08:41,154 --> 00:08:42,355 There is nothing of the state of the 229 00:08:42,355 --> 00:08:44,355 world. Yeah. Not much of value that I 230 00:08:44,355 --> 00:08:46,214 have found on many of the other social 231 00:08:46,274 --> 00:08:49,254 platforms. So LinkedIn is absolutely becoming 232 00:08:49,919 --> 00:08:52,100 that preferred social media for 233 00:08:52,480 --> 00:08:53,139 the podcast, 234 00:08:53,519 --> 00:08:54,960 although we are still on all the other 235 00:08:54,960 --> 00:08:58,559 ones. But speaking of AI and storage and 236 00:08:58,559 --> 00:09:00,980 data, we should probably dive into 237 00:09:01,360 --> 00:09:04,075 this is like the second part of episode 238 00:09:04,774 --> 00:09:05,835 four zero nine 239 00:09:06,215 --> 00:09:09,514 when we started talking about preparing for Copilot 240 00:09:09,815 --> 00:09:11,674 in Microsoft March, 241 00:09:11,894 --> 00:09:14,455 getting ready for it. And we didn't quite 242 00:09:14,455 --> 00:09:16,394 get to kind of the last 243 00:09:16,709 --> 00:09:19,269 point that I covered in the presentation I 244 00:09:19,269 --> 00:09:19,769 gave 245 00:09:20,389 --> 00:09:23,209 wherever I was for that one, Branson, Missouri 246 00:09:23,509 --> 00:09:24,009 around 247 00:09:24,549 --> 00:09:26,470 kind of diving into one of the, I 248 00:09:26,470 --> 00:09:29,769 would say, very quickly growing product in purview 249 00:09:29,990 --> 00:09:30,649 or a 250 00:09:31,205 --> 00:09:34,325 solution technically in Purview or doing a lot 251 00:09:34,325 --> 00:09:36,024 of the management, controlling, 252 00:09:36,565 --> 00:09:37,065 monitoring, 253 00:09:37,764 --> 00:09:38,264 copilot, 254 00:09:38,644 --> 00:09:42,665 and really other AI usages is the data 255 00:09:42,884 --> 00:09:43,384 security 256 00:09:44,240 --> 00:09:46,240 posture management or d 257 00:09:47,679 --> 00:09:49,139 DSPM for AI 258 00:09:49,679 --> 00:09:52,559 that exists in Purview. We should kind of 259 00:09:52,559 --> 00:09:54,240 talk through this one. It was a little 260 00:09:54,240 --> 00:09:56,639 bit of an interesting new area for me. 261 00:09:56,639 --> 00:09:59,004 Yeah. So if you haven't looked at it, 262 00:09:59,004 --> 00:10:01,644 I definitely recommend if you're doing anything with 263 00:10:01,644 --> 00:10:04,365 Copilot or really anything at all and you 264 00:10:04,365 --> 00:10:06,445 care about your dating, keeping it safe from 265 00:10:06,445 --> 00:10:08,524 AI, because there's aspects of this that don't 266 00:10:08,524 --> 00:10:10,439 apply to just Copilot. You should go check 267 00:10:10,439 --> 00:10:13,959 this out. So it's in Purview. And once 268 00:10:13,959 --> 00:10:14,860 you go into 269 00:10:15,559 --> 00:10:16,059 Purview, 270 00:10:16,439 --> 00:10:18,379 you'll just start on, like, a general 271 00:10:18,759 --> 00:10:19,259 overview, 272 00:10:19,639 --> 00:10:21,559 typical to a lot of the different admin 273 00:10:21,559 --> 00:10:24,365 centers that gives you some things to get 274 00:10:24,365 --> 00:10:26,865 started with. So there's kind of four 275 00:10:27,485 --> 00:10:28,384 big aspects 276 00:10:28,764 --> 00:10:31,485 to this whole data security posture management for 277 00:10:31,485 --> 00:10:34,440 AI that you need to enable that are 278 00:10:34,600 --> 00:10:37,559 required to really get going in terms of 279 00:10:37,559 --> 00:10:38,059 monitoring 280 00:10:38,519 --> 00:10:40,860 your data, because this is all about discovering 281 00:10:41,159 --> 00:10:44,139 what are people doing, securing AI activity. 282 00:10:44,679 --> 00:10:46,059 So in order to 283 00:10:46,440 --> 00:10:48,600 secure it, discover it, know what people are 284 00:10:48,600 --> 00:10:50,134 doing, you you kinda have to be able 285 00:10:50,134 --> 00:10:51,735 to look at the data. So there's Turns 286 00:10:51,735 --> 00:10:54,375 out. Yeah. So there's a whole just first, 287 00:10:54,375 --> 00:10:58,054 just activate Microsoft Purview audit. This is really 288 00:10:58,054 --> 00:11:00,454 just that audit log that we've had for 289 00:11:00,454 --> 00:11:03,659 years. That's both security center compliance center. It 290 00:11:03,659 --> 00:11:05,659 used to be the unified auto log. Now 291 00:11:05,659 --> 00:11:08,799 it's just audit, but then there's also in, 292 00:11:08,860 --> 00:11:10,539 I don't even remember when this came out. 293 00:11:10,539 --> 00:11:12,220 I don't remember ever talking about it, seeing 294 00:11:12,220 --> 00:11:13,759 it in the news. There's a Purview 295 00:11:14,139 --> 00:11:15,279 browser extension 296 00:11:15,820 --> 00:11:18,774 that you can deploy now, and it really 297 00:11:18,774 --> 00:11:19,274 doesn't 298 00:11:20,215 --> 00:11:22,475 I would say it doesn't do much. There's 299 00:11:22,535 --> 00:11:24,455 nothing really for end users to interact with. 300 00:11:24,455 --> 00:11:25,735 It's one of those that you can install 301 00:11:25,735 --> 00:11:27,095 and just kinda keep it hidden in the 302 00:11:27,095 --> 00:11:27,595 background. 303 00:11:28,054 --> 00:11:29,415 There's no reason to show it in your 304 00:11:29,415 --> 00:11:32,649 task bar, but it is really just watching 305 00:11:33,029 --> 00:11:35,590 browser activity. Install it there so it can 306 00:11:35,590 --> 00:11:37,429 see what are you doing within your edge 307 00:11:37,429 --> 00:11:39,830 browser. I think there's I think the extension 308 00:11:39,830 --> 00:11:41,830 also exists for Chrome. And if I remember 309 00:11:41,830 --> 00:11:44,710 right, the edge one may actually just be 310 00:11:44,710 --> 00:11:46,294 in the Chrome store. I have it for 311 00:11:46,294 --> 00:11:48,954 Firefox too. So edge Chrome, Firefox 312 00:11:49,495 --> 00:11:52,695 to really just help watch signals of what 313 00:11:52,695 --> 00:11:54,954 are people doing in the browser with data. 314 00:11:55,095 --> 00:11:57,495 Again, this kind of ties into, are people 315 00:11:57,495 --> 00:11:59,860 going to other AI sites, going to chat 316 00:11:59,860 --> 00:12:02,740 GPT, going to claw, going to some of 317 00:12:02,740 --> 00:12:03,240 those. 318 00:12:03,620 --> 00:12:05,620 So that's the next step. Just get that 319 00:12:05,620 --> 00:12:06,919 browser extension deployed. 320 00:12:07,460 --> 00:12:09,620 There's guides on, you can go do this 321 00:12:09,620 --> 00:12:10,360 with Intune, 322 00:12:11,184 --> 00:12:13,924 whatever solutions you kind of use to manage 323 00:12:14,225 --> 00:12:17,204 end user devices, leverage those to deploy Purview. 324 00:12:17,264 --> 00:12:19,985 And then after that, or along with that, 325 00:12:19,985 --> 00:12:23,184 is also onboarding devices to Purview. So this 326 00:12:23,184 --> 00:12:25,024 is one too that I've actually seen some 327 00:12:25,024 --> 00:12:25,524 people 328 00:12:25,910 --> 00:12:27,129 miss Scott is that 329 00:12:27,670 --> 00:12:30,570 just because you've onboarded the device into 330 00:12:31,110 --> 00:12:31,610 Intune 331 00:12:32,070 --> 00:12:33,290 or into other, 332 00:12:34,149 --> 00:12:36,149 enrolled it and enter ID joined it to 333 00:12:36,149 --> 00:12:39,269 enter ID. There's a whole nother aspect of 334 00:12:39,269 --> 00:12:40,889 actually onboarding devices 335 00:12:41,644 --> 00:12:43,565 into Purview as well. So you can have 336 00:12:43,565 --> 00:12:45,325 a device in Intune, have a device in 337 00:12:45,325 --> 00:12:47,105 Entra, and not have it 338 00:12:47,485 --> 00:12:49,664 onboarded into Purview. Yeah. I wonder 339 00:12:50,044 --> 00:12:52,924 can we take a step back? So Yeah. 340 00:12:52,924 --> 00:12:54,845 I'm I'm just kinda, like, watching your screen 341 00:12:54,845 --> 00:12:56,839 as it's up. So when you go look 342 00:12:56,839 --> 00:12:59,419 at Microsoft documentation and you say, hey, 343 00:13:00,039 --> 00:13:02,279 these two folks are talking about data security 344 00:13:02,279 --> 00:13:04,839 posture managements, and maybe you just go Google 345 00:13:04,839 --> 00:13:06,839 for that or Bing or DuckDuckGo or you 346 00:13:06,839 --> 00:13:07,659 search for TPSM, 347 00:13:08,360 --> 00:13:10,220 you're going to end up 348 00:13:11,205 --> 00:13:12,585 in one section 349 00:13:12,964 --> 00:13:14,345 of the Purview 350 00:13:14,964 --> 00:13:15,464 documentation. 351 00:13:16,164 --> 00:13:17,845 So you're gonna end up in a section 352 00:13:17,845 --> 00:13:18,345 around 353 00:13:18,725 --> 00:13:20,424 data security solutions. 354 00:13:21,044 --> 00:13:23,284 But as you've got the portal up, and 355 00:13:23,284 --> 00:13:26,289 if you kinda keep, like, Google being DuckDuckGo 356 00:13:26,750 --> 00:13:27,970 search engine of choice, 357 00:13:28,350 --> 00:13:29,970 you end up on 358 00:13:30,350 --> 00:13:32,370 a different page, which is DPSM 359 00:13:32,830 --> 00:13:33,809 for AI, 360 00:13:34,429 --> 00:13:37,809 and then starts talking about the specific considerations 361 00:13:38,029 --> 00:13:41,164 for that, onboarding to the additional set of 362 00:13:41,164 --> 00:13:41,664 capabilities, 363 00:13:42,365 --> 00:13:43,745 the co pilots, 364 00:13:44,125 --> 00:13:46,205 and things that come with that. So can 365 00:13:46,205 --> 00:13:49,024 you help me, like, disambiguate the two? DPSM, 366 00:13:49,485 --> 00:13:52,940 DPSM for AI? AI. So DSPM, 367 00:13:53,559 --> 00:13:55,639 this is one I haven't done a lot 368 00:13:55,639 --> 00:13:57,960 with yet. I actually click over to data. 369 00:13:57,960 --> 00:14:00,059 I don't know that I have 370 00:14:01,000 --> 00:14:02,759 full access into it. I do have some 371 00:14:02,759 --> 00:14:04,940 of it in mind. Where I would say 372 00:14:05,080 --> 00:14:05,580 DSPM 373 00:14:06,200 --> 00:14:07,820 is just really overall 374 00:14:08,334 --> 00:14:10,174 data security. Right? You're gonna go in and 375 00:14:10,174 --> 00:14:12,334 look at and if you go into the 376 00:14:12,334 --> 00:14:14,575 portal and look at it, it's risky user 377 00:14:14,575 --> 00:14:15,075 investigation. 378 00:14:15,455 --> 00:14:19,134 Are users doing performing risky behaviors with their 379 00:14:19,134 --> 00:14:20,115 data? Or 380 00:14:20,580 --> 00:14:23,960 where is that sensitive data? So this ties 381 00:14:24,019 --> 00:14:25,860 a little bit more into what I would 382 00:14:25,860 --> 00:14:28,920 say of information protection or even 383 00:14:29,300 --> 00:14:31,379 a little bit maybe it's not even information 384 00:14:31,379 --> 00:14:34,105 protection, it's a little bit higher. So you 385 00:14:34,105 --> 00:14:36,605 just have, like, what is my overall 386 00:14:37,225 --> 00:14:39,144 posture when it comes to keeping my data 387 00:14:39,144 --> 00:14:41,565 safe? It could include some of the information 388 00:14:41,625 --> 00:14:44,605 protection. It could include insider risk management. 389 00:14:45,080 --> 00:14:47,000 It could include, like, one of the other 390 00:14:47,000 --> 00:14:49,000 related solutions that shows up in Purview is 391 00:14:49,000 --> 00:14:50,220 data security investigations. 392 00:14:50,759 --> 00:14:52,679 It's broader, I would say, is how you 393 00:14:52,679 --> 00:14:55,580 look at data security posture management. The DSPM 394 00:14:55,799 --> 00:14:57,019 for AI really 395 00:14:57,485 --> 00:14:58,544 drills into 396 00:14:59,404 --> 00:15:02,924 then taking that data security posture management. How 397 00:15:02,924 --> 00:15:05,324 am I securing my data? Now let's look 398 00:15:05,324 --> 00:15:07,004 at it just through the lens of how 399 00:15:07,004 --> 00:15:09,024 am I securing it when it comes to 400 00:15:09,245 --> 00:15:12,690 interacting with AI. So that's things like your 401 00:15:12,750 --> 00:15:15,470 co pilots, maybe your agents that are out 402 00:15:15,470 --> 00:15:18,350 there, like your declarative agents, knowledge agents, and 403 00:15:18,509 --> 00:15:20,769 Yep. The co pilot portal or teams. 404 00:15:21,389 --> 00:15:24,029 It's basically like a superset of capabilities or 405 00:15:24,029 --> 00:15:27,184 a double click to go and monitor 406 00:15:27,565 --> 00:15:29,024 AI workloads specifically? 407 00:15:29,565 --> 00:15:32,365 Yeah. That's exactly it and guidance around it. 408 00:15:32,365 --> 00:15:33,965 Like, even if you go into the data 409 00:15:33,965 --> 00:15:37,965 security posture management portal in Purview, not the 410 00:15:37,965 --> 00:15:40,299 AI one, Really, it just talks about, like, 411 00:15:40,299 --> 00:15:42,879 there's some stuff here around risky user investigation, 412 00:15:43,019 --> 00:15:46,059 sensitive data, but it's really just an overview. 413 00:15:46,059 --> 00:15:48,960 You've got some reports around users performing 414 00:15:49,340 --> 00:15:50,720 risk related activities 415 00:15:51,100 --> 00:15:54,144 on unprotected sensitive assets. So I'm going into 416 00:15:54,144 --> 00:15:55,605 SharePoint files where 417 00:15:56,225 --> 00:15:56,884 I have 418 00:15:57,264 --> 00:15:59,045 credit card numbers, I have PII, 419 00:15:59,424 --> 00:16:00,085 I have 420 00:16:00,785 --> 00:16:03,125 IP addresses, I have connection strings, 421 00:16:03,504 --> 00:16:06,625 and there's people interacting with that sensitive data 422 00:16:06,625 --> 00:16:09,370 in some way. It doesn't necessarily have to 423 00:16:09,370 --> 00:16:10,110 be AI. 424 00:16:10,490 --> 00:16:12,570 It could be creating a sharing link to 425 00:16:12,570 --> 00:16:14,970 it. It could be emailing it to external 426 00:16:14,970 --> 00:16:17,870 users, some of that information protection type stuff. 427 00:16:17,929 --> 00:16:19,450 And it just kind of gives you an 428 00:16:19,450 --> 00:16:21,709 overview and some reports there, a few recommendations, 429 00:16:22,009 --> 00:16:24,514 but there's, I would say, DSPM, there's really 430 00:16:24,514 --> 00:16:26,274 not much there. It's more of a reporting 431 00:16:26,274 --> 00:16:28,754 and a little bit more monitoring. It's not 432 00:16:28,835 --> 00:16:30,595 it doesn't have many features in it, quite 433 00:16:30,595 --> 00:16:32,914 honestly. This is where, like when you mentioned 434 00:16:32,914 --> 00:16:35,095 the monitoring and some of those things, so 435 00:16:35,240 --> 00:16:37,720 this is the other areas, like, I think 436 00:16:37,720 --> 00:16:39,799 it's hard. If you don't find specifically the 437 00:16:39,799 --> 00:16:42,360 DPSM for AI section in the docs and 438 00:16:42,360 --> 00:16:44,299 you just end up on DSPM, 439 00:16:44,759 --> 00:16:46,839 you're gonna get, like, two different sets of 440 00:16:46,839 --> 00:16:49,319 guidance for onboarding Yep. Or, like, how far 441 00:16:49,319 --> 00:16:49,575 you 442 00:16:50,134 --> 00:16:51,654 should go and what you should turn on. 443 00:16:51,654 --> 00:16:53,595 So some of those things that you mentioned, 444 00:16:53,654 --> 00:16:54,554 like, if you're 445 00:16:54,934 --> 00:16:57,035 trying to specifically monitor 446 00:16:57,654 --> 00:16:59,754 AI usage within your organization, 447 00:17:00,134 --> 00:17:02,955 and maybe that includes things like third party 448 00:17:03,174 --> 00:17:05,179 gen AI sites, that could be OpenAI, 449 00:17:05,639 --> 00:17:06,859 Claude, Perplexity, 450 00:17:07,559 --> 00:17:09,960 things like that, Google, Gemini, things like that 451 00:17:09,960 --> 00:17:11,559 that are out there, then you do have 452 00:17:11,559 --> 00:17:13,980 to make sure that your devices are onboarded 453 00:17:14,039 --> 00:17:16,039 to Purview. So you gotta go through, like, 454 00:17:16,039 --> 00:17:18,164 that whole flow. You might need DLP 455 00:17:18,625 --> 00:17:22,345 in place. That browser extension becomes super important 456 00:17:22,705 --> 00:17:25,445 Yep. To put out there and make sure 457 00:17:25,664 --> 00:17:28,785 that's all good. The auditing piece, like, yeah, 458 00:17:28,785 --> 00:17:31,265 you gotta go turn all of that stuff 459 00:17:31,265 --> 00:17:33,730 on. And then there's always that pesky, like, 460 00:17:33,730 --> 00:17:35,190 little licensing consideration. 461 00:17:35,650 --> 00:17:37,569 So it looks like for some reason for, 462 00:17:37,569 --> 00:17:41,029 like, Copilot in fabric or the security Copilot, 463 00:17:41,250 --> 00:17:44,230 then you need the enterprise version of Microsoft 464 00:17:44,289 --> 00:17:46,974 Purview data governance, which then lights up a 465 00:17:46,974 --> 00:17:49,295 new set of APIs and a new set 466 00:17:49,295 --> 00:17:50,035 of capabilities 467 00:17:50,494 --> 00:17:53,134 behind it. So there's definitely, like, a lot 468 00:17:53,134 --> 00:17:54,894 of reading with this one, I think, just 469 00:17:54,894 --> 00:17:56,434 to figure out how it composes. 470 00:17:56,894 --> 00:17:58,710 And then what are you gonna go turn 471 00:17:58,710 --> 00:18:00,549 on? And then like you said, because it's 472 00:18:00,549 --> 00:18:02,869 primarily a reporting thing. And to a certain 473 00:18:02,869 --> 00:18:05,109 degree, like, remediation. Right? You're gonna use these 474 00:18:05,109 --> 00:18:07,509 reports to drive new behaviors in your organization, 475 00:18:07,509 --> 00:18:09,109 things like that. But you kinda have to 476 00:18:09,109 --> 00:18:09,609 decide 477 00:18:10,069 --> 00:18:11,669 what you wanna report on out there. Like, 478 00:18:11,669 --> 00:18:13,555 if you wanna report on usage of cloud 479 00:18:13,555 --> 00:18:15,475 in your organization, then you've gotta go down, 480 00:18:15,475 --> 00:18:17,875 like, this, like, wild path of kinda turning 481 00:18:17,875 --> 00:18:20,994 everything on. Yes. And you'll find and we 482 00:18:20,994 --> 00:18:22,674 can talk about some of this too. There 483 00:18:22,674 --> 00:18:26,215 is even some functionality in here that is 484 00:18:26,539 --> 00:18:28,220 pay as you go, where you end up 485 00:18:28,220 --> 00:18:30,619 having to go in and connect your Purview 486 00:18:30,619 --> 00:18:32,880 instance to an Azure subscription 487 00:18:33,339 --> 00:18:35,339 or some of the pay as you go 488 00:18:35,339 --> 00:18:37,659 functionality as well. I did see that. So 489 00:18:37,659 --> 00:18:39,819 there's this little note, Riley, here, like a 490 00:18:39,819 --> 00:18:42,444 little bullet that says, hey. For AI apps 491 00:18:42,444 --> 00:18:45,164 other than Copilot and Facilitator, you have to 492 00:18:45,164 --> 00:18:47,244 set up pay as you go billing for 493 00:18:47,244 --> 00:18:47,984 your organization. 494 00:18:48,845 --> 00:18:50,865 And they do guide you into 495 00:18:51,244 --> 00:18:52,784 kinda, like, where in the UI 496 00:18:53,164 --> 00:18:54,764 to turn it on and things. But it's 497 00:18:54,764 --> 00:18:58,250 a little weird because Purview has multiple billing 498 00:18:58,250 --> 00:19:00,570 models. It's got the per user billing model, 499 00:19:00,570 --> 00:19:02,890 and then you're blending the PAYGo model on 500 00:19:02,890 --> 00:19:05,210 top of it. It's not like one or 501 00:19:05,210 --> 00:19:05,950 the other. 502 00:19:06,329 --> 00:19:08,650 You've gotta get out there and kinda figure 503 00:19:08,650 --> 00:19:10,835 out what he uses 504 00:19:11,694 --> 00:19:12,835 what. Yeah. 505 00:19:13,134 --> 00:19:14,894 Yeah. And you might be there already. Like, 506 00:19:14,894 --> 00:19:16,734 that's the other thing I think that I 507 00:19:16,734 --> 00:19:18,595 noticed that I saw was 508 00:19:19,054 --> 00:19:21,454 remembering, like, my days of Purview. Like, we 509 00:19:21,454 --> 00:19:23,535 we already had customers who were doing things 510 00:19:23,535 --> 00:19:25,474 like monitoring AWS usage, 511 00:19:26,390 --> 00:19:28,069 And we were going out and deploying the 512 00:19:28,069 --> 00:19:28,569 proxies 513 00:19:29,109 --> 00:19:31,750 and the monitoring solutions and things like that. 514 00:19:31,750 --> 00:19:33,750 Those are all out there. Like, if so 515 00:19:33,750 --> 00:19:35,990 if you already have, say, like, AWS monitoring 516 00:19:35,990 --> 00:19:37,990 in place, you're probably a PayGo customer already, 517 00:19:37,990 --> 00:19:40,470 and you've probably already configured the PayGo PayGo 518 00:19:40,470 --> 00:19:42,484 billing. It was a little surprising to me 519 00:19:42,484 --> 00:19:45,044 to see, like, Azure services fall into the 520 00:19:45,044 --> 00:19:47,044 PayGo thing as well. I can understand why, 521 00:19:47,044 --> 00:19:50,244 like, Amazon or Dropbox, Google, things like that, 522 00:19:50,244 --> 00:19:53,125 but there's stuff like Microsoft Fabric that requires 523 00:19:53,125 --> 00:19:53,625 PayGo, 524 00:19:54,029 --> 00:19:54,529 monitoring 525 00:19:54,830 --> 00:19:57,410 Azure Data Lake Storage or Azure SQL 526 00:19:57,710 --> 00:20:00,750 data sources, that all requires PAYGo. It was 527 00:20:00,750 --> 00:20:03,230 kind of a a interesting list to look 528 00:20:03,230 --> 00:20:05,410 at. I'll make sure to put a look 529 00:20:05,549 --> 00:20:07,674 at the the billing docs and the billing 530 00:20:07,674 --> 00:20:08,174 considerations 531 00:20:08,474 --> 00:20:09,855 in the show notes. Yeah. 532 00:20:13,755 --> 00:20:15,835 Do you feel overwhelmed by trying to manage 533 00:20:15,835 --> 00:20:18,154 your Office three sixty five environment? Are you 534 00:20:18,154 --> 00:20:21,490 facing unexpected issues that disrupt your company's productivity? 535 00:20:21,710 --> 00:20:23,630 Intelligink is here to help. Much like you 536 00:20:23,630 --> 00:20:25,549 take your car to the mechanic that has 537 00:20:25,549 --> 00:20:27,630 specialized knowledge on how to best keep your 538 00:20:27,630 --> 00:20:30,609 car running, Intelligink helps you with your Microsoft 539 00:20:30,669 --> 00:20:32,929 cloud environment because that's their expertise. 540 00:20:33,544 --> 00:20:35,625 Intelligent keeps up with the latest updates in 541 00:20:35,625 --> 00:20:37,865 the Microsoft cloud to help keep your business 542 00:20:37,865 --> 00:20:40,025 running smoothly and ahead of the curve. Whether 543 00:20:40,025 --> 00:20:42,105 you are a small organization with just a 544 00:20:42,105 --> 00:20:44,585 few users up to an organization of several 545 00:20:44,585 --> 00:20:45,565 thousand employees, 546 00:20:46,019 --> 00:20:47,859 They want to partner with you to implement 547 00:20:47,859 --> 00:20:50,680 and administer your Microsoft cloud technology. 548 00:20:51,380 --> 00:20:54,920 Visit them at inteligync.com/podcast. 549 00:20:55,140 --> 00:21:01,875 That's intelligink.com/podcast 550 00:21:02,335 --> 00:21:04,414 for more information or to schedule a thirty 551 00:21:04,414 --> 00:21:06,515 minute call to get started with them today. 552 00:21:06,734 --> 00:21:10,095 Remember, Intelligink focuses on the Microsoft cloud so 553 00:21:10,095 --> 00:21:11,875 you can focus on your business. 554 00:21:14,015 --> 00:21:16,019 The one thing I would say when I 555 00:21:16,019 --> 00:21:18,279 started doing this, they do make it fairly 556 00:21:18,819 --> 00:21:19,319 straightforward 557 00:21:19,779 --> 00:21:21,539 to get going. So what I did, like, 558 00:21:21,539 --> 00:21:22,759 I went through that overview, 559 00:21:23,059 --> 00:21:25,700 turned on those those four required things, the 560 00:21:25,700 --> 00:21:27,960 auditing, the onboarding devices, 561 00:21:28,755 --> 00:21:29,974 extending insights 562 00:21:30,515 --> 00:21:33,154 was one of them, and then the browser 563 00:21:33,154 --> 00:21:35,394 extension. But even some of these, like when 564 00:21:35,394 --> 00:21:37,954 you click on, okay, we need to discover 565 00:21:37,954 --> 00:21:38,934 sensitive information, 566 00:21:39,394 --> 00:21:40,214 a lot of 567 00:21:40,595 --> 00:21:42,134 what DSPM is 568 00:21:42,529 --> 00:21:45,589 policy driven off of other areas 569 00:21:46,210 --> 00:21:48,609 within Purview. So when you click to start 570 00:21:48,609 --> 00:21:52,289 extending your insights for data discovery, what it 571 00:21:52,289 --> 00:21:53,589 gives you is 572 00:21:54,049 --> 00:21:56,934 what the three policies are. And I already 573 00:21:56,934 --> 00:21:58,454 have them turned on in mind, but if 574 00:21:58,454 --> 00:22:00,054 they're not turned on, it's like this is 575 00:22:00,054 --> 00:22:02,394 the PayGo policy or this is 576 00:22:02,934 --> 00:22:04,875 free depending on those interactions 577 00:22:05,414 --> 00:22:07,254 in just a one click button to deploy 578 00:22:07,254 --> 00:22:09,414 it. And then once you deploy it, you 579 00:22:09,414 --> 00:22:11,174 can always go in and look at policy 580 00:22:11,174 --> 00:22:11,674 details. 581 00:22:12,029 --> 00:22:12,529 So 582 00:22:12,830 --> 00:22:15,470 for extending that data discovery, like, again, the 583 00:22:15,470 --> 00:22:17,070 first part of this is what are people 584 00:22:17,070 --> 00:22:21,090 doing is like, are people putting sensitive information 585 00:22:21,630 --> 00:22:23,630 in AI prompts in Edge or in your 586 00:22:23,630 --> 00:22:24,850 browser? And 587 00:22:25,309 --> 00:22:26,544 this policy 588 00:22:26,845 --> 00:22:29,984 is actually a data loss prevention policy 589 00:22:30,444 --> 00:22:33,105 that sits in the collection policies 590 00:22:33,644 --> 00:22:36,525 in DLP. So when you click it, it's 591 00:22:36,525 --> 00:22:38,630 just going out and creating this. And when 592 00:22:38,630 --> 00:22:40,870 you would go into data loss prevention and 593 00:22:40,870 --> 00:22:41,930 your collection policies, 594 00:22:42,390 --> 00:22:45,190 you'll see all those DSPM policies that you've 595 00:22:45,190 --> 00:22:47,350 created, and you can go in and look 596 00:22:47,350 --> 00:22:49,910 at what those policies are doing. You can 597 00:22:49,910 --> 00:22:51,930 tweak them, turn them on or off. 598 00:22:52,855 --> 00:22:54,775 So while it is like a one click, 599 00:22:54,775 --> 00:22:57,015 just deploy it, I would also say go 600 00:22:57,015 --> 00:22:58,954 in and look at some of these policies 601 00:22:59,095 --> 00:23:00,474 because it might also 602 00:23:01,255 --> 00:23:03,835 highlight some additional functionality that's available 603 00:23:04,134 --> 00:23:06,694 within these different platforms that is I would 604 00:23:06,694 --> 00:23:08,929 say they've almost kind of snuck in there. 605 00:23:08,990 --> 00:23:10,789 Like these collections I mean, you're paying for 606 00:23:10,789 --> 00:23:12,909 it. Right. It's it's out there. And these 607 00:23:12,909 --> 00:23:15,470 collection policies, some of the newer ones that 608 00:23:15,470 --> 00:23:16,909 are out here now are like network and 609 00:23:16,909 --> 00:23:19,329 browser based. So this one was sensitive information 610 00:23:19,389 --> 00:23:22,029 shared in the browser, but now it's also 611 00:23:22,029 --> 00:23:23,569 detecting sensitive information 612 00:23:24,164 --> 00:23:26,424 shared via AI over 613 00:23:26,725 --> 00:23:27,384 the network. 614 00:23:27,684 --> 00:23:29,164 So not only just what am I doing 615 00:23:29,164 --> 00:23:31,545 in the browser, but watching my 616 00:23:31,924 --> 00:23:33,305 browsers, my applications, 617 00:23:33,765 --> 00:23:36,105 API calls, add ins, 618 00:23:36,779 --> 00:23:39,119 watching my different network traffic 619 00:23:39,500 --> 00:23:40,480 from my devices 620 00:23:40,940 --> 00:23:43,680 for sensitive information going to other 621 00:23:44,059 --> 00:23:46,619 AI sites. You brought up licensing. It does 622 00:23:46,619 --> 00:23:47,840 require the 623 00:23:48,380 --> 00:23:51,340 A little bit. Global secure access, the secure 624 00:23:51,340 --> 00:23:51,840 edge 625 00:23:52,264 --> 00:23:54,664 licensing as well. So you will start running 626 00:23:54,664 --> 00:23:55,164 into, 627 00:23:55,544 --> 00:23:58,204 Hey, now I want to start capturing just 628 00:23:58,345 --> 00:24:00,825 network data. Guess what? You need some solution 629 00:24:00,825 --> 00:24:03,544 to actually capture that network data. So you 630 00:24:03,544 --> 00:24:06,365 have some policies there just around data collection, 631 00:24:06,619 --> 00:24:08,539 but then this is where you also have 632 00:24:08,539 --> 00:24:10,220 a bunch of policies if you go into 633 00:24:10,220 --> 00:24:10,720 recommendations 634 00:24:11,420 --> 00:24:13,359 after you start doing data collection, 635 00:24:13,740 --> 00:24:15,840 and you can go in and start creating 636 00:24:16,059 --> 00:24:17,039 different policies 637 00:24:17,500 --> 00:24:18,000 around 638 00:24:18,619 --> 00:24:20,880 then detecting that risk information. 639 00:24:21,715 --> 00:24:23,015 If you're using ChatGPT 640 00:24:23,315 --> 00:24:23,815 Enterprise, 641 00:24:24,115 --> 00:24:26,615 there's built in policies here for 642 00:24:27,154 --> 00:24:30,055 discovering and governing interactions with ChatGPT 643 00:24:30,434 --> 00:24:30,934 Enterprise, 644 00:24:31,394 --> 00:24:34,115 using Copilot and agents to improve your data 645 00:24:34,115 --> 00:24:34,615 security, 646 00:24:34,994 --> 00:24:35,494 and 647 00:24:36,195 --> 00:24:37,414 a lot of different 648 00:24:38,410 --> 00:24:38,910 functionality 649 00:24:39,210 --> 00:24:42,349 around creating these different policies to prevent, 650 00:24:42,809 --> 00:24:44,109 monitor, alert 651 00:24:44,730 --> 00:24:47,930 on where's my sensitive information going when it 652 00:24:47,930 --> 00:24:51,545 relates, again, specifically to AI in this particular 653 00:24:51,765 --> 00:24:54,404 solution. Yeah. Yeah. We should probably spend the 654 00:24:54,404 --> 00:24:55,924 last couple of minutes here and kinda talk 655 00:24:55,924 --> 00:24:56,424 about 656 00:24:56,725 --> 00:24:58,485 once you've got the insights, what do you 657 00:24:58,485 --> 00:25:00,884 do with them? Yeah. So say you're out 658 00:25:00,884 --> 00:25:02,184 there. You've got, 659 00:25:02,565 --> 00:25:04,825 like you said, your DLP in place. 660 00:25:05,200 --> 00:25:08,180 You've got this solution that's doing this monitoring 661 00:25:08,480 --> 00:25:10,960 for you. And then what are you gonna 662 00:25:10,960 --> 00:25:12,019 do with the information? 663 00:25:12,559 --> 00:25:14,480 And how do you leverage those rest of 664 00:25:14,480 --> 00:25:16,019 the tools for remediation? 665 00:25:16,400 --> 00:25:18,265 You know, I I think about, like, that 666 00:25:18,265 --> 00:25:20,664 proxy that gets deployed, like you said, like, 667 00:25:20,664 --> 00:25:22,984 the global secure access thing. Well, you can 668 00:25:22,984 --> 00:25:25,304 block stuff through that. Yep. You wanna take 669 00:25:25,304 --> 00:25:27,304 this report and maybe go turn those kinds 670 00:25:27,304 --> 00:25:29,224 of things on. And I think the biggest 671 00:25:29,224 --> 00:25:32,079 one here when I start talking to clients 672 00:25:32,079 --> 00:25:33,679 and working on it is once you have 673 00:25:33,679 --> 00:25:34,960 the detection to your point, what are you 674 00:25:34,960 --> 00:25:36,880 gonna do about it, is going in and 675 00:25:36,880 --> 00:25:39,460 building out those data loss prevention policies. 676 00:25:39,919 --> 00:25:41,380 One of them that 677 00:25:41,839 --> 00:25:43,599 kind of comes out of this, you don't 678 00:25:43,599 --> 00:25:45,494 need the SPM to do it, but it 679 00:25:45,734 --> 00:25:47,974 walks you through getting everything in place for 680 00:25:47,974 --> 00:25:50,315 it, is just protecting sensitive information 681 00:25:50,615 --> 00:25:53,174 in your own environment from Copilot. And this 682 00:25:53,174 --> 00:25:55,994 is an example I give to clients is 683 00:25:56,055 --> 00:25:56,714 up until 684 00:25:57,255 --> 00:25:58,555 deploying this with DLP, 685 00:25:59,015 --> 00:26:01,115 the only option to, like, prevent 686 00:26:01,690 --> 00:26:03,470 data from going into 687 00:26:03,850 --> 00:26:06,750 Copilot was to disable the index, 688 00:26:07,049 --> 00:26:10,009 which doesn't impact just Copilot, but also index 689 00:26:10,090 --> 00:26:12,330 impacts your search index, or it's to remove 690 00:26:12,330 --> 00:26:14,170 permissions to it. There may be things, Scott, 691 00:26:14,170 --> 00:26:14,565 like, 692 00:26:15,125 --> 00:26:16,484 I need to get to all of the 693 00:26:16,484 --> 00:26:18,244 data in my tenant. I need to work 694 00:26:18,244 --> 00:26:19,605 with that. I need to work with, I 695 00:26:19,605 --> 00:26:21,704 have w nines out there. If I have 696 00:26:21,764 --> 00:26:23,384 bank statements out there, like, 697 00:26:24,004 --> 00:26:26,004 this is my data. There is going to 698 00:26:26,004 --> 00:26:27,845 be sensitive information out there that I'm gonna 699 00:26:27,845 --> 00:26:29,764 need access to, and that I may wanna 700 00:26:29,764 --> 00:26:31,869 search, but I may not want Copilot 701 00:26:32,250 --> 00:26:35,450 necessarily processing that returning it. So, by going 702 00:26:35,450 --> 00:26:37,690 in and starting to apply sensitivity labels to 703 00:26:37,690 --> 00:26:40,569 it and then using this protect sensitive information 704 00:26:40,569 --> 00:26:41,309 from Copilot, 705 00:26:41,609 --> 00:26:42,345 I still have 706 00:26:54,345 --> 00:26:56,369 Yeah. I Yeah. I think over time, that 707 00:26:56,369 --> 00:26:59,169 granularity is gonna continue to change, like because 708 00:26:59,169 --> 00:27:01,009 you're gonna have subsets of people who might 709 00:27:01,009 --> 00:27:02,609 need to work on things, and they might 710 00:27:02,609 --> 00:27:04,929 need Gen AI and Copilot for them. And 711 00:27:04,929 --> 00:27:06,704 then you might have people who don't. 712 00:27:07,585 --> 00:27:09,184 So you're back to kind of just the 713 00:27:09,184 --> 00:27:09,684 regular, 714 00:27:10,144 --> 00:27:11,904 hey, let me make sure this stuff is 715 00:27:11,904 --> 00:27:15,125 secure. But it's also funny, I think, how 716 00:27:15,265 --> 00:27:16,565 things do 717 00:27:17,345 --> 00:27:18,884 leak in Copilot 718 00:27:19,265 --> 00:27:20,660 just because organizations 719 00:27:21,200 --> 00:27:24,000 that largely haven't kept up, I think, with 720 00:27:24,000 --> 00:27:25,840 having a big corpus of data that lives 721 00:27:25,840 --> 00:27:28,320 in SharePoint. And they never really figured out 722 00:27:28,320 --> 00:27:31,200 the whole security trimmed search thing, let alone 723 00:27:31,200 --> 00:27:33,920 the security trimmed AI search thing and how 724 00:27:33,920 --> 00:27:36,535 that comes together. Yeah. And then I would 725 00:27:36,535 --> 00:27:38,234 say some of the other ones is like 726 00:27:38,535 --> 00:27:40,795 going back to the other AI sites. 727 00:27:41,095 --> 00:27:43,335 Once you're starting to capture it and depending 728 00:27:43,335 --> 00:27:45,095 on your licenses and what you have turned 729 00:27:45,095 --> 00:27:47,174 on, it's not just, yeah, I don't want 730 00:27:47,174 --> 00:27:49,894 Copilot to process this, but you know what? 731 00:27:49,894 --> 00:27:50,795 I can't, 732 00:27:51,289 --> 00:27:53,529 I can't, don't want, however you wanna phrase 733 00:27:53,529 --> 00:27:55,470 it, my users going in 734 00:27:56,169 --> 00:27:58,029 and using sensitive information 735 00:27:58,329 --> 00:28:01,609 in other sites. So some of these DLP 736 00:28:01,609 --> 00:28:03,789 policies then that you can apply to devices 737 00:28:03,849 --> 00:28:07,144 is auditing that sensitive data that is 738 00:28:07,684 --> 00:28:08,744 shared to 739 00:28:09,445 --> 00:28:11,845 other sites. And I'm pulling up what these 740 00:28:11,845 --> 00:28:15,445 are, like uploaded over the network or one 741 00:28:15,445 --> 00:28:17,285 of these policies. It's not this one that 742 00:28:17,285 --> 00:28:18,859 I just pulled up is 743 00:28:19,240 --> 00:28:21,819 looking specifically for people adding it to 744 00:28:22,279 --> 00:28:23,980 BARD or to ChatGPT. 745 00:28:24,920 --> 00:28:26,839 Because now that you are auditing it, you 746 00:28:26,839 --> 00:28:28,539 can see people are pasting 747 00:28:28,920 --> 00:28:31,420 PII or pasting social security numbers 748 00:28:31,755 --> 00:28:34,795 into these other third party Gen AI sites. 749 00:28:34,795 --> 00:28:37,674 And frankly, we just can't have that and 750 00:28:37,674 --> 00:28:41,035 need to prevent that from even happening or 751 00:28:41,035 --> 00:28:42,795 prevent it from even occurring. Yeah. I think 752 00:28:42,795 --> 00:28:44,670 it's one of those rabbit holes. Yeah. You 753 00:28:44,670 --> 00:28:46,750 start going down. I mean, DLP policies in 754 00:28:46,750 --> 00:28:47,250 general 755 00:28:47,710 --> 00:28:49,470 are their own rabbit hole. I do like 756 00:28:49,470 --> 00:28:52,109 having kind of the enabler of the policies 757 00:28:52,109 --> 00:28:54,509 are canned and kind of pre baked, and 758 00:28:54,509 --> 00:28:56,684 then you can tweak them from there. But 759 00:28:56,845 --> 00:28:58,845 there's a whole bunch, I think, to go 760 00:28:58,845 --> 00:29:01,325 figure out. And then products like these are 761 00:29:01,325 --> 00:29:03,884 so easy to just get caught in the 762 00:29:03,884 --> 00:29:06,205 the charts and the reports. But I think 763 00:29:06,205 --> 00:29:07,585 figuring out how you 764 00:29:08,125 --> 00:29:08,625 actually 765 00:29:09,250 --> 00:29:11,029 get it wired up in your environment 766 00:29:11,409 --> 00:29:12,849 and get it to where it needs to 767 00:29:12,849 --> 00:29:15,329 be, that's another story and another thing that 768 00:29:15,329 --> 00:29:17,169 needs to be taken care of. Yeah. Then 769 00:29:17,169 --> 00:29:18,609 the other thing I would say is just 770 00:29:18,609 --> 00:29:19,269 the activities 771 00:29:19,650 --> 00:29:21,970 explore in the last few minutes. If you, 772 00:29:21,970 --> 00:29:23,904 you can see, Scott, even some of the 773 00:29:23,904 --> 00:29:25,365 stuff that I've done is 774 00:29:25,664 --> 00:29:26,484 AI interactions 775 00:29:26,785 --> 00:29:28,945 start showing up now in your activity explorer 776 00:29:28,945 --> 00:29:29,445 alongside 777 00:29:30,384 --> 00:29:30,884 emails, 778 00:29:31,184 --> 00:29:31,684 alongside 779 00:29:32,945 --> 00:29:35,105 working with files in SharePoint, and it allows 780 00:29:35,105 --> 00:29:38,404 you to start even monitoring and alerting on 781 00:29:38,509 --> 00:29:40,990 what are users doing. So it will you 782 00:29:40,990 --> 00:29:42,769 wanna get super big brother, Scott. 783 00:29:43,070 --> 00:29:44,990 Like, your Microsoft three sixty five tenants, your 784 00:29:44,990 --> 00:29:46,590 employers, they can spy on you all they 785 00:29:46,590 --> 00:29:49,150 want to, and the ability is here. It 786 00:29:49,150 --> 00:29:50,830 starts pulling in. I can go in and 787 00:29:50,830 --> 00:29:52,430 look at any prompt that I've done in 788 00:29:52,430 --> 00:29:54,765 Copilot, what that response was, 789 00:29:55,305 --> 00:29:58,664 any additional responses to it, going and looking 790 00:29:58,664 --> 00:30:01,384 through, again, just that audit log, having that 791 00:30:01,384 --> 00:30:04,825 audit history of AI interaction, which, I mean, 792 00:30:04,825 --> 00:30:06,730 I think this does become more and more 793 00:30:06,730 --> 00:30:08,890 important as people are using AI for their 794 00:30:08,890 --> 00:30:10,029 jobs, for generating 795 00:30:10,490 --> 00:30:11,869 documents, for generating 796 00:30:12,410 --> 00:30:12,910 emails. 797 00:30:13,369 --> 00:30:15,470 Let's face it, we all do it. There 798 00:30:15,690 --> 00:30:17,710 is going to start being instances 799 00:30:18,009 --> 00:30:20,945 where there may be cases that arise that 800 00:30:20,945 --> 00:30:22,565 you need to go figure out 801 00:30:22,945 --> 00:30:24,884 where this certain employee misbehaved 802 00:30:25,184 --> 00:30:25,684 with 803 00:30:26,384 --> 00:30:28,865 AI. And having that audit log, that Activity 804 00:30:28,865 --> 00:30:29,365 Explorer, 805 00:30:29,904 --> 00:30:32,545 well, yes, it does feel big brotherish by 806 00:30:32,545 --> 00:30:36,580 an employer. From a legal perspective, compliance perspective, 807 00:30:36,580 --> 00:30:37,799 I think this is absolutely 808 00:30:38,340 --> 00:30:40,820 necessary as well. So, yeah, all of that 809 00:30:40,820 --> 00:30:42,580 gets built in there. And then there's some 810 00:30:42,580 --> 00:30:44,420 data risk assessments. If you want to go 811 00:30:44,420 --> 00:30:45,400 run some assessments 812 00:30:45,860 --> 00:30:46,360 around 813 00:30:46,865 --> 00:30:48,404 the amount of sensitive data, 814 00:30:48,785 --> 00:30:49,285 links 815 00:30:49,585 --> 00:30:50,884 that have gotten shared, 816 00:30:51,265 --> 00:30:52,884 how many links have been created 817 00:30:53,184 --> 00:30:54,005 in the 818 00:30:54,305 --> 00:30:54,805 last 819 00:30:55,184 --> 00:30:58,144 100 or the last 30 or so. There's 820 00:30:58,144 --> 00:31:00,240 also some of that. It's similar to what's 821 00:31:00,240 --> 00:31:01,220 like in the SharePoint, 822 00:31:01,680 --> 00:31:04,720 the data access governance reports in SharePoint. Some 823 00:31:04,720 --> 00:31:06,900 of these data risk assessments around 824 00:31:07,840 --> 00:31:10,559 what types of links and sensitive data have 825 00:31:10,559 --> 00:31:11,220 been shared 826 00:31:11,680 --> 00:31:14,315 across my environment so that I can go 827 00:31:14,315 --> 00:31:15,215 in and 828 00:31:15,914 --> 00:31:16,414 respond, 829 00:31:17,035 --> 00:31:19,055 maybe have user training because 830 00:31:19,515 --> 00:31:22,335 it's highlighting some bad behaviors of employees. 831 00:31:22,715 --> 00:31:23,994 But being able to run some of that 832 00:31:23,994 --> 00:31:26,955 reporting and assessment around where are people sharing 833 00:31:26,955 --> 00:31:28,634 data and how much sensitive data is out 834 00:31:28,634 --> 00:31:30,289 there? Where are they sharing data more than 835 00:31:30,289 --> 00:31:32,230 you think? How much is out there also 836 00:31:32,289 --> 00:31:34,869 more than you think? A 100%. 837 00:31:35,089 --> 00:31:36,849 The other interesting thing, Aaron, I wonder if 838 00:31:36,849 --> 00:31:38,809 you've run into this just, like, with any 839 00:31:38,809 --> 00:31:39,670 of your customers, 840 00:31:40,210 --> 00:31:40,710 is 841 00:31:41,089 --> 00:31:43,809 some of the Gen AI platforms don't actually 842 00:31:43,809 --> 00:31:46,144 run their own things. So, like, if you're 843 00:31:46,144 --> 00:31:49,125 a perplexity customer coming through a perplexity API, 844 00:31:49,265 --> 00:31:51,845 then you're actually using an underlying model from, 845 00:31:51,904 --> 00:31:54,625 like, an anthropic or OpenAI or something on 846 00:31:54,625 --> 00:31:56,785 the back end. So there there's all these 847 00:31:56,785 --> 00:31:59,150 weird little change. I I would also encourage 848 00:31:59,150 --> 00:32:00,829 folks, like, if you are looking at this, 849 00:32:00,829 --> 00:32:02,750 like and some of the stuff we talked 850 00:32:02,750 --> 00:32:05,150 about, like, hey, this thing can monitor AI 851 00:32:05,150 --> 00:32:07,890 sites. That's, like, a fixed list of sites 852 00:32:08,509 --> 00:32:11,144 that come out. So so they'd is very 853 00:32:11,545 --> 00:32:12,045 comprehensive. 854 00:32:12,424 --> 00:32:14,345 Like, I I will say, like, if you 855 00:32:14,345 --> 00:32:16,025 go through, like, the list of sites that 856 00:32:16,025 --> 00:32:18,744 the it does cover, it's a lot. Like, 857 00:32:18,744 --> 00:32:21,384 I hadn't even heard of, like, 90% of 858 00:32:21,384 --> 00:32:23,305 them easy. But, you know, if there's something 859 00:32:23,305 --> 00:32:25,349 out there where you're like, oh, this is 860 00:32:25,429 --> 00:32:26,970 a new Gen AI tool 861 00:32:27,429 --> 00:32:30,150 or AI products that my organization uses, it 862 00:32:30,150 --> 00:32:31,589 might not be on the list. You gotta 863 00:32:31,589 --> 00:32:33,769 go figure that stuff out too. Yes. Microsoft 864 00:32:33,990 --> 00:32:36,390 does work to keep it updated, but, yeah, 865 00:32:36,390 --> 00:32:37,750 I mean, you or I could go stand 866 00:32:37,750 --> 00:32:39,269 up a site on Azure, give it some 867 00:32:39,269 --> 00:32:40,970 random domain name tied into 868 00:32:41,535 --> 00:32:43,535 some LLM on the back end, and all 869 00:32:43,535 --> 00:32:44,894 of a sudden, there's a new Gen AI 870 00:32:44,894 --> 00:32:46,755 site out there hosted by the podcast. 871 00:32:47,855 --> 00:32:50,174 Is that what you wanna do? No. That 872 00:32:50,174 --> 00:32:51,775 is not what I wanna do. But we 873 00:32:51,775 --> 00:32:54,195 could. Enough, it does monitor. 874 00:32:54,779 --> 00:32:58,940 So it does monitor for azure.microsoft.com 875 00:32:58,940 --> 00:33:02,619 and specifically the OpenAI service product page. So, 876 00:33:02,619 --> 00:33:04,799 like, the page that would tell you about, 877 00:33:04,859 --> 00:33:07,580 not the learn docs and, how to use 878 00:33:07,580 --> 00:33:09,944 it, but more like the marketing page with 879 00:33:09,944 --> 00:33:11,865 the pricing and things like that on there. 880 00:33:11,865 --> 00:33:14,424 So that's on the list, but, azure.com is 881 00:33:14,424 --> 00:33:17,144 not. So like you said, you can go, 882 00:33:17,384 --> 00:33:19,704 potentially spin these things up because you can 883 00:33:19,704 --> 00:33:21,625 absolutely get into the portal. But it had 884 00:33:21,625 --> 00:33:22,744 a lot of, like, I was kind of 885 00:33:22,744 --> 00:33:24,585 impressed. I had like Devon, a lot of 886 00:33:24,585 --> 00:33:27,049 the smaller stuff was baked into there as 887 00:33:27,049 --> 00:33:29,769 well. Along with that, like, just like the, 888 00:33:29,769 --> 00:33:32,029 I think the more like US centric 889 00:33:32,650 --> 00:33:35,230 AI or European offerings, but also 890 00:33:35,609 --> 00:33:37,470 stuff out of Asia Pacific and 891 00:33:37,785 --> 00:33:40,424 China and things like that. So it had 892 00:33:40,424 --> 00:33:42,424 broad coverage, but, you know, you gotta check 893 00:33:42,424 --> 00:33:44,105 the list to make sure your thing is 894 00:33:44,105 --> 00:33:46,184 there. Yep. Yeah. They've done a good job 895 00:33:46,184 --> 00:33:48,184 with it. So I think that's kind of 896 00:33:48,184 --> 00:33:50,025 the last aspect to it. And that's what 897 00:33:50,025 --> 00:33:51,965 I talked about in that presentation is 898 00:33:52,359 --> 00:33:54,039 not only do you need to go in 899 00:33:54,039 --> 00:33:54,539 and 900 00:33:55,240 --> 00:33:56,779 be, let's say, preventative 901 00:33:57,079 --> 00:33:59,639 about where this data is going with some 902 00:33:59,639 --> 00:34:02,380 of the cleaning up security, cleaning up permissions, 903 00:34:02,519 --> 00:34:04,519 starting to get labels on your content, knowing 904 00:34:04,519 --> 00:34:06,714 what content is out there, But then leveraging 905 00:34:06,714 --> 00:34:09,434 something like DSPM where you can do some 906 00:34:09,434 --> 00:34:12,315 of that deal those DLP policies, a lot 907 00:34:12,315 --> 00:34:14,155 of this is just baked in to help 908 00:34:14,155 --> 00:34:16,014 you kinda get there, I would say, quickly. 909 00:34:16,315 --> 00:34:19,275 But then also that kinda ongoing monitoring, like, 910 00:34:19,275 --> 00:34:21,339 going in and looking at the activity explorer 911 00:34:21,339 --> 00:34:22,559 in here and some of the 912 00:34:22,940 --> 00:34:25,199 reports in here to just see, 913 00:34:25,500 --> 00:34:27,260 like, I've had 540 914 00:34:27,260 --> 00:34:29,500 activities in the last thirty days with different 915 00:34:29,500 --> 00:34:31,359 interactions with Copilot and agents. 916 00:34:31,659 --> 00:34:33,739 Going and looking at my total visits to 917 00:34:33,739 --> 00:34:35,579 other AI apps, you can see I do 918 00:34:35,579 --> 00:34:35,804 tend 919 00:34:36,844 --> 00:34:39,505 to favor Copilot, but like Notion and Perplexity 920 00:34:39,964 --> 00:34:42,925 and Suno and some of those other AI 921 00:34:42,925 --> 00:34:45,085 tools that I have used have been showing 922 00:34:45,085 --> 00:34:47,905 up in here. So just being aware of 923 00:34:47,964 --> 00:34:49,664 where are your users 924 00:34:50,360 --> 00:34:53,719 potentially exposing your data to places they shouldn't 925 00:34:53,719 --> 00:34:55,960 be. Yeah. I I think it's, it's an 926 00:34:55,960 --> 00:34:56,860 important one. 927 00:34:57,239 --> 00:34:59,239 Absolutely. But with that, are we supposed to 928 00:34:59,239 --> 00:35:00,760 go back to work now? Is that what's 929 00:35:00,760 --> 00:35:03,000 supposed to happen? We are we are supposed 930 00:35:03,000 --> 00:35:04,775 to go back to work. Oh. 931 00:35:05,155 --> 00:35:06,835 Alright. Go back to work. Before you go 932 00:35:06,835 --> 00:35:08,914 back to work. This far. And you're still 933 00:35:08,914 --> 00:35:09,414 listening. 934 00:35:09,875 --> 00:35:11,234 Feel free to reach out. We have a 935 00:35:11,234 --> 00:35:13,394 contact us page on the website. Let us 936 00:35:13,394 --> 00:35:14,914 know what you'd like to hear about, what 937 00:35:14,914 --> 00:35:16,514 topics are interesting to you. Give us a 938 00:35:16,514 --> 00:35:17,255 ping on LinkedIn. 939 00:35:17,769 --> 00:35:19,130 You can find Ben there. You can find 940 00:35:19,130 --> 00:35:21,309 myself there. You can find the podcast there. 941 00:35:21,450 --> 00:35:22,989 And let us know 942 00:35:23,450 --> 00:35:24,269 what topics, 943 00:35:24,809 --> 00:35:28,010 people, interviews, anything like that would be interesting 944 00:35:28,010 --> 00:35:30,329 to you. Absolutely. We'd love to hear from 945 00:35:30,329 --> 00:35:31,150 you. So 946 00:35:31,485 --> 00:35:34,125 thanks. Alright. Thanks, Ben. As always, I appreciate 947 00:35:34,125 --> 00:35:36,224 it. Definitely. And we'll talk to you later. 948 00:35:38,204 --> 00:35:40,445 If you enjoyed the podcast, go leave us 949 00:35:40,445 --> 00:35:42,684 a five star rating in iTunes. It helps 950 00:35:42,684 --> 00:35:44,469 to get the word out so more IT 951 00:35:44,469 --> 00:35:46,550 pros can learn about Office three sixty five 952 00:35:46,550 --> 00:35:47,210 and Azure. 953 00:35:47,750 --> 00:35:49,430 If you have any questions you want us 954 00:35:49,430 --> 00:35:51,590 to address on the show, or feedback about 955 00:35:51,590 --> 00:35:53,910 the show, feel free to reach out via 956 00:35:53,910 --> 00:35:56,090 our website, Twitter, or Facebook. 957 00:35:56,390 --> 00:35:58,309 Thanks again for listening, and have a great 958 00:35:58,309 --> 00:35:58,809 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