Skip to content
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

Commit a5c8071

Browse files
authored
Fix some typos
1 parent eca1425 commit a5c8071

1 file changed

Lines changed: 19 additions & 20 deletions

File tree

Instructions/Labs/AZ400_M07_Integrating_Azure_Key_Vault_with_Azure_DevOps.md

Lines changed: 19 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -11,20 +11,19 @@ lab:
1111

1212
Azure Key Vault provides secure storage and management of sensitive data, such as keys, passwords, and certificates. Azure Key Vault includes supports for hardware security modules, as well as a range of encryption algorithms and key lengths. By using Azure Key Vault, you can minimize the possibility of disclosing sensitive data through source code, which is a common mistake made by developers. Access to Azure Key Vault requires proper authentication and authorization, supporting fine grained permissions to its content.
1313

14-
In this lab, you will see how you can integrate Azure Key Vault with an Azure DevOps pipeline by using the following steps:
14+
In this lab, you will see how you can integrate Azure Key Vault with an Azure Pipelines by using the following steps:
1515

16-
- create an Azure Key vault to store a MySQL server password as a secret.
17-
- create an Azure service principal to provide access to secrets in the Azure Key vault.
18-
- configure permissions to allow the service principal to read the secret.
19-
- configure pipeline to retrieve the password from the Azure Key vault and pass it on to subsequent tasks.
16+
- create an Azure Key vault to store a ACR password as a secret.
17+
- create an Azure Service Principal to provide access to secrets in the Azure Key Vault.
18+
- configure permissions to allow the Service Principal to read the secret.
19+
- configure pipeline to retrieve the password from the Azure Key Vault and pass it on to subsequent tasks.
2020

2121
## Objectives
2222

2323
After you complete this lab, you will be able to:
2424

25-
- Create an Azure Active Directory (Azure AD) service principal.
26-
- Create an Azure key vault.
27-
- Track pull requests through the Azure DevOps pipeline.
25+
- Create an Azure Active Directory (Azure AD) Service Principal.
26+
- Create an Azure Key Vault.
2827

2928
## Lab duration
3029

@@ -58,7 +57,7 @@ If you don't already have an Azure DevOps organization that you can use for this
5857

5958
### Exercise 0: Configure the lab prerequisites
6059

61-
In this exercise, you will set up the prerequisites for the lab, which consist of a new Azure DevOps project with a repository based on the [eShopOnWeb](https://dev.azure.com/unhueteb/_git/eshopweb-az400).
60+
In this exercise, you will set up the prerequisites for the lab, which consist of a new Azure DevOps project with a repository based on the [eShopOnWeb](https://github.com/MicrosoftLearning/eShopOnWeb).
6261

6362
#### Task 1: (skip if done) Create and configure the team project
6463

@@ -86,20 +85,20 @@ In this task you will import the eShopOnWeb Git repository that will be used by
8685
### Exercise 1: Setup CI pipeline to build eShopOnWeb container
8786

8887
Setup CI YAML pipeline for:
89-
- Create an Azure Container Registry to keep the container images
90-
- Use Docker Compose to build and push **eshoppublicapi** and **eshopwebmvc** container images. Only **eshopwebmvc** container will be deployed.
88+
- Creating an Azure Container Registry to keep the container images
89+
- Using Docker Compose to build and push **eshoppublicapi** and **eshopwebmvc** container images. Only **eshopwebmvc** container will be deployed.
9190

92-
#### Task 1: (skip if done) Create a service principal
91+
#### Task 1: (skip if done) Create a Service Principal
9392

94-
In this task, you will create a service principal by using the Azure CLI, which will allow Azure DevOps to:
95-
- Deploy resources on your azure subscription
93+
In this task, you will create a Service Principal by using the Azure CLI, which will allow Azure DevOps to:
94+
- Deploy resources on your Azure subscription
9695
- Have read access on the later created Key Vault secrets.
9796

98-
> **Note**: If you do already have a service principal, you can proceed directly to the next task.
97+
> **Note**: If you do already have a Service Principal, you can proceed directly to the next task.
9998
100-
You will need a service principal to deploy Azure resources from Azure Pipelines. Since we are going to retrieve secrets in a pipeline, we will need to grant permission to the service when we create the Azure Key vault.
99+
You will need a Service Principal to deploy Azure resources from Azure Pipelines. Since we are going to retrieve secrets in a pipeline, we will need to grant permission to the service when we create the Azure Key Vault.
101100

102-
A service principal is automatically created by Azure Pipeline when you connect to an Azure subscription from inside a pipeline definition or when you create a new service connection from the project settings page (automatic option). You can also manually create the service principal from the portal or using Azure CLI and re-use it across projects.
101+
A Service Principal is automatically created by Azure Pipelines, when you connect to an Azure subscription from inside a pipeline definition or when you create a new Service Connection from the project settings page (automatic option). You can also manually create the Service Principal from the portal or using Azure CLI and re-use it across projects.
103102

104103
1. From the lab computer, start a web browser, navigate to the [**Azure Portal**](https://portal.azure.com), and sign in with the user account that has the Owner role in the Azure subscription you will be using in this lab and has the role of the Global Administrator in the Azure AD tenant associated with this subscription.
105104
1. In the Azure portal, click on the **Cloud Shell** icon, located directly to the right of the search textbox at the top of the page.
@@ -116,7 +115,7 @@ A service principal is automatically created by Azure Pipeline when you connect
116115
117116
> **Note**: Copy both values to a text file. You will need them later in this lab.
118117
119-
1. From the **Bash** prompt, in the **Cloud Shell** pane, run the following command to create a service principal (replace the **myServicePrincipalName** with any unique string of characters consisting of letters and digits) and **mySubscriptionID** with your Azure subscriptionId :
118+
1. From the **Bash** prompt, in the **Cloud Shell** pane, run the following command to create a Service Principal (replace the **myServicePrincipalName** with any unique string of characters consisting of letters and digits) and **mySubscriptionID** with your Azure subscriptionId :
120119
121120
```
122121
az ad sp create-for-rbac --name myServicePrincipalName \
@@ -132,7 +131,7 @@ A service principal is automatically created by Azure Pipeline when you connect
132131
133132
1. On the **New service connection** blade, select **Azure Resource Manager** and **Next** (may need to scroll down).
134133
135-
1. The choose **Service principal (manual)** and click on **Next**.
134+
1. The choose **Service Principal (manual)** and click on **Next**.
136135
137136
1. Fill in the empty fields using the information gathered during previous steps:
138137
- Subscription Id and Name
@@ -242,7 +241,7 @@ In this task, you will create a Variable Group in Azure DevOps that will retriev
242241
243242
![Variable Group create](images/vg-create.png)
244243
245-
#### Task 4: Setup CD Pipeline to deploy container in ACI
244+
#### Task 4: Setup CD Pipeline to deploy container in Azure Container Instance(ACI)
246245
247246
In this task, you will import a CD pipeline, customize it and run it for deploying the container image created before in a Azure Container Instance.
248247

0 commit comments

Comments
 (0)