When considering or analysing a migration to the cloud, it is often the case that you will need to make some decisions around which applications/services you will move and in which order.
This can start to get a little challenging if you have some legacy line of business applications which are possibly dependent on a client application being “next to” an application or database server/can only cope with certain latency. The most challenging are when “nobody really knows” if an application has latency dependencies or not!
If like me, you are spinning up demo or test Azure subscriptions. You will often want to quickly clear your subscription and delete everything within it.
This PowerShell script will allow you to select which Azure subscription you want to clear and will then delete EVERYTHING inside that subscription allowing you to start from scratch.
USE THIS WITH CAUTION!
I recently changed this blog to rossinthecloud.com from rossmc.co.uk/rossmc.net to have achieve more consistency across my blog and other social media platforms. After this change I wanted to redirect any traffic to the root of my old domains to this one.
There are a number of Azure services which can help us here, for example the fantastic Azure Front Door. But I wanted to look at not necessarily the “best” approach to this but one which is “good enough” and the cheapest option!
In this post I look at using Azure Functions to create a simple redirect without even writing a line of code!
A look into Azure Management Groups as I recently reorganised my own personal subscriptions into a new management group and wanted to share a quick example here.
If you or your organisation have multiple Azure subscriptions and aren’t using management groups, I would recommend a look into this.
If you have a scenario where you have some database or virtual machine files in Azure Storage which you no longer require in your live environment but need to retain in archive, you will probably find that you are unable to place these files into the archive tier in Azure.
This is because these files are typically held in page blobs. Page blobs are optimised for random IO (databases, VM’s) whereas block blobs are optimised for sequential IO (text files, images, videos, logs etc).
Most of the cost saving options like archive tier, blob level tiering etc are only available for block blobs and not for page blobs.
To work around this I started exploring whether it was possible to convert from page blob to block blob. None of the common tools such as AZCopy or Azure Storage Explorer appear to offer this functionality but we can accomplish this by using the hidden gem from Microsoft that is Blobporter.
In this post we will look at using Blobporter to convert page blob data to block blob and placing this data in the Azure Storage archive tier.