e s

Managing
ri g u
o d
n R
Al a
 Working with

You can add users to your Azure DevOps organization.

e s
i gu
d r
o
The users can be Microsoft Accounts or GitHub usernames.

R
l a n
A
The users can then be assigned to the required project.
DevOps
c
 Access levels

Basic
Stakeholder

1 s
This provides most of the This is a free access but has
features within Azure
3 u elimitations. Limited access
DevOps which excludes
Azure Test Plans.
ri g to Azure Boards and
Pipelines. No access to code

o d repositories.

n R
Basic + Test Plans
This gives access to the
l
A 2a Visual Studio

This depends on the Visual

Studio subscription
Basic Plan + Test Plans.

4 assigned to the user.

DevOps
c
 Project g e s
i u
d r
Ro
l an
A
A DevOps project can have a wiki.
e s
i g u
The wiki can be used to share information with the team so that they can understand and contribute to the
project.
d r
Ro
l a n
The project wiki uses a Git repository as the back-end.

DevOps
You need to have at least the Basic access to create and modify a wiki.
e s
i g u
Members who are part of the Contributors security group can add and edit wiki pages.

d r
o
The project wiki uses a Git repository as the back-end.
R
a n
To publish code as wiki, you need to have the Create Repository permission.
l
A

DevOps
 Query e s
i gu
d r
Ro
l an
A
 s
All users except those that are only assigned to the Readers group can create and edit their own queries.
e
They can save their queries under My Queries.
i g u
d r
o
Members of the Project Administrators Group can create and edit queries and folders under Shared Queries.
R
a n
Also, for saving under Shared Queries, you need to have Basic access level or higher.
l
A

DevOps
Managing e s
i gu
d r
Ro
l an
A
 Dashboards

Purpose
Widgets

1 s
These are customizable These display configurable
interactive signboards. They
3 u einformation and charts on
help to provide real-time
information.
ri g the dashboard.

o d
n R
Charts

Here you can create charts

l
A 2a In-context reports

These are system generated

charts based on specific
based on the work items.

4 services.
DevOps
c
Dashboard e s
i gu
d r
Ro
l an
A
 s
Dashboards are viewable by all members that are part of the Project Valid Users group.
e
i g u
Members of the Project Administrators group can set the default dashboard permissions for the teams.

d r
o
To add, edit and manage a team dashboard, you must also have Basic access or greater.
R
l a n
A

DevOps
 e s
Widgets i gu
d r
Ro
l an
A
 Widgets

Purpose

1 3 e s
i g
specified period of time.u
These charts focus on the remaining work within a

d r
Ro
l a n
A 2
4
DevOps
c
 Widgets

Purpose

1 3 e s
i g
work on it has started. u
This defines the time taken to close a work item after

d r
Ro
l a n
A 2
4
DevOps
c
 Widgets

Purpose

1 3 e s
was created.
i g u
This defines the time taken to close a work item after it

d r
Ro
l a n
A 2
4
DevOps
c
 Widgets

Purpose

1 3 e s
after sprint.
i g u
This tracks the team’s capacity to deliver work sprint

d r
Ro
l a n
A 2
4
DevOps
c
 Ta g g i n g g e s
iu
d r
Ro
l an
A
It can be used to specify which commit is important in the repository.
e s
You can mark release points with the use of tags.
i g u
d r
Two types of tags – lightweight and annotated.
Ro
a n
Lightweight tag is just a pointer to a specific commit.
l
A

DevOps
Annotated
e s
These are stored as full objects in the Git database.
i g u
d r
o
These are checksummed, they contain the tagger name, the email and date, have a message.
R
a n
It can also be signed and verified with GNU Privacy Guard.
l
A

DevOps
 e s
T e a m F o u n d a t i o ingu
d r
Ro
l a n
A
This is a centralized version control tool.
e s
i
Its different from Git which is a distributed version control tool.
g u
d r
o
With Team Foundation Version Control, a team member has only one version of each file on their local machine.
R
a n
The historical data for the files is held on the server.
l
A

DevOps
 s
Before developers can make changes to a file, they need to first check out the file from the server.
e
i g
When it comes to each file, you can apply permissions at the file level. u
d r
o
This contrasts with Git where the permissions can be set on the repository or branch level.
R
l a n
A

