Functions used as CIQS provisioning steps timed out after about 5 minutes of execution. That was inconvenient and often led to deployment failures.
One of the recent updates to the deployment engine removes this restriction and allows all functions, regardless of the programming language, to run indefinitely long. In addition, Functions used as provisioning steps no longer need to be anonymous (which essentially makes them publicly accessible). In fact, they don’t even need to be enabled! See this example to learn how to build more secure solutions.
CIQS will parse ARM errors to identify potentially recoverable conditions. If appropriate, a link to corresponding recovery steps will be shown to the user to assist them in successfully completing the deployment.