Page Comparison

Overview

...

When you create a new Microsoft Azure Cloud Provider the Cloud Management Platform (CMP): HyperCloud™ Platform

• Discovers Resource Manager Network and Security
• Lets Administrators and Users to create and manage these resources:
  
  
  • [CMP] Microsoft Azure Network & Security Services ManagementResource Groups
  • Virtual Private Cloud (Microsoft Azure vNet)
  • Subnets
  • Security Groups    

Anchor
Resource Groups Resource Groups

Resource Groups

...

Resource Groups are logical containers that hold your Microsoft Azure resources. All resources in a resource group must have the same life-cycle. You can deploy, update, and delete multiple resources in a resource group. 

Create a Resource Group

...

To create a new Resource Group:

...

Once you've created a resource group, you'll need to create a Virtual Private Cloud (VPC) for the same. 

Anchor
Virtual Private Cloud Virtual Private Cloud

Virtual Private Cloud (Microsoft Azure vNet)

...

Virtual private cloud in the Cloud Management Platform is addressed as Virtual Private Cloud (VPC) or Microsoft Azure vNet.

...

• Logically isolated from other networks
• Has its own firewall capabilities
• Scoped to a single Microsoft Azure Region.  

• A network made up of subnets. A subnet is a range of IP addresses in your virtual network. Like VPC networks, subnets are scoped to a single Microsoft Azure Region.

  Info
  title Info
  Microsoft Azure Virtual Network lets Microsoft Azure Virtual Machines (VM) securely communicate with: Each other Internet On-premise networks.

  
  

Create a Virtual Private Cloud (Microsoft Azure vNet)

...

To create a Microsoft Azure VPC:

1. Login to your CMP account.
2. Navigate to Service Orchestration > Services > Networks > Virtual Private Cloud > New > Azure.
   
   
3. Select your Microsoft Azure cloud Provider.
4. Select your Resource Group.
5. Enter a Name for your VPC. .
6. Enter a Description for your resource group. This is an optional field. 

7. Select your subnet IPV4 CIDR.

   Note
   icon false title Note
   The CMP validates of your CIDR for validity and overlaps. Newly created subnets must be within your IPV4 CIDR range. Subnets cannot not overlap. Info title Info To know more about IPV4 CIDR refer to the article on Understanding CIDR notation when designing Azure Virtual networks and subnets.

   
   

8. Enter the Subnet Name and the Subnet CIDR for your VPC.
   The CMP automatically creates a subnet when you create a VPC. You can add more subnets to your VPC later.

9. Click CREATE VPC.

Anchor
Subnets Subnets

Create Subnets

...

To add more subnets to your newly created VPC:

1. Login to your CMP account.
2. Navigate to Service Orchestration > Services > Networks > Virtual Private Cloud > Click to select your VPC > Actions > Create New Subnet.
   
   
3. Enter the following in the New Subnet dialog:
   
   1. Enter a Name for your subnet.
   2. Enter a Description for your subnet. This is an optional field. 
   3. Select your subnet IPV4 CIDR

   4. Click CREATE SUBNET.

      Note
      icon false title Note
      You can delete inactive or unused subnets. You'll not be able to delete a VPC unless you delete all the Subnets associated with the VPC.

      
      

Anchor
Security Groups Security Groups

Security Groups

...

Security Groups form an important layer of security firewall rules that:

• Control your VM traffic
• Let you filter your Microsoft Azure virtual network traffic
• Lets you tag your resources for resource tracking and management

Create a Security Group

...

To create a Security Group:

1. Login to your CMP account.
2. Navigate to Service Orchestration > Services > Security > Security Group.
3. Click New and select Azure.
   
   
4. From the Create Security Group dialog, select your Resource Pool. 
   
   
5. Select your Resource Group.
6. Enter a name for your Security Group.
7. Enter a Description for your security group. This is an optional field. 
8. Click Create. 

Create Inbound and Outbound Rules

...

Once you've created a Security Group, click your Security Group to add Firewall Rules. 

Anchor
Inbound Rule Inbound Rule

Add an Inbound Rule -  Needs verification

...

To add an Inbound Rule:

1. From the Security Group dialog, click Actions > Add Inbound Rule.
   
   
2. Enter a Name for your Inbound Rule.
3. Enter a Description for your subnet. This is an optional field. 
4. Enter a value for the Rule Priority. This field determines the precedence that other rules will take over your rule.
5. Choose:
   1. Allow or Deny to define the Rule Action that your firewall needs to perform. 
   2. Protocol from these options:
      • Any
      • TCP
      • UDP
   3. Any or IP Range to define the IP filter of your firewall.
   4. Any or Custom to define the port range filter of your firewall.  
   5. Any or IP Range to define the IP filter for the destination firewall.  
   6. Any or Custom Port Range to define the port filter for the destination firewall.  

Add an Outbound Rule

...

To Add an Outbound Rule:

1. From the Security Group dialog, click Actions > Add Outbound Rule.
2. Rest of the process is similar to that of Adding an Inbound Rule.