Idea Of Azure Digital Community With 4 Palms-On Labs


  • Introduction
  • Key terminology utilized in digital community
  • Lab 1: Create digital community utilizing Azure Portal
  • Lab 2: Create digital community utilizing Azure CLI
  • Lab 3: Create digital community utilizing PowerShell
  • Lab 4: Create digital community utilizing ARM template



On this article we’ll undergo the idea of Azure digital community, what Azure digital community is and phrases in digital community that are used to create digital community.


Key terminology utilized in digital community

  1. Digital Community
  2. IP Handle
  3. Subnet
  4. Community Interface Card
  5. Load Balancer
  6. Utility Gateway
  7. Site visitors Supervisor
  8. Community Safety Group
  9. Power Tunnelling
  10. Regional Digital Community
  11. Cross Premises Community

Digital Community


Digital community (VNet) is your personal non-public community within the azure cloud. This supplies you a safe approach to talk between your digital machines and different companies that are within your digital community in azure cloud or on-premises.


IP Handle


IP addresses are the vary of tackle that outline the community and every VM which is a part of a digital community can talk via this IP tackle. Every VM with within the Vnet can have non-public or public IP tackle, non-public IP tackle permits communication between a number of of the  VMs contained in the Vnet, however from outdoors of the Vnet public IP tackle is used over the web for communication.




It’s a community inside your community. In different phrases Subnet is small portion of IP tackle vary which is allotted to a digital community.


Community Interface Card


Community interface card is used to attach the VM via community.


Load Balancer


Load balancer is used to distribute the incoming site visitors evenly throughout a gaggle of servers. This distribution of site visitors primarily based on the well being probe of servers that are behind the load balancer.


Utility Gateway


It’s a net site visitors load balancer that lets you handle your site visitors to your net software. It’s on prime of load balancing your workloads, so it might probably make routing choices to move your URL request to the suitable node. For instance if there are two varieties of requests that come to the appliance gateway,  one is for photographs and second one is for movies, than the appliance gateway can decide the place to redirect these requests  if we now have two devoted servers, one for serving photographs and  one  for serving movies.


Site visitors Supervisor


It is usually used to distribute the site visitors on the DNS degree, for instance if I’ve an internet site and I’ve site visitors from many nations and to handle and I need to distribute the site visitors to handle the load in a means that US site visitors ought to go  via the US server and India site visitors ought to go  although the India server.


Community Safety Group


It is a  algorithm that work as a filter in your site visitors that connects with azure digital community (Vnet). It permits or denies inbound community safety community site visitors.


For instance if we now have a Vnet “xyz” and there are two VMs “A” and “B” contained in the Vnet “xyz” and we don’t need RDP connection to entry these VMs although the general public IP however each the machines can entry their RDP utilizing their non-public IP, then we will outline any such safety beneath the Community Safety Group.


Power Tunnelling


Power tunnelling controls the move of your site visitors, it’s for inspection and auditing of all internet-bound site visitors. It forces all of your internet-bound site visitors to your on-premise location through sit-to-site VPN tunnelling so you’ll be able to have the power to examine and audit the site visitors.


Regional Community


Microsoft Azure has a number of areas. We could have a number of Vnets that will work  in numerous areas, so the connections between these Vnets that are in numerous areas comes beneath this part.


Cross Premises Community


It’s a community that’s linked to your on-premise community. It permits your azure digital machine to be  a part of your on-premise community.


Lab 1 – Create Digital Community Utilizing Azure Portal

  • Log in to Azure portal
  • In search bar “Digital Community” and choose it


Determine 1.

  • Now click on on the “+ Add” to begin creating digital community


  • Enter the essential particulars for digital community

The primary tab, “Primary” is for including fundamental particulars for the digital community

    • Subscription: “Visual Studio Skilled”
    • Useful resource Group: In case you have current useful resource group then you’ll be able to choose it, I created an new one referred to as “Be taught-Vnet”
    • Title: VnetOne
    • Area: You’ll be able to choose any area; on this lab I’m going to pick “(US) Central US”
    • Both Click on “Evaluate + Create” or you’ll be able to click on “Subsequent : IP Addresses”

  • Ipv4 tackle area
    By default, an tackle area is mechanically created. You’ll be able to click on the tackle area to regulate it to mirror your personal values. You can even add extra tackle areas

  • Subnet
    In case you use the default tackle area, a default subnet is created mechanically. In case you change the tackle area, you’ll want to add a subnet. Choose + Add subnet to open the Add subnet window. Configure the next settings after which choose Add so as to add the values,
    • Subnet title – On this instance, we named the subnet “SubNet1”.
    • Subnet tackle vary – The tackle vary for this subnet.

  • On the Safety tab, presently, go away the default values,
    • BastionHost: Disable
    • Ddos safety commonplace: Primary
    • Firewall: Disabled
  • Go away the tag particulars empty
  • Choose Evaluate + create to validate the digital community settings.
  • After the settings have been validated, choose Create once you hit the create button your digital community shall be created.

