Comparing JSON and Bicep for templates
Bicep Playground allows you to view Bicep and equivalent JSON side-by-side. You can compare
implementations of the same infrastructure.
For example, you can see the file to run SQL Server and Database.
Bicep is half the size of the ARM template. Bicep Playground 0.31.34-gec82b47d63
To Modify an existing Bicep file, please refer to the below sources to get more information
Reference existing resource in Bicep - Azure Resource Manager | Microsoft Learn
Create or update Azure custom roles using Bicep - Azure RBAC | Microsoft Learn
Export a deployment as an ARM template or compile a
deployment as a Bicep file
Decompiling the ARM template will help you start bicep development. If you have a library of
ARM templates and want to use Bicep for future development, you can decompile them to
Bicep.
To export a deployment as an ARM template or compile a deployment as a Bicep file,
please refer to this → Decompile ARM template JSON to Bicep
If we want to move the Azure VM from one subscription or region to another
please refer to the
below sources
● Move Azure VMs across regions with Azure Resource Mover
● Special cases to move Azure VMs to new subscription or resource
group
--Back to Index-- 66
B) Create and configure Azure Virtual Machines
Azure Virtual Machines Introduction
There are 3 major delivery models when it comes to Cloud services. They are:
1. SAAS – Software as a Service
2. PAAS – Platform as a Service
3. IAAS - Infrastructure as a Service
● Azure Virtual Machines are part of the IAAS offering from Azure.
● As customers, we are responsible for managing the virtual machine, and just the
hardware will be provided to us by the cloud provider. We can start, stop and delete the
virtual machine.
● If we find that the capacity is insufficient or too high, we can change to a different
machine type. We can install any software as we like.
● Also, please note that this is the most expensive of the three offerings.
● We can create Windows or Linux VMs, and there are multiple locations throughout
the
world where resources can run from.
● When we create a VM, we need to attach a virtual hard disk, and the location that we
specify is where the hard disks are stored.
Here is the SLA table:
--Back to Index-- 67
Please see below details for VM types:
Creating an Azure Virtual Machine
You can create and deploy the Virtual machines in different methods,
Main are
→ Through Azure Portal
→ Through The Azure PowerShell/CLI
→ Through ARM Templates
When you create virtual machines (VMs) in the Azure portal, one of
your first decisions is to
specify which image to use. Azure supports Windows and Linux
operating systems and has
server and client platforms to choose from. You can also search for
other supported images(They
are similar to Windows and linux OS) in the Azure Marketplace:
(Source: Microsoft Documentation)
--Back to Index-- 68
We can create virtual machines by using Azure portal
You can use the Azure portal for reference of the process for creating
the virtual machine image.
(Source: Microsoft Documentation)
The process includes configuring basic and advanced options and
specifying details about disks,
virtual networks, and machine management.
The below are the main key-takeaways for creating a virtual machine.
● The Basics tab contains the project details, administrator account,
and inbound port rules.
● On the Disks tab, you select the OS disk type and specify your data
disks.
● The Networking tab provides settings to create virtual networks and
load balancing.
● On the Management tab, you can enable auto-shutdown and specify
backup details.
● On the Advanced tab, you can configure agents, scripts, or virtual
machine extensions.
● Other settings are available on the Monitoring and Tags tabs.
● If the validation is completed then we need to click the
“Review+Create” tab for final outp
