Table of Contents
Open Table of Contents
Résumé pour la direction
Scenario
Dans le cadre du provisioning de l’infrastructure de l’équipe Nautilus DevOps, il était nécessaire de créer un point d’entrée externe dédié afin d’exposer de futurs services de manière contrôlée et conforme aux bonnes pratiques Azure. Le besoin portait sur une adresse IP publique réservée, stable dans le temps, et adaptée à une intégration ultérieure avec une interface réseau ou un équilibreur de charge.
Le choix d’une Public IP Standard avec une allocation statique répond à plusieurs objectifs métiers et techniques : améliorer la prévisibilité des flux réseau, préparer l’architecture à des usages de production, et renforcer la posture de sécurité et de disponibilité de la plateforme.
Resolution
La ressource Azure Public IP a été créée avec succès via le portail Azure en utilisant les paramètres attendus : SKU Standard, allocation statique et IPv4. L’adresse est désormais prête à être associée à une NIC ou à un Load Balancer selon les besoins d’exposition des services.
Cette mise en place apporte une base réseau fiable pour les prochains déploiements, réduit le risque de changement d’adresse côté exposition externe, et aligne l’environnement avec les recommandations modernes de conception Azure.
Technical Implementation
Topology
The deployed resource is a dedicated Azure Public IP designed to act as the secure external ingress point for the Nautilus DevOps environment.
Resource parameters
- Name:
nautilus-pip - SKU:
Standard - Allocation method:
Static - IP version:
IPv4
The selected Standard SKU is aligned with current Azure best practices for production-oriented deployments, especially when predictable addressing and improved resiliency are required. The static allocation ensures the public endpoint remains stable over time, which is essential for firewall allowlisting, DNS mapping, and service exposure planning.
This operation was initially completed through the Azure Portal, but it is straightforward to convert into a repeatable CLI or PowerShell workflow for Infrastructure as Code adoption.
This Public IP is provisioned as a standalone network resource and is ready to be attached later to a Network Interface or Load Balancer.
While the provisioning requirements were broad, the Standard SKU with a Static Allocation Method was deliberately chosen over the Basic SKU.
The Basic SKU is on a deprecation path and lacks modern enterprise capabilities. The Standard SKU is secure by default (closed to inbound traffic unless explicitly permitted by an NSG), supports Zone Redundancy, and provides a fixed IP address that guarantees stability for DNS records and third-party firewall whitelisting.
Action
The implementation followed a simple resource provisioning workflow in the Azure Portal:
- Opened the Public IP addresses service in Azure.
- Started a new resource creation.
- Defined the resource name as
nautilus-pip. - Selected Standard as the SKU.
- Chose Static as the allocation method.
- Set the IP version to IPv4.
- Validated and deployed the resource.
From an automation perspective, this portal-based task maps directly to concise infrastructure commands. Since only the Public IP was required, no extra networking components were created, keeping the implementation minimal and aligned with clean IaC practices.
The Public IP was successfully provisioned and is immediately reusable for downstream network bindings.
For repeatability across environments, this provisioning step should ideally be embedded into a scripted deployment workflow rather than repeated manually in the portal.
Azure CLI
az network public-ip create \
--resource-group kml_rg_main-99650e5e8bc74e04 \
--name nautilus-pip \
--location eastus \
--sku Standard \
--allocation-method Static \
--version IPv4provision-public-ip.shAzure PowerShell
New-AzPublicIpAddress `
-ResourceGroupName "kml_rg_main-99650e5e8bc74e04" `
-Name "nautilus-pip" `
-Location "East US" `
-Sku Standard `
-AllocationMethod Static `
-IpAddressVersion IPv4provision-public-ip.ps1