Load Balancer SKU retired on 30 September 2025. It was open by default, worked only with Basic public IPs and lacked zones and HA Ports, and its backend pool was confined to a single availability set, scale set or standalone VM.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Basic Load Balancer in context, with comparison tables and the common traps.
Terms in this definition
- ELT
Extract, load, transform: raw data lands in the target system first and is transformed there. See ETL for the opposite order.
- SKU
The size or tier of a service, for example a VM size or the Premium tier of ACR.
- Basic
Low-cost Log Analytics table plan where ingestion is cheap but each query is charged per GB and runs at workspace scope. Full KQL and simple log search alerts are supported; standard log search alerts are not.
- HA Ports
A rule on an internal Standard Load Balancer, using protocol All and port 0, that balances every TCP and UDP flow on every port, which suits active-active NVAs.
- Backend pool
Targets of a load balancer, identified by IP address or NIC IP configuration. A pool can't span VNets, and a Standard load balancer won't accept a VM that has a Basic public IP.
- Availability set
Grouping that distributes VMs across as many as 3 fault domains and 20 update domains inside a single datacentre, backed by a 99.95% SLA. It offers neither autoscale nor zone distribution.
- Set
Secret permission in Key Vault for writing secrets; some older material refers to it as Create.