My Blog

1. Design the VNet and CIDR Planning

Theory: Virtual Network (VNet) address space planning is the crucial first step. Proper planning ensures you have sufficient non-overlapping IP space for current and future resources, regions, and VPN connections. Using large, well-defined CIDR blocks (e.g., /16 for an entire region or /24 for a standard Subnet) simplifies routing and avoids complex renumbering later.

Designing a clear Azure structure requires deciding which taxonomy level should enforce Azure Policy, RBAC, and isolation. This article presents the hierarchy from Entra ID Tenant down to Azure Resources, explains where to apply governance, and gives practical tips you can use to build a maintainable cloud structure.

As the diagram shows, the first takeaway is that Microsoft Entra ID is the identity management branch and Azure is the resource governance branch.

When an Application Gateway reports backend health check failures, a frequent but easy-to-miss cause is a TLS negotiation mismatch between the gateway and the backend. This article shows how to diagnose the problem, align TLS settings and probes, validate the fix, and codify the correct configuration in IaC.

Azure Pipelines support two types of expressions to control pipeline behavior: compile-time expressions (evaluated at pipeline creation) and runtime expressions (evaluated during pipeline execution). Template expressions, a subcategory of compile-time, help you create reusable pipeline components.

The key takeaway: Use compile-time expressions with parameters for fixed values needed at pipeline creation, and runtime expressions with variables for dynamic behavior based on execution state.

Want to dive deeper into all this terminology? Read along to learn all the details.

When working with Azure, you will encounter various types of IDs in the form of GUIDs (Globally Unique Identifiers). Understanding these IDs is crucial for managing resources, configuring access, and using the Azure CLI (az) effectively.

We’ll explore these IDs (terms in backticks match the Azure portal labels):

• Tenant ID — identifies your Microsoft Entra ID directory; used for authentication and identity management.
• Subscription ID — identifies a subscription; used for billing and scoping resource operations.
• Resource GUID — an internal GUID assigned to a resource instance; helpful for cross-referencing resources.
• Resource ID — the full ARM path showing where a resource lives; used in ARM templates and API calls.
• Application (Client) ID — the client identifier (appId) for a registered application; used in OAuth flows.
• Object ID — a tenant-scoped identifier for directory objects like users and service principals.