Prevent Creation of Legacy Machine Learning Workspace Commitment Plans and classic web services so Tags can be Enforced.

Our organization sets a Tag policy on resource groups so that newly created resources within that resource group will inherit tags. The main tag is 'Department Code', and is used for Chargeback for resource usage. Any Machine Learning 'classic' web services, that were created using the Machine Learning Studio portal will be created outside of the standard tagged resource group and thus, will not inherit standard tags used for Chargeback.

We also need a migration method for existing classic web services to be migrated to ARM web services, which is currently not supported by Microsoft. We will need to delete deployed instances from classic web services and deploy web services instead of classic web service from ML studio, and this has to be done one experiment at a time.

Recently we had a problem where we had ~1h of downtime which could have been avoided if VIP swap wasn’t failing.
The problem was that 1 single VM was in a busy state in Production slot. All VMs in the staging slot were up and Running.

Can you please allow a VIP swap if:
1. All VMs in Staging slot are in Running state
2. There’s the same or higher number of VMs in Staging slot compared to Production

I know that it’s by design that VIP swap is possible only if all VMs in both Staging and Production slot are in Running state. However, the point of doing the VIP Swap is to promote Staging slot to Production quickly, without downtime and to recover quickly from a bad state in Production slot to a healthy one in Staging slot.

Having a single busy VM in the Production slot, blocking the recovery and causing unnecessary service downtime does not make sense and looks like horrible design.

In the MFA release plan of a large company, thousands users are impossible to actually "force" from the day.

So, the user needs a period which setting for the MFA can be skipped, before force setting period.

In the period, it provide a selection such as "set up later" in the MFA setting wizard at the initial sign-in.

if someone did not have a mobile device on that day,
if someone wants to ask questions about MFA, etc...
they can not access any Office 365.
becouse, even if you set a policy to skip MFA on the LAN, the MFA Setup Wizard will be forced.
As a result, Organization is subjected to a large negative impact!

We are testing a production database migration to Azure SQL. The database is 50GB and even on the S3 tier we are going on 30 hours still and the import isn't complete (pegged at 100% DTU). At this point I couldn't even tell you when this will finish. I understand I could have chosen the highest premium tier to import this and it might have been quicker, however I only want to test this database and right now I've lost 3-4 days on this (importing at S0, S1 tiers). My suggestion is to allow an option when going through the import process that imports the database at the highest tier and automatically downgrades it to the selected tier when it is finished. It is consumption based we get it, but an import shouldn't be this painful taking days isn't a good experience.

We are unable to use the Enterprise Applications blade to find our applications. The interface only lists the first 20 applications. You cannot even download a list of them. In order to search for one on the list you have to know what letters the application name starts with. You cannot do partial search on part of the name, you must start with the first name. This is a HUGE problem if we forgot the name of an application.

For example. We created an Application called Ameris Webex. It is not listed in the first 20 applications, therefore we have to search for it. I cannot search on 'webex' - nothing shows in the results. I have to know the application name begins with Ameris to find it. This is RIDICULOUS. Come on Microsoft.... at LEAST have partial name searching/indexing or the ability to search another way or download the list. You have partial name searching on everything else in Azure Portal but this....