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: learn-pr/azure/manage-end-end-deployment-scenarios-using-bicep-azure-pipelines/includes/4-exercise-set-up-environment.md
+20-10Lines changed: 20 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,24 +22,34 @@ The modules in this learning path are part of a progression. For learning purpos
22
22
23
23
### Run the template
24
24
25
-
Run a template that sets up your Azure DevOps project.
25
+
Run a template that sets up your Azure DevOps organization.
26
26
27
-
> [!div class="nextstepaction"]
28
-
> [Run the template](https://azuredevopsdemogenerator.azurewebsites.net/?name=bicependtoend)
27
+
1.[Get and run the ADOGenerator project](https://github.com/microsoft/AzDevOpsDemoGenerator/blob/main/docs/RunApplication.md) in Visual Studio or the IDE of your choice.
29
28
30
-
On the Azure DevOps Demo Generator site, do the following steps:
29
+
1. When prompted to **Enter the template number from the list of templates**, enter **43** for **Manage end-to-end deployment scenarios by using Bicep and Azure Pipelines**, then press **Enter**.
31
30
32
-
1.Select **Sign In**, and then agree to the site usage terms by selecting **Accept**.
31
+
1.Choose your authentication method. You can [set up and use a Personal Access Token (PAT)](/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate#create-a-pat) or use device login.
33
32
34
-
1. On the **Create New Project** page, select your Azure DevOps organization and then, in the **New Project Name** box, enter a project name, such as *toy-website-end-to-end*.
33
+
> [!NOTE]
34
+
> If you set up a PAT, make sure to authorize the necessary [scopes](/azure/devops/integrate/get-started/authentication/oauth#scopes). For this module, you can use **Full access**, but in a real-world situation, you should ensure you grant only the necessary scopes.
35
35
36
-
:::image type="content" source="../media/4-create-new-project.png" alt-text="Screenshot of the Azure DevOps Demo Generator pane for creating a new project.":::
36
+
1. Enter your Azure DevOps organization name, then press **Enter**.
37
37
38
-
1.Select **Create Project**.
38
+
1.If prompted, enter your Azure DevOps PAT, then press **Enter**.
39
39
40
-
The template takes a few moments to run. It automatically creates a pipeline and Bicep file for you to work with in the next few exercises.
40
+
1. Enter a project name such as *toy-website-end-to-end*, then press **Enter**.
41
41
42
-
1. Select **Navigate to project** to go to your project in Azure DevOps.
42
+
1. Once your project is created, go to your Azure DevOps organization in your browser (at `https://dev.azure.com/<your-organization-name>/`) and select the project.
43
+
44
+
### Fork the repository
45
+
46
+
If you haven't already, create a fork of the **mslearn-manage-end-end-deployment-scenarios-using-bicep-github-actions** repository.
47
+
48
+
1. On GitHub, go to the [mslearn-manage-end-end-deployment-scenarios-using-bicep-github-actions](https://github.com/MicrosoftDocs/mslearn-manage-end-end-deployment-scenarios-using-bicep-github-actions) repository.
49
+
50
+
1. Select **Fork** at the top-right of the screen.
51
+
52
+
1. Choose your GitHub account as the **Owner**, then select **Create fork**.
0 commit comments