Azure DevOps organization and projects - Step-by-Step Execution

Process Flow - Azure DevOps organization and projects

Create Azure DevOps Organization

↓

Add Users and Set Permissions

↓

Create Project inside Organization

↓

Configure Project Settings

↓

Start Using Repos, Pipelines, Boards, Artifacts

This flow shows how you start by creating an organization, then add users, create projects inside it, configure them, and finally use Azure DevOps services.

Execution Sample

Azure

1. Create organization 'MyOrg'
2. Add user '[e-mail]'
3. Create project 'MyProject'
4. Set project visibility to private
5. Start using repos and pipelines

This sequence shows creating an Azure DevOps organization, adding a user, creating a project, setting its visibility, and starting work.

Process Table

Step	Action	Input/Setting	Result/State Change
1	Create organization	Name: MyOrg	Organization 'MyOrg' created
2	Add user	User: [e-mail]	User '[e-mail]' added with Contributor role
3	Create project	Name: MyProject	Project 'MyProject' created inside 'MyOrg'
4	Set project visibility	Visibility: Private	Project 'MyProject' set to private
5	Start using services	Use repos and pipelines	Repos and pipelines ready for 'MyProject'
6	End	No more actions	Setup complete, ready for development

💡 All steps completed successfully, organization and project ready for use

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Organization	None	MyOrg	MyOrg	MyOrg	MyOrg	MyOrg
Users	Empty	Empty	[e-mail]	[e-mail]	[e-mail]	[e-mail]
Projects	Empty	Empty	Empty	MyProject	MyProject	MyProject
Project Visibility	None	None	None	None	Private	Private
Services Ready	No	No	No	No	No	Yes

Key Moments - 3 Insights

Why do we create an organization before projects?

Because the organization is the top-level container that holds projects. Without an organization, you cannot create projects. See execution_table step 1 and 3.

Can a project exist without users?

Technically yes, but no one can work on it. Adding users with roles is needed to collaborate. See execution_table step 2 and 3.

What does setting project visibility to private do?

It restricts access to only authorized users, protecting code and pipelines. See execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'Users' after step 2?

A Empty

B MyOrg

C [e-mail]

D MyProject

💡 Hint

Check the 'Users' row in variable_tracker after step 2

At which step does the project visibility change to private?

A Step 1

B Step 4

C Step 2

D Step 5

💡 Hint

Look at execution_table step 4 for visibility setting

If you skip adding users, what would be the state of 'Users' after step 3?

A Empty

B [e-mail]

C MyProject

D MyOrg

💡 Hint

Refer to variable_tracker 'Users' before and after step 2

Concept Snapshot

Azure DevOps starts with an organization as the top container.
Inside it, create projects to organize work.
Add users to the organization with roles for access.
Set project visibility (private or public).
Use projects to manage repos, pipelines, boards, and artifacts.

Full Transcript

This visual execution shows how to set up Azure DevOps by first creating an organization, then adding users, creating projects inside the organization, setting project visibility, and finally starting to use Azure DevOps services like repos and pipelines. Each step changes the state of variables like organization name, users list, projects list, and project visibility. Key points include the organization being required before projects, users needed for collaboration, and visibility controlling access. The quiz tests understanding of these states and steps.

Practice

1. What is the main purpose of an Azure DevOps organization?

easy

A. To manage virtual machines

B. To store only your code repositories

C. To replace Azure subscriptions

D. To hold and manage all your projects in one place

Solution

1. Step 1: Understand the role of an Azure DevOps organization

   An Azure DevOps organization acts as a container for all your projects, grouping them together for management.

2. Step 2: Differentiate from other Azure services

   It is not for managing virtual machines or replacing subscriptions, but specifically for organizing projects and related resources.

3. Final Answer:

   To hold and manage all your projects in one place -> Option D

4. Quick Check:

   Organization = container for projects [OK]

Hint: Organization groups projects, not just code or VMs [OK]

Common Mistakes:

• Confusing organization with Azure subscription
• Thinking organization manages VMs
• Assuming organization stores only code

2. Which Azure CLI command correctly creates a new Azure DevOps project named MyProject in an organization?

easy

A. az devops create project MyProject

B. az devops project create --name MyProject

C. az project create --org MyProject

D. az devops new project --project MyProject

Solution

1. Step 1: Identify the correct Azure CLI syntax for project creation

   The correct command uses az devops project create with the --name parameter to specify the project name.

2. Step 2: Check the options for syntax errors

   The other options use incorrect command structures or parameters not recognized by Azure CLI.

3. Final Answer:

   az devops project create --name MyProject -> Option B

4. Quick Check:

   Correct CLI syntax = az devops project create --name MyProject [OK]

Hint: Use 'az devops project create --name' to create projects [OK]

Common Mistakes:

• Using wrong command order
• Missing --name parameter
• Confusing project and organization parameters

3. What will be the output of this Azure CLI command if the organization MyOrg has two projects named Alpha and Beta?

az devops project list --organization https://dev.azure.com/MyOrg

medium

A. An empty list with no projects

B. An error saying organization not found

C. A list showing projects Alpha and Beta with their IDs and descriptions

D. A list of all Azure subscriptions

Solution

1. Step 1: Understand the command purpose

   The command az devops project list lists all projects in the specified organization URL.

2. Step 2: Predict output based on existing projects

   Since the organization has two projects, the output will list both with details like IDs and descriptions.

3. Final Answer:

   A list showing projects Alpha and Beta with their IDs and descriptions -> Option C

4. Quick Check:

   List projects command outputs existing projects [OK]

Hint: List projects shows all projects in the given organization [OK]

Common Mistakes:

• Expecting subscription list instead of projects
• Assuming error if organization exists
• Thinking output is empty when projects exist

4. You run the command az devops project create --name without specifying a project name. What is the most likely result?

medium

A. The CLI returns an error about missing required parameter

B. The command runs but creates an empty project

C. A new organization is created instead

D. The project is created with a default name

Solution

1. Step 1: Analyze the command syntax

   The --name parameter is required to specify the project name when creating a project.

2. Step 2: Predict CLI behavior on missing required parameter

   Without a project name, the CLI will return an error indicating the missing required argument.

3. Final Answer:

   The CLI returns an error about missing required parameter -> Option A

4. Quick Check:

   Missing required parameter causes CLI error [OK]

Hint: Always provide --name when creating projects [OK]

Common Mistakes:

• Assuming default project name is assigned
• Expecting organization creation instead
• Thinking command silently succeeds

5. You want to organize your team's work by creating multiple projects under one Azure DevOps organization. Which of the following is the best practice?

hard

A. Create multiple projects within a single organization to share resources and users

B. Use a single project for all work to simplify management

C. Create one organization per project to isolate resources

D. Create projects only after creating separate Azure subscriptions

Solution

1. Step 1: Understand organization and project roles

   An Azure DevOps organization is designed to hold multiple projects, allowing teams to share users and resources efficiently.

2. Step 2: Evaluate best practice for team collaboration

   Creating multiple projects within one organization is best for managing related work and sharing access, rather than isolating each project in separate organizations.

3. Final Answer:

   Create multiple projects within a single organization to share resources and users -> Option A

4. Quick Check:

   One organization, many projects = best practice [OK]

Hint: Use one organization for many projects to share access [OK]

Common Mistakes:

• Creating too many organizations causing management overhead
• Putting all work in one project losing separation
• Confusing Azure subscriptions with DevOps organizations