 Yeah. So Tito says, hello all, I'm looking for a holistic approach to secure my Azure backends like App Services and Function Apps by secure. I mean control what we can talk to these services and how. I looked into securing back-end services with API M, but that doesn't prevent me from going directly to the back-end around API M. I know you had put some comments in there and you want to. I got comments. Yeah. So for me, it was more about the scenario. The API management front-end is going to offer an ability to do a whole bunch of things, manage and control, provide essentially an access point for multiple APIs, and you can secure them and control the access to them. However, it is in many respects, it is just an odd choice, but it is a pulling together of those APIs from different locations. So it basically provides a consolidated view of where they are. Those APIs still exist in the original locations. So is the concern here that he's trying to control the access to those APIs from external users, or is it just that he can hit them up internally? If you can hit them up internally, that may not necessarily be an issue. But if he's real concern is, I only want things to go through the management API, then there's things you can do in terms of controlling some of the simple Azure security scenarios, like network security groups around the location of where the APIs hosted. Those kind of things are elements you can do. I think we need a little bit more of a bigger picture about what his concern is, about why he can do that, and what he's trying to protect it from. Yeah, I would agree with Neil 100 percent on this because really the more information on this, this really gets into a lot of different areas around the API security. There are multiple ways that you can handle, like Neil had described, and it really focuses on, again, as he said, internal and external. But what is his overall goal? I mean, he mentions that he wants to control what can talk to these services and how, but we need more information because it depends on the service as well, and how that service is being addressed. If it's being addressed externally, if it's being addressed only by a certain vNet, if it's only isolated to a specific Azure group or any time of RBAC that lays behind the application, so there are a bunch of questions. I feel personally that this is something that might take a little while to feel out, but at the same time, I think that if we understood it a little bit better, we might be able to get a better answer around what he's looking for.