Key points

• Separate resources used by supported internet-facing frontends and interfaces.
• Allocation, SKU, zone, and attachment must be compatible with the target resource.
• A public IP exposes a network path but does not itself allow ports through an NSG or application firewall.

Best-known use cases

• Give a public Load Balancer a stable frontend.
• Publish a deliberately internet-facing Azure endpoint.

What candidates often confuse it with

• Public IP vs private IP: internet-routable Azure address vs address inside VNet space.
• Public IP vs Bastion: direct public endpoint component vs managed access to private VM addresses.

Key takeaway

Attach a public IP only where internet reachability is intentional and pair it with the required filtering and service configuration.

Related services

• Azure Virtual Network and subnets
• VNet peering

Relevant exam tasks

• D4.1.S1 — Create and configure virtual networks and subnets
• D4.1.S2 — Create and configure virtual network peering
• D4.1.S3 — Configure public IP addresses

Learn more

• Azure public IP addresses documentation