myVMX - Virtualisation, Cloud

When you connect PowerBi via Microsoft Azure Consumption Insights (Beta) connector you will get the last month of consumption data and you may want to report further back. There is a way to do it where you can report back up to a maximum of 36 months. If you follow my article https://blog.myvmx.com/2020/12/using-azure-tags-in-your-powerbi.html up to step "On the menu bar select "Transform data > Transform data" first. On the menu bar select "Transform data > Transform data"     Under the "Home" ribbon locate and select "Advanced Editor" You should see the query that has been applied which is currently based on this format let     Source = MicrosoftAzureConsumptionInsights.Tables(EnrollmentNumber, []),     usagedetails = Source{[Key="usagedetails"]}[Data] in     usagedetails We would need to change it to let     enrollmentNumber = "EnrollmentNumber",     optionalParameters = [ numberOfMonth = 3, dataType = "De

By default, when you deploy your new Azure subscription the "Service administrator" is the same as "Account administrator" which means that this account has permissions to both the EA portal and the Azure portal. For us we had to change this as Azure Account team didn't need access to the Azure portal. To change this, it was a simple process as both the Service administrator and Account administrator is the same user.    First go to https://portal.azure.com with the account that you used to sign up for the subscription then head to subscriptions and locate your subscription. If we want to check to make sure you are logged in as the "Service Administrator" then click "subscriptions" then go to "Access control (IAM)" then "Classic administrators" tab and you should see the your account there with the role of "Service administrator". As we are still in the subscription blade click on "properties" and clic

So you have gone through the hard work of defining tags and its value for all the resources in Azure portal which you want to make use of them when reporting the costing in PowerBi. Here I will describe how you can expose those tags for billing purposes so that you can filter your costing via tags as well. First of all we need to get the API access key and enrollment number which you will need to ask whoever that has access to your Enterprise agreement information. You can check if you have access by going to https://ea.azure.com in case someone has given you access. Within the EA portal you will see your enrollment number on the top left of the screen which you will need to note down. To get the API access key you will need to click on "reports" then go to "Download Usage > API Access Key". You will see two keys, make sure you have a look at the effective date (remember US date format). Once you have decided which key to use then click on "expand key"

One of the painful things when I first started to use Azure policy to conduct audits was that it could take up to 24 hours before it would do it first initial scan. If I was to make changes it could take up to 24 hours before the policy would run again. Going backwards and forwards like this means usually it could take up to a week before the policy I am writing could be completed. There were ways to speed it up by either: issuing API calls to force a rescan but it was something that I couldn't quite grasp at the time or you could delete the policy and recreate it which would trigger a initial scan which nowdays should run within a few hours. Moving forward now, there is a powershell cmdlet to help speed up the policy rescan which can be targeted at specific resource group or a complete subscription. At present there doesn't seem to be a way with powershell to trigger a specific policy rescan. Here is how you do it As this cmdlet is based on the new Az modules I tend to just us

One of the first things to do once you have a Azure subscription created is to set up a service health alert. These alerts will tell you if Microsoft are doing any maintenance or having trouble with a particular service. These alerts are not designed to tell you specifically if your resources will be impacted but more as a overall health status for services so that you are aware that there are issues on the platform. Setting up ... First login to your subscription via https://portal.azure.com . Once you have logged in then use the search bar to locate "Service Health" You will be taken to the Service Health blade which will show you any current issues within Azure. From here you can drill down to the data centres on the world map or see what issues that have been trigger in the last seven days. To add a service health click on "Add service health alert". You will be taken to the "create alert rule" page.  The rule can only target one subscription so under