Comment 5 for bug 1626484

This is a straight 'juju deploy [apache-processing-mapreduce|bigtop-processing-mapreduce] of the bundle from the charm store, no constraints or anything unusual. The Azure account was a brand new one created specifically to test this so nothing odd setup at all. It was intended as a simple dmeo to a customer of a big data deployment...

It sounds like the bundle is looking for a certain spec and the nearest match is an AWS type which is only available in VPS - but that doesn't explain the failure in Azure...