DevOps
 Azure e s
i gu
d r
Ro
l an
A
 Azure Pipelines

Automation
Languages

1 s
Build and test your code It has support for languages
projects.
3 u e– Python, Java, PHP, Ruby,

ri g C#.

o d
n R
Functionality

You can use Azure Pipelines

l
A 2a Deployment

You can deploy your

application to multiple
for both continuous
integration and continuous
delivery.
4 targets or environments.
DevOps
c
YAML syntax
e s
You can define your pipeline in YAML syntax.
i g u
d r
o
Here a file called azure-pipelines.yml will be created and version controlled along with your code.
R
a n
This helps to easily identity changes in the pipeline that could break the deployment.
l
A

DevOps
Classic Interface
e s
This gives you a graphical interface.
i g u
d r
o
You can then define your pipelines with the use of this interface.
R
l a n
A

DevOps
 e s
What is rig u
o d
n R
Al a
 What is Terraform

Tool Language

Open-source tool
1 3 e s
It uses a declarative language

u
developed by HashiCorp. to define the code.

ri g
o d
n R
Infrastructure
l
A 2
It helps to automate and
a Cloud

You can use it to build

infrastructure on multiple
manage your infrastructure.
4 cloud environments.
Terraform
c
 e s
Terraform
ri g u
o d
n R
Al a
Core Terraform workflow
e s
1. Write – Here you create the code configuration file.
i g u
d r
2. Plan – Here you can see the changes that are going to be made by Terraform.

Ro
3. Apply – This will apply the changes.

l a n
A

Terraform
 s
Terraform configuration – This is the complete document in the Terraform language. This tells terraform how to
e
manage the infrastructure.
i g u
d r
Providers – These are plugins for Terraform. This helps Terraform to work with cloud providers.

Ro
l a n
A

Terraform
 e s
Using ri gu
od
n R
Al a
 Using Variables

Usage Define

Helps to define and reuse a

1 3 e s You can define the same

u
value within the pipeline. variable in different places.

ri g The most locally scoped

variable will take effect.

o d
n R
Change
l
A 2
The value of the variable
a Expressions

You can also use variables

within expressions.
can change from run to run
or from job to job.
4
DevOps
c
 e s
Variablerig u
o d
n R
Al a
 Variable groups

Storage Usage

Here you can store values

1 3 e s
Variable groups can be used

u
and secrets. across multiple pipelines in a

ri g project.

o d
n R
Pipelines
l
A 2
You can access the values
a Azure CLI

You can also use the Azure

CLI to work with variable
from the YAML pipelines.
4 groups.
DevOps
c
 Azure e s
i gu
d r
Ro
l an
A
 s
Feeds is just a mechanism that allows you to store, manage and group packages together.
e
i g u
Normally the feeds are project-based. Here only people within the project can access the feed.

d r
You can also create a public feed.
Ro
a n
The public feed allows you to share packages within anyone on the Internet.
l
A

DevOps
Requirements for public feeds
e s
They need to be created within public projects.
i gu
d r
They cannot have upstream sources.
Ro
a n
Public users cannot download universal packages.
l
A

DevOps
Upstream sources
e s
i g
Here you can store packages from different sources onto your feed. u
d r
o
Here the copy of the package from the upstream source will be stored in the feed.
R
l a n
A

DevOps
Feed views
e s
Feed views helps to share certain packages.
i gu
d r
o
The default views are @Local, @Prerelease and @Release.
R
a n
By default all packages are released to the @Local view.
l
A

DevOps
Azure e s
i gu
d r
Ro
l an
A
 Azure App Configuration

Central Service Encryption

Provides a central service

1 3 e s
It provides encryption of

u
for managing application sensitive information at rest
settings and feature flags .

ri g and in transit.

o d
n R
Managed
l
A 2a Frameworks
Azure App Configuration

It integrates with popular

This is a fully managed frameworks.
service.
4
c
Te s t e s
i gu
d r
Ro
l a n
A
 What are Azure Test Plans

Testing Pipelines

Planned Manual testing,

1 3 e s There is integration with

u
user acceptance testing. Azure Pipelines.
Capture test results.

ri g
o d
n R
Feedback
l
A 2
You can also get stakeholder
a Traceability

