diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_app_service_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_app_service_arm_template/_index.md index fabdefa8..7eae0eb8 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_app_service_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_app_service_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an App S - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_apimgmt_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_apimgmt_arm_template/_index.md index ae863df0..534a36d2 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_apimgmt_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_apimgmt_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an Azure - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_function_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_function_arm_template/_index.md index 6a2cd81b..23542eb7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_function_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_azure_function_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an App S - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_container_apps_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_container_apps_arm_template/_index.md index 204da50e..fa076313 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_container_apps_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_container_apps_arm_template/_index.md @@ -54,7 +54,7 @@ In this scenario, you will deploy a [Container Apps environment](https://learn.m - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_logic_app_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_logic_app_arm_template/_index.md index 21070e83..033b4e85 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_logic_app_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/aks/aks_logic_app_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an App S - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apimgmt_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apimgmt_arm_template/_index.md index fd017a0f..ee97cacd 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apimgmt_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apimgmt_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have a CAPI Kubernetes cluster deployed wi - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apps_service_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apps_service_arm_template/_index.md index 4cc22325..5210c47d 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apps_service_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/apps_service_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have a CAPI Kubernetes cluster deployed wi - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/azure_function_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/azure_function_arm_template/_index.md index 2af3b909..e1c9ca5e 100644 --- a/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/azure_function_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_app_svc/cluster_api/capi_azure/azure_function_arm_template/_index.md @@ -50,7 +50,7 @@ By the end of this scenario, you will have a CAPI Kubernetes cluster deployed wi - "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_dc_vanilla_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_dc_vanilla_arm_template/_index.md index a6dafb16..9a90a615 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_dc_vanilla_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_dc_vanilla_arm_template/_index.md @@ -53,7 +53,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_mssql_mi_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_mssql_mi_arm_template/_index.md index d52f9517..0fa083cd 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_mssql_mi_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_mssql_mi_arm_template/_index.md @@ -51,7 +51,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_postgresql_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_postgresql_arm_template/_index.md index 968d6e41..e753d9b8 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_postgresql_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/aks/aks_postgresql_arm_template/_index.md @@ -53,7 +53,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_dc_vanilla_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_dc_vanilla_arm_template/_index.md index c52c766a..75690d4f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_dc_vanilla_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_dc_vanilla_arm_template/_index.md @@ -51,7 +51,7 @@ By the end of this scenario, you will have an ARO cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_mssql_mi_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_mssql_mi_arm_template/_index.md index 2e4e5e9c..1b32a5da 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_mssql_mi_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_mssql_mi_arm_template/_index.md @@ -49,7 +49,7 @@ By the end of this scenario, you will have an ARO cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_postgresql_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_postgresql_arm_template/_index.md index 2d4d18ab..793e622e 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_postgresql_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/aro/aro_postgresql_arm_template/_index.md @@ -51,7 +51,7 @@ By the end of this scenario, you will have an ARO cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_dc_vanilla_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_dc_vanilla_arm_template/_index.md index b9b68f7b..d0141580 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_dc_vanilla_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_dc_vanilla_arm_template/_index.md @@ -51,7 +51,7 @@ By the end of this scenario, you will have a CAPI Kubernetes cluster deployed wi - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_mssql_mi_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_mssql_mi_arm_template/_index.md index 0c07e031..d9f265c9 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_mssql_mi_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_mssql_mi_arm_template/_index.md @@ -51,7 +51,7 @@ By the end of this scenario, you will have a CAPI Kubernetes cluster deployed wi - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_postgresql_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_postgresql_arm_template/_index.md index f7ffc85b..39f8c43b 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_postgresql_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/cluster_api/capi_azure_postgresql_arm_template/_index.md @@ -51,7 +51,7 @@ By the end of this scenario, you will have a CAPI Kubernetes cluster deployed wi - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_arm_template_ado/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_arm_template_ado/_index.md index 9d2f5a96..436c0e3c 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_arm_template_ado/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_arm_template_ado/_index.md @@ -46,7 +46,7 @@ By the end of this scenario, you will have an Azure DevOps Release pipeline to d - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_dr/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_dr/_index.md index d256423a..5277a1b4 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_dr/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_dr/_index.md @@ -51,7 +51,7 @@ By the end of this guide, you will have two Azure Kubernetes Service (AKS) clust - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_mi_ad_auth_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_mi_ad_auth_arm_template/_index.md index 846220f0..3b795186 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_mi_ad_auth_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_mi_ad_auth_arm_template/_index.md @@ -49,7 +49,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_migrate/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_migrate/_index.md index 0866de05..a50bea4f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_migrate/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_mssql_migrate/_index.md @@ -49,7 +49,7 @@ By the end of this scenario, you will have an AKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_postgresql_arm_template_ado/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_postgresql_arm_template_ado/_index.md index e5e7bd4a..418ba728 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_postgresql_arm_template_ado/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/day2/aks/aks_postgresql_arm_template_ado/_index.md @@ -46,7 +46,7 @@ By the end of this scenario, you will have an Azure DevOps Release pipeline to d - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_dc_vanilla_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_dc_vanilla_terraform/_index.md index 70a9bce2..4ca78e91 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_dc_vanilla_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_dc_vanilla_terraform/_index.md @@ -39,7 +39,7 @@ By the end of this scenario, you will have an EKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_mssql_mi_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_mssql_mi_terraform/_index.md index 7d5b8c05..bf43df02 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_mssql_mi_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_mssql_mi_terraform/_index.md @@ -39,7 +39,7 @@ By the end of this scenario, you will have an EKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_postgres_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_postgres_terraform/_index.md index f3e89961..bcdfe8fb 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_postgres_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/eks/eks_postgres_terraform/_index.md @@ -41,7 +41,7 @@ By the end of this scenario, you will have an EKS cluster deployed with an Azure - "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - "Monitoring Metrics Publisher" - Required for being Azure Arc-enabled data services billing, monitoring metrics, and logs management - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_dc_vanilla_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_dc_vanilla_terraform/_index.md index 514c0fde..193cc937 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_dc_vanilla_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_dc_vanilla_terraform/_index.md @@ -57,7 +57,7 @@ By the end of this scenario, you will have a GKE cluster deployed with an Azure - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, and logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_mssql_mi_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_mssql_mi_terraform/_index.md index 67729d96..6d207d30 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_mssql_mi_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_mssql_mi_terraform/_index.md @@ -58,7 +58,7 @@ By the end of this scenario, you will have a GKE cluster deployed with an Azure - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, and logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_postgres_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_postgres_terraform/_index.md index 5b7fab79..849a5f7f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_postgres_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/gke/gke_postgres_terraform/_index.md @@ -58,7 +58,7 @@ By the end of this scenario, you will have a GKE cluster deployed with an Azure - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, and logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_dc_vanilla_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_dc_vanilla_arm_template/_index.md index a86dca50..68c2d575 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_dc_vanilla_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_dc_vanilla_arm_template/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have a Kubeadm Kubernetes cluster deployed - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, and logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_mssql_mi_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_mssql_mi_arm_template/_index.md index d71b8ad2..cd63f9e4 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_mssql_mi_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_mssql_mi_arm_template/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have a Kubeadm Kubernetes cluster deployed - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, and logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_postgresql_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_postgresql_arm_template/_index.md index 8c69c3e2..682a592f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_postgresql_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/kubeadm/kubeadm_azure_postgresql_arm_template/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have a Kubeadm Kubernetes cluster deployed - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, and logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_dc_vanilla_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_dc_vanilla_arm_template/_index.md index c322e8de..49ad177f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_dc_vanilla_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_dc_vanilla_arm_template/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have a Microk8s Kubernetes cluster deploye - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_mssql_mi_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_mssql_mi_arm_template/_index.md index 25af066d..cda024ba 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_mssql_mi_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_mssql_mi_arm_template/_index.md @@ -46,7 +46,7 @@ By the end of this scenario, you will have a Microk8s Kubernetes cluster deploye - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_postgresql_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_postgresql_arm_template/_index.md index 5e26a367..d5415260 100644 --- a/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_postgresql_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_data/microk8s/mk8s_postgresql_arm_template/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have a Microk8s Kubernetes cluster deploye - "Owner" - Required for provisioning Azure resources, interact with Azure Arc-enabled data services billing, monitoring metrics, logs management and creating role assignment for the Monitoring Metrics Publisher role. - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_arm_template/_index.md index 8adec0a4..1b53c394 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_arm_template/_index.md @@ -44,7 +44,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Azur - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_terraform/_index.md index efc2c92f..9cd7848f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/aks/aks_terraform/_index.md @@ -30,7 +30,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/aro/aro_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/aro/aro_arm_template/_index.md index f2cc6a0a..9b137163 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/aro/aro_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/aro/aro_arm_template/_index.md @@ -26,7 +26,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Azur - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Owner” role, or “Contributor” and “User Access Administrator” roles are required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Owner” role, or “Contributor” and “User Access Administrator” roles are required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/cluster_api/capi_azure/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/cluster_api/capi_azure/_index.md index d0d587e4..e2c4d1ac 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/cluster_api/capi_azure/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/cluster_api/capi_azure/_index.md @@ -30,7 +30,7 @@ in this scenario, a [Rancher K3s](https://rancher.com/docs/k3s/latest/en/), sing - Create Azure service principal (SP). To deploy this scenario, an Azure service principal assigned with "Contributor" Role-based access control (RBAC) is required for provisioning Azure resources - To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_basic/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_basic/_index.md index 8dafbdfb..f93c91b7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_basic/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_basic/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_helm/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_helm/_index.md index 543bc365..7ce6fb4c 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_helm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_gitops_helm/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_monitor/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_monitor/_index.md index 26ef93ce..1d83ac99 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_monitor/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_monitor/_index.md @@ -30,7 +30,7 @@ in this scenario, you will hook the AKS cluster to Azure Monitor by deploying th * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_policy/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_policy/_index.md index 71c7a1f0..950d1479 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_policy/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/aks/aks_policy/_index.md @@ -72,7 +72,7 @@ The following Jumpstart scenario will guide you on how to enable [Azure Policy f > **Note:** This guide assumes you will be working with a service principal assigned with the 'Contributor' role as described below. If you want to further limit the Role-based access control (RBAC) scope of your service Principal, you can assign it with the 'Policy Insights Data Writer (Preview)' role the Azure Arc-enabled Kubernetes cluster as described [here](https://github.com/MicrosoftDocs/azure-docs/edit/master/articles/governance/policy/concepts/policy-for-kubernetes#L247-L275). - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in Azure Cloud Shell). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in Azure Cloud Shell). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_gitops_helm/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_gitops_helm/_index.md index 13149603..51642ac7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_gitops_helm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_gitops_helm/_index.md @@ -72,7 +72,7 @@ By doing so, you will be able to make real-time changes to the application and s * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command. + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command. ```powershell Connect-AzAccount diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_monitor/aks_hci_monitor_extension/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_monitor/aks_hci_monitor_extension/_index.md index a546d5cc..07562d92 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_monitor/aks_hci_monitor_extension/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/archive/aks_stack_hci/aks_hci_monitor/aks_hci_monitor_extension/_index.md @@ -34,7 +34,7 @@ The commands below and the script described in this scenario should be run on th * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_defender_extension/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_defender_extension/_index.md index 82253ebb..56af2a86 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_defender_extension/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_defender_extension/_index.md @@ -36,7 +36,7 @@ Kubernetes extensions are add-ons for Kubernetes clusters. The extensions featur * "Security admin" - Required for installing Cloud Defender Azure-Arc enabled Kubernetes extension and dismiss alerts * "Security reader" - Required for being able to view Azure-Arc enabled Kubernetes Cloud Defender extension findings - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_basic/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_basic/_index.md index 3295dc01..0b1c6bfa 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_basic/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_basic/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_helm/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_helm/_index.md index 95b6d332..1958b266 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_helm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_gitops_helm/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_keyvault_extension/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_keyvault_extension/_index.md index ac0a2a5e..061dda7e 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_keyvault_extension/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_keyvault_extension/_index.md @@ -32,7 +32,7 @@ Kubernetes extensions are add-ons for Kubernetes clusters. The extensions featur - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_osm_extension/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_osm_extension/_index.md index 8f9f62ee..eb9b8d28 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_osm_extension/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/cluster_api/cluster_api_osm_extension/_index.md @@ -32,7 +32,7 @@ Kubernetes extensions are add-ons for Kubernetes clusters. The extensions featur - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_basic/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_basic/_index.md index e4d83440..d1078c65 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_basic/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_basic/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_helm/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_helm/_index.md index 26c5ef35..6299f4af 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_helm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_gitops_helm/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor/_index.md index 8e6eee32..e2e93437 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor/_index.md @@ -30,7 +30,7 @@ in this scenario, you will hook the GKE cluster to Azure Monitor by deploying th * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor_extension/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor_extension/_index.md index e12f2edd..528d89b5 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor_extension/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_monitor_extension/_index.md @@ -32,7 +32,7 @@ Kubernetes extensions are add-ons for Kubernetes clusters. The extensions featur * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_policy/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_policy/_index.md index 8777534a..078e4949 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_policy/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/gke/gke_policy/_index.md @@ -70,7 +70,7 @@ The following Jumpstart scenario will guide you on how to enable [Azure Policy f > **Note:** This guide assumes you will be working with a service principal assigned with the 'Contributor' role as described below. If you want to further limit the Role-based access control (RBAC) scope of your service Principal, you can assign it with the 'Policy Insights Data Writer (Preview)' role the Azure Arc-enabled Kubernetes cluster as described [here](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/governance/policy/concepts/policy-for-kubernetes.md#install-azure-policy-add-on-for-azure-arc-enabled-kubernetes-preview). -* To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in Azure Cloud Shell). +* To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in Azure Cloud Shell). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/kind/local_kind_gitops_helm/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/kind/local_kind_gitops_helm/_index.md index da995165..977aa743 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/kind/local_kind_gitops_helm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/kind/local_kind_gitops_helm/_index.md @@ -48,7 +48,7 @@ By doing so, you will be able to make real-time changes to the application and s * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_gitops_helm/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_gitops_helm/_index.md index 463e5a1c..00947f98 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_gitops_helm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_gitops_helm/_index.md @@ -42,7 +42,7 @@ GitOps on Azure Arc-enabled Kubernetes uses [Flux](https://fluxcd.io/docs/), a p - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_monitor/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_monitor/_index.md index b0369c5e..b816eed6 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_monitor/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/microk8s/local_microk8s_monitor/_index.md @@ -30,7 +30,7 @@ in this scenario, you will hook the microK8s cluster to Azure Monitor by deployi * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/azure_policy/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/azure_policy/_index.md index 7449162c..6742cf50 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/azure_policy/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/azure_policy/_index.md @@ -47,7 +47,7 @@ Kubernetes extensions are add-ons for Kubernetes clusters. The extensions featur - "Contributor" - Required for provisioning Azure resources - "Resource Policy Contributor" - Required to assign Azure Policy definition - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/container_insights/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/container_insights/_index.md index 412bea9a..e0da25dd 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/container_insights/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/day2/multi_distributions/container_insights/_index.md @@ -46,7 +46,7 @@ Kubernetes extensions are add-ons for Kubernetes clusters. The extensions featur - "Contributor" - Required for provisioning Azure resources - To create it login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To create it login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/developer/dapr/dapr_statestore/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/developer/dapr/dapr_statestore/_index.md index 72090a48..c8db894d 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/developer/dapr/dapr_statestore/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/developer/dapr/dapr_statestore/_index.md @@ -36,7 +36,7 @@ Dapr is a portable, event-driven runtime that makes it easy for any developer to - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/general/onboard_k8s/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/general/onboard_k8s/_index.md index 6d816038..76f2eccd 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/general/onboard_k8s/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/general/onboard_k8s/_index.md @@ -28,7 +28,7 @@ The following Jumpstart scenario will guide you on how to connect an existing Ku * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/gke/gke_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/gke/gke_terraform/_index.md index 04a8d9bd..2e6ca527 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/gke/gke_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/gke/gke_terraform/_index.md @@ -30,7 +30,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/kind/local_kind/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/kind/local_kind/_index.md index 65ed8067..615f5b3b 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/kind/local_kind/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/kind/local_kind/_index.md @@ -38,7 +38,7 @@ The following Jumpstart scenario will guide you on how to use [kind](https://kin * Create Azure service principal (SP) - The Azure service principal assigned with the "Contributor" role is required to complete the scenario and its related automation. To create it, log in to your Azure account run the below command (you could also do this in [Azure Cloud Shell](https://shell.azure.com/). + The Azure service principal assigned with the "Contributor" role is required to complete the scenario and its related automation. To create it, log in to your Azure account run the below command (you could also do this in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/microk8s/local_microk8s/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/microk8s/local_microk8s/_index.md index 0fce511c..c71bdfcb 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/microk8s/local_microk8s/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/microk8s/local_microk8s/_index.md @@ -30,7 +30,7 @@ The following Jumpstart scenario will guide you on how to use [MicroK8s](https:/ - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/pf9/pf9_bareos/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/pf9/pf9_bareos/_index.md index a74b0b4f..d48845ea 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/pf9/pf9_bareos/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/pf9/pf9_bareos/_index.md @@ -45,7 +45,7 @@ The following Jumpstart scenario will guide on how to deploy a Kubernetes cluste - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_arm_template/_index.md index 13442ce6..d72fec38 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_arm_template/_index.md @@ -26,7 +26,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Azur - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_terraform/_index.md index a6ed2275..7360573c 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/azure_terraform/_index.md @@ -28,7 +28,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/vmware_terraform/_index.md b/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/vmware_terraform/_index.md index 7537a103..2a78631a 100644 --- a/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/vmware_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_k8s/rancher_k3s/vmware_terraform/_index.md @@ -30,7 +30,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_ml/aks/aks_blob_mnist_arm_template/_index.md b/docs/azure_arc_jumpstart/azure_arc_ml/aks/aks_blob_mnist_arm_template/_index.md index 1668b48b..5ad097cc 100644 --- a/docs/azure_arc_jumpstart/azure_arc_ml/aks/aks_blob_mnist_arm_template/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_ml/aks/aks_blob_mnist_arm_template/_index.md @@ -67,7 +67,7 @@ To demonstrate the various architecture components, the ML pipeline we deploy is - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/aws/aws_terraform_ubuntu/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/aws/aws_terraform_ubuntu/_index.md index 82584c49..7f07241b 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/aws/aws_terraform_ubuntu/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/aws/aws_terraform_ubuntu/_index.md @@ -46,7 +46,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To connect the AWS virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the AWS virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_linux/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_linux/_index.md index 4812227d..d968f4db 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_linux/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_linux/_index.md @@ -28,7 +28,7 @@ However, **for demo purposes only**, the below guide will allow you to use and o - Create Azure service principal (SP). - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_win/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_win/_index.md index 9e3999d5..a28e77f7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_win/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/azure/azure_arm_template_win/_index.md @@ -28,7 +28,7 @@ However, **for demo purposes only**, the below guide will allow you to use and o - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_builtin_profiles/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_builtin_profiles/_index.md index 4a700a76..9390c255 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_builtin_profiles/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_builtin_profiles/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have an Azure Arc-enabled server with Azur - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_custom_profiles/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_custom_profiles/_index.md index 585993ba..749251c0 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_custom_profiles/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_automanage/arc_automanage_custom_profiles/_index.md @@ -48,7 +48,7 @@ By the end of this scenario, you will have an Azure Arc-enabled server with Azur - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_azuresentinel/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_azuresentinel/_index.md index 2656e97a..fc0d28f1 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_azuresentinel/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_azuresentinel/_index.md @@ -42,7 +42,7 @@ in this scenario, you will enable and configure Microsoft Sentinel on your Azure - Create Azure service principal (SP). - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_datadog/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_datadog/_index.md index 7328941d..72b1c9d1 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_datadog/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_datadog/_index.md @@ -39,7 +39,7 @@ The following Jumpstart scenario will guide you on how to onboard an Azure Arc-e - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_defender/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_defender/_index.md index 8a30106f..938ad15e 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_defender/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_defender/_index.md @@ -49,7 +49,7 @@ in this scenario, you will enable and configure Microsoft Defender for Cloud on - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_extended_security_updates/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_extended_security_updates/_index.md index 4a91935e..e6820a5f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_extended_security_updates/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_extended_security_updates/_index.md @@ -20,7 +20,7 @@ In this scenario, you can choose between working with Windows Server 2012 R2, SQ - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_policies_mma/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_policies_mma/_index.md index d2b6ddae..a8daf68e 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_policies_mma/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_policies_mma/_index.md @@ -47,7 +47,7 @@ Please review the [Azure Monitor supported OS documentation](https://learn.micro - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_run_command/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_run_command/_index.md index 535b62fc..0296cba7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_run_command/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_run_command/_index.md @@ -50,7 +50,7 @@ The following Jumpstart scenario will guide you on how to use the Run command on ```shell az connectedmachine show --name --resource-group --query "properties.agentVersion" ``` -- If the Connected Machine agent version is lower than 1.39 then upgrade the extension using [this guidance](https://learn.microsoft.com/en-us/azure/azure-arc/servers/manage-agent). +- If the Connected Machine agent version is lower than 1.39 then upgrade the extension using [this guidance](https://learn.microsoft.com/azure/azure-arc/servers/manage-agent). - To use PowerShell you need to check if the installed version of module _Az.ConnectedMachine_ is 0.6.0 or higher. Use the following PowerShell command to check the installed version: diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_ssh/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_ssh/_index.md index 6b128fe2..7031ddac 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_ssh/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_ssh/_index.md @@ -35,7 +35,7 @@ The following Jumpstart scenario will guide you on how to enable [SSH access to - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_vm_extension_customscript_arm/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_vm_extension_customscript_arm/_index.md index ffafe718..5490026b 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_vm_extension_customscript_arm/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/day2/arc_vm_extension_customscript_arm/_index.md @@ -37,7 +37,7 @@ You can use the Azure portal, Azure CLI, an ARM template, PowerShell or Linux Sh - Create Azure Service Principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_ubuntu/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_ubuntu/_index.md index 74899995..e4143e39 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_ubuntu/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_ubuntu/_index.md @@ -56,7 +56,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To connect the GCP virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the GCP virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_windows/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_windows/_index.md index f7ec2200..f34198af 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_windows/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/gcp/gcp_terraform_windows/_index.md @@ -38,7 +38,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To connect the GCP virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the GCP virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_linux/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_linux/_index.md index 1edbef5b..a07188e3 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_linux/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_linux/_index.md @@ -20,7 +20,7 @@ The following Jumpstart scenario will guide you on how to connect an Linux serve - Create Azure service principal (SP) - To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_win/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_win/_index.md index f2670cd0..e2690dd7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_win/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_win/_index.md @@ -20,7 +20,7 @@ The following Jumpstart scenario will guide you on how to connect an Windows mac - Create Azure service principal (SP) - To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/aws_scaled_ansible/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/aws_scaled_ansible/_index.md index bbe0254c..45db7341 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/aws_scaled_ansible/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/aws_scaled_ansible/_index.md @@ -52,7 +52,7 @@ This guide can be used even if you do not already have an existing Ansible test - Create Azure service principal (SP) - To connect the AWS virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the AWS virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_runscript/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_runscript/_index.md index 78fac8d3..8ba859a7 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_runscript/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_runscript/_index.md @@ -23,7 +23,7 @@ This guide assumes that you already have an installation of [Microsoft Configura - Create Azure service principal (SP) - To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_tasksequence/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_tasksequence/_index.md index ea68730d..13b61538 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_tasksequence/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/configuration_manager_scaled_tasksequence/_index.md @@ -21,7 +21,7 @@ This guide assumes that you already have an installation of [Microsoft Configura - Create Azure service principal (SP) - To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a server to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_linux/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_linux/_index.md index ffde7e71..3751b70f 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_linux/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_linux/_index.md @@ -69,7 +69,7 @@ This guide assumes you already have an exiting inventory of VMware Virtual Machi - Create Azure service principal (SP) - To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_win/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_win/_index.md index 750f425f..ff5907af 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_win/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/scaled_deployment/vmware_scaled_powercli_win/_index.md @@ -47,7 +47,7 @@ This guide assumes you already have an exiting inventory of VMware Virtual Machi - Create Azure service principal (SP) - To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_ubuntu/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_ubuntu/_index.md index fd1d9372..aaa78e95 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_ubuntu/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_ubuntu/_index.md @@ -40,7 +40,7 @@ The following Jumpstart scenario will guide you on how to deploy a local **Ubunt - Create Azure service principal (SP) - To connect the Vagrant virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the Vagrant virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_windows/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_windows/_index.md index 438ed1f6..0edbd073 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_windows/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/vagrant/local_vagrant_windows/_index.md @@ -40,7 +40,7 @@ The following Jumpstart scenario will guide you on how to deploy a local **Windo - Create Azure service principal (SP) - To connect the Vagrant virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the Vagrant virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_ubuntu/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_ubuntu/_index.md index 534623a4..c2343286 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_ubuntu/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_ubuntu/_index.md @@ -32,7 +32,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_winsrv/_index.md b/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_winsrv/_index.md index 7bcbc10f..b69ed9f3 100644 --- a/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_winsrv/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_servers/vmware/vmware_terraform_winsrv/_index.md @@ -32,7 +32,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr - Create Azure service principal (SP) - To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/aws/aws_terraform_winsrv/_index.md b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/aws/aws_terraform_winsrv/_index.md index 0b9f3068..b2b7e20d 100644 --- a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/aws/aws_terraform_winsrv/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/aws/aws_terraform_winsrv/_index.md @@ -31,7 +31,7 @@ By the end of the guide, you will have an AWS EC2 instance installed with Window * Create Azure service principal (SP) - To connect the EC2 instance to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the EC2 instance to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/azure/azure_arm_template_sqlsrv_winsrv_defender/_index.md b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/azure/azure_arm_template_sqlsrv_winsrv_defender/_index.md index 6840c138..8a5e447e 100644 --- a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/azure/azure_arm_template_sqlsrv_winsrv_defender/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/azure/azure_arm_template_sqlsrv_winsrv_defender/_index.md @@ -33,7 +33,7 @@ By the end of the guide, you will have an Azure VM **JS-Client** installed with - Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Owner” role is required. To create it, login to your Azure account by running the below commands (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Owner” role is required. To create it, login to your Azure account by running the below commands (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/day2/esu/_index.md b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/day2/esu/_index.md index f2c01c3a..a53a0ab2 100644 --- a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/day2/esu/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/day2/esu/_index.md @@ -20,7 +20,7 @@ In this scenario, you will be able to choose between working with Windows Server - Create Azure service principal (SP) - To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect a VM or bare-metal server to Azure Arc, Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/gcp/gcp_terraform_winsrv/_index.md b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/gcp/gcp_terraform_winsrv/_index.md index a41215e6..81ea06a2 100644 --- a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/gcp/gcp_terraform_winsrv/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/gcp/gcp_terraform_winsrv/_index.md @@ -40,7 +40,7 @@ By the end of the guide, you will have a GCP VM instance installed with Windows * Create Azure service principal (SP) - To connect the GCP virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the GCP virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/vmware/vmware_terraform_winsrv/_index.md b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/vmware/vmware_terraform_winsrv/_index.md index e69edf9d..56a36a57 100644 --- a/docs/azure_arc_jumpstart/azure_arc_sqlsrv/vmware/vmware_terraform_winsrv/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_sqlsrv/vmware/vmware_terraform_winsrv/_index.md @@ -32,7 +32,7 @@ By the end of the guide, you will have a VMware vSphere VM installed with Window - Create Azure service principal (SP) - To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To connect the VMware vSphere virtual machine to Azure Arc, an Azure service principal assigned with the "Contributor" role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_arc_vsphere/day2/vmware_arm_template_win/_index.md b/docs/azure_arc_jumpstart/azure_arc_vsphere/day2/vmware_arm_template_win/_index.md index 33c4ea35..ca21d7e8 100644 --- a/docs/azure_arc_jumpstart/azure_arc_vsphere/day2/vmware_arm_template_win/_index.md +++ b/docs/azure_arc_jumpstart/azure_arc_vsphere/day2/vmware_arm_template_win/_index.md @@ -28,7 +28,7 @@ The following Jumpstart scenario will guide you on how to use the provided ARM t - Create Azure service principal (SP). - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full/_index.md b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full/_index.md index b38d8ad0..c9d7f34d 100644 --- a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full/_index.md +++ b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full/_index.md @@ -26,7 +26,7 @@ The following Jumpstart scenario will show how to Create an AKS Edge Essentials - Create Azure service principal (SP) - To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full_akri/_index.md b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full_akri/_index.md index d39567ca..dec79cfa 100644 --- a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full_akri/_index.md +++ b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_full_akri/_index.md @@ -28,7 +28,7 @@ Akri is an open source project for a Kubernetes resource interface that lets you - Create Azure service principal (SP) - To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single/_index.md b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single/_index.md index 9f4cf707..0086ff74 100644 --- a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single/_index.md +++ b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single/_index.md @@ -30,7 +30,7 @@ However, **for demo purposes only**, the below guide will allow you to use and o - Create Azure service principal (SP) - To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_akri/_index.md b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_akri/_index.md index 961570c4..9e9918b4 100644 --- a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_akri/_index.md +++ b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_akri/_index.md @@ -32,7 +32,7 @@ However, **for demo purposes only**, the below guide will allow you to use and o - Create Azure service principal (SP) - To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_esa/_index.md b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_esa/_index.md index a1c8c433..35e5a0a7 100644 --- a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_esa/_index.md +++ b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_edge_essentials_single_esa/_index.md @@ -35,7 +35,7 @@ The automation in this scenario deploys Edge Storage Accelerator on an AKS Edge - Create Azure service principal (SP) - To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To complete the scenario and its related automation, an Azure service principal with the “Contributor” role assigned is required. To create it, login to your Azure account and run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_iot_edge_terraform/_index.md b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_iot_edge_terraform/_index.md index f25fdc6e..ca068059 100644 --- a/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_iot_edge_terraform/_index.md +++ b/docs/azure_arc_jumpstart/azure_edge_iot_ops/aks_iot_edge_terraform/_index.md @@ -32,7 +32,7 @@ The following Jumpstart scenario will guide you on how to use the provided [Terr * Create Azure service principal (SP) - To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/). + To be able to complete the scenario and its related automation, Azure service principal assigned with the “Contributor” role is required. To create it, login to your Azure account run the below Bash shell command (this can also be done in [Azure Cloud Shell](https://shell.azure.com/)). ```shell az login diff --git a/docs/azure_jumpstart_ag/manufacturing/contoso_motors/ai_inferencing/_index.md b/docs/azure_jumpstart_ag/manufacturing/contoso_motors/ai_inferencing/_index.md index 0a87010a..d1b2feb2 100644 --- a/docs/azure_jumpstart_ag/manufacturing/contoso_motors/ai_inferencing/_index.md +++ b/docs/azure_jumpstart_ag/manufacturing/contoso_motors/ai_inferencing/_index.md @@ -33,18 +33,18 @@ The Edge AI inference flow can be divided into two configuration steps and three | Model | Scenario | Links | | ----- | -------- | ----- | | Yolo8 | Object detection | [Yolo8 Models](https://docs.ultralytics.com/modes/#introduction) | - | Safety-Yolo | Helmet detection | *[safety-yolo8.bin](https://jsfiles.blob.core.windows.net/ai-models/safety-yolo8.bin)*, *[safety-yolo8.xml](https://jsfiles.blob.core.windows.net/ai-models/safety-yolo8.xml)* | - | Weld-porosity | Weld porosity detection (no weld, weld, porosity) | *[weld-porosity-detection-0001.bin](https://jsfiles.blob.core.windows.net/ai-models/weld-porosity-detection-0001.bin)*, *[weld-porosity-detection-0001.xml](https://jsfiles.blob.core.windows.net/ai-models/weld-porosity-detection-0001.xml)* | - | Pose-estimation | Human pose estimation | *[human-pose-estimation-0007.bin](https://jsfiles.blob.core.windows.net/ai-models/human-pose-estimation-0007.bin)*, *[human-pose-estimation-0007.xml](https://jsfiles.blob.core.windows.net/ai-models/human-pose-estimation-0007.xml)* | + | Safety-Yolo | Helmet detection | *[safety-yolo8.bin](https://jumpstartprodsg.blob.core.windows.net/ai-models/safety-yolo8.bin)*, *[safety-yolo8.xml](https://jumpstartprodsg.blob.core.windows.net/ai-models/safety-yolo8.xml)* | + | Weld-porosity | Weld porosity detection (no weld, weld, porosity) | *[weld-porosity-detection-0001.bin](https://jumpstartprodsg.blob.core.windows.net/ai-models/weld-porosity-detection-0001.bin)*, *[weld-porosity-detection-0001.xml](https://jumpstartprodsg.blob.core.windows.net/ai-models/weld-porosity-detection-0001.xml)* | + | Pose-estimation | Human pose estimation | *[human-pose-estimation-0007.bin](https://jumpstartprodsg.blob.core.windows.net/ai-models/human-pose-estimation-0007.bin)*, *[human-pose-estimation-0007.xml](https://jumpstartprodsg.blob.core.windows.net/ai-models/human-pose-estimation-0007.xml)* | 1. **Video Downloader:** this is an init-container in Kubernetes responsible for downloading sample video files used to simulate an RTSP video feed. All video streams are simulated using the **RTSP Simulator**. The videos are downloaded from the storage account and stored in a Kubernetes volume for use in the deployment. | Video | Scenario | Link | | ----- | -------- | ---- | - | Worker on normal routine | Object detection | *[object-detection.mp4](https://jsfiles.blob.core.windows.net/video/agora/object-detection.mp4)* | - | Worker walking with safety-gear | Helmet detection | *[helmet-detection.mp4](https://jsfiles.blob.core.windows.net/video/agora/helmet-detection.mp4)* | - | Welding feed | Weld porosity detection | *[welding.mp4](https://jsfiles.blob.core.windows.net/video/agora/welding.mp4)* | - | Worker interacting with robot | Human pose estimation | *[object-detection.mp4](https://jsfiles.blob.core.windows.net/video/agora/object-detection.mp4)* | + | Worker on normal routine | Object detection | *[object-detection.mp4](https://jumpstartprodsg.blob.core.windows.net/video/agora/object-detection.mp4)* | + | Worker walking with safety-gear | Helmet detection | *[helmet-detection.mp4](https://jumpstartprodsg.blob.core.windows.net/video/agora/helmet-detection.mp4)* | + | Welding feed | Weld porosity detection | *[welding.mp4](https://jumpstartprodsg.blob.core.windows.net/video/agora/welding.mp4)* | + | Worker interacting with robot | Human pose estimation | *[object-detection.mp4](https://jumpstartprodsg.blob.core.windows.net/video/agora/object-detection.mp4)* | After the configuration is complete, the inference flow can be initiated. The **Web AI Inference and UI** application retrieves data, such as video frames from an RTSP source or images, and applies any necessary preprocessing, such as resizing an image to a specific size with a specific RGB/BGR format. The data is then sent to the model server for inference, and any required post processing is applied to store or display the results to the user. diff --git a/docs/azure_jumpstart_ag/manufacturing/contoso_motors/workers_safety/_index.md b/docs/azure_jumpstart_ag/manufacturing/contoso_motors/workers_safety/_index.md index 4ee6cdec..5fb14b64 100644 --- a/docs/azure_jumpstart_ag/manufacturing/contoso_motors/workers_safety/_index.md +++ b/docs/azure_jumpstart_ag/manufacturing/contoso_motors/workers_safety/_index.md @@ -54,7 +54,7 @@ If you're interested in learning more about the AI inference flow, check out the ### Model -The model was created by the Arc Jumpstart team, based on the [Yolo8](https://yolov8.com/) model. The model files can be downloaded from [safety-yolo8.bin](https://jsfiles.blob.core.windows.net/ai-models/safety-yolo8.bin) and [safety-yolo8.xml](https://jsfiles.blob.core.windows.net/ai-models/safety-yolo8.xml). +The model was created by the Arc Jumpstart team, based on the [Yolo8](https://yolov8.com/) model. The model files can be downloaded from [safety-yolo8.bin](https://jumpstartprodsg.blob.core.windows.net/ai-models/safety-yolo8.bin) and [safety-yolo8.xml](https://jumpstartprodsg.blob.core.windows.net/ai-models/safety-yolo8.xml). #### Inputs diff --git a/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/_index.md b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/_index.md index 04871fdf..57c9d85c 100644 --- a/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/_index.md +++ b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/_index.md @@ -118,9 +118,13 @@ Contoso's DevOps team has received a request from the _Chicago_ store managers t - Connect to the Client VM _Ag-VM-Client_ using the instructions in the [deployment guide](../deployment/#connecting-to-the-agora-client-virtual-machine). +- We need to have "Docker Desktop" running in the background. Open it from the Start menu and have it minimized. + + ![Screenshot showing opening Docker Dekstop from the start menu](./img/start_docker_desktop.png) + - Open VSCode from the desktop shortcut. - ![Screenshot showing the the VSCode icon on the desktop](./img/open_vscode.png) + ![Screenshot showing the VSCode icon on the desktop](./img/open_vscode.png) - Bring up the VSCode command palette. diff --git a/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/img/start_docker_desktop.png b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/img/start_docker_desktop.png new file mode 100644 index 00000000..2c85453f Binary files /dev/null and b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ai/img/start_docker_desktop.png differ diff --git a/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/_index.md b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/_index.md index aecf6c73..b4c15420 100644 --- a/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/_index.md +++ b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/_index.md @@ -97,6 +97,10 @@ The development process will start from the local _dev_ cluster, where as a deve - Connect to the Client VM _Ag-VM-Client_ using the instructions in the [deployment guide](../deployment/#connecting-to-the-agora-client-virtual-machine). +- We need to have "Docker Desktop" running in the background. Open it from the Start menu and have it minimized. + + ![Screenshot showing opening Docker Dekstop from the start menu](./img/start_docker_desktop.png) + - Open VSCode from the desktop shortcut. ![Screenshot showing the the VSCode icon on the desktop](./img/open_vscode.png) diff --git a/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/img/start_docker_desktop.png b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/img/start_docker_desktop.png new file mode 100644 index 00000000..2c85453f Binary files /dev/null and b/docs/azure_jumpstart_ag/retail/contoso_supermarket/ci_cd/img/start_docker_desktop.png differ diff --git a/docs/release_notes/_index.md b/docs/release_notes/_index.md index c961efb2..c49509f0 100644 --- a/docs/release_notes/_index.md +++ b/docs/release_notes/_index.md @@ -9,6 +9,45 @@ weight: 6 > **Note:** Release notes will be released around the first week of each month and will cover the previous month. +## June 2024 + +### Release highlights + +- Various critical bugs fixes and features +- Jumpstart Assets - Arc Architecture Posters and Diagrams (APD) [June release](https://www.linkedin.com/feed/update/urn:li:activity:7211732533040799744/) + +### Jumpstart HCIBox + +- [Bug: High MTU (9014) causes network congestion on nested VMs when using Windows Server 20348.2340.240303 or later #2579](https://github.com/microsoft/azure_arc/issues/2579) +- [Feature: HCI box unable to create RG - Unable to acquire a token error. #2571](https://github.com/microsoft/azure_arc/issues/2571) + +### Arc-enabled data services + +- [Feature: Azure Arc-enabled data services - June release #2582](https://github.com/microsoft/azure_arc/issues/2582) + +## May 2024 + +### Release highlights + +- Maintenance release + +### Cross Jumpstart + +- [Feature: Remove use of SAS tokens for VHD downloads #2551](https://github.com/microsoft/azure_arc/issues/2551) + +### Jumpstart ArcBox + +- [Feature: Leverage Managed Identity for authentication #2550](https://github.com/microsoft/azure_arc/issues/2550) + +### Jumpstart HCIBox + +- [Bug: Failed to deploy HCIBox: failure when processing extension 'Bootstrap' Missing an argument for parameter 'spnProviderId' #2541](https://github.com/microsoft/azure_arc/issues/2541) +- [Bug: Syntax error line 169 - preprovision.ps1 #2546](https://github.com/microsoft/azure_arc/issues/2546) + +### Arc-enabled servers + +- [Bug: Failed to deploy Azure Arc-enabled servers connectivity behind a proxy server #303](https://github.com/Azure/arc_jumpstart_docs/issues/303) + ## April 2024 ### Release highlights @@ -26,6 +65,10 @@ weight: 6 - [Feature: Update HCIBox VHDX images for April release #2524](https://github.com/microsoft/azure_arc/issues/2524) - [Documentation: Jumpstart HCIBox 23H2 Deployment - Where or how to get Windows Admin Center #2490](https://github.com/microsoft/azure_arc/issues/2490) +### Arc-enabled servers + +- [Documentation: Code snippet to create service principal for Microsoft Azure: Windows Server Virtual Machine has error, causing it to fail #285](https://github.com/Azure/arc_jumpstart_docs/issues/285) + ### Arc-enabled data services - [Feature: Azure Arc-enabled data services - April release #2495](https://github.com/microsoft/azure_arc/issues/2495)