I was thinking the same. I’d just create a web app and deploy it, even if it had a whole bunch of static content. By doing that, you pick up all the niceness.
Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com<http://www.sqldownunder.com/> From: [email protected] [mailto:[email protected]] On Behalf Of Andrew Coates (DX AUSTRALIA) Sent: Thursday, 28 January 2016 9:47 AM To: ozDotNet <[email protected]> Subject: RE: Azure static web sites Hi Greg, Is there a reason you’d want to do it this way rather than using a Web App? Web apps will give you all of that (host headers, logging etc) as well as reliability and scaling if need be. Cheers, Coatsy Andrew Coates, ME, MCPD, MCSD MCTS, Developer Evangelist, Microsoft, 1 Epping Road, NORTH RYDE NSW 2113 Ph: +61 (2) 9870 2719 • Mob +61 (416) 134 993 • Fax: +61 (2) 9870 2400 • http://blogs.msdn.com/acoat From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Thursday, 28 January 2016 9:17 AM To: ozDotNet <[email protected]<mailto:[email protected]>> Subject: Azure static web sites Folks, I was thinking of moving some of my old static web sites to Azure, and I've noticed via links from others in here that they must doing this already. It looks you don't actually "deploy" a static web site to Azure (like an application), you just make a Blob container, upload the files and make the container access public. A quick test confirms this works okay, but there are some differences ... what's the equivalent of the old IIS log files to track usage? And because it's not your own IIS, what's replaces host headers so that someone going to www.mysite.com.au<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fwww.mysite.com.au&data=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c4f9e6d4075b1475e87b508d327679ac3%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=mYNnU%2bcr0DVJGvpjxBQ8iSYmKByEjz9Omrihpxs6rB4%3d> thinks they're at my domain but in reality they're looking something like this: https://myaccount.blob.core.windows.net/web-mysite-com-au/index.htm<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fmyaccount.blob.core.windows.net%2fweb-mysite-com-au%2findex.htm&data=01%7c01%7cACOAT%40064d.mgd.microsoft.com%7c4f9e6d4075b1475e87b508d327679ac3%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=5HYukAO3huVyWpSDNDz3wk3bu1mnRQ8O3JoTFAQ6mj8%3d> You want to make visitors feel like they're at your domain, not some weird Azure blob url. Greg K
