This will be multipart article series on DevOps. In this part I am going to configure SCM git (Source control) and push my code to centralized repository on Github.com. For this first I need a system where I will complete all my DevOps Labs configuration and use it as a workstation. I will create a Virtual Machine on Microsoft Azure and use it as a workstation.
If you don't have Azure subscription account, you can sign up free for azure trial account on https://azure.microsoft.com/en-in/free/, which will give you access to Azure subscription for 1 month with worth of 200$ credit to create and test resources.
Article Series:
DevOps Part 1.1 SCM Git - Create Resource Group in Microsoft Azure
DevOps Part 1.2 SCM Git - Create Virtual Network (vNET) in Microsoft Azure
For the first task I am creating a Resource Group,
In Azure, a resource group acts as a container that holds interconnected resources for a specific Azure solution. Its purpose is to provide a logical grouping and management structure for resources within your Azure subscription.
When working with resource groups, you have the flexibility to decide which resources should be included based on your organization's needs. You can choose to place all the resources related to a particular solution in a single resource group or create multiple resource groups to organize resources according to different criteria, such as application, environment, or department.
By organizing resources into resource groups, you gain the ability to manage them collectively. For example, you can easily deploy, update, and remove all the resources within a resource group as a unified entity. Furthermore, resource groups enable you to set access controls and enforce policies specifically on a set of resources.
Resource groups also serve as a scope for managing permissions and applying policies. By managing role-based access control (RBAC) assignments at the resource group level, you can control who has access to the resources within that group. This allows you to assign specific permissions to individuals or groups for managing the resources contained within the resource group.
In essence, Azure resource groups offer a way to logically group and manage interconnected resources, providing organizational and management advantages for your Azure solutions.
To create a new resource group type in search bar on the top, from searched items click Resource Groups.
You will be in the Resource Groups view. Click Create button to create new. I already have few resource groups created. A resource group is a collection of resources that share the same lifecycle, permissions, and policies
An Azure subscription is a payment plan and access level that provides you with the ability to use and manage Azure services and resources. It is the fundamental unit of ownership and access control in Microsoft Azure.
In the Basics select Subscription from list if you have more than one, Provide Resource Group a name and Region (location) where it will be created. As a best practice make sure when you create resources they match with Resource Groups (You can club different region resources in different Resource group as well).
Next Apply Tags to Resource Group to logically organize them by categories. A tag consists of a key (name) and a value. Tag names are case-insensitive and tag values are case-sensitive.
An Azure region refers to a geographical location where Azure data centers are located. Azure regions are strategically distributed around the world to provide customers with global coverage and low-latency access to Azure services and resources.
This is a last part of Review + Create, verify the information of resource and click Create. It takes few seconds, resource group creation succeeded.
Either you can click go to resource group or search it in the list. There are no resources created yet. In the next part I will create Virtual Network (vNET). Inside this resource group.
Useful Articles
Create key vault and secrets with access policies in Microsoft Azure
Working With Azure Key Vault Using Azure PowerShell and AzureCLI
Use Key Vault secret identifier url to get the secret value using Powershell
Use a Azure VM system assigned managed identity to access Azure Key Vault
Create Azure Key Vault Certificates on Azure Portal and Powershell
Export certificates from Azure Key Vault using PowerShell
