Skip to content

Commit 3ad5938

Browse files
authored
Update deploy-cli.md
added detail to 'Create' command and 'Show'
1 parent 94332f5 commit 3ad5938

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

articles/azure-arc/resource-bridge/deploy-cli.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ Checks the configuration files for a valid schema, cloud and core validations (s
3333

3434
Downloads the OS images from Microsoft and uploads them to the on-premises cloud image gallery to prepare for the creation of the appliance VM.
3535

36-
This command can take up to 30 minutes to complete, depending on the network download speed. Allow the command to complete before continuing with the deployment.
36+
This command can take about 15-30+ minutes to complete, depending on the network speed. Allow the command to complete before continuing with the deployment.
3737

3838
## az arcappliance deploy
3939

@@ -43,11 +43,19 @@ Deploys an on-premises instance of Arc resource bridge as an appliance VM, boots
4343

4444
Creates Arc resource bridge in Azure as an ARM resource, then establishes the connection between the ARM resource and on-premises appliance VM.
4545

46-
Running this command is the last step in the deployment process.
46+
Once the `create` command initiates the connection, it will return in the terminal even though the connection between the ARM resource and on-premise appliance VM is not yet complete. The resource bridge needs about 5 minutes to establish the connection between the ARM resource and the on-premise VM.
4747

4848
## az arcappliance show
4949

50-
Gets the ARM resource information for Arc resource bridge. This information helps you monitor the status of the appliance. Successful appliance creation results in `ProvisioningState = Succeeded` and `Status = Running`.
50+
Gets the status of the Arc resource bridge and ARM resource information.
51+
52+
While the Arc resource bridge is connecting the ARM resource to the on-premise VM, the resource bridge will progress through the stages below:
53+
54+
`ProvisioningState` will be `Creating`, `Created`, `Failed`, `Deleting`, or `Succeeded`.
55+
56+
`Status` will transition between `WaitingForHeartbeat` -> `Validating` -> `Connected` -> `Running`.
57+
58+
Successful Arc resource bridge creation results in `ProvisioningState = Succeeded` and `Status = Running`.
5159

5260
## az arcappliance delete
5361

0 commit comments

Comments
 (0)