diff --git a/docs/azure_jumpstart_hcibox/deployment_az/_index.md b/docs/azure_jumpstart_hcibox/deployment_az/_index.md index a18c14df..1af47a05 100644 --- a/docs/azure_jumpstart_hcibox/deployment_az/_index.md +++ b/docs/azure_jumpstart_hcibox/deployment_az/_index.md @@ -9,7 +9,7 @@ weight: 4 ## Azure CLI -Azure CLI can be used to deploy HCIBox into your Azure subscription. Azure CLI is recommended if you have been provided a service principal by your Azure administrator for use with HCIBox. If you can create application registrations in Microsoft Entra ID, then [Azure Developer CLI](/azure_jumpstart_hcibox/deployment_azd) will be the optimal deployment option that satisfies most other prerequisites. Otherwise, read on to learn how to deploy HCIBox with Azure CLI. +Azure CLI is used to deploy HCIBox into your Azure subscription. To deploy, you require a service principal by your Azure administrator for use with HCIBox. Read on to learn how to deploy HCIBox with Azure CLI. ### Prepare the environment diff --git a/docs/azure_jumpstart_hcibox/deployment_azd/_index.md b/docs/azure_jumpstart_hcibox/deployment_azd/_index.md deleted file mode 100644 index df7e43f8..00000000 --- a/docs/azure_jumpstart_hcibox/deployment_azd/_index.md +++ /dev/null @@ -1,55 +0,0 @@ ---- -type: docs -linkTitle: "Azure Developer CLI Deployment" -isGettingStarted: false -weight: 3 ---- -# Deploy HCIBox infrastructure with Azure Developer CLI - -[Azure Developer CLI](https://learn.microsoft.com/azure/developer/azure-developer-cli/overview) automates the creation or retrieval of several HCIBox deployment requirements. It's best used when the deploying user has permission to [create applications in Microsoft Entra ID](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#cloud-application-administrator). - -## Prepare environment - -- Clone the Azure Arc Jumpstart repository - - ```shell - git clone https://github.com/microsoft/azure_arc.git - ``` - -- Follow to install guide for the [Azure Developer CLI](https://learn.microsoft.com/azure/developer/azure-developer-cli/install-azd?tabs=winget-windows%2Cbrew-mac%2Cscript-linux&pivots=os-linux) for your environment. - - > **Note:** PowerShell is required for using azd with HCIBox. If you are running in a Linux environment be sure that you have [PowerShell for Linux](https://learn.microsoft.com/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.3) installed. - -- Login with azd using *`azd auth login`* which will open a browser for interactive login. - - ![Screenshot showing azd auth login](./azd_auth_login.png) - -- Run the *`azd init`* command from the _*azure_jumpstart_hcibox*_ folder within your cloned repo. - - ![Screenshot showing azd init](./azd_init.png) - -## Deploy the environment - -- Run the *`azd up`* command to deploy the environment. Azd will prompt you to enter the target subscription, region, and all required parameters. It is highly recommended to use _eastus_ as your region. - - > **Note:** It is possible that you might experience an error such as "Unable to acquire token". Please run ```Connect-AzAccount``` in PowerShell with the correct credential and re-run ```azd up```. Reference: [https://github.com/microsoft/azure_arc/issues/2443](https://github.com/microsoft/azure_arc/issues/2443). - - ![Screenshot showing azd up](./azd_up.png) - -- Wait for the deployment to complete, then continue by logging into the _HCIBox-Client_ VM using RDP or Bastion. - -## Start post-deployment automation - -Once your deployment is complete, you can open the Azure portal and see the initial HCIBox resources inside your resource group. Now you must remote into the _HCIBox-Client_ VM to continue the next phase of the deployment. [Continue in Cloud Deployment guide](/azure_jumpstart_hcibox/cloud_deployment) for the next steps. - - ![Screenshot showing all deployed resources in the resource group](./deployed_resources.png) - -## Clean up the deployment - -After you are finished with your HCIBox deployment use ```azd down``` to delete your resources. - - ```Azure Developer CLI - azd down - ``` - - ![Screenshot showing azd down](./azd_down.png) diff --git a/docs/azure_jumpstart_hcibox/deployment_azd/azd_auth_login.png b/docs/azure_jumpstart_hcibox/deployment_azd/azd_auth_login.png deleted file mode 100644 index fbee7c60..00000000 Binary files a/docs/azure_jumpstart_hcibox/deployment_azd/azd_auth_login.png and /dev/null differ diff --git a/docs/azure_jumpstart_hcibox/deployment_azd/azd_down.png b/docs/azure_jumpstart_hcibox/deployment_azd/azd_down.png deleted file mode 100644 index 4306b2d4..00000000 Binary files a/docs/azure_jumpstart_hcibox/deployment_azd/azd_down.png and /dev/null differ diff --git a/docs/azure_jumpstart_hcibox/deployment_azd/azd_init.png b/docs/azure_jumpstart_hcibox/deployment_azd/azd_init.png deleted file mode 100644 index fdbdbdad..00000000 Binary files a/docs/azure_jumpstart_hcibox/deployment_azd/azd_init.png and /dev/null differ diff --git a/docs/azure_jumpstart_hcibox/deployment_azd/azd_up.png b/docs/azure_jumpstart_hcibox/deployment_azd/azd_up.png deleted file mode 100644 index 96ca8e5b..00000000 Binary files a/docs/azure_jumpstart_hcibox/deployment_azd/azd_up.png and /dev/null differ diff --git a/docs/azure_jumpstart_hcibox/deployment_azd/deployed_resources.png b/docs/azure_jumpstart_hcibox/deployment_azd/deployed_resources.png deleted file mode 100644 index 9db38d5b..00000000 Binary files a/docs/azure_jumpstart_hcibox/deployment_azd/deployed_resources.png and /dev/null differ diff --git a/docs/azure_jumpstart_hcibox/getting_started/_index.md b/docs/azure_jumpstart_hcibox/getting_started/_index.md index 58c13f05..1ef13a6c 100644 --- a/docs/azure_jumpstart_hcibox/getting_started/_index.md +++ b/docs/azure_jumpstart_hcibox/getting_started/_index.md @@ -57,8 +57,7 @@ Deploying HCIBox is a multi-step process that includes: ![Screenshot showing deployment flow diagram for Bicep-based deployments](./deployment_flow.png) ## Deploy HCIBox -- [Deploy HCIBox with Azure Developer CLI](/azure_jumpstart_hcibox/deployment_azd) : Best for those with access to Microsoft Entra ID -- [Deploy HCIBox with Azure CLI](/azure_jumpstart_hcibox/deployment_az) : Alternative to Microsoft Entra ID, requires pre-configured service principle. +- [Deploy HCIBox with Azure CLI](/azure_jumpstart_hcibox/deployment_az) : Requires pre-configured service principle. Looking for something else related to HCIBox?