Web App using Git Deploy Create flow

As part of the Azure App Service team , we are constantly imprving the experience with application created from Azure marketplace. The following apps are using an updated create workflow using Git deploy .

  • WordPress
  • Bakery
  • Node JS empty site
  • Node JS  Express site
  • Node JS Starte site
  • ASPNET Starter site
  • ASPNET Empty site
  • Photo Gallery
  • Ghost
  • Boilerplate
  • HTML5 Empty site
  • Jetty
  • Tomcat
  • Django
  • Flask
  • Bottle
  • Azure ML Batch Execution Service Web App
  • Azure ML Request-Response Service Web App
  • Java Coffee Shop

The create workflow now copies the application code from github repository for the specific application you selected from the list above. There is no change is the user experience when you create the application .The advantage of this process is to easily sync application version updates from the github repository .

We will continue to upgrade apps though multiple phases to the new git deploy workflow . Please check this blog post for update or check out my twitter feed for updates (@mksuni) .

How to update an application installed from Azure Marketplace from Web Apps

If the application you used is listed in the above list , the follow this process to update your application when a new version of the app is available


  • Select settings -> Deployment Source -> Sync



ClearDB and Web Apps FAQ

If you are currently using ClearDB (MySQL ) service  with Azure App Service (Web Apps ) or planning to use these services , check out the FAQ  to understand how procurement of ClearDB which is third party service works with Web Apps for different types of Azure subscriptions.

Using Log parser 2.2 to parse IIS logs for Azure web apps

Log parser is a powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows operating system such as the Event Log, the Registry, the file system, and Active Directory. This is how a IIS web server  log looks like which is hard to read when you want to gather information to either diagnose an issue or analyze the logs.


Parsing IIS logs

Log Parser tool allows you to analyze web server logs and event logs to provide you the snippet of information you are looking for .Download the tool and install the MSI package of the tool.

  • Usually the tool is installed on C:\Program Files\LogParser or  C:\Program Files (x86)\LogParser locally when running it from your client machine.
  • Another option is to upload LogParser.exe onto web app file server ( under D:\home) and run it using Azure web app KUDU debug console.

Here are some sample queries or command you can use to gather information about IPs , number of hits etc . To run these you need to execute LogParser.exe  with this command format

LogParser.exe -i:W3C Query -o:CSV Continue reading “Using Log parser 2.2 to parse IIS logs for Azure web apps”

Azure Billing and Support

The charges for Microsoft Azure subscriptions vary by rate plan. Some rate plans, such as the Visual Studio Ultimate with MSDN, Enterprise Agreement etc include monthly credits that you can use on any Azure service based on your needs. You dont need a paid support plan for any billing related questions. Here are some reference articles to help with your billing questions

Understand your bill
How to create a support ticket for Billing related question
How to change you Credit card associated with your subscription
How to cancel your Azure subscription
What to do if Azure subscription is disabled
How to download usage data and invoice

Azure Storage plugin issue with WordPress 4.4


Windows Azure Storage plugin has a incompatibility bug with the latest WordPress 4.4 version. The generation of URLs for the set of featured images is not being handled by the plugin. Thanks to  Project Nami team  who came up with a solution  for this issue.

We are working on getting this plugin fix updated in the WordPress plugin repository as soon as possible.  Until then you can find the code fix here .