But when need to save this data as template for future use the you’ll be able to click on the “Obtain as template for automation” as proven highlighted in Determine 8.


  • Click on the “Obtain” to obtain this as json template as proven in determine 9
  • Or you’ll be able to add it to your library

Determine 9.

  1. {    
  2.     “$schema”: “http:  
  3.     “contentVersion”: “”,    
  4.     “parameters”: {    
  5.         “location”: {    
  6.             “sort”: “string”    
  7.         },    
  8.         “virtualNetworkName”: {    
  9.             “sort”: “string”    
  10.         },    
  11.         “resourceGroup”: {    
  12.             “sort”: “string”    
  13.         },    
  14.         “addressSpaces”: {    
  15.             “sort”: “array”    
  16.         },    
  17.         “ipv6Enabled”: {    
  18.             “sort”: “bool”    
  19.         },    
  20.         “subnetCount”: {    
  21.             “sort”: “int”    
  22.         },    
  23.         “subnet0_name”: {    
  24.             “sort”: “string”    
  25.         },    
  26.         “subnet0_addressRange”: {    
  27.             “sort”: “string”    
  28.         },    
  29.         “ddosProtectionPlanEnabled”: {    
  30.             “sort”: “bool”    
  31.         },    
  32.         “firewallEnabled”: {    
  33.             “sort”: “bool”    
  34.         },    
  35.         “bastionEnabled”: {    
  36.             “sort”: “bool”    
  37.         }    
  38.     },    
  39.     “variables”: {},    
  40.     “sources”: [    
  41.         {    
  42.             “name”: “[parameters(‘virtualNetworkName’)]”,    
  43.             “sort”: “Microsoft.Community/VirtualNetworks”,    
  44.             “apiVersion”: “2019-09-01”,    
  45.             “location”: “[parameters(‘location’)]”,    
  46.             “dependsOn”: [],    
  47.             “tags”: {},    
  48.             “properties”: {    
  49.                 “addressSpace”: {    
  50.                     “addressPrefixes”: [    
  51.                         “”    
  52.                     ]    
  53.                 },    
  54.                 “subnets”: [    
  55.                     {    
  56.                         “name”: “SubNet1”,    
  57.                         “properties”: {    
  58.                             “addressPrefix”: “”    
  59.                         }    
  60.                     }    
  61.                 ],    
  62.                 “enableDdosProtection”: “[parameters(‘ddosProtectionPlanEnabled’)]”    
  63.             }    
  64.         }    
  65.     ]    
  66. }    
  •  Clicking “Deploy” button will redirect you to the customized deployment web page the place you’ll be able to Edit your template once more for modifications.
  • You’ll be able to change the setting in your digital community configuration
  • However I’m going to go away this as it’s and return to our “Create Digital Community” from the breadcrumb display to finish the creation of our digital community.
  • Click on “Create”
  • Your digital community shall be prepared to be used after few moments as proven in determine 13.

Determine 13.


Lab 2 – Create digital community utilizing Azure CLI

  • Login to Azure portal
  • Click on the cloud shell button within the header

  • To confirm now go to the Azure portal within the search bar and kind “Useful resource Teams”

Determine 17.




Determine 19.


If you wish to specify your personal subnet when creating digital community


First create a Digital community with out default subnet

  1. az community vnet create –title Vnet2 –resource-group rgVnet  

Itemizing 2.


Determine 20.


Now create a subnet and ssociate it with digital community Vnet2

  1. az community vnet subnet create –resource-group rgVnet –vnet-name Vnet2 –title subnet2 –address-prefix   

Itemizing 3.



Determine 21.


To confirm  to the azure portal seek for Digital Community and you will see that a digital community “Vnet2” with Subnet “Subnet2”



Determine 22.


