Public IP addresses in Azure - Step-by-Step Execution

Process Flow - Public IP addresses

Request Public IP

↓

Azure assigns IP

↓

IP linked to resource

↓

Resource accessible via IP

↓

Release or keep IP

↓

Keep: IP reserved

↓

Release: IP freed

This flow shows how Azure assigns a public IP to a resource, making it accessible from the internet, and how the IP can be kept or released.

Execution Sample

Azure

az network public-ip create --resource-group MyGroup --name MyPublicIP --allocation-method Static

This command creates a static public IP address in Azure linked to a resource group.

Process Table

Step	Action	Input	Azure Response	Result
1	Request Public IP creation	Resource group: MyGroup, Name: MyPublicIP, Allocation: Static	Accepted	Public IP resource created with pending status
2	Azure assigns IP address	N/A	IP assigned: 52.170.12.34	Public IP resource now has IP 52.170.12.34
3	Link IP to resource	Associate with VM or Load Balancer	Association successful	Resource accessible via 52.170.12.34
4	Use IP	Connect from internet	Connection established	Resource reachable externally
5	Decide to keep or release IP	Keep or delete IP resource	If kept: IP reserved; If deleted: IP freed	IP either reserved or released
6	Exit	N/A	N/A	Process ends

💡 Process ends after IP is either reserved or released

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 5	Final
Public IP Resource	None	Created (pending)	Assigned IP 52.170.12.34	Linked to resource	Kept or Released	Kept or Released
IP Address	None	None	52.170.12.34	52.170.12.34	52.170.12.34 or None	52.170.12.34 or None
Resource Accessibility	No	No	No	Yes	Yes or No	Yes or No

Key Moments - 3 Insights

Why does the public IP resource show 'pending' after creation?

Because Azure first creates the resource placeholder before assigning an actual IP address, as shown in step 1 and 2 of the execution_table.

What happens if I delete the public IP resource after use?

The IP address is released back to Azure and no longer reserved, so the resource becomes unreachable, as explained in step 5.

Can I use a dynamic public IP instead of static?

Yes, but the IP can change over time. The example uses static allocation to keep the IP fixed, as shown in the command in execution_sample.

Visual Quiz - 3 Questions

Look at the execution_table, what is the IP address assigned at step 2?

A 10.0.0.4

B 52.170.12.34

C None

D 192.168.1.1

💡 Hint

Check the 'Azure Response' column at step 2 in the execution_table.

At which step does the resource become accessible from the internet?

A Step 3

B Step 1

C Step 5

D Step 6

💡 Hint

Look for 'Resource accessible via IP' in the 'Result' column.

If you delete the public IP resource after use, what happens to the IP address?

A It remains reserved for you

B It changes to a new IP automatically

C It is released and can be assigned to others

D It becomes private

💡 Hint

Refer to step 5 in the execution_table about keeping or releasing the IP.

Concept Snapshot

Public IP addresses in Azure allow resources to be reachable from the internet.
You create a public IP resource, which Azure assigns an IP address.
The IP can be static (fixed) or dynamic (may change).
Link the public IP to a resource like a VM or load balancer.
Keep the IP to reserve it or delete to release it back to Azure.

Full Transcript

This visual execution shows how Azure handles public IP addresses. First, you request a public IP resource creation. Azure creates the resource in a pending state. Then, Azure assigns an actual IP address to this resource. Next, you link this public IP to a resource such as a virtual machine or load balancer. Once linked, the resource becomes accessible from the internet via this IP. Finally, you decide whether to keep the IP reserved or release it. Keeping it reserves the IP for your use; releasing it frees the IP back to Azure. This process ensures your resource can be reached externally with a stable or dynamic IP as needed.