Skip to content

Commit 24577fe

Browse files
GabstaMSFTGabstaMSFT
committed
Updating CPLat Extension OS Support Information
1 parent 73abcd6 commit 24577fe

File tree

7 files changed

+109
-30
lines changed

7 files changed

+109
-30
lines changed

‎articles/virtual-machines/extensions/custom-script-linux.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,19 @@ Please switch new and existing deployments to use Version 2. The new version is
2828

2929
## Prerequisites
3030

31-
### Operating system
32-
33-
The Custom Script Extension for Linux will run on supported operating systems. For more information, see [Endorsed Linux distributions on Azure](../linux/endorsed-distros.md).
31+
### Linux Distro’s Supported
32+
| **Linux Distro** | **x64** | **ARM64** |
33+
|:-----|:-----:|:-----:|
34+
| Alma Linux | 9.x+ | 9.x+ |
35+
| CentOS | 7.x+, 8.x+ | 7.x+ |
36+
| Debian | 10+ | 11.x+ |
37+
| Flatcar Linux | 3374.2.x+ | 3374.2.x+ |
38+
| openSUSE | 12.3+ | Not Supported |
39+
| Oracle Linux | 6.4+, 7.x+, 8.x+ | Not Supported |
40+
| Red Hat Enterprise Linux | 6.7+, 7.x+, 8.x+ | 8.6+, 9.0+ |
41+
| Rocky Linux | 9.x+ | 9.x+ |
42+
| SLES | 12.x+, 15.x+ | 15.x SP4+ |
43+
| Ubuntu | 18.04+, 20.04+, 22.04+ | 20.04+, 22.04+ |
3444

3545
### Script location
3646

‎articles/virtual-machines/extensions/custom-script-windows.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -23,21 +23,21 @@ This article details how to use the Custom Script Extension by using the Azure P
2323
> [!NOTE]
2424
> Don't use the Custom Script Extension to run `Update-AzVM` with the same VM as its parameter, because it will wait for itself.
2525
26-
### Operating system
27-
28-
The Custom Script Extension for Windows will run on these supported operating systems:
29-
30-
* Windows Server 2008 R2
31-
* Windows Server 2012
32-
* Windows Server 2012 R2
33-
* Windows 10
34-
* Windows Server 2016
35-
* Windows Server 2016 Core
36-
* Windows Server 2019
37-
* Windows Server 2019 Core
38-
* Windows Server 2022
39-
* Windows Server 2022 Core
40-
* Windows 11
26+
### **Windows OS’ Supported**
27+
| **Windows OS** | **x64** |
28+
|:----|:----:|
29+
| Windows 10 | Supported |
30+
| Windows 11 | Supported |
31+
| Windows Server 2008 SP2 | Supported |
32+
| Windows Server 2008 R2 | Supported |
33+
| Windows Server 2012 | Supported |
34+
| Windows Server 2012 R2 | Supported |
35+
| Windows Server 2016 | Supported |
36+
| Windows Server 2016 Core | Supported |
37+
| Windows Server 2019 | Supported |
38+
| Windows Server 2019 Core | Supported |
39+
| Windows Server 2022 | Supported |
40+
| Windows Server 2022 Core | Supported |
4141

4242
### Script location
4343

‎articles/virtual-machines/extensions/vmaccess.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -21,20 +21,22 @@ This article shows you how to use the Azure VMAccess Extension to check or repai
2121
> If you use the VMAccess Extension to reset the password of your VM after installing the AAD Login Extension you will need to rerun the AAD Login Extension to re-enable AAD Login for your machine.
2222
2323
## Prerequisites
24-
### Operating system
2524

2625
The VM Access extension can be run against these Linux distributions:
2726

28-
| Distribution | Version |
29-
|---|---|
30-
| Ubuntu | 16.04 LTS, 14.04 LTS and 12.04 LTS |
31-
| Debian | Debian 7.9+, 8.2+ |
32-
| Red Hat | RHEL 6.7+, 7.1+ |
33-
| Oracle Linux | 6.4+, 7.0+ |
34-
| Suse | 11 and 12 |
35-
| OpenSuse | openSUSE Leap 42.2+ |
36-
| CentOS | CentOS 6.3+, 7.0+ |
37-
| CoreOS | 494.4.0+ |
27+
### Linux Distro’s Supported
28+
| **Linux Distro** | **x64** | **ARM64** |
29+
|:-----|:-----:|:-----:|
30+
| Alma Linux | 9.x+ | 9.x+ |
31+
| CentOS | 7.x+, 8.x+ | 7.x+ |
32+
| Debian | 10+ | 11.x+ |
33+
| Flatcar Linux | 3374.2.x+ | 3374.2.x+ |
34+
| openSUSE | 12.3+ | Not Supported |
35+
| Oracle Linux | 6.4+, 7.x+, 8.x+ | Not Supported |
36+
| Red Hat Enterprise Linux | 6.7+, 7.x+, 8.x+ | 8.6+, 9.0+ |
37+
| Rocky Linux | 9.x+ | 9.x+ |
38+
| SLES | 12.x+, 15.x+ | 15.x SP4+ |
39+
| Ubuntu | 18.04+, 20.04+, 22.04+ | 20.04+, 22.04+ |
3840

3941
## Ways to use the VMAccess Extension
4042
There are two ways that you can use the VMAccess Extension on your Linux VMs:

‎articles/virtual-machines/linux/run-command-managed.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,22 @@ The *updated* managed Run Command uses the same VM agent channel to execute scri
2828
- Support for long running (hours/days) scripts
2929
- Passing secrets (parameters, passwords) in a secure manner
3030

