Skip to content

Commit 24dd868

Browse files
updated wording and date for managed run command windows
1 parent 6277eab commit 24dd868

File tree

1 file changed

+8
-1
lines changed

1 file changed

+8
-1
lines changed

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

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.service: virtual-machines
66
ms.collection: windows
77
author: nikhilpatel909
88
ms.author: erd
9-
ms.date: 11/03/2022
9+
ms.date: 03/10/2023
1010
ms.topic: how-to
1111
ms.reviewer: erd
1212
ms.custom: devx-track-azurepowershell, devx-track-azurecli
@@ -28,6 +28,13 @@ 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+
## Limiting access to Run Command
32+
33+
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.
34+
35+
Running a command requires the `Microsoft.Compute/virtualMachines/runCommand/write` permission. The [Virtual Machine Contributor](../../role-based-access-control/built-in-roles.md#virtual-machine-contributor) role and higher levels have this permission.
36+
37+
You can use one of the [built-in roles](../../role-based-access-control/built-in-roles.md) or create a [custom role](../../role-based-access-control/custom-roles.md) to use Run Command.
3138

3239
## Azure CLI
3340

0 commit comments

Comments
 (0)