Discovered an unexpected dependency

I had planned to develop the full-text search feature for the new blog engine before starting to deploy anything to production, but I hit a snag. Microsoft Azure only allows you to have one free search service per subscription. Since my dev/test subscription already uses one (for the Weather Now dev environment), I'll have to create a free search instance in my production environment. And because I don't want to deal with cross-subscription security and all that shiznit, that means I'll have to create at least the Cosmos database and key vault production instances as well.

Oh, and the beta test instance of the new blog won't have search capabilities; it'll only work in production and in local development, again because of cross-subscription security barriers.

Also, creating a production environment is a pain in the ass.

Bottom line: I probably won't release the new app into production for a couple of weeks.