Scribd
Upload
11 views3 pages

azuer basic 21

The document provides a step-by-step guide for deploying a virtual network and managing virtual machines using Azure templates and extensions. It introduces Bicep, a domain-specific language for deploying Azure resources, highlighting its features such as declarative syntax, modularity, and tooling support. Additionally, it explains the benefits of using Bicep for improved maintainability and integration with Azure services.

Uploaded by

Mahmud Rayhan Shajib
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
11 views3 pages

azuer basic 21

The document provides a step-by-step guide for deploying a virtual network and managing virtual machines using Azure templates and extensions. It introduces Bicep, a domain-specific language for deploying Azure resources, highlighting its features such as declarative syntax, modularity, and tooling support. Additionally, it explains the benefits of using Bicep for improved maintainability and integration with Azure services.

Uploaded by

Mahmud Rayhan Shajib
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

You see a blank template.

4. Replace the blank template with the following template.


5. It deploys a virtual network with a subnet → then Select Save Option.
6. You see the blade for providing deployment values. Again, select
myResourceGroup for the
resource group. You can use the other default values. When you're done providing
values,
select Review + create.
7. After the portal validates the template, select Create.
8. When the deployment is complete, you will see the deployment status.
This time select a resource group name.
9. Notice that your resource group now contains a storage account and a virtual
network.
--Back to Index-- 60
Pls Refer to the below links for more information
● Deploy template - Azure portal - Azure Resource Manager | Microsoft Learn
● Tutorial - Create and deploy template - Azure Resource Manager | Microsoft Learn
Virtual machines extensions
● Creating and managing virtual machines can be difficult and burdensome.
● Also many of the maintenance tasks are repetitive and time consuming. To solve
this there are
several ways to automate the tasks of creating, managing and removing virtual
machines.
● Virtual machine extension is one way to meet our needs.
● Extensions are small apps that provide post-deployment configuration &
automation on VMs.
● The Azure platform hosts a number of extensions that cover VM configuration,
monitoring,
security, and utility applications.
Example: Consider a scenario where a virtual machine needs software installation
or anti-virus
protection, or when a machine configuration script needs to be run.
You can use virtual machine extensions to accomplish these tasks. Extensions are
all about
managing your virtual machines.
You can apply VM extensions to an existing VM through the Azure portal. Select the
VM in the
portal, select Extensions, and then select Add. Select the extension you want from
the list of
available extensions and follow the instructions in the wizard.
Below image shows the installation of the Microsoft Antimalware extension from the
Azure portal:
--Back to Index-- 61
Fore more information → Virtual machine extensions and features for
Windows
Bicep File Overview
Bicep is a domain-specific language (DSL) for deploying Azure resources declaratively. It
simplifies the authoring of Azure Resource Manager (ARM) templates by providing a
more readable and maintainable syntax.
--Back to Index-- 62
Source: What is Bicep? - Azure Resource Manager | Microsoft Learn
Key Features:
● Declarative Syntax: Bicep uses a declarative syntax to define Azure resources,
making
it easier to read and write compared to JSON-based ARM templates.
● Modularity: You can break down complex deployments into smaller, reusable
modules, promoting better organization and reuse of code.
● Type Safety: Bicep provides type safety and validation at compile time, reducing
errors and improving reliability.
● Tooling Support: Bicep integrates with Visual Studio Code, offering features
like
IntelliSense, syntax highlighting, and error checking.
● Automatic Conversion: You can decompile existing ARM templates into Bicep
files,
facilitating the transition from JSON to Bicep.
Basic Structure:
A Bicep file typically includes:
● Parameters: Define inputs to the deployment.
● Variables: Store values that can be reused throughout the file.
● Resources: Declare the Azure resources to be deployed.
● Outputs: Specify values to be returned after deployment.
--Back to Index-- 63
Example:
Here’s a simple example of a Bicep file that deploys an Azure Storage account:
param storageAccountName string
param location string = resourceGroup().location
resource storageAccount 'Microsoft.Storage/storageAccounts@2021-04-01' = {
name: storageAccountName
location: location
sku: {
name: 'Standard_LRS'
}k
ind: 'StorageV2'
}o
utput storageAccountName string = storageAccount.name
Benefits:
● Simple Syntax: Easier to write and understand compared to JSON.
● Improved Maintainability: Modular structure and reusable components.
● Enhanced Tooling: Better development experience with integrated tools.
● Support for all resource types and API versions: Immediate
support for Azure services
[for both preview and GA versions]
● Modularity: You can use modules to break up your bicep code into manageable
chunks.
Comprehensive Support for all Azure service resource types and API
versions, alongside
modularity for organizing your Bicep code into manageable segments.
● Modularity: You can use modules to break up your bicep code into manageable
chunks.
● Azure services integrations: Bicep integrates with Azure services[ Azure
Policy, template
specs, and Azure Blueprints].
● Preview updates/Changes: You can use the what-if operation to preview
the changes
before running the Bicep file.
● No state or state files to manage: All state is stored in Azure. Users can
contribute and
be confident that their updates are performed as expected.
● No Cost and Open Source: Since Bicep is completely free, you don't need
to pay for
premium capabilities. It is also supported by

You might also like