Azure Community Support
Ask questions, get answers and connect with Microsoft engineers and Azure community experts
Introducing Azure on Q&A
Find answers to your technical questions about Azure products and services. Connect with Microsoft and community experts, share feedback, and learn from others. Azure on Q&A, on the Microsoft Q&A site, is replacing the MSDN forum. But you can still browse the forum archives.
Microsoft and community responses to older Azure technical questions
Forum: Azure Networking (DNS, Traffic Manager, VPN, VNET)
Forum: Azure N-Series Virtual Machines
Forum: Microsoft Azure Site Recovery
Forum: Azure Active Directory
Community responses to development questions
Community responses to Sys/Net admin questions
Post ideas or suggestions based on your experience with Azure
The calling of an environment variable through a Cron job should have the same accessibility for calling environment variables through the provided kudu Shell
Currently there is no system to manage the diagnostic logs lifecycle other than creating automation jobs. Please create a system to delete/overwrite logs after 1, 3, 6 12 months.
During an EA to CSP or between CSPs migration RIs are not moved, they have to be cancelled and re-purchased. This brings massive challenges.- Microsoft only allows cancellations of RIs up to 50k per year for a customer. Any cancellations request above this have to be approved by the business desk and the likelihood is they will deny it.- When re-purchased the clocks reset. That is, if you have a 3 year reservation bought 1 year ago, when you re-purchase it you start a new 3 year term.- The challenge is even worst for CSPs. If they purchase reservations for a customer and customer leaves they have to continue to pay for these reservations. They might be able to move internally to another customer, if they lucky to have another customer which is using the same instance types, etc.The key here is that the customer will continue to buy Microsoft services during such migration, only the channel he is buying from changes. So they should not be penalized this way.
Make Azure AD Premium Free. A lot of our Tenants are having their mailboxes breached. Seems like Azure Premium has good security features that could really help us but it costs too much. This should be free.
After February 1st 2010, it's going to be tough for developers/freelancers/hobbiest to learn, test and deploy azure applications as it's going to be billed for everything. Like Google AppEngine (http://code.google.com/appengine/whyappengine.html#norisk) Azure should provide free offering for developers with some similar limitations and if the usage goes beyond, one can enter in billing.
The option of using Azure Data Factory v2 to migrate data to the Power Platform / CDS / D365 is good, although there are a few features that are missing that almost negate considering the tool as a viable option. Two such examples are:-1. You cannot write to the createdby field on any entity as the createdby is always set in the context of the user in the Linked Service and does not respect the data that is passed to it as part of the Sink data source2. There is no way to migrate data into the native CDS / D365 many-to-many entities (aka mapping table / entity), despite these only consisting of 3 fields (a unique ID and the 2 Foreign Keys of the related entities).3. No support for PartyList type fields
When you create a custom error page in Application Gateway, the storage blob stored the error page file needs to be accessible publicly now.It would be nice to be able to limit access to the storage blob so that we can make sure our data is secure.
I want to transfer a client certificate to the backend with Azure Front Door.However, Azure Front Door doesn't support the SSL passthrough function.I would like to support transferring the client certificate used in the TLS session established between Azure Front Door and the client to the backend.
For now,when customers want to disassociate WAF policy from Application Gateway,we have to change Application Gateway from WAF SKU to Standard SKU.When we changed to Standard SKU,system can be exposed to threats.Please redesign this just like that disassociating WAF policy from listener.