<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by SHANUKA THUSHARA MAHESHWA on Medium]]></title>
        <description><![CDATA[Stories by SHANUKA THUSHARA MAHESHWA on Medium]]></description>
        <link>https://medium.com/@shanukathushara?source=rss-ea3adf51db05------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*TWpg6VGqlS9MeAxSYLaUBg.png</url>
            <title>Stories by SHANUKA THUSHARA MAHESHWA on Medium</title>
            <link>https://medium.com/@shanukathushara?source=rss-ea3adf51db05------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 20:02:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shanukathushara/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why Azure Container Registry (ACR) is required?]]></title>
            <link>https://medium.com/@shanukathushara/why-azure-container-registry-acr-is-required-fe550a73c9a2?source=rss-ea3adf51db05------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe550a73c9a2</guid>
            <category><![CDATA[microsoft-azure]]></category>
            <category><![CDATA[azure-web-app]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[azure-container-registry]]></category>
            <dc:creator><![CDATA[SHANUKA THUSHARA MAHESHWA]]></dc:creator>
            <pubDate>Sun, 18 Oct 2026 18:59:25 GMT</pubDate>
            <atom:updated>2026-10-18T19:17:51.412Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUAeHj9jBCSjCxF9iifFhg.png" /></figure><p>Modern cloud applications are increasingly deployed using containers. Technologies such as <strong>Docker</strong> and <strong>Kubernetes</strong> allow organizations to package applications with their dependencies, simplify deployment, and improve consistency across different environments.</p><p>However, building a container image is only one part of the deployment process. Once an image is created, it must be stored, secured, versioned, and made available to the environment where the application runs.</p><p>This is where <strong>Azure Container Registry (ACR)</strong> becomes valuable.</p><p>Azure Container Registry is Microsoft’s managed container registry service that enables organizations to store, manage, and distribute container images and related artifacts within their cloud infrastructure.</p><p>But why do we need ACR? Is it mandatory for Azure App Service? What benefits does it provide, and when should organizations consider using it?</p><p><em>Let’s explore these questions from an Azure architecture perspective.</em></p><h3>1. What Is Azure Container Registry?</h3><p><strong>Azure Container Registry (ACR)</strong> is a private registry for storing and managing container images.</p><p>A Docker image packages your application code, runtime and dependencies into a deployable unit. Once built, the image is stored in a registry such as ACR, where Azure services can retrieve it for deployment.</p><p>ACR is commonly used with containerised workloads such as <strong>AKS, Azure App Service and Azure Container Apps</strong>.</p><p>How to deploy ACR <a href="https://learn.microsoft.com/en-us/azure/container-registry/container-registry-get-started-portal?tabs=azure-cli">Quickstart:</a></p><blockquote>In simple terms, <strong>Docker builds the image, ACR stores the image, and your Azure hosting service runs the application.</strong></blockquote><h3>2. Why Do We Need Azure Container Registry?</h3><p>When an application is packaged as a <strong>Docker image</strong>, it needs a reliable place to store and retrieve that image for deployment. <strong>Azure Container Registry (ACR)</strong> provides this centralised registry within Azure.</p><p><strong>Why use ACR?</strong></p><ul><li><strong>Secure storage</strong> for container images</li><li><strong>Centralised image management</strong></li><li><strong>Consistent deployments</strong> across environments</li><li><strong>CI/CD integration</strong> with tools such as GitHub Actions</li><li><strong>Scalable distribution</strong> across Azure container workloads</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*vThftj06SA7jSyjiplSARw.png" /></figure><p>ACR therefore becomes an important component of a container-based application delivery architecture.</p><h3>3. Key Benefits of Azure Container Registry</h3><h4>3.1 Secure and Private Container Storage</h4><p>Container images may contain proprietary application code and dependencies. Organizations need to control who can publish, access, and deploy these images.</p><p>ACR supports private repositories, Microsoft Entra ID integration, and Azure role-based access control capabilities, depending on the selected configuration and authorization model.</p><p>For example, you can configure a deployment identity to push images to a registry while allowing the application hosting environment to pull images.</p><p>This supports the principle of least privilege: each identity receives only the permissions it needs.</p><p>Additional controls, such as network restrictions and private endpoints, can be incorporated where supported and required by the architecture.</p><h4>3.2 Integration with Azure Services</h4><p>ACR integrates with several Azure services, making it easier to deploy containerized workloads.</p><p>Common examples include:</p><ul><li><strong>Azure App Service:</strong> Run applications packaged as custom containers.</li><li><strong>Azure Kubernetes Service:</strong> Supply container images for Kubernetes deployments.</li><li><strong>Azure Container Apps:</strong> Deploy containerized applications and microservices.</li><li><strong>Azure Container Instances:</strong> Run containers without managing a full orchestration platform.</li></ul><p>This integration reduces the effort involved in connecting image storage to the application runtime.</p><h4>3.3 CI/CD Automation with GitHub Actions and Azure DevOps</h4><p>One of the most valuable benefits of ACR is its role in automated deployment pipelines.</p><p><strong>Consider a typical workflow:</strong></p><ol><li>A developer pushes code to GitHub.</li><li>GitHub Actions runs the build pipeline.</li><li>The pipeline builds a Docker image.</li><li>The image is pushed to Azure Container Registry.</li><li>The target Azure service retrieves the image.</li><li>The updated application is deployed.</li></ol><p>This eliminates the need to manually transfer container images between environments.</p><p>It also helps standardize deployments and reduce errors caused by inconsistent build and release processes.</p><p>The same concept can be implemented using Azure DevOps pipelines.</p><h4><strong>3.4 Image Versioning and Rollback</strong></h4><p>In production environments, knowing exactly which application version is running is essential.</p><p>ACR allows images to be organized into repositories and identified using tags. For example:</p><ul><li>invoice-api:1.0.0</li><li>invoice-api:1.1.0</li><li>invoice-api:2.0.0</li></ul><p>When a new release introduces an issue, the team can redeploy a previously tested image, provided the image is retained and the deployment configuration supports rollback.</p><p>For stronger release traceability, teams should record and deploy images by their immutable digest rather than relying exclusively on mutable tags such as latest.</p><p>This improves consistency between testing and production and makes deployments easier to audit.</p><h4>3.5 Scalability for Microservices and Enterprise Applications</h4><p>As applications grow, they often evolve from a single application into multiple independently deployed services.</p><p>For example, an e-commerce platform may contain:</p><ul><li>Customer management</li><li>Product catalog</li><li>Order processing</li><li>Payment processing</li><li>Notification services</li></ul><p>Each service may have its own container image and release cycle.</p><p>ACR provides a shared registry where these images can be managed and retrieved by the relevant deployment platforms.</p><p>This is particularly useful when an organization operates multiple containerized applications across different environments or teams.</p><h4><strong>3.6 Image Security and Supply Chain Governance</strong></h4><p>Container security begins before an image reaches production.Organizations need visibility into the software components included in their images, potential vulnerabilities, and the provenance of the artifacts they deploy.</p><p>ACR can be integrated with supported image-scanning and security tooling, including Microsoft Defender for Cloud capabilities where applicable.</p><p>A broader container security strategy may include:</p><ul><li>Scanning images for known vulnerabilities.</li><li>Restricting who can publish production images.</li><li>Using trusted build pipelines and controlled image sources.</li><li>Retaining image digests and build metadata.</li><li>Applying network and identity controls.</li><li>Removing outdated or unnecessary images through retention policies.</li></ul><p>These measures help establish a more controlled container supply chain. They require appropriate configuration and, in some cases, additional services or licensing.</p><h3>4. Is Azure Container Registry Mandatory for Azure Web App?</h3><p>This is one of the most common questions in Azure application deployment.</p><p><strong>No. Azure Container Registry is not mandatory for every Azure Web App.</strong></p><p>The requirement depends on the deployment model.</p><h4>1. Scenario : Deploying Application Source Code</h4><p>Suppose you have a Node.js application hosted in a GitHub repository and want to deploy it directly to Azure App Service.</p><p>You can use a supported source-code or build-artifact deployment workflow through GitHub Actions.</p><p>In this scenario, ACR is generally unnecessary because you are not publishing a container image to a registry.</p><h4>2. Scenario : Deploying a Docker Container</h4><p>Now suppose you package the same Node.js application into a Docker image.</p><p>The image must be available from a container registry that Azure App Service supports.</p><p>ACR is a strong choice because it provides private image storage and integrates with Azure identity and deployment services.</p><p>However, ACR is not the only supported registry option.</p><h4><strong>3. Scenario C: Deploying to Azure Kubernetes Service</strong></h4><p>For AKS, container images must be accessible to the cluster’s workloads.</p><p>ACR is commonly used because it provides centralized image management and can integrate with AKS authentication and authorization.</p><p>The cluster or workload infrastructure must be configured with the appropriate permissions to pull the images.</p><h4>4. Scenario D: Deploying to Azure Container Apps</h4><p>Azure Container Apps supports container-based deployment from supported registries. ACR is often suitable for private images and automated Azure-centric deployment pipelines.</p><p>The registry authentication configuration depends on the chosen deployment model.</p><p>The important distinction is that <strong>a containerized deployment requires an accessible image registry, but it does not always require ACR specifically</strong></p><h3>5. Reference Architecture: GitHub to Azure App Service Using ACR</h3><p>Consider a real-world example in which an organization wants to deploy a Node.js application using Docker, GitHub Actions, Azure Container Registry, and Azure App Service.</p><p>The architecture consists of four main components.</p><p><strong>Step 1 — GitHub repository</strong></p><p>The developer maintains the application source code and Dockerfile in GitHub.</p><p><strong>Step 2 — GitHub Actions</strong></p><p>When a change is pushed to the configured branch, the workflow builds and validates the application image.</p><p><strong>Step 3 — Azure Container Registry</strong></p><p>The pipeline authenticates to ACR and publishes the versioned container image.</p><p><strong>Step 4 — Azure App Service</strong></p><p>App Service is configured to retrieve the image from ACR and run the container.</p><p>The application can then be updated by publishing and deploying a new image through the pipeline.</p><p>This design separates the application source code, container artifact storage, and application hosting responsibilities.</p><p>For a production implementation, use managed identity or federated identity credentials where supported, grant only the required permissions, and configure the registry pull identity separately from the pipeline’s image-push identity.</p><h3>6. Azure Container Registry vs. Docker Hub</h3><p>Both ACR and Docker Hub can store and distribute container images. The right choice depends on the deployment environment, security requirements, and operational preferences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*5zPeDIkaMoZ2DrBlbTlbHw.png" /></figure><p>For organizations already using <strong>Microsoft Azure</strong>, ACR is often a practical choice because it fits naturally into existing <strong>Azure identity</strong>, <strong>networking</strong>, and deployment architectures.</p><blockquote>However, Docker Hub or another supported registry may be more appropriate when the organization already relies on a different registry platform.</blockquote><h3>7. Cost Considerations</h3><p>ACR is a managed service, but it is not automatically free.</p><p>Costs depend on the selected service tier and applicable usage, including storage, data transfer, and other chargeable operations or features.</p><p>Before deploying ACR, consider:</p><ul><li>The number and size of container images.</li><li>How frequently images are built and published.</li><li>How many environments and applications use the registry.</li><li>Image retention and cleanup requirements.</li><li>Network architecture and data transfer.</li><li>Security features and the selected service tier.</li></ul><p>Avoid retaining every obsolete image indefinitely. Implement retention and cleanup policies appropriate to your release and recovery requirements.</p><p>For a small application deployed directly from source code, ACR may add unnecessary cost. For a containerized application portfolio, the management and security benefits may justify the additional expense.</p><p>Always validate the expected cost against the current Azure pricing for your region and configuration.</p><h3><strong>8. Best Practices for Using Azure Container Registry</strong></h3><p>When designing an ACR solution, consider the following recommendations:</p><ol><li><strong>Use least-privilege access.</strong> Separate image-publishing permissions from image-pulling permissions.</li><li><strong>Automate image builds.</strong> Use GitHub Actions or Azure DevOps to create repeatable artifacts.</li><li><strong>Use meaningful version tags.</strong> Avoid relying solely on latest for production deployments.</li><li><strong>Deploy by digest where appropriate.</strong> This helps ensure the exact tested image is deployed.</li><li><strong>Scan images.</strong> Integrate supported vulnerability-scanning tools into the build and release process.</li><li><strong>Configure networking deliberately.</strong> Use public access restrictions or private connectivity where the security requirements justify them.</li><li><strong>Manage image retention.</strong> Remove unused artifacts without deleting images required for rollback or compliance.</li><li><strong>Monitor deployment failures.</strong> Verify registry permissions, image references, network connectivity, and application startup configuration.</li><li><strong>Protect production releases.</strong> Use appropriate approvals, environment controls, and trusted build pipelines.</li></ol><p>These practices help make ACR part of a reliable deployment architecture rather than simply another storage resource.</p><h3>Conclusion</h3><p>ACR provides a <strong>secure and managed way to store, version and distribute container images</strong> within Azure.</p><p>However, <strong>ACR is not mandatory for every Azure Web App</strong>. Its value is strongest for containerised workloads that require secure image management, CI/CD automation and scalable deployments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe550a73c9a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mastering Azure Kubernetes Service (AKS)]]></title>
            <link>https://medium.com/@shanukathushara/mastering-azure-kubernetes-service-aks-c50009eac6ce?source=rss-ea3adf51db05------2</link>
            <guid isPermaLink="false">https://medium.com/p/c50009eac6ce</guid>
            <category><![CDATA[kubernetes-cluster]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[ak]]></category>
            <category><![CDATA[dockerfiles]]></category>
            <dc:creator><![CDATA[SHANUKA THUSHARA MAHESHWA]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 20:16:06 GMT</pubDate>
            <atom:updated>2026-09-07T20:16:06.022Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5MvEbccFROGbNPnl1Tvsrw.png" /></figure><h3><strong>Introduction</strong></h3><p>Azure Kubernetes Service (AKS) is a managed Kubernetes platform that helps organisations deploy, scale, and manage containerised applications with ease. By reducing the complexity of Kubernetes operations, AKS enables teams to focus on innovation rather than infrastructure management.</p><p><strong>Understanding the Basics</strong></p><p>Imagine you have a web application that needs to serve thousands of users. Running it on a single server creates risks:</p><ul><li>Server failure causes downtime</li><li>Manual scaling is difficult</li><li>Updates can disrupt users</li></ul><blockquote>This is where <strong>containers</strong> and <strong>Kubernetes</strong> come in.</blockquote><p><strong>Step 1: Containerise the Application</strong></p><p>The application is packaged into a container using technologies such as Docker.</p><p>A container includes:</p><ul><li>Application code</li><li>Runtime</li><li>Libraries</li><li>Dependencies</li></ul><blockquote>This ensures the application runs consistently everywhere.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a3YD9l0Aht8eJhC99UETFw.png" /></figure><p><strong>Step 2: Kubernetes Orchestrates Containers</strong></p><p>Kubernetes automates:</p><ul><li>Deployment</li><li>Scaling</li><li>Load balancing</li><li>Self-healing</li><li>Updates</li></ul><blockquote>If a container crashes, Kubernetes automatically recreates it.</blockquote><p><strong>Step 3: AKS Simplifies Kubernetes</strong></p><p>Managing Kubernetes manually can be complex. AKS removes much of that operational burden by handling:</p><ul><li>Cluster management</li><li>Health monitoring</li><li>Automatic upgrades</li><li>Scaling</li><li>Security integrations</li></ul><blockquote>This allows organisations to focus on business applications rather than infrastructure.</blockquote><p><strong>How AKS Works</strong></p><p>A High-level AKS architecture looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*I_FVkwM_KZ7z_SHR1xw9hA.png" /></figure><p><strong>When user traffic increases:</strong></p><ol><li>More requests arrive.</li><li>Kubernetes detects the demand.</li><li>Additional application instances (Pods) are created automatically.</li><li>Traffic is distributed across all instances.</li><li>Users continue to receive a fast experience.</li></ol><p><strong>Key AKS Components</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*UIGvsfxJkyO_STwm2-H5sA.png" /></figure><p><strong>Why Businesses Use AKS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*i2Pw8Q-Dnv5pgodXhQDk0w.png" /></figure><blockquote><strong>Key Takeaway:</strong> AKS combines scalability, reliability, security, and cost efficiency, making it an ideal platform for modern cloud-native applications.</blockquote><p><strong>Real-World Example: E-Commerce on AKS</strong></p><p>Imagine a retail company running its online store on <strong>Azure Kubernetes Service (AKS)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/1*AUCR0nsTdeNQIdfG7VGICQ.png" /></figure><blockquote><strong>Result:</strong> The company maintains excellent performance during peak demand while only paying for the resources it actually uses.</blockquote><p><strong>When Should You Use AKS?</strong></p><p>AKS is ideal when:</p><ul><li>Building modern cloud-native applications</li><li>Migrating applications to Azure</li><li>Running microservices architectures</li><li>Deploying AI and data workloads at scale</li><li>Implementing DevOps and CI/CD pipelines</li></ul><h3><strong>Conclusion</strong></h3><blockquote><strong>AKS</strong> simplifies Kubernetes by handling much of the infrastructure management for you. With built-in scaling, high availability, and security integrations, AKS enables organisations to focus on building and delivering applications rather than managing clusters.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c50009eac6ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Azure Hub-and-Spoke Architecture for Enterprise Landing Zones]]></title>
            <link>https://medium.com/@shanukathushara/azure-hub-and-spoke-architecture-for-enterprise-landing-zones-f79ce3831a31?source=rss-ea3adf51db05------2</link>
            <guid isPermaLink="false">https://medium.com/p/f79ce3831a31</guid>
            <category><![CDATA[azure-networking]]></category>
            <category><![CDATA[azure-services]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[azure-security]]></category>
            <category><![CDATA[azure-landing-zone]]></category>
            <dc:creator><![CDATA[SHANUKA THUSHARA MAHESHWA]]></dc:creator>
            <pubDate>Fri, 28 Aug 2026 13:16:49 GMT</pubDate>
            <atom:updated>2026-08-28T13:31:28.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hWwbAp-G5dkmMymP5yKHxA.png" /></figure><p><strong>Introduction</strong></p><p><strong>Azure Hub-and-Spoke </strong>network architecture is a proven enterprise design pattern that enables centralized control, strong security boundaries, and scalable connectivity. This article explains the architecture, its components, traffic flow, design considerations, and best practices from a real-world Azure architecture perspective.</p><p><strong>Architecture Overview</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUFAouPDYlVOCC6xTnFhUQ.png" /></figure><p>Refe: <a href="https://learn.microsoft.com/en-us/azure/architecture/networking/architecture/hub-spoke">https://learn.microsoft.com/en-us/azure/architecture/networking/architecture/hub-spoke</a></p><p><strong>Why Hub-and-Spoke Architecture Is Needed</strong></p><p>Flat or loosely structured network designs introduce several challenges as environments mature:</p><ul><li>Lack of centralized security enforcement</li><li>Difficulty managing hybrid connectivity</li><li>Limited isolation between workloads</li><li>Increased risk of misconfiguration</li><li>Poor scalability as VNets multiply</li></ul><blockquote>Hub-and-Spoke architecture addresses these challenges by introducing <strong>clear separation of concerns</strong>, where shared services and security controls are centralized while workloads remain isolated.</blockquote><p><strong>Why is Hub-Spoke Architecture?</strong></p><p>Azure Hub-and-Spoke is a <strong>network topology</strong> consisting of:</p><ul><li>A <strong>Hub VNet</strong> that acts as the central point of connectivity</li><li>Multiple <strong>Spoke VNets</strong> that host workloads</li><li><strong>VNet peering</strong> between the hub and each spoke</li><li>Centralized routing and security enforcement through the hub</li></ul><blockquote>Spokes do <strong>not</strong> peer directly with each other. All inter-spoke communication flows through the hub, preserving centralized control and avoiding a mesh network.</blockquote><p><strong>Core Architectural Factors:</strong></p><ol><li><strong>Hub Virtual Network</strong></li></ol><p>The hub VNet is designed for <strong>connectivity and control</strong>, not for application workloads. It typically hosts:</p><ul><li>Azure VPN Gateway or ExpressRoute Gateway</li><li>Azure Firewall or third-party Network Virtual Appliance (NVA)</li><li>Azure Bastion</li><li>Shared DNS services</li><li>Domain Controllers or identity-related services (if required)</li><li>Azure Route Server (for advanced routing scenarios)</li></ul><p>The hub is responsible for <strong>routing, traffic inspection, and hybrid connectivity</strong>.</p><p><strong>2. Spoke Virtual Networks</strong></p><p>Spoke VNets host isolated workloads such as:</p><ul><li>Line-of-business applications</li><li>Web, application, and database tiers</li><li>Dev/Test or Production environments</li><li>Business unit–specific workloads</li></ul><p>Each spoke connects only to the hub and remains isolated from other spokes unless explicitly routed through the hub.</p><p><strong>3. VNet Peering</strong></p><p>VNet peering enables <strong>private, high-performance connectivity</strong> between VNets.</p><p>Key configuration concepts:</p><ul><li><strong><em>Hub-to-spoke peering allows gateway transit</em></strong></li><li><strong><em>Spoke-to-hub peering uses the remote gateway</em></strong></li></ul><p>This setup allows spokes to consume centralized gateways without deploying their own.</p><p><strong>4. Centralized Security and Routing</strong></p><p>Traffic inspection and routing are enforced via:</p><ul><li>Azure Firewall or third-party NVAs</li><li>User Defined Routes (UDRs)</li><li>Network Security Groups (NSGs)</li></ul><p>This ensures <strong>consistent security policies</strong> across all spokes.</p><p><strong>Traffic Flow in Hub-and-Spoke</strong></p><p><strong>Spoke-to-Hub:</strong></p><ul><li>Workloads in spokes access shared services (DNS, AD, Bastion) in the hub.</li></ul><p><strong>Spoke-to-Spoke:</strong></p><ul><li>Traffic is routed <strong>via the hub firewall/NVA</strong></li><li>Requires UDRs pointing spoke address spaces to the hub appliance</li></ul><p>This preserves the <strong>hub-and-spoke model</strong>, avoiding a mesh topology.</p><p><strong>On-Premises Connectivity:</strong></p><ul><li>On-premises networks connect to the hub via:</li><li>Site-to-Site VPN</li><li>Point-to-Site VPN</li><li>ExpressRoute</li></ul><p>All spokes inherit this connectivity through the hub.</p><p>Why Not “Peering” Sopokes directly?</p><p>Direct spoke-to-spoke peering creates a <strong>mesh topology</strong>, which:</p><ul><li>Increases management complexity</li><li>Makes security enforcement inconsistent</li><li>Scales poorly as VNets grow</li></ul><p>Hub-based routing ensures <strong>central governance, auditing, and security inspection</strong>.</p><h3>Use Cases:</h3><ul><li>Enterprise landing zones</li><li>Multi-environment (Dev/Test/Prod) isolation</li><li>Multi-subscription architectures</li><li>Hybrid connectivity (on-prem to Azure)</li><li>Centralized firewall and DNS services</li></ul><h3>Best Practices</h3><ol><li><strong>Keep the hub lightweight</strong><br>Only deploy shared and network-centric services.</li><li><strong>Use UDRs carefully</strong><br>Route spoke-to-spoke and internet-bound traffic via the hub firewall.</li><li><strong>Enable transitive connectivity explicitly</strong><br>Use gateway transit and remote gateway options correctly.</li><li><strong>Separate subscriptions where possible</strong><br>Place hub and spokes in different subscriptions for governance.</li><li><strong>Plan IP addressing upfront</strong><br>Avoid overlapping address spaces.</li><li><strong>Monitor traffic centrally</strong><br>Use Azure Monitor, Network Watcher, and Firewall logs.</li></ol><p><strong>Hub and Spoke vs Mesh Architecture:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/1*lE5QuxKvffCC8q6W4FpjlQ.png" /></figure><p><strong>Conclusion</strong></p><blockquote>Hub-and-Spoke architecture, you will learn how Azure Landing Zones provide secure, scalable, and well-governed cloud environments, centralizing control while isolating workloads for enterprise-ready deployments.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f79ce3831a31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Step 1]]></title>
            <link>https://medium.com/@shanukathushara/step-1-da839a5c58a9?source=rss-ea3adf51db05------2</link>
            <guid isPermaLink="false">https://medium.com/p/da839a5c58a9</guid>
            <dc:creator><![CDATA[SHANUKA THUSHARA MAHESHWA]]></dc:creator>
            <pubDate>Fri, 14 Apr 2023 19:53:03 GMT</pubDate>
            <atom:updated>2023-04-14T20:44:36.353Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>How to install Terraform on Windows.</strong></blockquote><blockquote><strong>Introduction</strong></blockquote><blockquote>Terraform is an open-source infrastructure as code (IaC) software tool developed by HashiCorp. It is used to manage and automate provisioning infrastructure resources in a cloud environment, such as virtual machines, containers, load balancers, and databases.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8f3pY5f7IPiyR2cOUWfbw.png" /></figure><p><strong>Step 1</strong></p><p>Navigate to Terraform official website and find the Windows version of Terraform. Click here. <a href="https://developer.hashicorp.com/terraform/downloads">Install | Terraform | HashiCorp Developer</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/1*2iot_BRiBUrjNcE7gHYdwQ.png" /></figure><p><strong>Step 2</strong></p><p>Open your downloaded file and extract it. and copy the terraform.exe file</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/739/1*idFnHQwbyf9Z1RSfyj7LOw.png" /></figure><p><strong>Step 3</strong></p><p>Copy the terraform.exe and past on C:\Program Files\Terraform</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*upxkzctuynAHLcsJ450R6g.png" /></figure><p><strong>Step 4</strong></p><p>Press the Win key and type the environment variables and select</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/1*BftOyA0j0O_hcZ2dofNRSA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*JFSjLfLmIEDl7hWbZsNDfw.png" /></figure><p><strong>Step 5</strong></p><p>Copy your terraform file path example.</p><p><strong>C:\Program Files\Terraform</strong></p><p>And past on the User variable section</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*Nve1WunHgeIJZ4nh6_BZRg.png" /></figure><p><strong>Step 6</strong></p><p>Copy the <strong>C:\Program Files\Terraform </strong>and create a new entry and past on the <strong>System Variables</strong> Section</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*RRrflgWVoQ79b6HnxO_9EQ.png" /></figure><blockquote><strong>Now you can verify the terraform version using a cmdlet.</strong></blockquote><p>Step 1</p><p>Open CMD and type</p><p><strong><em>Terraform version</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NtEnaxkkobCWtCq4zxbOMA.png" /></figure><blockquote>Conclusion</blockquote><blockquote>This article taught us how to install Terraform on Windows operating systems. If you have any questions, please contact me.</blockquote><blockquote>Thanks.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da839a5c58a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>