How to map Microsoft Azure resources to Ardoq Solutions

Microsoft Azure is a cloud computing platform that provides Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS) and a variety of other related tools and frameworks. These services are delivered by a range of resources within the Azure environment, typically networking, storage, and compute (servers). Many of these resources are available through the Ardoq Azure integration and can be used to model and analyse the organizational technology landscape. For a full list of available resources and for more information regarding the Ardoq Azure integration please see: Azure Integration | Ardoq Help

Mapping between Ardoq Solutions and Microsoft Azure resources

Problem Statement

Microsoft Azure contains a wide range of different resources and it is not always obvious how best to map these into existing Ardoq workspaces. The guidance below describes the recommended approach to importing Azure resources for alignment with existing Ardoq Solutions.

Ardoq Solution Component Types to Azure Mapping

Default mapping between Azure resources and Ardoq Solution component types.

It is recommended that Azure resources should be held within a separate workspace from other infrastructure for ease of management. This workspace, Azure Cloud Infrastructure Workspace, will already have been created if you are using the Application Hosting (AH) or Technology Portfolio Management (TPM) Solutions. This is also the case for Locations within the Cloud Locations & Regions Workspace.

Recommendations

Additional Parent Component Types

When importing Azure resources it is recommended that four additional component types be created to hold the Azure subscription, resource group, and tag information.

Recommended component type mapping when importing Azure resources.

These new component types are:

Subscription - as the parent of Resource Group
Resource Group - as the parent of Azure resources (Technology Service components)
Tag - the tags that can be assigned to Azure resources
Tag Value - the value of a given tag for a resource

These component types should be created within the Azure Cloud Infrastructure workspace. The Resource Group and Subscription component types exist as parent and grandparent respectively to the Azure resource Technology Service components. Tags are children of the Subscription, and Tag Values are children of a Tag.

Additional Reference Types

An additional reference type ‘Has Tag’ should be created within the Azure Cloud Infrastructure workspace to enable the connection between resources and tag values. Note: Subscriptions and resource groups can also be linked to tag values.

Additional Fields

When importing Azure resources it is recommended that the following fields be added:

Workspace: Cloud Locations & Regions

Component Type: Location

Field	Type	Comment
Cloud ID	Text	Custom ID to hold the Azure region ‘id’