Lab 3 – Create digital community utilizing PowerShell


Create a useful resource group

  1. New-AzResourceGroup -Title rgVnet3 -Location CentralUS  
  1. $virtualNetwork = New-AzVirtualNetwork -ResourceGroupName rgVnet3 -Location CentralUS -Title Vnet3 -AddressPrefix   

Itemizing 5.


Go to the digital community part on the Azure portal and you will note “Vnet3” digital community has been created however there is no such thing as a subnet related to this digital community as proven in determine 24.



  1. $subnetConfig = Add-AzVirtualNetworkSubnetConfig -Title subnet3 -AddressPrefix -VirtualNetwork $virtualNetwork  

Affiliate the Subnet with digital community

  1. $virtualNetwork | Set-AzVirtualNetwork     

Itemizing 7.



Determine 25.


Determine 26.


Lab 4 – Create digital community utilizing ARM template


An ARM template is a JSON file with some parameters and with their values, it defines infrastructure and configuration of your azure sources.

  1. {    
  2.     “$schema”“”,    
  3.     “contentVersion”“”,    
  4.     “parameters”: {    
  5.         “virtualNetworks_Vnet4_name”: {    
  6.             “defaultValue”“Vnet4”,    
  7.             “sort”“String”    
  8.         }    
  9.     },    
  10.     “variables”: {},    
  11.     “sources”: [    
  12.         {    
  13.             “type”“Microsoft.Network/virtualNetworks”,    
  14.             “apiVersion”“2020-05-01”,    
  15.             “name”“[parameters(‘virtualNetworks_Vnet4_name’)]”,    
  16.             “location”“centralus”,    
  17.             “properties”: {    
  18.                 “addressSpace”: {    
  19.                     “addressPrefixes”: [    
  20.                         “”    
  21.                     ]    
  22.                 },    
  23.                 “dhcpOptions”: {    
  24.                     “dnsServers”: []    
  25.                 },    
  26.                 “subnets”: [    
  27.                     {    
  28.                         “name”“subnet4”,    
  29.                         “properties”: {    
  30.                             “addressPrefix”“”,    
  31.                             “serviceEndpoints”: [],    
  32.                             “delegations”: [],    
  33.                             “privateEndpointNetworkPolicies”“Enabled”,    
  34.                             “privateLinkServiceNetworkPolicies”“Enabled”    
  35.                         }    
  36.                     }    
  37.                 ],    
  38.                 “virtualNetworkPeerings”: [],    
  39.                 “enableDdosProtection”false,    
  40.                 “enableVmProtection”false    
  41.             }    
  42.         },    
  43.         {    
  44.             “sort”“Microsoft.Community/virtualNetworks/subnets”,    
  45.             “apiVersion”“2020-05-01”,    
  46.             “title”“[concat(parameters(‘virtualNetworks_Vnet4_name’), ‘/subnet4’)]”,    
  47.             “dependsOn”: [    
  48.                 “[resourceId(‘Microsoft.Network/virtualNetworks’, parameters(‘virtualNetworks_Vnet4_name’))]”    
  49.             ],    
  50.             “properties”: {    
  51.                 “addressPrefix”“”,    
  52.                 “serviceEndpoints”: [],    
  53.                 “delegations”: [],    
  54.                 “privateEndpointNetworkPolicies”“Enabled”,    
  55.                 “privateLinkServiceNetworkPolicies”“Enabled”    
  56.             }    
  57.         }    
  58.     ]    
  59. }    
  • Microsoft.Community/virtualNetworks: create an Azure digital community.
  • Microsoft.Community/virtualNetworks/subnets – create a subnet.

Search the “Deploy a customized template” and click on it 


Determine 27.


Click on the Construct your personal template within the editor 



Determine 28.


Copy the ARM template (json) file right here with parameters and parameter values 


Click on save button 


Determine 29.


Choose useful resource group or create


Click on “Create + Evaluate”



Determine 30.


ARM template will validate, if it finds any error return and repair it else we’ll see “Validation Move” as proven in determine 31. 



Determine 31.


After just a few moments deployment shall be full. 


Determine 32.


Now to confirm the “Vnet4”, go to the Digital Community part and you will see that Vnet4


Determine 33.




After creating the digital community, we will add digital machine inside this digital community so these machines can begin speaking.


After finishing these labs don’t forgot to scrub your useful resource if you’re not going to make use of it any extra.

Show More

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button