Provisioning a Public IP Address

1. Start Locally

Firstly, we need to launch Locally which we can do from a terminal by running:

Once Locally has started, the Locally Dashboard will open automatically:

2. Create a Resource Group

Next we can create the Resource Group:

There's two things to note here:

1. The Azure CLI supports Automatic Configuration, meaning that it can automatically be configured to work against Locally just by prefixing commands with locally run.
2. Locally intentionally uses a different set of locations to Azure as a safety precaution, so that you can be confident you're deploying against Locally rather than regular Azure. You can also configure Locally to use the Azure locations too, but you'll want to be extra sure that you're prefixing commands with locally run when you do.

3. Create the Public IP Address

With the Resource Group in place, we can create the Public IP Address. The two decisions worth making are the SKU and whether the address is statically or dynamically allocated:

{
  "ip": "127.1.0.3",
  "method": "Static",
  "name": "sample-pip",
  "sku": "Standard",
  "state": "Succeeded"
}

We can read the address back at any point, which is what you'd do when wiring it into something else:

And list the addresses in the Resource Group:

Name        IP          Method
----------  ----------  --------
sample-pip  127.1.0.3   Static

A Public IP Address on its own doesn't do much - it becomes useful once attached to something, such as a Load Balancer or a virtual machine's network interface.

We can see the Public IP Address in the Locally Dashboard too:

4. Tidy up

Finally, we can tidy up. To remove the Resource Group and everything within it:

There's nothing billable to clean up, since everything ran on your machine, but it's still worth checking your teardown scripts work here before you run them against Azure.

Doing this with other tooling

Whilst this guide used the Azure CLI, Public IP Addresses work the same way through any of the tooling that Locally supports - a Microsoft.Network/publicIPAddresses resource in HashiCorp Terraform or OpenTofu, Pulumi, Bicep or an ARM Template all provision against Locally in the same way, with only the location changed.

Next steps

A NAT Gateway uses a Public IP for outbound traffic. With a Public IP on a Virtual Machine, you can connect to it with the Locally CLI - see Virtual Machines.

Should you encounter any issues, please take a look at the troubleshooting section.