Azure Load Balancer website screenshot

Azure Load Balancer

Azure Load Balancer is a high-performance, low-latency layer-4 load balancing service for distributing inbound and outbound network traffic across virtual machines and other Azure resources. It supports public and internal load balancers, health probes, NAT rules, and HA scenarios.

Azure Load Balancer is listed with 2 APIs on the APIs.io network: Load Balancers API and Operations API. Tagged areas include Microsoft Azure, High Availability, Layer 4, Load Balancing, and Networks.

Azure Load Balancer’s developer surface includes authentication, developer portal, documentation, pricing, engineering blog, support, and 13 more developer resources.

46.9/100 developing ▬ flat Agent 20/100 agent aware saas Full breakdown ↓
scored 2026-10-23 · rubric v0.25.0 · Show this score on your site →
AccessFreemiumSelf serve⚡ Free to try
2 APIs 6 Features 3 Use Cases
Microsoft AzureHigh AvailabilityLayer 4Load BalancingNetworks

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Information Technology Management
BC-600
Load Balancers
PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/loadBalancers/{name}

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-10-23 · rubric v0.25.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Azure Load Balancer It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/microsoft-azure-load-balancer/"><img src="https://apis.io/badge/microsoft-azure-load-balancer/card.svg" alt="Azure Load Balancer on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/microsoft-azure-load-balancer: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Cisco DevNet Ecosystem (builders on Meraki, Catalyst, ISE, ThousandEyes, Splunk) undeclared - - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

Azure Load Balancer Load Balancers API

Load Balancers operations

Azure Load Balancer Operations API

Operations operations

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

FinOps 1

Cost, billing, and metering signals for API financial operations.

Features 6

Notable capabilities this provider offers.

Layer-4 Load Balancing

Distribute TCP and UDP traffic across virtual machines and resources with high performance and low latency.

Public and Internal Load Balancers

Support both public-facing and internal load balancing scenarios for diverse network architectures.

Health Probes

Monitor backend instance health with configurable TCP, HTTP, and HTTPS probes for automatic failover.

NAT Rules

Configure inbound NAT rules to forward traffic to specific backend instances on designated ports.

High Availability Ports

Load balance all TCP and UDP flows on all ports simultaneously for network virtual appliance scenarios.

Cross-Region Load Balancing

Distribute traffic across Azure regions for global high availability and disaster recovery.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Microsoft Azure Load Balancer Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Microsoft Azure Load Balancer Scopes

1 scope · implicit

1 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Microsoft Azure Load Balancer Agentic Access

7 operations · 3 acting

7 operations · 3 acting

AGENTIC

Use Cases 3

What developers build with this provider.

Web Application High Availability

Distribute traffic across multiple web servers for improved reliability and uptime.

VM Scale Set Load Balancing

Automatically balance traffic across virtual machine scale sets with auto-scaling capabilities.

Network Virtual Appliance Distribution

Distribute traffic across multiple firewall or NVA instances using HA ports.

Integrations 3

Pre-built integrations with other platforms and tools.

Azure Virtual Machines

Distribute network traffic across pools of Azure virtual machines.

Azure Virtual Machine Scale Sets

Integrate with VMSS for automatic scaling and load distribution.

Azure Monitor

Monitor load balancer health, performance metrics, and diagnostic logs.

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 5

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
name: Azure Load Balancer
description: Azure Load Balancer is a high-performance, low-latency layer-4 load balancing service for distributing inbound
  and outbound network traffic across virtual machines and other Azure resources. It supports public and internal load balancers,
  health probes, NAT rules, and HA scenarios.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://azure.microsoft.com/svghandler/load-balancer/
url: https://azure.microsoft.com/en-us/services/load-balancer/
created: '2026-03-13'
modified: '2026-05-19'
specificationVersion: '0.23'
tags:
- Microsoft Azure
- High Availability
- Layer 4
- Load Balancing
- Networks
tags_raw:
- Azure
- High Availability
- Layer 4
- Load Balancing
- Network
apis:
- aid: microsoft-azure-load-balancer:microsoft-azure-load-balancer-load-balancers-api
  name: Azure Load Balancer Load Balancers API
  description: Load Balancers operations
  humanURL: https://learn.microsoft.com/en-us/rest/api/load-balancer/
  baseURL: https://management.azure.com
  tags:
  - Load Balancer
  tags_raw:
  - Load Balancers
  properties:
  - type: OpenAPI
    url: openapi/microsoft-azure-load-balancer-load-balancers-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/load-balancer/
  - type: APIReference
    url: https://learn.microsoft.com/en-us/rest/api/load-balancer/
  - type: Authentication
    url: https://learn.microsoft.com/en-us/rest/api/azure/
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/load-balancer/quickstart-load-balancer-standard-public-portal
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/load-balancer/
  - type: SDKs
    url: https://learn.microsoft.com/en-us/python/api/overview/azure/network
  - type: SDKs
    url: https://learn.microsoft.com/en-us/dotnet/api/overview/azure/resourcemanager.network-readme
