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: articles/trusted-signing/quickstart.md
+38-31Lines changed: 38 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,16 +47,38 @@ A resource provider is a service that supplies Azure resources. Use the Azure po
47
47
48
48
# [Azure CLI](#tab/registerrp-cli)
49
49
50
-
You can register Trusted Signing resource provider with the commands below:
50
+
1. If you're using a local installation, login to Azure CLI using the `az login` command.
51
+
52
+
2. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
53
+
54
+
3. When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the [Azure CLI](/cli/azure/azure-cli-extensions-overview).
55
+
56
+
4. To see the versions of Azure CLI and dependent libraries that are installed, use the `az version` command.
57
+
• To upgrade to the latest version, use the following command:
58
+
59
+
```bash
60
+
az upgrade [--all {false, true}]
61
+
[--allow-preview {false, true}]
62
+
[--yes]
63
+
```
64
+
65
+
5. To set your default subscription ID, use the `az account set -s <subscriptionId>` command.
66
+
67
+
6. You can register Trusted Signing resource provider with the command below:
51
68
52
69
```
53
70
az provider register --namespace "Microsoft.CodeSigning"
54
71
```
55
72
56
-
You can verify that registration is complete with the commands below:
73
+
7. You can verify that registration is complete with the command below:
74
+
75
+
```
76
+
az provider show --namespace "Microsoft.CodeSigning"
77
+
```
57
78
79
+
8. You can add the extension for Trusted Signing with the command below:
58
80
```
59
-
az provider show --namespace "microsoft.ConfidentialLedger"
81
+
az extension add --name trustedsigning
60
82
```
61
83
62
84
---
@@ -120,32 +142,13 @@ The resources must be created in Azure regions where Trusted Signing is currentl
120
142
121
143
Complete the following steps to create a Trusted Signing account with Azure CLI:
122
144
123
-
1. If you're using a local installation, login to Azure CLI using the `az login` command.
124
-
125
-
2. To finish the authentication process, follow the steps displayed in your terminal. For other sign-in options, see [Sign in with the Azure CLI](/cli/azure/authenticate-azure-cli).
126
-
127
-
3. When you're prompted, install the Azure CLI extension on first use. For more information about extensions, see Use extensions with the [Azure CLI](/cli/azure/azure-cli-extensions-overview).
128
-
129
-
4. To see the versions of Azure CLI and dependent libraries that are installed, use the `az version` command.
130
-
• To upgrade to the latest version, use the following command:
131
-
132
-
```bash
133
-
az upgrade [--all {false, true}]
134
-
[--allow-preview {false, true}]
135
-
[--yes]
136
-
```
137
-
138
-
5. To set your default subscription ID, use the `az account set -s <subscriptionId>` command.
139
-
140
-
6. Create a resource group using the following command:
145
+
1. Create a resource group using the following command (Skip this step if you plan to use an existing resource group):
141
146
142
147
```
143
148
az group create --name MyResourceGroup --location EastUS
144
149
```
145
150
146
-
- To list accounts under the resource group, use the `trustedsigning list -g MyResourceGroup` command.
147
-
148
-
7. Create a unique Trusted Signing account using the following command. (See the below Certificate Profile naming constraints for naming requirements.)
151
+
2. Create a unique Trusted Signing account using the following command. (See the below Certificate Profile naming constraints for naming requirements.)
0 commit comments