31+
## Prerequisites
32+
33+
### Linux Distro’s Supported
34+
| **Linux Distro** | **x64** | **ARM64** |
35+
|:-----|:-----:|:-----:|
36+
| Alma Linux | 9.x+ | Not Supported |
37+
| CentOS | 7.x+, 8.x+ | Not Supported |
38+
| Debian | 10+ | Not Supported |
39+
| Flatcar Linux | 3374.2.x+ | Not Supported |
40+
| openSUSE | 12.3+ | Not Supported |
41+
| Oracle Linux | 6.4+, 7.x+, 8.x+ | Not Supported |
42+
| Red Hat Enterprise Linux | 6.7+, 7.x+, 8.x+ | Not Supported |
43+
| Rocky Linux | 9.x+ | Not Supported |
44+
| SLES | 12.x+, 15.x+ | Not Supported |
45+
| Ubuntu | 18.04+, 20.04+, 22.04+ | Not Supported |
46+
3147
## Limiting access to Run Command
3248

3349
Listing the run commands or showing the details of a command requires the `Microsoft.Compute/locations/runCommands/read` permission on Subscription level. The built-in [Reader](../../role-based-access-control/built-in-roles.md#reader) role and higher levels have this permission.

‎articles/virtual-machines/linux/run-command.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,22 @@ You can access your virtual machines in multiple ways. Run Command can run scrip
2424

2525
This capability is useful in all scenarios where you want to run a script within a virtual machine. It's one of the only ways to troubleshoot and remediate a virtual machine that doesn't have the RDP or SSH port open because of network or administrative user configuration.
2626

27+
## Prerequisites
28+
29+
### Linux Distro’s Supported
30+
| **Linux Distro** | **x64** | **ARM64** |
31+
|:-----|:-----:|:-----:|
32+
| Alma Linux | 9.x+ | 9.x+ |
33+
| CentOS | 7.x+, 8.x+ | 7.x+ |
34+
| Debian | 10+ | 11.x+ |
35+
| Flatcar Linux | 3374.2.x+ | 3374.2.x+ |
36+
| openSUSE | 12.3+ | Not Supported |
37+
| Oracle Linux | 6.4+, 7.x+, 8.x+ | Not Supported |
38+
| Red Hat Enterprise Linux | 6.7+, 7.x+, 8.x+ | 8.6+, 9.0+ |
39+
| Rocky Linux | 9.x+ | 9.x+ |
40+
| SLES | 12.x+, 15.x+ | 15.x SP4+ |
41+
| Ubuntu | 18.04+, 20.04+, 22.04+ | 20.04+, 22.04+ |
42+
2743
## Restrictions
2844

2945
The following restrictions apply when you're using Run Command:

‎articles/virtual-machines/windows/run-command-managed.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,24 @@ The *updated* managed Run Command uses the same VM agent channel to execute scri
2828
- Support for long running (hours/days) scripts
2929
- Passing secrets (parameters, passwords) in a secure manner
3030

31+
## Prerequisites
32+
33+
### **Windows OS’ Supported**
34+
| **Windows OS** | **x64** |
35+
|:----|:----:|
36+
| Windows 10 | Supported |
37+
| Windows 11 | Supported |
38+
| Windows Server 2008 SP2 | Supported |
39+
| Windows Server 2008 R2 | Supported |
40+
| Windows Server 2012 | Supported |
41+
| Windows Server 2012 R2 | Supported |
42+
| Windows Server 2016 | Supported |
43+
| Windows Server 2016 Core | Supported |
44+
| Windows Server 2019 | Supported |
45+
| Windows Server 2019 Core | Supported |
46+
| Windows Server 2022 | Supported |
47+
| Windows Server 2022 Core | Supported |
48+
3149
## Limiting access to Run Command
3250

3351
Listing the run commands or showing the details of a command requires the `Microsoft.Compute/locations/runCommands/read` permission on Subscription Level. The built-in [Reader](../../role-based-access-control/built-in-roles.md#reader) role and higher levels have this permission.

‎articles/virtual-machines/windows/run-command.md

Lines changed: 18 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,30 @@ ms.devlang: azurecli
1616

1717
The Run Command feature uses the virtual machine (VM) agent to run PowerShell scripts within an Azure Windows VM. You can use these scripts for general machine or application management. They can help you to quickly diagnose and remediate VM access and network issues and get the VM back to a good state.
1818

19-
2019
## Benefits
2120

2221
You can access your virtual machines in multiple ways. Run Command can run scripts on your virtual machines remotely by using the VM agent. You use Run Command through the Azure portal, [REST API](/rest/api/compute/virtual-machines/run-command), or [PowerShell](/powershell/module/az.compute/invoke-azvmruncommand) for Windows VMs.
2322

2423
This capability is useful in all scenarios where you want to run a script within a virtual machine. It's one of the only ways to troubleshoot and remediate a virtual machine that doesn't have the RDP or SSH port open because of improper network or administrative user configuration.
2524

25+
## Prerequisites
26+
27+
### **Windows OS’ Supported**
28+
| **Windows OS** | **x64** |
29+
|:----|:----:|
30+
| Windows 10 | Supported |
31+
| Windows 11 | Supported |
32+
| Windows Server 2008 SP2 | Supported |
33+
| Windows Server 2008 R2 | Supported |
34+
| Windows Server 2012 | Supported |
35+
| Windows Server 2012 R2 | Supported |
36+
| Windows Server 2016 | Supported |
37+
| Windows Server 2016 Core | Supported |
38+
| Windows Server 2019 | Supported |
39+
| Windows Server 2019 Core | Supported |
40+
| Windows Server 2022 | Supported |
41+
| Windows Server 2022 Core | Supported |
42+
2643
## Restrictions
2744

2845
The following restrictions apply when you're using Run Command:

0 commit comments

Comments
 (0)