Sunday, July 28, 2019

How to Create a virtual network (classic) with multiple subnets in Azure Portal

Portal

  1. In an Internet browser, go to the Azure portal. Log in using your Azure account. If you don't have an Azure account, you can sign up for a free trial.
  2. Click Create a resource in the portal.
  3. Enter Virtual network in the Search the Marketplace box at the top of the New pane that appears. Click Virtual network when it appears in the search results.
  4. Select Classic in the Select a deployment model box in the Virtual Network pane that appears, then click Create.
  5. Enter the following values on the Create virtual network (classic) pane and then click Create:
    SettingValue
    NamemyVnet
    Address space10.0.0.0/16
    Subnet namePublic
    Subnet address range10.0.0.0/24
    Resource groupLeave Create new selected, and then enter myResourceGroup.
    Subscription and locationSelect your subscription and location.
    If you're new to Azure, learn more about resource groupssubscriptions, and locations (also referred to as regions).
  6. In the portal, you can create only one subnet when you create a virtual network. In this tutorial, you create a second subnet after you create the virtual network. You might later create Internet-accessible resources in the Public subnet. You also might create resources that aren't accessible from the Internet in the Private subnet. To create the second subnet, enter myVnetin the Search resources box at the top of the page. Click myVnet when it appears in the search results.
  7. Click Subnets (in the SETTINGS section) on the Create virtual network (classic) pane that appears.
  8. Click +Add on the myVnet - Subnets pane that appears.
  9. Enter Private for Name on the Add subnet pane. Enter 10.0.1.0/24 for Address range. Click OK.
  10. On the myVnet - Subnets pane, you can see the Public and Private subnets that you created.
  11. Optional: When you finish this tutorial, you might want to delete the resources that you created, so that you don't incur usage charges:
    • Click Overview on the myVnet pane.
    • Click the Delete icon on the myVnet pane.
    • To confirm the deletion, click Yes in the Delete virtual network box.

Azure CLI

  1. You can either install and configure the Azure CLI, or use the CLI within the Azure Cloud Shell. The Azure Cloud Shell is a free Bash shell that you can run directly within the Azure portal. It has the Azure CLI preinstalled and configured to use with your account. To get help for CLI commands, type azure <command> --help.
  2. In a CLI session, log in to Azure with the command that follows. If you click Try it in the box below, a Cloud Shell opens. You can log in to your Azure subscription, without entering the following command:
    Azure CLI
    azure login
    
  3. To ensure the CLI is in Service Management mode, enter the following command:
    Azure CLI
    azure config mode asm
    
  4. Create a virtual network with a private subnet:
    Azure CLI
    azure network vnet create --vnet myVnet --address-space 10.0.0.0 --cidr 16  --subnet-name Private --subnet-start-ip 10.0.0.0 --subnet-cidr 24 --location "East US"
    
  5. Create a public subnet within the virtual network:
    Azure CLI
    azure network vnet subnet create --name Public --vnet-name myVnet --address-prefix 10.0.1.0/24
    
  6. Review the virtual network and subnets:
    Azure CLI
    azure network vnet show --vnet myVnet
    
  7. Optional: You might want to delete the resources that you created when you finish this tutorial, so that you don't incur usage charges:
    Azure CLI
    azure network vnet delete --vnet myVnet --quiet
    
 Note
Though you can't specify a resource group to create a virtual network (classic) in using the CLI, Azure creates the virtual network in a resource group named Default-Networking.

PowerShell

  1. Install the latest version of the PowerShell Azure module. If you're new to Azure PowerShell, see Azure PowerShell overview.
  2. Start a PowerShell session.
  3. In PowerShell, log in to Azure by entering the Add-AzureAccount command.
  4. Change the following path and filename, as appropriate, then export your existing network configuration file:
    PowerShell:-
    Get-AzureVNetConfig -ExportToFile c:\azure\NetworkConfig.xml
    
  5. To create a virtual network with public and private subnets, use any text editor to add the VirtualNetworkSite element that follows to the network configuration file.
    XML
    <VirtualNetworkSite name="myVnet" Location="East US">
        <AddressSpace>
          <AddressPrefix>10.0.0.0/16</AddressPrefix>
        </AddressSpace>
        <Subnets>
          <Subnet name="Private">
            <AddressPrefix>10.0.0.0/24</AddressPrefix>
          </Subnet>
          <Subnet name="Public">
            <AddressPrefix>10.0.1.0/24</AddressPrefix>
          </Subnet>
        </Subnets>
      </VirtualNetworkSite>
    
  6. Import the network configuration file:
    PowerShell:-
    Set-AzureVNetConfig -ConfigurationPath c:\azure\NetworkConfig.xml
    
     Warning:-
    Importing a changed network configuration file can cause changes to existing virtual networks (classic) in your subscription. Ensure you only add the previous virtual network and that you don't change or remove any existing virtual networks from your subscription.
  7. Review the virtual network and subnets:
    PowerShell:-
    Get-AzureVNetSite -VNetName "myVnet"
    
  8. Optional: You might want to delete the resources that you created when you finish this tutorial, so that you don't incur usage charges. To delete the virtual network, complete steps 4-6 again, this time removing the VirtualNetworkSite element you added in step 5.
 Note:-
Though you can't specify a resource group to create a virtual network (classic) in using PowerShell, Azure creates the virtual network in a resource group named Default-Networking.

No comments:

Post a Comment

Lab 09: Publish and subscribe to Event Grid events

  Microsoft Azure user interface Given the dynamic nature of Microsoft cloud tools, you might experience Azure UI changes that occur after t...