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
+4-7Lines changed: 4 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,6 @@ To create project environment types:
86
86
87
87
1. Confirm that the environment type appears in the list.
88
88
89
-
90
89
## Configure a service connection
91
90
92
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.
@@ -106,16 +105,14 @@ In Azure Pipelines, you create a *service connection* in your Azure DevOps proje
106
105
|**Service Connection Name**| Enter a unique name for the service connection. |
107
106
|**Grant access permission to all pipelines**| Select the checkbox. |
108
107
109
-
1. In the list of service connections, select the one you just created, and then select **Manage Service Principal**.
110
-
The Azure portal opens in a separate browser tab and shows the service principal details.
111
-
1. In the Azure portal, copy the **Display name** value.
112
-
You use this value in the next step to grant permissions for running load tests to the service principal.
113
-
114
108
### Grant the service connection access to the Deployment Environments project
115
109
116
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.
117
111
118
112
1. In the [Azure portal](https://portal.azure.com/), go to your Deployment Environments project.
113
+
1.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.
119
116
1. Select **Access control (IAM)** > **Add** > **Add role assignment**.
120
117
1. On the **Role** tab, select **Deployment Environments User** in the list of job function roles.
121
118
1. On the **Members** tab, select **Select members**, and then use the display name you copied previously to search for the service principal.
@@ -128,7 +125,7 @@ You can now use the service connection in your Azure Pipelines workflow definiti
128
125
129
126
To view environments created by other users, including the service connection, you need to grant your account read access to the Deployment Environments project.
130
127
131
-
1. In the [Azure portal](https://portal.azure.com/), go to your Deployment Environments project.
128
+
1. In the [Azure portal](https://portal.azure.com/), go to your Deployment Environments project.
132
129
1. Select **Access control (IAM)** > **Add** > **Add role assignment**.
133
130
1. On the **Role** tab, select **Deployment Environments Reader** in the list of job function roles.
134
131
1. On the **Members** tab, select **Select members**, and then search for your own account.
0 commit comments