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

## PowerShell task to get MSI object id
To run the PowerShell script that gets an object id (or Azure CLI scripts), we will use the pipeline task `AzureCLI@1`. This task (and script) does the following:

1. Gets the object id from Azure Active Directory by app service display name.
2. Prints the variable app service name `$(appServiceName)` and object id (`$objectId`) to the dev console.
3. Shares object id local variable to be accessible between other pipeline tasks. It assigns a variable to the pipeline global variable (`avmAppServiceObjectId`) using the command `echo "##vso[task.setvariable variable=avmAppServiceObjectId;]$objectId"`.

You can find the complete reference [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-cli?view=azure-devops).


# PowerShell task to get MSI object id
To run the PowerShell script that gets an object id (or Azure CLI scripts), we will use the pipeline task `AzureCLI@1`. This task (and script) does the following:

1. Gets the object id from Azure Active Directory by app service display name.
2. Prints the variable app service name `$(appServiceName)` and object id (`$objectId`) to the dev console.
3. Shares object id local variable to be accessible between other pipeline tasks. It assigns a variable to the pipeline global variable (`avmAppServiceObjectId`) using the command `echo "##vso[task.setvariable variable=avmAppServiceObjectId;]$objectId"`.

You can find the complete reference [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-cli?view=azure-devops).


# PowerShell task to get MSI object id
To run the PowerShell script that gets an object id (or Azure CLI scripts), we will use the pipeline task `AzureCLI@1`. This task (and script) does the following:

1. Gets the object id from Azure Active Directory by app service display name.
2. Prints the variable app service name `＄(appServiceName)` and object id (`＄objectId`) to the dev console.
3. Shares object id local variable to be accessible between other pipeline tasks. It assigns a variable to the pipeline global variable (`avmAppServiceObjectId`) using the command `echo "##vso[task.setvariable variable=avmAppServiceObjectId;]＄objectId"`.

You can find the complete reference [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-cli?view=azure-devops).


Learn how to set up the automation pipeline to configure the Managed Service Identity (MSI).

Introduction

Architecture

Building CI/CD

Conclusion

Setting Permissions for Managed Identity (MSI)

PowerShell task to get MSI object id