Answer from @AzureSupport on twitter:
Thank you for brining this to our notice. We appreciate your time and efforts. We have escalated the concern to the team and our team will look into this on priority and get it corrected. Please feel free to reach out to us in case if you have any Azure related questions. We are available 24X7. ^DM
Not sure if relevant teams received link to this thread. At least support refused to open thread to get all the extra information they needed.