We are using Twitter Bootstrap and FontAwesome for icon support.
When deploying to one of our IIS servers I need to add MIME support.
When deploying to Azure, it
UPDATE
This answer is now unnecessary due to recent changes in the FontAwesome nuget package.
In addition to the solution described in the accepted answer, I noticed that the fonts in my project were in ~/Content/fonts, but the site was looking for the fonts in /fonts on Azure.
As a workaround, I copied the font files to ~/fonts (making sure the Build Action was set to Content
for all) and all is good in the cloud.