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.