name

The service URL returned after creating our Principal Service

password

The password returned after creating our Principal Service

tenant

The tenant ID returned after creating our Principal Service

organization

project

webUrl

Discover how to design complex event-driven architectures in Azure, with insights into resource management, monitoring, and integrating VMs and databases for enterprise solutions.

Building Event Driven and Microservices Architecture in Azure.png

azure_microservices.tar.gz

run pwsh

run code

run code-cli

run code-cli-copy

Building a cloud infrastructure can be a challenging task. There are a lot of dependencies in your software and services like database, storage, and connections to log analytics that make it difficult.

In this course, you will learn how to easily design and build complex solutions based on the Event-Driven Architecture in the Azure Cloud. You will cover how to design, manage and monitor infrastructure. You will also learn how to select and combine resources like virtual machines and run books, databases, and application servers.

By the time you finish this course, you will be able to design and build complex architectures for enterprise-ready solutions based on Azure Cloud.

For the course, basic knowledge of Azure cloud or another cloud provider is needed.

Building Event Driven and Microservices Architecture in Azure

# Setting up an Azure DevOps service connection
 
In this lesson, we will configure our Azure DevOps service connection. It is necessary for our pipelines to get access to our subscription and to be able to create resources.

## PowerShell vs. CLI
Until now, we have been using PowerShell to run our commands using the terminal. However, DevOps requires us to use the CLI so we will be using that moving forward. This means that we will have to authenticate the CLI interactively. We will use the `az login` command to log in.


## CLI
To set up a service connection, we will need to create a service principal. This can be done with the following command:
```text
az ad sp create-for-rbac --name ServicePrincipalName
```
The output for this command includes a password key. **Copy this value and paste it somewhere safe as it can not be retrieved again.**

> Before running the code below, you may notice that there are three API keys required. Once you run your code and get your output, please update these keys so that they may be used again in the upcoming terminals.


Learn how to create a service connection and enable MSI.

Introduction

Architecture

Building CI/CD

Conclusion

Authentication and Azure Managed Identities

Setting up an Azure DevOps service connection

PowerShell vs. CLI