- aid: microsoft-azure-load-balancer:microsoft-azure-load-balancer-operations-api
  name: Azure Load Balancer Operations API
  description: Operations operations
  humanURL: https://learn.microsoft.com/en-us/rest/api/load-balancer/
  baseURL: https://management.azure.com
  tags: []
  tags_raw:
  - Operations
  properties:
  - type: OpenAPI
    url: openapi/microsoft-azure-load-balancer-operations-api-openapi.yml
  - type: Documentation
    url: https://learn.microsoft.com/en-us/azure/load-balancer/
  - type: APIReference
    url: https://learn.microsoft.com/en-us/rest/api/load-balancer/
  - type: Authentication
    url: https://learn.microsoft.com/en-us/rest/api/azure/
  - type: GettingStarted
    url: https://learn.microsoft.com/en-us/azure/load-balancer/quickstart-load-balancer-standard-public-portal
  - type: Pricing
    url: https://azure.microsoft.com/en-us/pricing/details/load-balancer/
  - type: SDKs
    url: https://learn.microsoft.com/en-us/python/api/overview/azure/network
  - type: SDKs
    url: https://learn.microsoft.com/en-us/dotnet/api/overview/azure/resourcemanager.network-readme
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
common:
- type: Plans
  url: plans/microsoft-azure-load-balancer-plans-pricing.yml
- type: RateLimits
  url: rate-limits/microsoft-azure-load-balancer-rate-limits.yml
- type: FinOps
  url: finops/microsoft-azure-load-balancer-finops.yml
- type: CapabilityMap
  url: capabilities/microsoft-azure-load-balancer-capability-edges.yml
  name: Azure Load Balancer Business Capability Map
- type: Website
  url: https://www.microsoft.com/
- type: AgenticAccess
  url: agentic-access/microsoft-azure-load-balancer-agentic-access.yml
- type: DomainSecurity
  url: security/microsoft-azure-load-balancer-domain-security.yml
- type: Authentication
  url: authentication/microsoft-azure-load-balancer-authentication.yml
- type: OAuthScopes
  url: scopes/microsoft-azure-load-balancer-scopes.yml
- type: GitHubOrganization
  url: https://github.com/Azure
- type: Portal
  url: https://portal.azure.com/
- type: Documentation
  url: https://learn.microsoft.com/en-us/azure/load-balancer/
- type: Pricing
  url: https://azure.microsoft.com/en-us/pricing/details/load-balancer/
- type: StatusPage
  url: https://status.azure.com/
- type: Blog
  url: https://azure.microsoft.com/en-us/blog/
- type: Support
  url: https://azure.microsoft.com/en-us/support/
- type: TermsOfService
  url: https://azure.microsoft.com/en-us/support/legal/
- type: PrivacyPolicy
  url: https://privacy.microsoft.com/en-us/privacystatement
- type: Features
  data:
  - name: Layer-4 Load Balancing
    description: Distribute TCP and UDP traffic across virtual machines and resources with high performance and low latency.
  - name: Public and Internal Load Balancers
    description: Support both public-facing and internal load balancing scenarios for diverse network architectures.
  - name: Health Probes
    description: Monitor backend instance health with configurable TCP, HTTP, and HTTPS probes for automatic failover.
  - name: NAT Rules
    description: Configure inbound NAT rules to forward traffic to specific backend instances on designated ports.
  - name: High Availability Ports
    description: Load balance all TCP and UDP flows on all ports simultaneously for network virtual appliance scenarios.
  - name: Cross-Region Load Balancing
    description: Distribute traffic across Azure regions for global high availability and disaster recovery.
- type: UseCases
  data:
  - name: Web Application High Availability
    description: Distribute traffic across multiple web servers for improved reliability and uptime.
  - name: VM Scale Set Load Balancing
    description: Automatically balance traffic across virtual machine scale sets with auto-scaling capabilities.
  - name: Network Virtual Appliance Distribution
    description: Distribute traffic across multiple firewall or NVA instances using HA ports.
- type: Integrations
  data:
  - name: Azure Virtual Machines
    description: Distribute network traffic across pools of Azure virtual machines.
  - name: Azure Virtual Machine Scale Sets
    description: Integrate with VMSS for automatic scaling and load distribution.
  - name: Azure Monitor
    description: Monitor load balancer health, performance metrics, and diagnostic logs.
- type: LlmsText
  url: https://portal.azure.com/llms.txt
x-parent: microsoft-azure
x-relationship: product

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/microsoft-azure-load-balancer"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/microsoft-azure-load-balancer/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/microsoft-azure-load-balancer/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.