{"id":1429,"date":"2020-10-13T05:48:40","date_gmt":"2020-10-13T05:48:40","guid":{"rendered":"https:\/\/www.notwhattheyseem.com\/?p=1429"},"modified":"2021-11-10T12:30:51","modified_gmt":"2021-11-10T12:30:51","slug":"5-things-you-may-not-know-about-resource-map","status":"publish","type":"post","link":"https:\/\/www.notwhattheyseem.com\/5-things-you-may-not-know-about-resource-map\/","title":{"rendered":"5 things you may not know about Resource Map"},"content":{"rendered":"
<\/span><\/h2>\n
The common struggle that Azure users undergo is managing their cloud estate. As the investment in the cloud grows this problem is compounded and they quickly find that the estate becomes so complex they lose sight of what it looks like and how it relates to their overall architecture. At this point, the customers come up with requests like,<\/span><\/p>\n By understanding the customer needs, Serverless360 has come up with a new feature, <\/span>Azure Resource Map<\/span><\/a>.<\/span><\/p>\n Resource Map is a platform to visualize and govern Azure resources originating from different subscriptions at one place.<\/span><\/p>\n This blog covers all the top features of Resource Map that you should know about.<\/span><\/p>\n It is easy to keep track of the cost spent on an individual Azure Resource in the Azure portal, but the problem arises when the application was built using different Azure services and the user wants to visualize the cost at application level or environment\u00a0 level like production, dev and staging. Unfortunately, it is not possible to achieve it through Azure portal. This problem can be solved with <\/span>Resource Maps which has the capability to provide the cost spent on an entire application in the form of easily understandable charts.<\/span><\/p>\n It is also possible to view the cost spent on a specific resource, resource type or environment and can also obtain the cost spent for a specific time period by using filters like From and To.<\/span><\/p>\n Managing Azure resources can be effortlessly done by using Resource Maps where it allows you to sync Azure Resources from different subscriptions at one place. These resources are brought into Resource Maps by associating service principal with <\/span>Serverless360<\/span><\/a>.\u00a0<\/span><\/p>\n There are two options to sync the resources to a Resource Map, it can be either made automatic by enabling Auto sync or can be done manually using Sync resources option and <\/span>all the synced resources are segregated into various categories in different tabs like Unmapped Resources, Resources, Recently Synced, Ignored Resources and Rules.\u00a0<\/span><\/p>\n The picture below shows all the tabs and options available in the Resource Maps.<\/span>\u00a0\u00a0\u00a0\u00a0<\/span>\u00a0\u00a0<\/span><\/p>\n Resource Map<\/span><\/a> allows you to group Azure resources into logical scopes which is highly customizable by the users according to their business need<\/span>. Scope can have multiple environments and resources underlying and all these resources can also be grouped to represent an organisational hierarchy. All the synced resources can be mapped to a scope by using Map Resources option and it is possible to map a resource to more than one scope.\u00a0\u00a0<\/span><\/p>\n There will be a default parent scope under which any number of scopes can be created as per the requirement of the user and performing operations like moving or deleting on a parent scope will affect the scopes below it.\u00a0\u00a0<\/span><\/p>\n There are various tabs like Summary, Environments, Resources, Resource Assignments, Rules and Cost available for scopes in the Resource Map where each tab will have a specified role to be performed.<\/span><\/p>\n Using summary tab, it is possible to get an overview of a scope in which different metrics are represented in numerical count or in the form of pie charts.\u00a0<\/span><\/p>\n In a real-time scenario, an application will have stages like development, testing, production and much more depending upon the user. In this case, there will be different versions of the same resource and the user might find it hard to identify which environment does a Particular resource belong to.<\/span><\/p>\n\n
\n
Cost visualization is made easy in Resource Maps<\/span><\/h2>\n<\/li>\n<\/ul>\n
\n
Azure Resources across Multiple Subscriptions under one-roof<\/span><\/h2>\n<\/li>\n<\/ul>\n
\n
Logical grouping of Azure resources in the form of Scopes.<\/span><\/h2>\n<\/li>\n<\/ul>\n
\n
Managing Multiple Environments of an Application.<\/span><\/h2>\n<\/li>\n<\/ul>\n