Azure is prohibitively expensive for small businesses and new/poor developers.

£150 for 30 days is not long enough to get up and running and to make a viable website/app to cover the costs.

Suggestions:
-Allow users to use the free credits over 12 or 6 or even 3 months.
-Or return to your previous offer with free monthly credits for a year.
-Or offer SSL on the shared plan. (sites without SSL are not an option)

£50-£60/pm for a basic website with custom domain and SSL is ridiculous.

I feel my only option is to abandon Azure and look at something like Google's GCP (who are offering $300 for a year), which means I have wasted many years learning the Microsoft and Azure stack.

I really hope you can review your current offers and make Azure a better choice.

Thanks

Need Payment history and total outstanding per subscription.

As a subscriber I can only see invoices at azure, but there is no payment history which tells me how and when azure has captured this payment.

It is our legal right to see the payments captured by AZURE. Tomorrow AZURE go and capture another payment from my card how I will reconcile which payment is for what.

If you are taking payment then you must show somewhere that we have captured this payment via this way against this invoice or for this purpose.

Also there is no way I can see what is my total outstanding. Say my card expired so what happened actually I must know.

If you are hiding payments then how I will come to know whether you are charging me double or any other fraud is happening with me.

Regards
Alok

Currently, Azure status history ( https://azure.microsoft.com/status/history/ )doesn't have permalink. I want to have permalink per status/failuer.

Current issues:
* Status history feed hide status older than 90 days. I can't know older history.
* I can't specify a specific status in history.

Why permalink?
* I should announse failuer or issue of Azure for customers when status updated (occurred and solved). In this case, I added evidence by quoting status report from Azure status history. However Azure status history doesn't have permalink and I should use quote always. That is weak as evidence. (They confuse and dificult look up issues in history.)

Can I use Azure Service Helth?
* Yes. But that is require login to Azure portal. If AzureAD occurred problem such as 6th April 2018, I can't show Azure Service Helth.

related feedbacks:
https://feedback.azure.com/forums/34192--general-feedback/suggestions/15228267-improved-azure-status-page-past-incidents

Despite that PCI compliance is promoted at Azure, a Web App created at Azure is non compliant by default, and cannot be set-up appropriately.

I understand that a Web App is not as isolated as an ASE (that still is not compliance by default, needs advanced set-up), with instances sharing system level settings with other clients (so cannot be changed independently), and I understand some set-up changes that apply to all clients, even ones that do not require PCI, can lead to problems to some of them.

I propose an option to opt-in to PCI compliance at Web App level; enable it can put the instance inside a system with appropriated set-up, shared with other clients that had enabled the option too. Alternatively (if that's not possible), a new 'PCI Web App' service, that has all Web App features plus the PCI compliance by default and keep up to date; on this case, an easy way to migrate existent Web App into this one will be useful.

As an example, a PCI Web App will disable TLS_RSA_WITH_3DES_EDE_CBC_SHA, TLS1.0, both enabled at Web App right now and not compliant.

Currently, you can tag most types of resources using portal.azure.com, Powershell or any other tool for that matter. Tagging "hidden" type of resources (for example Microsoft.Network/networkWatchers) is hidden on the portal, but they can be tagged by using a Powershell script which for example tags every resource inside a resource group.

This behaviour is inconsistent, because after this, listing tags on the portal show that the specific tag key:value pair is in use, but you won't see which resources use it. You need to rely on Get-AzureRmTag or other means to actually reveal which resources are tagged.

As of currently, this seems quite inconsistent and can result in errors when using tags for billing data or other purposes. Please streamline the tagging experience by allowing tagging on hidden resources (and showing them) in the portal, or prevent tagging hidden resources entirely.

The attachment is about a law in Turkey by BDDK (Banking Regulation and Supervision Agency).

LAW ON PAYMENT AND SECURITY SETTLEMENT SYSTEMS,
PAYMENT SERVICES AND ELECTRONIC MONEY INSTITUTIONS.

-------

Keeping documents and records, protecting personal information and
notifying changes.

ARTICLE 23 – (1) The system operator, payment institution and electronic money institution shall keep the documents and records related to the issues mentioned on this Law for a period of minimum ten years at a safe place offering access anytime desired in the country. The system operator, payment institution and electronic money institution shall keep the information systems used for conducting the activities and their backups within the country.

Source: https://www.bddk.org.tr/WebSitesi/english/Legislation/129166493kanun_ing.pdf

we hosted application in Azure VM and configured WAF Application Gateway. But we are getting following error

Request body no files data length is larger than the configured limit (131072).. Deny with code (413)

For this we done so much googling and found the solution that we need to increase following parameters in the application gateway. If not possible then need configuration to by pass this limit checking so our application will not stuck because sometime application need to send request with this length.

Request to increase the mod_security limit for following attributes : SecRequestBodyLimit 536870912 SecRequestBodyNoFilesLimit 536870912

Many others are facing same issue and reported to Microsoft as well.