{"id":4408,"date":"2017-06-11T14:40:10","date_gmt":"2017-06-11T12:40:10","guid":{"rendered":"http:\/\/contoso.se\/blog\/?p=4408"},"modified":"2017-06-13T11:16:23","modified_gmt":"2017-06-13T09:16:23","slug":"keep-your-azure-subscription-tidy-with-azure-automation-and-log-analytics","status":"publish","type":"post","link":"http:\/\/contoso.se\/blog\/?p=4408","title":{"rendered":"Keep your Azure subscription tidy with Azure Automation and Log Analytics"},"content":{"rendered":"

When delivering Azure training or Azure engagements there is always a discussion about how important it is to have a policy and a lifecycle for Azure resources. Not only do we need a process to deploy resources to Azure, we also need a process to remove resources. From a cost perspective this is extra important, as an orphan IP address or disk will cost many, even if they are not in use. We also need policy to make sure everything is configured according to company policy. Much can be solved with ARM policies<\/a>, but not everything. For example, you can\u00e2\u20ac\u2122t make sure all resources have locks configured.<\/p>\n

To keep the Azure subscription tidy and to get an event\/recommendation when something is not configured correctly we can use an Azure Automation and OMS Log Analytics. In this blog post, I will show an example how this can be done \u00f0\u0178\u02dc\u0160 The data flow is<\/p>\n

    \n
  1. Azure Automation runbook triggers based on a schedule or manual. The runbook run several checks, for example if there are any orphan disks.<\/li>\n
  2. If there is anything that should be investigated an event is created in OMS Log Analytics.<\/li>\n
  3. In the OMS portal, we can build a dashboard to get a good overview of these events.<\/li>\n<\/ol>\n

    The example dashboard shows (down the example dashboard here<\/a>)<\/p>\n