Shulou(Shulou.com)06/03 Report--

This article introduces how to use Public IP Prefex in Azure. Read the full article I believe everyone has a certain understanding of Azure Public IP Prefex. Let's look at the role of Public IP Prefex.

In the enterprise, firewall is indispensable, in communication with services on the cloud, especially some PaaS services, we need to add the corresponding IP address to the white list, for PaaS services, Microsoft actually has some fixed network segments, the information of these network segments is actually published, we can download it directly from Microsoft's official website, so that when setting firewall rules, you can add IP to the rules. For some services of IaaS, if you don't want to manually add public IP every time, in fact, Azure provides a function that can provide users with a pool of public IP addresses. Users can get a batch of public IP addresses for specific addresses, so that they don't need to manually add firewall rules one by one every time. This function is actually Public IP Prefex.

Currently, IP in Public IP Prefex can be associated with the following services

Resource Scenario Steps Virtual Machines Associating a public IP from a prefix to a virtual machine in Azure reduces the administrative overhead of creating an allow list IP in a firewall. A single firewall rule simplifies the process of creating the entire prefix permission list. When scaling virtual machines in Azure, you can associate IPs from the same prefix, saving cost, time, and administrative overhead. Associate IP from a prefix to a virtual machine: 1. Create a prefix. 2. Create IP from prefix. 3. Associate IP to virtual machine network interfaces. IP can also be associated to a VM scale set. A standard Load Balancer (Basic LB is not allowed) associates a public IP from a prefix to the front-end IP configuration or outbound rules of the Load Balancer to ensure that the Azure public IP address space is simplified. You can simplify your scenario by collating outbound connections that originate from a contiguous range of IP addresses defined by a common IP prefix. Associate IP from a prefix to a Load Balancer: 1. Create a prefix. 2. Create IP from prefix. 3. When creating a Load Balancer, select or update the IP created in step 2 above as the front-end IP for the Load Balancer. Azure Firewall can use public IP addresses from prefixes as outbound SNAT. This means that all outbound virtual network traffic is converted to Azure Firewall public IP. This IP comes from a predetermined prefix, so it's easy to know ahead of time what the public IP footprint in Azure will look like in the future. 1. Create a prefix. 2. Create IP from prefix. 3. When deploying Azure Firewall, be sure to select IP that was previously assigned by prefix. Application Gateway v2 For auto-scaling and area-redundant Application Gateway v2, you can use a common IP from the prefix. This IP comes from a predetermined prefix, so it's easy to know ahead of time what the public IP footprint in Azure will look like in the future. 1. Create a prefix. 2. Create IP from prefix. 3. When deploying an application gateway, be sure to select the IP that was previously assigned by prefix.

It should be noted that for Public IP Prefex, the following restrictions currently exist.

IP address of prefix cannot be specified. Azure assigns IP addresses for prefixes based on the specified size.

You can create IP addresses with prefixes up to 16 or/28. For more information, see Azure Limits.

The scope cannot be changed after the prefix is created.

Static public IP addresses created using only standard SKUs can be assigned from prefix ranges. To learn more about public IP address SKUs, see Public IP addresses.

Addresses in the scope can only be assigned to Azure Resource Manager resources. These addresses cannot be assigned to resources created through the classic deployment model.

All public IP addresses created with prefixes must be in the same Azure region and subscription as the prefix, and must be assigned to resources in the same region and subscription.

If any address in the prefix is assigned to a common IP address resource associated with a resource, the prefix cannot be removed. First, disassociate all public IP address resources that have IP addresses assigned to them by prefixes.

The use of Public IP Prefex is actually very simple, let's take a look

Public IP Prefex is created by network segment. The size of the network segment determines the number of IPs in the pool. It should be noted that the larger the network segment, the more the number of IPs in the pool will be, and the more expensive the charge will be.

You can see that after the creation is completed, you can create a public IP by adding an IP.

Try creating two IP addresses, and you'll see that you're creating consecutive IP addresses.

The rest is no different from ordinary public IP. It can be mounted on the corresponding service. However, it is still necessary to remind that the IP created by Public IP Prefex is a Standard IP. There is no way to mount it on some Basic services.

After reading the above, do you have any further understanding of Public IP Prefex? If you still want to learn more skills or want to know more about related content, welcome to pay attention to the industry information channel, thank you for reading.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.