Hey friends! Azure App Service offers more than 60 troubleshooting tools for diagnosing different types of issues. But where do you start? Now you can ask Microsoft Copilot for Azure about the problem you're experiencing, and you'll get diagnostics and help resolving your issue. Hanna Endrias is here to show me how it works today on Azure Friday. Hey friends, it's Azure Friday. I'm here with Hanna from the Azure Developer Experience team, and we've got a really cool exclusive right now. At the time of the recording of this video, Azure Copilot experience was actually in public preview. It's a limited preview, so if you go ahead and share your screen, there's an AKA link that folks can visit. We'll have it in the show notes as well. You can sign up and you can request access to Microsoft Copilot for Azure. Hanna, this is pretty cool stuff. So we've got you set up with a to show us in an inside preview of this Copilot for Azure. Yeah, I'm really excited to talk about it. I think one way to take advantage of Azure Copilot is to use to actually troubleshoot and solve your issues. So, I'll show you how how that might actually look like. First, let's show you an unhealthy resource. We can see here that my resources unhealthy as it's experiencing, internal server error. And, you know, if you're a power user, you might actually be aware that we have built in diagnostics located in the diagnose and solve blade right here on the left. these are diagnostics that our team has worked really hard to curate, and has kind of organized in very specific ways. So we have them under these tiles and if you click on it, then it can help you figure out which, you know, problem areas to investigate. So this is definitely one approach, one valuable approach to take to troubleshooting your issues. And obviously we will still recommend it, but with the Azure Copilot experience, it's located at the top over here where you can actually do is type in your problem. So in my scenario, I can say my web app is down right. It'll take a minute to process, you know what, I've provided it and actually direct this to the appropriate diagnostics tool. And so like Scott had mentioned earlier, we have more than 60 tools, diagnostic pages that you could explore. So it's, exploring, you know, every single branch, this kind of directs you to the right, tooling. And does it look at, like, what kind of things does it know? Because, like, I might have dozens of sites and, you know, in that case it's recommending a tool for you. But does it know what blade you're on and how much context does it have about what's currently happening? Yeah. So to actually get to this experience, I'm going to open up the web app down to what is the appropriate tool for this scenario. if you happen to be in the overview page, it'll ask you what resource you want to investigate. certain Copilot experiences are blade specific. but this one can, you can open up from anywhere. Pretty much. Cool. Yeah. This one got you directly in there, right? So I didn't have to check all of the other wonderful tools that we've built. I've actually gotten to the one related to my web app being down. and I'll kind of break down how we go about designing our troubleshooting experiences. we try to be very thoughtful about the visualization and the information that's presented to you. So to even just get started with this graph here, you can actually notice that what it's saying is that Azure is pretty healthy. The platform itself, but our, our resource has actually been going up and down in regards to its availability. So we definitely need to take a look at it. the other way that the other piece of how we're structuring these pages is that we try to surface the most important, troubleshooting information at the top. So we'll have it organized in the observations and solutions. These, issues will often be expanded, whereas these other 17 healthy, troubleshooting avenues will be collapsed and at the bottom. So, you know, traditionally without this information, you might have to investigate all these other 17 relevant troubleshooting, avenues. But now with this tool, you're actually able to just focus on the top five. So that's what makes it, that's what makes taking advantage of diagnose and solve really powerful. Yeah. You know, one of the things that I think is cool is that and this is my opinion, speaking not as a Microsoft person, but just as a as a person that uses Azure, is that there's a lot of really awesome stuff that's kind of in the portal that maybe people aren't aware of, right? And you have to know that they exist. Right? So there's 60 plus different diagnostic tools. And, you know, you could search for them. You can go and Google with Bing for stuff, but but you could dig around in the UI. But in this case here you got the right diagnostic tool because you use natural language within the Microsoft Copilot experience. And then it's surfaced stuff that you may not have already know that you may not have known this existed, right? Right. But you don't want to bury your tools. You want them to be upfront. It got you the right tool at the right moment for the right job, which I think is really cool. Yeah. You really captured, you know, what we're trying to do with our Azure Copilot experience. so I'll dive right into it. You know, we have, a website to get up and running again. So if I take a look at just this first error, the HP server errors, I can see that it's saying that there's something wrong with my application code or the platform serving the requests. And it's saying that maybe I should take a look at our web.config. for this application. So in order to access that, I will go back to the overview page for my resource. And. Let's go back to. And I can actually type in Q2. this is a trick here. This is a good secret trick. So Kudu is a code name. So you got to the device diagnostic advanced tools by using the classic code name Kudu. Yep. and with Kuda, you're going to be able to essentially get to, this page here. and from here, to get to my web.config file, I'll need to go to the debug console. There's a couple other tabs that you should definitely take some time to explore, but just for troubleshooting, I'll focus. That's where we need to go. We'll go to the sites and then we'll go to WW dot root under here I found the web.config file. So I'll just zoom in a little bit. Make sure you guys can see it. Thank you. We'll take a quick look at our web.config file and see if anything stands out to us. Oh, and then I noticed I actually did not close out my configuration tag. So let's try doing that and let's go back up to save these changes. Isn't that always the way it's either XML or DNS? Always something small. So let's try refreshing this page and hopefully we'll get to see our puppy adoption website up and running. Making a change to a web.config causes a complete reset. A reboot of your application. So it takes a second. And here you go. Here we are getting to enjoy these cute little puppies. so our website is thankfully up and running. So this is one way you can actually use, you know, Azure Copilot to troubleshoot your problems today. another way that you can take advantage of are, oh. Let me explain this out. Take advantage of, the Azure Copilot experience is by seeing what you could do to be proactive about, your resources health. So I might type in, best practices for my app. And so this is actually going to provide you with some of the diagnostic tools that we use, and recommendations that we've kind of come up with over the years to keep your app running as healthy as possible. Yeah. I think one of the cool things about this is that what is the difference, you know, between, you know, searching the web for something and using a Copilot. And the difference is context. And because you're logged in and inside of the the Azure portal, it knows things and it knows things about the blade you're on. It knows things about your Azure account. So it's offering very specific, you know, diagnostic advice or it didn't just search the web right. It offered contextual advice here. So what is it suggesting we do. Right. So it's in here that there's some potential issues that that could impact our availability performance, which is actually something we, we're dealing with right now. This is the content, in the text form. I'll just click opening up the risk assessment tab. But you can see here that it's saying we're not taking advantage of our auto heal, experience. We're not utilizing our health check feature. we should consider distributing our web app across multiple instances, but it says we're actually doing a pretty good job in regards to how many sites we have on this app service plan. So this is just a really quick summary, but you can actually do a deeper dive, on these other areas where we think you could benefit from making these adjustments to your App Service plan or to your resource itself. I have never seen this part before. I thought I knew most of the diagnostics that for App Service are these part of those 60 diagnostics which were included back in that as well? Yeah. So we have a lot of recommendations, a lot of ways you can avoid, you know, hopefully heartache. puppy related heartache. If you don't mind, click on the View solutions on that health check feature one. Because like I said, I've never seen this before and I thought I was very familiar with, how this stuff works. So it'll actually walk you through updating things, fixing things, enabling stuff. So it's gotten very prescriptive. And you've only you're only two clicks away. Look at that. Your two clicks away from where you started in Copilot by announcing on new feature rep that you're, we really do bring we try to bring, you know, our collective wisdom into this experience so that you don't have to, you know, redo the the wheel and these, these, diagnostics tools, they're, they're they're being added. Right. Like, I know that there's 60 I probably didn't come with 60. They're probably been added and improved and some of them are contextual about what kind of app you have. It knows about your app. In this case, you know that it's not distributed. It's just one instance of some one application, corrupt. Yeah. But you can definitely go through any of these other details for your the possible solutions to figure out how to make your app more healthy. but this is so this is one of the ways that you can take advantage of Azure Copilot by being proactive. The other, and the other was to troubleshoot and diagnose, troubleshoot and solve for resource with Azure Copilot. With the Azure Copilot, we've integrated certain set of experiences for it. So right now you're actually able to ask questions about risk alerts ways that you can be proactive web up down web apps, low high CPU and event loans. And we're still in the process of mapping, you know, certain customer problems with diagnostics that we already have right now. Yeah. When you say that you're in the process of mapping with that, what I hear is like, it's just going to get smarter and there's even more like stuff that's going to light up because I'll ask it a question and it's going to like you just showed me, tell me about tools I didn't know already existed. And those tools will contextually get me to the answer faster, like you were two clicks and now I've got advice and two clicks or one sentence and a click, and I got an answer. And you fix your website. Yep. Exactly. That's what we're trying to get to. Just making it easier to take advantage of the tools that we've already worked so hard on. and just, yeah, making it easier to find, you know, there's a, there's a, a little historical kind of like joke that the Microsoft Word team told me once, and they said that they could pretend that there were no new features in Word and just tell people about awesome old features, and they would probably have like ten years of, like, new versions of Word, but it's literally just showing them awesome stuff. And I feel like App Service because, you know, I'm an App Service fan, has so many great tools and like 60 diagnostics tools, people are always digging around in logs and I'm like, no, use the diagnostic tools. So I think it's really cool that that you're going to surface those great tools with the Copilot experience. And this is going to be hopefully, you know, rolling out to more and more people in the in the future. Right? Yeah. We really want, more and more people to have access to this so that they, you know, take advantage of everything that we've all done. That's cool. Let's go ahead and go back to that web page and, see where folks can sign up. We're going to have a link in the show notes as well. this is something that is kind of going out because at the time of this video, it's in preview. So you can go ahead and request access from that AKA.MS link. And maybe if you're watching this video in the future, you already have this access and you can check it out, but you do have access, right? Hanna. Two of the diagnostics tools. So even if you don't have Copilot, go check out the diagnostics tools today, because those risk assessments I didn't even know that existed. And where do I find that? we'll give it. The risk assessment section is right here. Very cool. You'll click on this tile and then give it a minute to load. and then will show you all the other ways you can do that. So you've got diagnostics tools, risk assessments that are all custom to your application. Love it. That's hot. Very cool. Well thanks so much for hanging out with me today Hanna I appreciate it. Thank you for having me. All right. I am learning all about the Microsoft Copilot experience and the underlying cool tools that I can use to diagnose and solve the problems with my applications today on Azure Friday. Hey, thanks for watching this episode of Azure Friday. Now I need you to like it, comment on it, tell your friends, retweet it. Watch more Azure Friday.
