(General Feedback)

Do you have an idea or suggestion based on your experience with Azure? We would love to hear it! Please take a few minutes to submit your idea in the one of the forums available on the right or vote up an idea submitted by another Azure customer. All of the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.

This forum (General Feedback) is used for any broad feedback related to Azure. If you have feedback on a specific service such as Azure Virtual Machines, Web Apps, or SQL Database, please submit your feedback in one of the forums available on the right.

Within the Office 365 Group Expiration setup there should be a way to set it such that all groups *except* specific ones are subject to the expiration setting. As it stands now it's the other way around; all groups or only the selected ones. In an environment where users are permitted to created their own groups (something I was told even Microsoft allows) you really need the expiration feature enabled by default. But there are certainly use cases where as an admin you will want specific groups exempted from this setting.

we need an easy way to lift and **** Mainframes/ AS400 to lift and **** to Azure. instead of replatforming if Microsoft can build a layer which AS 400 or Mainframe apps can run on, can help drive consumption of Azure. Hopefully Microsoft can do it before AWS

Application Insights on Azure lets me upload a .webtest file to monitor application availability. My application is a REST/JSON service, and so my .webtest references a custom ExtractJSONRule derived from the ExtractionRule base class to pick out and check data from the JSON response. I can upload the .webtest file OK, but of course, without the custom C# code for the ExtractJSONRule, it always fails.

Please provide a mechanism to allow .webtest files which reference one or more custom .cs files for custom ExtractionRule and ValidationRule classes.

Currently you can only configure the inbound tcp timout. The default outbound timeout for TCP connections is 4 minutes and is non configurable/by design. It's important that users have the ability to change this, perhaps up to a value of 30 which is similar to the inbound properties.

CSP is a great purchasing model for small and medium businesses, but has some serious problems.

1) Migrating between CSP and any other offer is a very laboursome and expensive project (not to mention that many resources cannot be migrated). This can cause Vendor lock-in and some other major risks for customers using CSP. Currently even PAYG to CSP is not easy.

2) CSP customers are unequal to other Azure users despite the fact that they pay the same or sometimes even more, because they do not have the same services available to them.

3) CSP resellers have to put in a lot of labour to onboard existing customers.

Please work on harmonizing the services between the different offer types so that a Customer in CSP is equal in terms of what services they can use. Furthermore, work on enabling (MS Support assisted or self-service) migration from CSP to PAYG/EA AND vice versa ON THE BILLING LEVEL without service interruptions (as with PAYG to EA or EA to PAYG).

CSP is a great purchasing model for small and medium businesses, but has some serious problems.

1) Migrating between CSP and any other offer is a very laboursome and expensive project (not to mention that many resources cannot be migrated). This can cause Vendor lock-in and some other major risks for customers using CSP. Currently even PAYG to CSP is not easy.

2) CSP customers are unequal to other Azure users despite the fact that they pay the same or sometimes even more, because they do not have the same services available to them.

Users can sometimes approve MFA notifications on their device because they do not know whether it is their device authenticating or a hacker who has phished their credentials. Therefore, to help users know why they are being asked to accept authentication include additional details such as the application name, IP address and location in the MFA prompt. Apple includes the location and a map of the location in their own two-factor implementation.

Additionally, users should be notified with an email any time a new device is used to authenticate to their account.

The Microsoft Azure status board should live outside Azure's ecosystem just because when there is a problem with some Azure´s service, the Microsoft Azure status page may not be available for the same issue.

We have a managed service provider and some customers that need a degree of permissions at the subscription level. There are several resource groups that I do not want them to have the same level of access they have at the subscription level. For instance, I would like to remove them from the Azure Automation RG or provide them read level access to our OS image folder.

Usually when you create a resource you do not know when was created and by whom, the information in logs is available only for a determined period of time and then lost, that is something that will be very helpful to include in the Overview section.

RBAC role created so a group can be added for the single purpose of Reserved Instance creation, without keys to the kingdom (Owner rights). Capacity and Procurement would not need such keys as they would only be creating RI’s, following Least Privilege Access.

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 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…

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.

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.

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.

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…