[Azure Load Balalncer]How to extract the report for Azure Load Balancer Inbound NAT rule V1 for Azure VMs and Azure VMSS the using query in Azure portal and extract with subscription name ,ResourceGroup,LoadBalancer Name

Hi Lineesh Mm (PSP),

Thanks for reaching out in Microsoft Q&A forum,

If you want to pull a report of all your Azure Load Balancer Inbound NAT Rule V1 entries (both single-VM and VMSS) along with Subscription, Resource Group and Load Balancer name, you can do it right from the Azure Portal using Resource Graph Explorer (or via CLI/PowerShell). Here’s a quick walkthrough:

1. Go to Azure Portal → Resource Graph Explorer
2. Paste and run this Kusto query:

      Resources
      | where type == "microsoft.network/loadbalancers"
      | mv-expand inboundNat = properties.inboundNatRules
      | project
      SubscriptionId   = subscriptionId,
      ResourceGroup    = resourceGroup,
      LoadBalancer     = name,
      NatRuleName      = inboundNat.name,
      FrontendIPConfig = tostring(inboundNat.frontendIPConfiguration.id),
      FrontendPort     = inboundNat.frontendPort,
      BackendPort      = inboundNat.backendPort,
      Protocol         = inboundNat.protocol
   

3. Hit “Run” and you’ll see a table of every Inbound NAT rule (V1) with your subscription ID, RG, LB name and rule details.
4. Click the “Export” button (CSV/JSON) to download your report.

If you’d rather use Azure CLI (in Cloud Shell) you can achieve the same across a single RG or the entire subscription like this:

az network lb inbound-nat-rule list \
  --query "[].{
    Subscription: subscriptionId,
    ResourceGroup: resourceGroup,
    LoadBalancer: loadBalancerName,
    NatRule: name,
    FrontendPort: frontendPort,
    BackendPort: backendPort,
    Protocol: protocol
  }" \
  -o table

And in PowerShell:

Get-AzLoadBalancer | ForEach-Object {
  $lb = $_
  $lb.InboundNatRules | Select-Object `
    @{N='Subscription';Expression={$lb.Id.Split('/')[2]}},
    @{N='ResourceGroup';Expression={$lb.ResourceGroupName}},
    @{N='LoadBalancer';Expression={$lb.Name}},
    Name, FrontendPort, BackendPort, Protocol
}

Hope that helps you build your report in minutes!

Reference docs

• Inbound NAT rules overview: https://learn.microsoft.com/azure/load-balancer/inbound-nat-rules
• Manage inbound NAT rules (incl. CLI/PS examples): https://learn.microsoft.com/azure/load-balancer/manage-inbound-nat-rules
• Monitor Load Balancer via Log Analytics: https://learn.microsoft.com/azure/load-balancer/monitor-load-balancer#log-analytics-query-for-vnet-flow-logs
• Nat rules v1→v2 migration guidance: https://learn.microsoft.com/azure/load-balancer/load-balancer-nat-pool-migration

Kindly let us know if the above helps or you need further assistance on this issue.

Please do not forget to and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Hello Lineesh Mm (PSP),

Greetings! Thanks for raising this question in Q&A forum.

This is a great question! The reason there's no direct "export" button for Inbound NAT rules in the Azure Load Balancer blade is that Azure doesn't provide a built-in report for this out of the box. However, you can easily extract this information using the Azure Resource Graph Explorer in the Azure portal it lets you query your resources across subscriptions and export the results to CSV or Excel.

Here's a simple step-by-step guide to get it done:

Open the Azure Portal and in the top search bar, type "Resource Graph Explorer" and open it.

On the left side of the Resource Graph Explorer, make sure you select the subscriptions you want to query.

Copy and paste the following Kusto query into the query window:

Resources
| where type == "microsoft.network/loadbalancers"
| extend lbName = name
| mv-expand inboundNatRules = properties.inboundNatRules
| extend natRuleName = tostring(inboundNatRules.name)
| extend natRuleProps = inboundNatRules.properties
| project
    subscriptionId,
    resourceGroup,
    lbName,
    natRuleName,
    frontendIPConfiguration = tostring(natRuleProps.frontendIPConfiguration.id),
    frontendPort = tostring(natRuleProps.frontendPort),
    backendPort = tostring(natRuleProps.backendPort),
    protocol = tostring(natRuleProps.protocol),
    backendPool = tostring(natRuleProps.backendAddressPool.id),
    backendIPConfiguration = tostring(natRuleProps.backendIPConfiguration.id)
| order by subscriptionId, resourceGroup, lbName, natRuleName

Click the "Run query" button. The results will appear in a table below showing the Subscription ID, Resource Group, Load Balancer Name, NAT Rule Name, Frontend Port, Backend Port, Protocol, and Backend target details.

Once results are displayed, click "Export to CSV" or "Export to Excel" from the top of the results pane to download your report.

A few helpful things to note:

• The subscriptionId and resourceGroup columns are pulled automatically from the Resources table.
• The backendIPConfiguration column will point to either an Azure VM NIC or a VMSS NIC instance, so you can distinguish between VMs and VMSS during post-processing if needed.
• This query works for both V1 (single backend IP) and V2 (backend pool/VMSS) style NAT rules both are surfaced through the same properties.inboundNatRules field.

This approach gives you a clean, complete report across all your Load Balancers in one go without having to click through each resource manually!

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.