You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: learn-pr/azure/provision-linux-virtual-machine-in-azure/2-provision-linux-virtual-machine-using-the-azure-portal.yml
Copy file name to clipboardExpand all lines: learn-pr/azure/provision-linux-virtual-machine-in-azure/3-provision-linux-virtual-machine-using-azure-cli.yml
Copy file name to clipboardExpand all lines: learn-pr/azure/provision-linux-virtual-machine-in-azure/4-provision-linux-virtual-machine-using-terraform.yml
Copy file name to clipboardExpand all lines: learn-pr/azure/provision-linux-virtual-machine-in-azure/includes/1-introduction.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ The Azure CLI is a cross-platform command-line tool that you can use to access A
18
18
19
19
### Terraform
20
20
21
-
Terraform is an open-source, multiplatform Infrastructure as Code (IaC) tool that you can use to provision and configure a wide range of environments, including multivendor public and private clouds. Unlike Azure CLI—which provides an _imperative approach_ to resource management—Terraform follows a _declarative_ approach.
21
+
Terraform is an open-source, multiplatform Infrastructure as Code (IaC) tool that you can use to provision and configure a wide range of environments, including multivendor public and private clouds. Unlike Azure CLI—which provides an _imperative approach_ to resource management—Terraform follows a _declarative_ approach.
22
22
23
23
An imperative approach involves writing scripts or running a sequence of commands. You explicitly provide the steps to run to produce a desired outcome. When you use imperative deployments, it's your responsibility to manage dependencies, error handling, and resource updates. A declarative approach involves writing a definition that describes the desired outcome, rather than the steps to implement it; the tooling determines the optimal method to deliver that outcome for you. It does this by inspecting the current state of your environment, comparing it to your target state, and then implementing the changes required to make them identical.
24
24
@@ -40,7 +40,7 @@ Azure supports two types of templates for declarative provisioning:
40
40
41
41
You can use both these templates to deploy practically any Azure resource. These templates also easily integrate into version-control systems and deployment pipelines, resulting in improved automation and reliability. However, in comparison to Azure Resource Manager templates, Bicep templates offer several additional benefits, including more concise syntax and built-in dependency management.
42
42
43
-
## What will we be doing?
43
+
## What will we learn?
44
44
45
45
In this module, you'll choose the optimal deployment method of provisioning Linux VMs in Azure. Your choice will be dependent on the criteria that have been established during the deployment planning phase.
Copy file name to clipboardExpand all lines: learn-pr/azure/provision-linux-virtual-machine-in-azure/includes/2-provision-linux-virtual-machine-using-the-azure-portal.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ On the Virtual machines page, select the **+ Create** link. This step is the sam
32
32
33
33
### Assign resource-specific settings
34
34
35
-
The settings you assign at this stage will determine the properties of the deployed resource. Although you can modify most of the settings after deployment, there are some settings that are immutable. The immutable settings include the resource name and the operating system (OS) image, so it's important to carefully consider their assignments. In addition, some of the modifiable settings might impact the resource availability if changed after deployment. For example, you can change an online Azure VM's resource group, but moving it across virtual networks, subscriptions, and regions (although possible) will result in downtime. Similarly, changing the Azure VM size, while straightforward and commonly done, requires an OS restart.
35
+
The settings you assign at this stage determine the properties of the deployed resource. Although you can modify most of the settings after deployment, there are some settings that are immutable. The immutable settings include the resource name and the operating system (OS) image, so it's important to carefully consider their assignments. In addition, some of the modifiable settings might impact the resource availability if changed after deployment. For example, you can change an online Azure VM's resource group, but moving it across virtual networks, subscriptions, and regions (although possible) results in downtime. Similarly, changing the Azure VM size, while straightforward and commonly done, requires an OS restart.
36
36
37
37
> [!NOTE]
38
38
> Microsoft doesn't support moving resources across subscriptions associated with different Microsoft Entra ID tenants, and provisioning multiple resources that are part of a larger deployment should follow a planning stage that determines their optimal configuration, including a naming convention.
@@ -65,7 +65,7 @@ The settings on this page configure the target subscription, either an existing
65
65
66
66
67
67
> [!CAUTION]
68
-
> If you deploy an individual Azure VM for testing or evaluation purposes, you might choose to allow connectivity from the internet due to the convenience it provides. However, in general, you should avoid exposing Azure VMs to connections originating from the internet without additional constraints. To enhance security in such scenarios, consider implementing Azure Bastion or just-in-time (JIT) VM access, which is available as part of the Defender for Cloud service. Azure also offers hybrid connectivity options, including Site-to-Site (S2S) virtual private network (VPN), Point-to-Site (P2S) VPN, and Azure ExpressRoute. All three options eliminate the need for assigning public IP addresses to Azure VM network interfaces for connections originating from your on-premises datacenter or designated, internet-connected computers.
68
+
> If you deploy an individual Azure VM for testing or evaluation purposes, you might choose to allow connectivity from the internet due to the convenience it provides. However, in general, you should avoid exposing Azure VMs to connections originating from the internet without additional constraints. To enhance security in such scenarios, consider implementing Azure Bastion or just-in-time (JIT) VM access, which is available as part of the Defender for Cloud service. Azure also offers hybrid connectivity options, including Site-to-Site (S2S) virtual private network (VPN), Point-to-Site (P2S) VPN, and Azure ExpressRoute. All three options eliminate the need for assigning public IP addresses to Azure VM network interfaces for connections originating from your on-premises datacenter or designated, internet-connected computers.
Copy file name to clipboardExpand all lines: learn-pr/azure/provision-linux-virtual-machine-in-azure/includes/3-provision-linux-virtual-machine-using-azure-cli.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ You can install Azure CLI locally on Linux, macOS, and Windows operating systems
5
5
6
6
To use Azure CLI interactively, launch a shell available within your operating system, such as cmd.exe in Windows, or Bash in Linux or macOS, and then issue a command at the command prompt. To automate repetitive tasks, assemble the CLI commands into a shell script using your chosen shell's script syntax, then run the script.
7
7
8
-
If you want to avoid installing Azure CLI, you can use Azure Cloud Shell. Azure Cloud Shell is an interactive, authenticated shell that you can use to manage Azure resources from a web browser. Azure Cloud Shell can run Bash and Azure PowerShell, and it has the current version of Azure CLI already preinstalled. To access Azure Cloud Shell, open the [Azure Cloud Shell](https://shell.azure.com/) link in a web browser or launch it from the Azure portal by selecting the Azure Cloud Shell icon next to the global search textbox.
8
+
If you want to avoid installing Azure CLI, you can use Azure Cloud Shell. Azure Cloud Shell is an interactive, authenticated shell that you can use to manage Azure resources from a web browser. Azure Cloud Shell can run Bash and Azure PowerShell, and it has the current version of Azure CLI already preinstalled. To access Azure Cloud Shell, open the [Azure Cloud Shell](https://shell.azure.com/) link in a web browser or launch it from the Azure portal by selecting the **Cloud Shell** icon next to the global search textbox.
9
9
10
10
11
11
@@ -21,7 +21,7 @@ The process of provisioning an Azure VM running Linux by using Azure CLI typical
21
21
- Create and configure a virtual network.
22
22
- Create an Azure VM.
23
23
24
-
Depending on your existing environment and requirements, it might not be necessary to complete each of the preceding steps. For example, you might use an existing resource group or a virtual network subnet for your deployment. In addition, Azure CLI supports a wide range of default settings, which automatically apply if you decide not to explicitly assign values to some of the resource settings. For example, as with the Azure portal-based deployment, if you don't specify an existing virtual network, Azure CLI will automatically provision one for you. In this module, you'll rely on the Azure CLI default settings and skip the process of creating a virtual network.
24
+
Depending on your existing environment and requirements, it might not be necessary to complete each of the preceding steps. For example, you might use an existing resource group or a virtual network subnet for your deployment. In addition, Azure CLI supports a wide range of default settings, which automatically apply if you decide not to explicitly assign values to some of the resource settings. For example, as with the Azure portal-based deployment, if you don't specify an existing virtual network, Azure CLI automatically provisions one for you. In this module, you'll rely on the Azure CLI default settings and skip the process of creating a virtual network.
25
25
26
26
> [!NOTE]
27
27
> For information regarding implementing virtual networks by using Azure CLI, refer to [Quickstart: Use Azure CLI to create a virtual network](/azure/virtual-network/quick-create-cli).
@@ -45,7 +45,7 @@ az vm image list-publishers --location eastus --query [].name --output tsv | gre
45
45
```
46
46
47
47
> [!NOTE]
48
-
> The list is quite extensive, so you should ensure that you limit the output to the available session buffer.
48
+
> The list is quite extensive, so you should ensure that you limit the output to the available session buffer. To exit the list, you can use **CTRL** + **C** on your keyboard.
49
49
50
50
Assume you chose `Canonical`. Next, identify the offers available from that publisher by running the following command:
51
51
@@ -79,7 +79,7 @@ In addition to image availability, you also should ensure that the VM size you i
79
79
az vm list-sizes --location eastus --output table
80
80
```
81
81
82
-
Identify the VM size suitable for your sample deployment from the listing and note the value in the Name column. You'll need to enter the name in the identical format when running the Azure CLI command that initiates the Azure VM provisioning. Assume you chose *Standard_F4s*.
82
+
Identify the VM size suitable for your sample deployment from the listing and note the value in the *Name* column. You'll need to enter the name in the identical format when running the Azure CLI command that initiates the Azure VM provisioning. Assume you chose *Standard_F4s*.
83
83
84
84
> [!IMPORTANT]
85
85
> Before you proceed, verify that this VM size is available in the Azure region you're targeting, and if needed, adjust the values of parameters in the subsequent commands accordingly.
0 commit comments