<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>azure on Youssef El Jirari</title><link>https://eljirari.me/tags/azure/</link><description>Recent content in azure on Youssef El Jirari</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://eljirari.me/tags/azure/index.xml" rel="self" type="application/rss+xml"/><item><title>IPAM: Why We Need It and Why It Gets Hard at Scale</title><link>https://eljirari.me/posts/ipam-at-scale/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eljirari.me/posts/ipam-at-scale/</guid><description>IP address management looks unnecessary when the environment is small.
You have a few VNets, somebody keeps a spreadsheet with the CIDRs, and before creating a new network you check that the range is not already used. It works.
Then the cloud estate grows.
You have tens or hundreds of subscriptions, multiple regions, separate production and non-production environments, connectivity hubs, private endpoints, on-premises networks and different teams deploying infrastructure independently. At that point, the problem is no longer which CIDR should I use?</description></item><item><title>Azure Landing Zones: Centralize the Guardrails, Not Every Decision</title><link>https://eljirari.me/posts/azure-landing-zones/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://eljirari.me/posts/azure-landing-zones/</guid><description>An Azure landing zone is sometimes presented as a collection of subscriptions, policies and management groups that you deploy before application teams arrive.
That is technically true, but it undersells the problem.
The real objective is to make it possible for many teams to use Azure independently without every team having to redesign identity, networking, security, governance and operations from zero.
Why a landing zone appears With one subscription and one team, governance can be informal.</description></item></channel></rss>