You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/deployment-environments/tutorial-deploy-environments-in-cicd-azure-devops.md
+16-13Lines changed: 16 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,12 +36,13 @@ In this tutorial, you learn how to:
36
36
-[Create an account for free](https://azure.microsoft.com/services/devops/?WT.mc_id=A261C142F).
37
37
- An Azure DevOps organization and project.
38
38
- In Azure Deployment Environments:
39
-
-[Dev center and project](./quickstart-create-and-configure-devcenter.md).
39
+
-[A dev center and a project](./quickstart-create-and-configure-devcenter.md).
40
40
-[Sample catalog](https://github.com/Azure/deployment-environments) attached to the dev center.
41
41
42
42
## Create and configure an Azure Repos repository
43
43
44
-
1. Sign in to your Azure DevOps organization (`https://dev.azure.com/<your-organization>`). Replace `<your-organization>` with your project identifier. Select your project.
44
+
1. Sign in to your Azure DevOps organization (`https://dev.azure.com/<your-organization>`). Replace `<your-organization>` with your project identifier.
45
+
1. Select your project.
45
46
1. Select **Repos** > **Files**.
46
47
1. In **Import a repository**, select **Import**.
47
48
1. In **Import a Git repository**, select or enter the following:
@@ -50,7 +51,7 @@ In this tutorial, you learn how to:
50
51
51
52
## Configure environment types
52
53
53
-
Environment types define the types of environments that your development teams can deploy. You can apply different settings for each environment type. You create environment types at the dev center level and at the project level.
54
+
Environment types define the types of environments that your development teams can deploy. You can apply different settings for each environment type. You can create environment types at the dev center level and at the project level.
54
55
55
56
To create dev center environment types:
56
57
@@ -88,35 +89,37 @@ To create project environment types:
88
89
89
90
## Configure a service connection
90
91
91
-
In Azure Pipelines, you create a *service connection* in your Azure DevOps project to access resources in your Azure subscription. When you create the service connection, Azure DevOps creates a Microsoft Entra service principal object.
92
+
In Azure Pipelines, you create a *service connection* in your Azure DevOps project to access resources in your Azure subscription.
92
93
93
-
1. Sign in to your Azure DevOps organization (`https://dev.azure.com/<your-organization>`). Replace `<your-organization>` with your project identifier. Select your project.
94
+
1. Sign in to your Azure DevOps organization (`https://dev.azure.com/<your-organization>`). Replace `<your-organization>` with your project identifier.
|**Subscription ID**| Enter the ID of the Azure subscription that hosts your dev center resource. |
103
105
|**Subscription name**| Enter the name of the subscription. |
104
106
|**Tenant Id**|Enter the ID of the tenant.|
105
107
|**Service Connection Name**| Enter a unique name for the service connection. |
106
-
|**Grant access permission to all pipelines**| Select the checkbox. |
108
+
|**Grant access permission to all pipelines**| Select this checkbox. |
107
109
108
110
### Grant the service connection access to the Deployment Environments project
109
111
110
-
Deployment Environments uses role-based access control to grant permissions for performing specific activities on your Deployment Environments resource. To make changes from a CI/CD pipeline, you grant the Deployment Environments User role to the service principal.
112
+
Deployment Environments uses role-based access control to grant permissions for performing specific activities on your Deployment Environments resource. To make changes from a CI/CD pipeline, you grant the Deployment Environments User role to the managed identity.
111
113
112
114
1. In the [Azure portal](https://portal.azure.com/), go to your Deployment Environments project.
113
-
1. In the left menu, under **Settings**, select **Identity**.
114
-
1. On the **System assigned** tab, set the **Status** to **On**.
115
-
1. Select **Save**, and then confirm that you want to enable the identity.
115
+
1. If you don't have a managed identity for the project, complete these steps:
116
+
1. In the left menu, under **Settings**, select **Identity**.
117
+
1. On the **System assigned** tab, set the **Status** to **On**.
118
+
1. Select **Save**, and then confirm that you want to enable the identity.
116
119
1. Select **Access control (IAM)** > **Add** > **Add role assignment**.
117
120
1. On the **Role** tab, select **Deployment Environments User** in the list of job function roles.
118
121
1. On the **Members** tab, select **Managed identity** and **Select members**.
119
-
1. In the Select managed identities tab, under Managed identity, select the **Project** identity, select the project name, and then select **Select**.
122
+
1. In the **Select managed identities** tab, under **Managed identity**, select the **Project** identity, select the project name, and then select **Select**.
120
123
1. On the **Review + assign** tab, select **Review + assign** to add the role assignment.
121
124
122
125
You can now use the service connection in your Azure Pipelines workflow definition to access your Deployment Environments environments.
0 commit comments