Azure Hierarchy Support

Photo by Edvard Alexander Rølvaag on Unsplash

In Understanding and aligning the portfolio hierarchy, a set of definitions for the portfolio hierarchy and role mapping established a hierarchy of scope for most portfolio approaches. As described in that article, you might not need each of the outlined levels or scopes. Minimizing the number of layers reduces complexity, so these layers shouldn’t all be viewed as a requirement.

Organizing the hierarchy in Azure

--

--

--

making the🌎 a better place by taking care of data

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Understanding Computer Networking — a quick dive.

The secret behind NODY ecosystem you need to know.

Student Exploration- Reverse the Field (answers)

Understanding Dev Speak 101

How to use new Windows 10 feature

How to Improve Facility Maintenance using Agile Project Management (Guide)

Importing GCP Projects into your Organization with Python

How I Built My Blog with Gatsby and Ghost

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
dataninja

dataninja

making the🌎 a better place by taking care of data

More from Medium

Developing a File Sharing Platform using Azure! (PRACTICAL)

Azure Sphere

Getting list of Azure subscriptions of customers who deployed your Azure Managed Application

Assigning Azure built-in roles vs Azure AD built-in roles with Azure CLI