The test cases and suites

can be linked to the user
feedback.
4 stories features to provide
end to end traceability.
DevOps
c
 Access Levels

e s
i g u
d r
Ro
l a n
A 2
4
DevOps

Reference - https://docs.microsoft.com/en-us/azure/devops/test/overview?view=azure-devops
c
Test Runner
e s
i g
Here you can run the tests for your web and desktop applications. u
Here you can mark tests and passed or failed.
d r
Ro
l a n
The test outcomes can also gather results such as screen recordings and screen captures.

DevOps
Test & Feedback extension
e s
i g
This is a browser-based extension that works with web applications. u
You can get stakeholder feedback with the extension.
d r
Ro
l a n
The test outcomes can also gather results such as screen recordings and screen captures.

DevOps
 Azure Test Plans

Test plans Test cases

This is used to group test

1 3 e s This is used to define the

u
suites and test cases. actual steps required to test

ri g the application.

o d
n R
Test suite

This is used to group test

l
A 2a Shared steps

You can have shared steps

that need to be shared
cases into separate testing
scenarios.
4 across test cases.
DevOps
c
 Scale Set g e s
i u
dr
Ro
l an
A
You can monitor the health of your individual instances.
e s
i g
This can be useful when it comes to rolling upgrades for your instances. u
d r
o
You can monitor the application health of each instance in the scale set and perform instance repairs.
R
l a n
A

DevOps
Dynamic e s
i gu
d r
Ro
l an
A
Dynamic thresholds
e s
i g u
Here Azure Monitor uses machine learning to check the historical behavior of metrics.

d r
Based on the historical data, it can then identify patterns and anomalies that could indicate possible issues.

Ro
l a n
A

Azure Monitor
Sensitivity
e s
i g
High – Here the alert rule will be triggered even for the smallest deviation. u
d r
Medium – Here you have more balanced thresholds and fewer alerts will be generated.

Ro
l a n
Low – Here alerts will only triggered on large deviations.

Azure Monitor
 e s
Ser vice ri gu
od
n R
Al a
 Service Map

Discovery Log Analytics

Helps to discover
1 3 e s The machines need to

u
application components on connected to a Log Analytics
Windows and Linux
systems.
ri g workspace.

o d
n R
Information
l
A 2
You can see information
a Agent

The machines also need to

have the Dependency agent
such as connections
between servers, latency for
connections.
4 installed.
DevOps
c
Application g e s
iu
dr
Ro
l an
A
 Application Insights

Monitoring Applications

This provides the feature of

e s
This works for applications

u
hosted in Azure, on-premises
application performance
management and monitoring

ri g environments, or other cloud

platforms.

d
of live web applications.

Aspects
RoApplication Integration

Here you can see aspects such

l a n Insights It has Integration with the

Visual Studio IDE.

A
as detecting performance
issues or any other issues.
Application Insights

Support Users

There is support for .NET, You can also see how users
Node.js, Java and Python. interact with your application.
c
How does it work
e s
i g u
You can install a small instrumentation package (SDK) for your application. Or use the Application Insights agent.

d r
You can instrument web applications, background components and JavaScript in web pages.

Ro
l a n
The telemetry data sent by Application Insights has very little impact on the performance of your application.

Application Insights
Application g e s
iu
dr
Ro
l an
A
Users, Sessions and Events
e s
i g u
Users – Here you can see how many people have used your application and its features.

d r
Session – You can see sessions of user activity. This includes certain pages and features of the application.

Ro
l a n
Events – This gives a view of how often certain pages and features have been used in the application.

Application Insights
 s
Funnels – Here you can have multiple stages like a pipeline. And then you can see how users are progressing
e
through your application as an entire process.
i g u
d r
Cohorts – This is a set of users, sessions, events or operations that have something in common. It helps to analyze
a particular set of users or events.
Ro
l a n
A
Impact – Here you can see how load times and other aspects of your application impact the conversion rate for

Application Insights
your application.
 s
Retention – Here you can analyze how many users return back to your application.
e
i g
User flows – This can help in answering useful questions such as u
d r
o
1. What do users click on a page within the application
R
l a n
2. Where are the places within the application that users churn the most from the site.

Application Insights
3. Are there places in the application where the users repeat the same action over and over again.