{"id":135,"date":"2024-09-12T11:21:53","date_gmt":"2024-09-12T11:21:53","guid":{"rendered":"https:\/\/cloudvlabs.com\/?page_id=135"},"modified":"2026-08-03T00:59:58","modified_gmt":"2026-08-03T00:59:58","slug":"the-azure-vnet","status":"publish","type":"page","link":"https:\/\/cloudvlabs.com\/?page_id=135","title":{"rendered":"The Azure vNet"},"content":{"rendered":"\n

Project Title: Deploying a Multi environment architecture on Azure.<\/strong><\/p>\n\n\n\n

I wanted to set up two separate Azure environments, similar to the lifecycle management approach I’ve seen in many organizations I’ve worked with. Having dedicated Development\/Test and Production environments makes it much easier to build, test, and validate changes before they’re rolled out to production.
In larger enterprise environments, changes usually go through a formal change control process where every change has to be reviewed and approved before it’s implemented. Depending on the change, that approval process can sometimes take weeks.
By having separate Development\/Test and Production environments, I can follow a similar workflow without the delays of change control. I can deploy and test new resources in the Development\/Test environment, work through any configuration issues or unexpected problems, and then deploy the same validated changes into Production with much more confidence.<\/p>\n\n\n\n

Table of Contents<\/div><\/div>
<\/div>
    <\/ol><\/div><\/div><\/div>\n\n\n\n

    objective<\/h2>\n\n\n\n

    Deploy a multi environment architecture on Azure cloud to support a development Life Cycle. Common multi environment architecture development stages include:<\/p>\n\n\n\n

      \n
    1. Development \/Test<\/li>\n\n\n\n
    2. Production<\/li>\n<\/ol>\n\n\n\n

      Create an environment for each deployment stage, ensuring networking and secure the production environment with inbound and outbound networking rules.<\/p>\n\n\n\n

      Requirements<\/h3>\n\n\n\n
        \n
      1. Azure Virtual Network (vNet)<\/strong>:\n
          \n
        • Create a vNets to host all resources for each stage (e.g, Dev\/Test, Stage and production<\/li>\n\n\n\n
        • Divide the vNets into subnets for different application layers (e.g., Web, Application, Database).<\/li>\n<\/ul>\n<\/li>\n\n\n\n
        • Subnets<\/strong>:\n
            \n
          • Web Subnet<\/strong>: Hosts the front-end web servers (e.g., Azure App Service or Virtual Machines).<\/li>\n\n\n\n
          • Application Subnet<\/strong>: Hosts the application servers that handle business logic.<\/li>\n\n\n\n
          • Database Subnet<\/strong>: Hosts the database servers (e.g., Azure SQL Database or Cosmos DB).<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

            4 vNet Peering:<\/strong><\/p>\n\n\n\n

              \n
            • Peering: <\/strong>establish peering between Dev\/test\/, Stage and production<\/li>\n<\/ul>\n\n\n\n
                \n
              1. Network Security Group (NSG)<\/strong>:\n
                  \n
                • Create a single NSG to control inbound and outbound traffic for production vNet<\/li>\n\n\n\n
                • Define rules to allow:\n
                    \n
                  • HTTP\/HTTPS traffic between vNets.<\/li>\n\n\n\n
                  • Deny all other traffic by default.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                  • Outcomes<\/strong>:\n
                      \n
                    • Set up the Azure vNet and create the necessary subnets.<\/li>\n\n\n\n
                    • Configure vNet Peering<\/li>\n\n\n\n
                    • Configure the NSG and apply it to production vNet.<\/li>\n\n\n\n
                    • Test Network Connectivity.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n\n\n\n

                      Topology<\/h3>\n\n\n\n

                      <\/p>\n","protected":false},"excerpt":{"rendered":"

                      Project Title: Deploying a Multi environment architecture on Azure. I wanted to set up two separate Azure environments, similar to the lifecycle management approach I’ve seen in many organizations I’ve worked with. Having dedicated Development\/Test and Production environments makes it much easier to build, test, and validate changes before they’re rolled out to production.In larger enterprise […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-135","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=\/wp\/v2\/pages\/135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=135"}],"version-history":[{"count":60,"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=\/wp\/v2\/pages\/135\/revisions"}],"predecessor-version":[{"id":891,"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=\/wp\/v2\/pages\/135\/revisions\/891"}],"wp:attachment":[{"href":"https:\/\/cloudvlabs.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}