Latest / Microsoft Cloud IT Pro Podcast / Episode 439: Azure SRE Agent vs. the Azure Copilot Troubleshooting Agent
Transcript
- 0:00Welcome to Episode 439 of the Microsoft Cloud IT Pro Podcast, recorded live on October 19, 2026.
- 0:11This is a show about Microsoft 365 and Azure from the perspective of IT pros and end users, where we discuss a topic or recent news and how it relates to you.
- 0:21In this episode, Ben and Scott compare two new AI agents for Azure, the Azure Copilot Troubleshooting Agent, a free helper in the Azure portal, and the Azure SRE Agent, a paid service with a portal of its own.
- 0:35They get into why the two have such different names, the different use cases for them, what the SRE Agent's usage-based pricing might really cost, and the guardrails and network setup that decide how far you can trust an agent with production.
- 0:51Can I start sending agents to conferences to speak for me?
- 0:55Probably.
- 0:56There's a guy who does these, he posts like the AI interviewers, and he just messes with them completely.
- 1:05I don't know that I've seen that.
- 1:06I'll have to find some and put them in the show notes or things like that.
- 1:10But he'll hop on with somebody and they'll go like, what have you done?
- 1:14He's like, I'm Chick Bongo, and I'm a salesperson, blah, blah, blah.
- 1:21He had one where he brought an AI agent to, and these are all like video, like real-time, like video agents kinds of things, like IVR++ when you're on a phone tree.
- 1:34But he brought a virtual agent to an interview, so he was being interviewed by a virtual agent.
- 1:42He brought his own virtual agent, and then he was there.
- 1:44And then the two agents just started talking to each other, and his virtual agent, like the one that was interviewing, said, what salary are you looking for?
- 1:53And the salary range of the job is $120,000 to $150,000 US, something like that.
- 1:59And his virtual agent, who's like his representative, who's supposed to be negotiating on his behalf, goes $60,000.
- 2:05It's a great starting point.
- 2:07And he's like, no, no, no, you can't do that.
- 2:10That's funny.
- 2:10I'll pull some together, you'll get a kick out of them.
- 2:13I should actually go speak at conferences and let my agents do my work for me.
- 2:17I was going to say, you should probably flip it or reverse it if you could, while you still can.
- 2:23Or, you go to the conference, you just hang out, and you put your little virtual agent up on the screen or whatever.
- 2:30It's all good.
- 2:31Like, you know, they can scan you, it'll look just like you, it'll sound like you-ish, maybe.
- 2:37Can you make it talk Upper Peninsula?
- 2:39That would be pretty sweet.
- 2:40Well, I sent you the one because Riverside let you do that, right?
- 2:43I sent you the, did I send you the Riverside agent or the Riverside, I can't remember what they call it in Riverside,
- 2:50where it can take all of our recordings and create our own virtual agents, essentially, our own virtual people.
- 2:57And you can just type in what you want it to say and post to social media.
- 3:00No.
- 3:03It was kind of creepy.
- 3:05I showed it to my family.
- 3:06I showed it to my kids for an example of, this is why you don't just trust anybody calling anytime.
- 3:13Because this is not something I said, this is something Riverside made from recordings of me.
- 3:20And I just typed in what I wanted it to say.
- 3:25Love it.
- 3:26You can absolutely do it.
- 3:27It was, it did a really good job.
- 3:29It, like, I could tell, my wife could tell it wasn't me.
- 3:32Just some of the, the mannerisms, the phrasing of how it, how it articulated certain things.
- 3:40Like, there were still, still signs, but it was, it was kind of scarily good.
- 3:46If you weren't paying attention super close or weren't looking for it,
- 3:50it could easily be interpreted as actually being me.
- 3:54Okay.
- 3:54Yeah.
- 3:55I'll have to go make one.
- 3:56I'll send you one.
- 3:57Looking out for, for that one too next, huh?
- 4:00But we are not here to talk about Agent Ben or Agent Scott.
- 4:04No?
- 4:04Unless it's not really us recording the podcast.
- 4:07Unless it's our agents recording the podcast pretending to be us.
- 4:10No, there's a couple new agents in Azure that we were going to talk about.
- 4:14Because, what else would we talk about other than AI?
- 4:18I'm going to find some topics, Scott.
- 4:20That's my new goal, find a non-AI.
- 4:23Good luck.
- 4:24So I was going to say, like, very, very much, like, good luck to you.
- 4:29Good luck to that.
- 4:30It's a, it's, it's a goal, I guess.
- 4:33It can be a goal.
- 4:33We got some more agents today.
- 4:36So we chatted a little while back.
- 4:40Well, I mean, last time we chatted, we were chatting about just LLM wikis, right?
- 4:45And how we kind of wrap these things and a little bit what you can do with skills and harnesses.
- 4:49I think you could apply a lot of what we talked about there to what we're going to talk about today.
- 4:54Because really, it's just that manifestation of going beyond single skills and into more of these composite workflows with agents.
- 5:06And, you know, there's still the, I think, the crisis or maybe not a crisis, but like, what's the definition of an agent and how does that all come together?
- 5:15But I think of them as just composition of skills and we can run these things on a schedule or we can interact with them or put them in a harness and have them run to some kind of outcome.
- 5:25But we're going to talk about two other agents today.
- 5:27So we also talked in the past about project perception and kind of what comes with some of the agent side with kind of red teams, blue teams, green teams, things like that.
- 5:39That was a little bit more Defender-based, like M365, Microsoft Defender, Security World.
- 5:44Today, we're going to talk about Azure mostly and kind of focus on two things.
- 5:48So the Azure SRE agent and the Azure Copilot troubleshooter or the Azure Copilot troubleshooting agent, I guess is the other way you could think about it.
- 6:01Can I ask a question?
- 6:02Why is it not the Azure Copilot SRE agent?
- 6:05Why is it the Azure SRE agent and the Azure Copilot troubleshooting agent?
- 6:09I feel like there's some naming mismatch there.
- 6:11I think somebody, you know, just had to think about ways to break them up.
- 6:17So I don't know if this is the right mental model, but I'll give you a little bit of my mental model for these two things.
- 6:23Okay.
- 6:24My mental model for Azure SRE agent and the Azure Copilot troubleshooting agent is you can think of the troubleshooting agent as the free version of the SRE agent.
- 6:43So there's a set of capabilities that kind of exist across both of them.
- 6:47But the thing you have to keep in mind is with the, and I hate to get into licensing already, but with the Azure SRE agent, it is a consumption-based offering.
- 6:58So it's paid versus the troubleshooting agent, which is effectively your lowest friction entry point, no additional cost.
- 7:07You know, you can just walk right in the front door kind of thing along the way.
- 7:10So you've got this simple troubleshooter native built into experiences like the Azure portal.
- 7:17It's ready to go for you.
- 7:20Or you've got this other thing, SRE agent, which kind of does the same things the troubleshooting agent does, but it actually does more than them.
- 7:28So it's, like I said, it's consumption-based.
- 7:31It's a paid platform.
- 7:32It's an operational platform.
- 7:35So where the troubleshooting agent is coming in and that's just you asking a question like,
- 7:39hey, I think this network security group rule, this NSG rule is broken, can you help me fix it?
- 7:46Versus SRE agent being more like operational platform side of things.
- 7:51It's got its own managed identity, its own operational context.
- 7:56It can run CLI in human-in-the-loop, basically like a review mode, or it can go fully autonomous for you.
- 8:04So it's these degrees of maturity along the way.
- 8:07I don't know why they couldn't just call it all SRE agent and find a way to bundle that experience.
- 8:13Like that is kind of weird and bifurcated today.
- 8:17And even from the point of where I started putting the note together for this one a couple weeks ago,
- 8:22a month, two months ago, whenever it was, the experience has changed.
- 8:27Like SRE agents started in the Azure portal and now it's got its own website and its own experience.
- 8:33We should probably talk about this at some point too, how product groups are moving away from the Azure portal
- 8:39as their grounding experience for their Azure products.
- 8:43That's kind of a weird one to me too.
- 8:44But yeah, you basically have these two agents.
- 8:47They're named two different things, but my mental model is they're all kind of the same thing.
- 8:53You're basically looking at here's a set of free capabilities versus here's a set of metered or paid capabilities.
- 8:59Does that help?
- 9:00That helps.
- 9:01It almost looks like, too, as I was looking at this, that the SRE agent, and you can correct me if I'm wrong,
- 9:10it looks like it pulls in more context than troubleshooting.
- 9:14Like troubleshooting is relatively basic.
- 9:18Like you said, go look at this firewall and figure out what's wrong with my network path or something like that,
- 9:24where the SRE agent is looking at diagnostic logging, and it can look at log analytics, and it can look at Defender.
- 9:31And it's pulling in a lot more of your context to give you a much more, I would say like a much more holistic or complete using a much broader set of data than maybe this troubleshooting agent is.
- 9:45I don't know if this analogy lands or this way of framing it either.
- 9:49One is the troubleshooting agent, the Azure Copilot troubleshooting agent.
- 9:54I would argue that's the more reactive one.
- 9:57That's like there to help you solve something point in time when it goes wrong.
- 10:02So very human in the loop, like I'm going to use this as an extension of me kind of thing.
- 10:07It doesn't even have its own identity.
- 10:08Its identity is you.
- 10:10So that Azure troubleshooting agent can help you solve a case.
- 10:14I have this point in time issue, and I want to go solve this.
- 10:17Can it help you do that?
- 10:19Yes.
- 10:19The other side of that is the Azure SRE agent.
- 10:23And like you said, it can be autonomous, and it knows more about your environment just based on the context and the permissions and having its own identity and things.
- 10:32So versus troubleshooting agent where I'm saying, hey, this is an extension of me.
- 10:39Azure SRE agent is an extension of your team, right?
- 10:42It's another identity that's out there.
- 10:43So one is being reactive, help me solve this case, or help me solve this problem right now.
- 10:49The other one is, it's just an operator.
- 10:51It's a member of your team.
- 10:54Granted, it's a member of your team who is on a spectrum of autonomy, like how much you grant it and what you give it and what you trust it with.
- 11:02So there's definitely a whole trust angle and trust boundary thing that comes into play there.
- 11:08But arguably, like the latter, the Azure SRE agent, far more actually an agent than the troubleshooting agent, which is more, I guess, akin to a skill, right?
- 11:19I'm going to go fire this thing up point in time.
- 11:21It's got some grounded knowledge about Azure.
- 11:23It knows how to, in context of me, go look at an NSG rule, a firewall rule, something like that.
- 11:31So again, it's all on the spectrum.
- 11:34It'd be way easier if they just named it Azure SRE agent.
- 11:38And you said, here's Azure SRE agent and the set of clearly human in the loop capabilities.
- 11:44And here's Azure SRE agent, the autonomous side of things, rather than having to say troubleshooting agent and SRE agent when it's all very much kind of in the same vein.
- 11:55Yeah.
- 11:56And the troubleshooting agent to get started with that is super simple, too.
- 12:00Like you said, you just go into Azure.
- 12:01You can open up Copilot there in the upper menu bar by your search.
- 12:06And troubleshooting agent just shows up there, pop it open, and just start chatting with it.
- 12:11And it gives you a few sample prompts, can't connect to my virtual machine, help me understand this Azure error, what could be causing performance issues.
- 12:20Like that's really all there is to it.
- 12:23Versus like you said, the SRE agent has an entirely separate site now, but also a significantly, there's a little bit more to do to get it set up and things to pay for.
- 12:35There is.
- 12:36I mean, it's like any other fully agentic thing.
- 12:39It's got its own identity, and that means you have to onboard it basically like you would onboard a person.
- 12:45You're going to go and give it a set of permissions and capabilities within your environment, all that good stuff.
- 12:51Oh, and you can create agents within the SRE agent.
- 12:55Or is it, no, it's just creating my first SRE agent.
- 12:58So I have not gone through the onboarding yet.
- 13:00So I just went to the website, and I can get my 30-day trial at sre.azure.com.
- 13:06And then it's create my first Azure SRE agent.
- 13:10Another weird one.
- 13:11Like I said, you're into this operational flow of, I'm going to start in the portal, and it's immediately going to kick me out to another place.
- 13:18And it looks like I can create multiple SRE agents, which I guess makes sense because you're going in and connecting them to different data sources.
- 13:27You can put them in different subscriptions for different billing models because it is the pay-per-go.
- 13:33If you've played with security Copilot, like this is very security Copilot feeling with opening a new portal and having billing and then going in and doing all the configuration within that separate portal, where Azure is really just a way to bill based on usage more so than anything else.
- 13:54Yeah, so I think from the thing, like you said, it's like other agents that are out there.
- 14:00I think that experience is fairly consistent.
- 14:02You have to give these things an identity.
- 14:04There is a consumption model there for billing, so you've got to go bootstrap it and stand all that up.
- 14:10And as you're doing that, like I said, you should think about how you bootstrap these things as bootstrapping members of your team.
- 14:16So in your case, if you were going to onboard a new contractor, effectively that Azure SRE agent, it's a new contractor for you to come in and take a look at your environment and be an extension of you and the things you do.
- 14:32So have you looked at, because this always gets me with these, the pricing and billing for these yet.
- 14:39I was looking at it a little bit.
- 14:42And again, I'm going to draw parallels to security Copilot because that's what I've used.
- 14:46Where security Copilot, we had security compute units that were what you paid for that were always on, SCUs.
- 14:54The Azure SRE agent uses AAUs or Azure agent units, which is a standardized measure of agentic processing used across all pre-built Azure agents, except for apparently security Copilot.
- 15:10Well, is security Copilot an Azure agent, or is it a security Copilot agent, or is it part of Defender?
- 15:17That's not even what defines an agent.
- 15:19That's just like what org ships this thing.
- 15:22Yeah.
- 15:22Which part of the world, yeah, which part of the org, like I said, is the thing that pushes this one through.
- 15:29Yes.
- 15:30So we do have a new measure of agentic processing, and then it goes through all of these.
- 15:41I mean, I looked at this.
- 15:43I don't even know how you'd start pricing something like this out.
- 15:48Like, there's scenarios on here for quick questions, and then you have input tokens and output tokens and cash read, cash write.
- 15:56Whether you're using Claude Opus or GPT, a whole bunch of math that at the end of the day, it feels like they say just spin it up and monitor your cost.
- 16:10And that's how you price this out is you start seeing how much something costs you.
- 16:15Because they don't even, I don't even see dollar amounts on here.
- 16:18They just give you guidelines of like how many tokens each of these are going to take and what your billing impact is, how to set spending limits, how to monitor your usage.
- 16:32But there is not a single dollar amount on the entire pricing and billing page.
- 16:37No, this is definitely one of those that you need to go and kind of POC.
- 16:44So you've got to get out there and say, okay, hey, I'm going to run this through a couple of workflows and see what it does.
- 16:52And it's kind of a crappy answer, but I think it is part of the state we're at, too.
- 16:57Like, it's very hard to predict when you stand these things up.
- 17:00Number of input tokens, number of output tokens, things like that.
- 17:04Especially considering like the models that you can run behind them between things like Opus and GPT and things like that.
- 17:13Because you might have a, given your environment, a better experience even with one model over another.
- 17:19Just based on like the grounded system prompts and things that are out there.
- 17:22So it is kind of pay-per-use, input tokens, output tokens, and a little harder to figure out in that world.
- 17:32So you've got to go kind of POC it and see if it's there.
- 17:36Arguably not for everybody.
- 17:38Like, if you're looking for the, I know this thing is going to cost me $30 a month and it's going to be fixed costs.
- 17:44Like, this just wouldn't be the offering for you.
- 17:46I would also argue that that's kind of hard to find these days.
- 17:50That doesn't exist.
- 17:52I even see, like we talked about this a while ago, too, right?
- 17:54The shift in kind of like billing and consulting and things like that.
- 17:58Like, folks bill around outcomes, not necessarily hours.
- 18:02So, you know, how much does it cost you to get to that outcome is a variable thing depending on the issue that you're trying to solve for.
- 18:08Scott, while you were talking about that, I did go just type into Claude.
- 18:14Don't tell anybody.
- 18:15I just asked how much an AAU is for the Azure SRE agent and it did give back some numbers.
- 18:22So again, precursor, this is just Claude spitting it back at me.
- 18:26Was that it's $0.10 per AAU pay-as-you-go rates.
- 18:33Microsoft, similar to Security Copilot, recommends four AAUs, so $0.40 per hour, just base cost to have it up and running.
- 18:41It's $0.10 per agent per month, which works out to about $300 per agent per month, just to sit there.
- 18:49So this is not actually doing any work.
- 18:51This is like that based cost of sitting there.
- 18:55But then, I mean, expensive, maybe?
- 18:59I mean, you compare what you pay for Claude and some of that.
- 19:02Like it's not, that is not the obscene cost to me that like Security Copilot was.
- 19:08Security Copilot was a little over the top.
- 19:09This feels attainable by most organizations.
- 19:14I think given some of the things it does, especially, so the way Microsoft describes some of these things,
- 19:22like they'll walk you through where they sit on that spectrum and what they do, right?
- 19:26So I think troubleshooting Copilot, or sorry, Azure Copilot troubleshooting agent,
- 19:31like ACTA, you know, needs a, has a pretty definitive workflow for it.
- 19:38So I have a problem, I'm a human operator, I step in, I describe my problem.
- 19:43That problem's going to be within a given scope.
- 19:45Typically a resource, but it could be at a higher level, like a resource group or subscription.
- 19:50So that's what I mean.
- 19:51When I say scope there, it's going to diagnose at whatever scope it has access to.
- 19:56It'll recommend a fix.
- 19:57And if a fix can't be recommended, it'll let you escalate it and create a support request.
- 20:04Like, fairly simple, straightforward, covers, you know, VMs, VM scale sets, AKS, all that kind of stuff is there.
- 20:14The SRE agent, like, way richer than that.
- 20:18So rather than me coming in and saying, hey, I'm trying to solve a case,
- 20:22it's kind of out there always looking, or it can be always looking.
- 20:26So that means it can look at things like, you mentioned diagnostic logs.
- 20:30Like, Azure Monitor Resource Logs, Diagnostic Logs, App Insights.
- 20:34If you have Log Analytics spun up, it can run Kusto queries for you against that Log Analytics workspace.
- 20:41It's integrated with Azure Monitor Alerts, all those kinds of things.
- 20:45It can also monitor GitHub repos or Azure DevOps repos.
- 20:50So that's interesting.
- 20:51If you think about, like, N10, CI, CD, and having this agent be able to, like, troubleshoot
- 20:56as you're doing deployments, things like that, it can step in and do things like that along the way.
- 21:02And then, you know, it's got all sorts of, like, lifecycle hooks and other things that are there.
- 21:08So in that vein of, like, it does more, to your point of $300,
- 21:12like, how much do you pay an MSP to come in and have some level of access to your environment?
- 21:20Most folks are paying more than $300 for, you know, a full MSP to be sitting there, kind of ready to go.
- 21:28So that ROI could be there if it can kind of inflict some of the value that you're looking for within your organization.
- 21:38Absolutely.
- 21:38And I was looking at some of this pricing.
- 21:40This pulled up from a third-party article, too, that compares a whole bunch of different SRE agents.
- 21:45So take some of that pricing stuff with a grain of salt, because it was not pulling all from 100%.
- 21:52If you're managing file storage today, you've probably felt the pressure.
- 21:58Refresh cycles are harder to plan.
- 22:00Costs and complexity are increasing, especially as file workloads scale across regions.
- 22:05That's why Microsoft customers trust Nasuni.
- 22:08As an Azure-certified software, Nasuni provides a global file system designed for enterprise-scale environments,
- 22:15keeping file data secure, governed, and accessible across Azure environments without added infrastructure complexity.
- 22:22It's the foundation to keep your unstructured data stable, even as your infrastructure evolves.
- 22:28To see how much you could save while keeping your initiatives on track, visit nasuni.com slash TCO.
- 22:36That's N-A-S-U-N-I dot com slash TCO.
- 22:41No, this is...
- 22:43I'm with you.
- 22:44That pricing is relatively inexpensive.
- 22:48It feels like it can do a lot and...
- 22:50On one hand, it sounds expensive when you say it.
- 22:52On the other, it's actually like really aggressive when you talk about potentially tearing down a whole industry that sits behind it,
- 22:59should these things take off in the way that they're being positioned.
- 23:03It's a double-edged sword, right?
- 23:05The agent doth come for us all.
- 23:08It'll also be interesting to see what this will do.
- 23:10I would be interested to spin this up, and I may end up doing this for a month or two in my tenant,
- 23:17because it does...
- 23:18To your point, it talks about...
- 23:21You're looking at things like diagnostic logs, like at Log Analytics.
- 23:24It talks in the Microsoft articles about incident response plans or other automated triggers.
- 23:29How close can you get to even some of the security Copilot stuff with the SRE agent in terms of...
- 23:36If it's just Azure you're talking about, I think you can get darn close,
- 23:39because you can even inject your own custom skills and things like that in there.
- 23:44So it can run Azure CLI.
- 23:47It can execute Python scripts.
- 23:49It's all like, what level of things do you give to it?
- 23:52So it'd be interesting to maybe take a step back.
- 23:56I'd have to go look at and run it through.
- 23:58I was certainly doing it for this one.
- 24:00But one of the things that I find helpful is when you're trying to compare these things,
- 24:03like they all sit on a spectrum, is just what's the operating model for them?
- 24:08Or what's the boundary of the operating model?
- 24:10So we talked about the troubleshooting agent is really trigger,
- 24:15what scope am I at, diagnose, resolve, and if it's not resolved, escalate.
- 24:21It's simple, right?
- 24:22Five steps that are there.
- 24:24The Azure SRE agent can do the observability part.
- 24:27So rather than trigger, it's observe.
- 24:30So I'm not triggering it, it's out there observing for me.
- 24:33It can correlate, it can hypothesize, which is another interesting thing,
- 24:37like that's a different mental model.
- 24:39And then it can propose, or it can execute, or it can do both,
- 24:42depending on what you've chosen to do.
- 24:44It can actually verify what it did,
- 24:46and then it retains that context for the next time.
- 24:49So should that issue or that particular thing crop up again,
- 24:53it knows, knows, big air quotes, it knows.
- 24:57But it can at least go back and re-eval in context and get it going.
- 25:01So you think about that operating model of observe, correlate,
- 25:04hypothesize, verify, retain context,
- 25:07like, yeah, the security agent was kind of there.
- 25:11The perception stuff was totally different, right?
- 25:13That was a mix of agents that were coming through and kind of running up.
- 25:18So then maybe the other thing to think about is,
- 25:20could you wire all this up yourself?
- 25:22Sure.
- 25:23Like, this is a set of connectors, right?
- 25:24It's MCPs and CLIs,
- 25:27and at the end of the day, it's skills that are being composed as an agent,
- 25:31and kind of an agent in a box to you as a consumer of it.
- 25:35Could you build all that yourself?
- 25:36Sure.
- 25:37How long would it take you?
- 25:38Like, how many tokens would you burn to get there?
- 25:40Maybe you can do it for, let's say, $100,
- 25:44but then you run it.
- 25:47Does it only cost you $300 a month to run?
- 25:49Or does it cost you more than that?
- 25:51It all depends.
- 25:52It's very hard and very fuzzy to figure out.
- 25:56But if you're like, I don't think Azure SRE agent is the type of thing that's there for,
- 26:03you know, you have a super well-known, super constrained workload.
- 26:08Like, it's all on Rails.
- 26:09And I think for a lot of that stuff, the troubleshooting agent's fine, right?
- 26:13You stand it up, you deploy it, infrastructure is code,
- 26:16you know what all your firewall rules and NSG rules
- 26:19and your VMSS configuration and everything is from the start.
- 26:23So you just fire that out.
- 26:25It's there for when something probably more goes wrong on the Azure side
- 26:29than on your side kind of things.
- 26:31Versus the other, I think the Azure SRE agent would be way better fit
- 26:35for like a mixed environment.
- 26:36I run lots of workloads in here.
- 26:39I have multiple teams doing deployments.
- 26:41They all need to kind of live within the same boundary,
- 26:43but that boundary is a little fuzzy sometimes, right?
- 26:46When I say like, hey, go ahead and deploy into my fully governed
- 26:49landing zone subscription over here.
- 26:52And it's got its own set of constraints that come with it.
- 26:56That can be a little bit harder for teams to kind of figure out
- 27:00and stand up and get going.
- 27:02Even the fact that the troubleshooting agent,
- 27:05and they highlight it in some of the documentation,
- 27:07is one of the secondary steps of the troubleshooting agent
- 27:10is it can go open a support ticket for you.
- 27:13Troubleshooting agent is a little bit more like that first line of,
- 27:17it's almost like a first line of tech support,
- 27:20kind of like you said with SRE, it's much more operationalized,
- 27:24a member of your team, that type of thing,
- 27:28which is probably it's going to use more compute.
- 27:31That's why you're going to pay for it more.
- 27:32But I mean, let's be honest,
- 27:33the troubleshooting agent probably is going to help Microsoft
- 27:36lessen the number of support tickets that come in as their hope,
- 27:40because it's able to help people solve issues, yes,
- 27:43before that support ticket hits a Microsoft support desk.
- 27:48I mean, at the end of the day, it boils down to
- 27:50ad hoc troubleshooting, troubleshooting agent,
- 27:53versus repeatable incident response SRE agent.
- 27:58You know, you got to kind of like pick the mental model
- 28:00that works for your org,
- 28:01and what you're trying to solve for along the way.
- 28:05You do have these kind of options that sit in front of you.
- 28:09Very cool.
- 28:10I was looking through more of the connecting sources
- 28:13and spinning up agents and onboarding teams into it.
- 28:18There's a whole bunch in there that it can do.
- 28:20There's a bunch of learned documentation
- 28:22that we'll have links to in the show notes as well for,
- 28:25here's how you even go start setting up this SRE agent.
- 28:29Again, very similar to how you would set up security Copilot,
- 28:35that type of thing in terms of connecting data sources
- 28:37and setting up activities and skills,
- 28:40and you can connect MCP servers to it and all of that.
- 28:43It would be interesting to me,
- 28:45I'm going to harp on this over and over again, Scott,
- 28:47if they could consolidate these.
- 28:49Like, I don't want,
- 28:50if I'm a large organization running security Copilot,
- 28:53I want to run the Azure SRE agent.
- 28:56I can see an argument
- 28:57for not having this stuff in the Azure portal,
- 29:00for having a separate agent
- 29:03or a separate AI website
- 29:06where all these things are.
- 29:08I don't want 10 different websites
- 29:10where all these things are.
- 29:12I want, like,
- 29:13whether it's,
- 29:14you can somehow fold all this into copilot.microsoft,
- 29:17or you can have agents.microsoft,
- 29:20something like that
- 29:21where me as a end user can go
- 29:25and I can go connect
- 29:30to these different agents,
- 29:32have these different skills.
- 29:34Wouldn't it be great
- 29:35if it was just part of, like,
- 29:36maybe, like,
- 29:36that whole agent 365 thing or something, right?
- 29:39Like, single pane of glass,
- 29:41here's all my agents,
- 29:42here's what they do,
- 29:43all that, yeah.
- 29:44Welcome to,
- 29:45at some point,
- 29:46you're always going to see
- 29:47somebody ships the org.
- 29:50And, hey,
- 29:51here's the org chart
- 29:53manifesting out in the real world.
- 29:56100%.
- 29:56What is going on here?
- 29:58We'll see.
- 29:58Azure just had a big reorg last week,
- 30:01so now it's all under one banner.
- 30:03One banner?
- 30:03I've started seeing emails, too,
- 30:05about my pricing changing in Azure.
- 30:07Your pricing?
- 30:08My pricing.
- 30:09That's another topic
- 30:10we can talk about another day.
- 30:11Speaking of Azure,
- 30:12I just popped up
- 30:13because you said Azure reorg,
- 30:15and I was like,
- 30:15Azure reorg and
- 30:17Azure pricing
- 30:18and
- 30:19all the Azure things.
- 30:21Yeah, another topic.
- 30:22Another day.
- 30:23There was some new Copilot stuff
- 30:25and OneDrive stuff.
- 30:26Oh, yeah,
- 30:26we have more topics we can talk about.
- 30:28I'm not going to make any promises.
- 30:29Yeah, more topics.
- 30:30But we should close this one out.
- 30:31So, let's see,
- 30:32what else with this thing?
- 30:33So, SRE agent,
- 30:35much richer,
- 30:36even if you're not going to deploy these things.
- 30:38So, to your point of,
- 30:39could you build the skill yourself
- 30:41and could you run it and do it?
- 30:43Absolutely.
- 30:44I do think it's helpful
- 30:45to look at how Microsoft
- 30:47or even AWS GCP
- 30:49as they do their agents
- 30:51for their clouds kind of thing manifest
- 30:53is what are the permissions
- 30:55that come with them?
- 30:56What can they do?
- 30:57What can they not do?
- 30:59So, if you look at Azure SRE agent,
- 31:01it's got some interesting guardrails.
- 31:02It can't delete or remove anything
- 31:04just out of the gate.
- 31:06That's all blocked.
- 31:07It can't get at your key faults.
- 31:09All those commands are blocked.
- 31:11So, when I'm saying blocked,
- 31:12they're blocked in the CLI.
- 31:14Agent can totally figure out
- 31:15how to run a REST request
- 31:17if you want it to kind of thing.
- 31:18But at least from the CLI that's integrated,
- 31:21delete and remove blocked,
- 31:22easy key vault blocked,
- 31:24respects your management locks
- 31:25or your resource locks.
- 31:28So, hey, this resource group
- 31:29has a do not delete lock on it
- 31:31kind of thing.
- 31:32It'll validate your subscription IDs.
- 31:35It always logs all the actions
- 31:38and results of CLI things it takes.
- 31:41So, even if they said,
- 31:42even if you're not going to use it,
- 31:43you're going to go build your own skill,
- 31:44it'd be great to pump these rule sets
- 31:46into your own things, right?
- 31:47Give them a little bit of guardrail
- 31:49and make them a little bit more
- 31:51constrained out of the gate.
- 31:53Oh, this is interesting too,
- 31:54even with VNets.
- 31:56Operations agents that cannot reach
- 31:57private resources.
- 31:59VNets are another weird one.
- 32:00So, that was like an extra capability
- 32:02that came.
- 32:03That is,
- 32:03because it looks like the SRE agent
- 32:04can always limit it to only
- 32:06public management plane signals.
- 32:08It can't go through private resources
- 32:11or private things that are just
- 32:13private links on a VNet.
- 32:15I'm reading that right?
- 32:16Which is funny,
- 32:17because depending on a resource,
- 32:20I'm colored because I live in storage land.
- 32:23So, a storage account is never really private
- 32:25until you go into the firewall
- 32:26and crank it down.
- 32:27It's always got a public endpoint,
- 32:29even if you stand up a PE on it.
- 32:31And there are other resources
- 32:32out there like that too.
- 32:33So, yeah.
- 32:34So, the VNet stuff was an add-on.
- 32:37It was like a GA after GA capability,
- 32:41I guess, that came to things.
- 32:43So, by default, yes,
- 32:44it does look to just the
- 32:46public management plane
- 32:48or control plane signals
- 32:49from Azure Resource Manager.
- 32:51And with this VNet integration,
- 32:53you can start to bring it into VNet mode.
- 32:57And then it can reach your private endpoints.
- 33:00And it can even reach out
- 33:02to on-premises systems.
- 33:05So, if you're hooked up
- 33:06through like a site-to-site VPN
- 33:08or ExpressRoute
- 33:09and your policies and routing
- 33:12allow for that,
- 33:14you can get going
- 33:15with some of that stuff.
- 33:16It does require,
- 33:17it does have some own networking requirements
- 33:19on its own side.
- 33:20Maybe similar to like Bastion
- 33:22when you stand that up.
- 33:23Like, it needs its own network segment
- 33:25to stand in.
- 33:26So, you need a slash 27
- 33:28or larger subnet
- 33:30that you can delegate out there.
- 33:33Subnet has to be in the same region
- 33:34as the agent that's out there.
- 33:37It's also egress only.
- 33:39So, the agent talks out,
- 33:41but you can't do some kind of like
- 33:43private inbound connectivity
- 33:45from that VNet
- 33:46to that agent kind of thing.
- 33:49But it lets you do some,
- 33:50the biggest thing for me
- 33:51would be like internal package repos
- 33:54or like private package repos.
- 33:56So, lots of orgs block
- 33:58like public NPM.
- 34:00You might publish
- 34:00like NPM packages
- 34:01that are vetted.
- 34:02Same thing with like PyPy.
- 34:04You know, Python being so popular
- 34:05with these agents.
- 34:06You don't want like a weird
- 34:07like man in the middle
- 34:08or like supply chain attacks.
- 34:10So, you might have
- 34:10your own PyPy registries,
- 34:12things like that
- 34:13that are there.
- 34:14So, it lets you kind of
- 34:15navigate that entire system
- 34:17on the network side of things.
- 34:19Ooh, that's another topic, Scott.
- 34:21Add this one to the list.
- 34:22Supply chain attacks
- 34:23in Microsoft 365.
- 34:26Did you see the news
- 34:27last week about that?
- 34:28Different topic.
- 34:28We're not going to talk about it here.
- 34:29I did not.
- 34:30We should talk about this here
- 34:31on a future episode.
- 34:33For now,
- 34:34we can wrap this one up.
- 34:35I like that we're coming up
- 34:35with ideas.
- 34:36So, folks should go
- 34:37check these out.
- 34:38I think, like I said,
- 34:39the low-hanging fruit
- 34:41of getting started
- 34:42with this stuff
- 34:43is that Azure Copilot
- 34:44troubleshooting agent.
- 34:45It's kind of like
- 34:46a no harm, no foul.
- 34:47It's there for you.
- 34:48It's in the portal
- 34:49for everybody.
- 34:50You might want to try it out
- 34:51because if it helps, it helps.
- 34:52And if it can deflect
- 34:53a support ticket,
- 34:54that saves you money.
- 34:56So, good.
- 34:57I would say go try
- 34:58out the SRE1 too.
- 34:59Like, again,
- 35:00300 bikes for a month.
- 35:01If you don't even
- 35:02spin it up for a month,
- 35:03like, this is one of those.
- 35:04It does have a trial
- 35:05that you can get started with.
- 35:07I have a 30-day trial,
- 35:09but you can also,
- 35:10similar,
- 35:11I've done this with
- 35:12Security Copilot,
- 35:12which is why I'm bringing it up.
- 35:13You can go spin it up
- 35:14because you're spinning up
- 35:15these AAUs
- 35:16and even try it
- 35:17for two or three days.
- 35:19And then just delete it.
- 35:20Like, it's a resource
- 35:21that you can just
- 35:21create and delete.
- 35:23If you want to try it out
- 35:23for two or three days,
- 35:25it costs you,
- 35:26what,
- 35:2710 or 20 bucks
- 35:27to try it out
- 35:28for a couple days.
- 35:29See how you might be able
- 35:30to use it
- 35:31in your own environment
- 35:31and let us know
- 35:33if you've used it,
- 35:34what your experience
- 35:35has been with
- 35:35the SRE agent.
- 35:37Absolutely.
- 35:38With that,
- 35:38are we going to go
- 35:39attack our days
- 35:41or let agents
- 35:42attack our day for us?
- 35:43We're going to do something.
- 35:44Do something like that.
- 35:45All right.
- 35:46Well,
- 35:47thanks again,
- 35:48everybody.
- 35:48Again,
- 35:49let us know SRE agents,
- 35:50LinkedIn,
- 35:52probably the best way
- 35:53to let us know
- 35:54how you're using these,
- 35:55how you want to try them out.
- 35:58And Scott,
- 35:59if people are going
- 36:00to be in Dallas,
- 36:00I'll be in Dallas
- 36:01the beginning of November
- 36:02for M365 conference
- 36:04down in Dallas.
- 36:06And I'll be out
- 36:07in Scottsdale
- 36:08in January
- 36:08for the
- 36:09Workplace Ninjas conference.
- 36:11Back to some
- 36:12IT Pro cloud show
- 36:13on the road.
- 36:14Oh,
- 36:15folks should go
- 36:15check that out.
- 36:16Those were all posted
- 36:17up on LinkedIn
- 36:18and things like that.
- 36:19We'd love to get
- 36:20your feedback there
- 36:22as Ben's out
- 36:23traveling the country.
- 36:24Do you want to see
- 36:25more live streams
- 36:27when Ben's
- 36:29running around
- 36:29our defense?
- 36:30He did get that nice
- 36:31board behind him
- 36:33printed up.
- 36:34Yeah.
- 36:34Yes.
- 36:35I have to think
- 36:35Jay Leask did most
- 36:37of the work on that one.
- 36:38That was a
- 36:39Jay Leask initiative,
- 36:41but it did turn out nice.
- 36:43We had fun with that.
- 36:43Jay and I were at
- 36:44that conference
- 36:45in Branson
- 36:46last week
- 36:46and did a whole bunch
- 36:47of interviews.
- 36:48I might try to do
- 36:49some of those in Dallas.
- 36:51Jay and I will be doing
- 36:51it again in Scottsdale.
- 36:53So like you said,
- 36:54Scott,
- 36:55go check those videos
- 36:55out on YouTube.
- 36:56Let us know
- 36:56what you want to hear.
- 36:57And then Scott,
- 36:58we need to get you
- 36:59at a conference.
- 36:59Maybe,
- 37:00I don't know where.
- 37:02We got to get to a conference.
- 37:03We got to get you
- 37:04to a conference.
- 37:05The problem,
- 37:06yeah,
- 37:07what I've hit.
- 37:07I think I might submit
- 37:08for one of the
- 37:10live 360 events
- 37:11in August.
- 37:13They're going to be
- 37:13in Redmond,
- 37:14so it's an interesting
- 37:14way for me to get
- 37:15out to campus.
- 37:17Maybe I'll see
- 37:18if I can pitch
- 37:19a couple sessions
- 37:20around Azure
- 37:21storage development
- 37:22or something like that.
- 37:24Yeah,
- 37:24we'll figure out
- 37:25one of these
- 37:26conferences.
- 37:27Yeah,
- 37:28we'll figure one out,
- 37:29Scott,
- 37:29so you and I can do it
- 37:30with a fancy banner
- 37:31behind us.
- 37:32Yeah,
- 37:32we'll just have to run
- 37:33one here in Jacksonville.
- 37:34We'll have everybody
- 37:34come to us.
- 37:35We can just do a live,
- 37:36our own live.
- 37:38All right.
- 37:38All right.
- 37:38Well,
- 37:39thanks for chatting
- 37:39agents with me today.
- 37:41I know it's more
- 37:42AI beat down,
- 37:43but it's what's
- 37:44in front of us.
- 37:45It's what's out there now.
- 37:47Yes,
- 37:47absolutely.
- 37:48You're welcome.
- 37:48Enjoy your week
- 37:49and we'll talk to you later.
- 37:50Thanks, Ben.
- 37:52If you enjoyed the podcast,
- 37:54go leave us a five-star
- 37:55rating in iTunes.
- 37:56It helps to get the word out
- 37:58so more IT pros
- 37:59can learn about
- 38:00Office 365 and Azure.
- 38:02If you have any questions
- 38:03you want us to address
- 38:04on the show
- 38:05or feedback about the show,
- 38:07feel free to reach out
- 38:08via our website,
- 38:09Twitter,
- 38:10or Facebook.
- 38:11Thanks again for listening
- 38:12and have a great day.