This has a dependency with the client app/technology (.net, etc). I assume the article would avoid deploying a simple .net application too and all of it's complexity? Seems beyond the scope for SQL server, however you may want to scope in a trivial .net app since this is an intrinsic part of moving to the cloud (debatably).
Perhaps scope this to SQL server and refer to an existing article somewhere about deploying the app? I would only guess that the other article would cover the db deployment as well, invalidating this article.
Your call Steve.