Consider using pricing plans that allow continuous running when using an MSDN subscription about azure-iot-remote-monitoring HOT 5 CLOSED

Thanks for the feedback, @networkfusion - for the time being, feel free to create a branch for these changes so others can leverage your suggested defaultValues for the Azure services in their custom implementations.

from azure-iot-remote-monitoring.

Closing for now, feel free to reopen if you have additional questions.

from azure-iot-remote-monitoring.

I would like to hear more about the scenario and the minimum requirements and Azure services you would like to see in a lower cost solution

from azure-iot-remote-monitoring.

I applied the above suggestions on my custom solution for PoC purposes at a client. To lower the costs I also merged the webapp and webjob in one Basic App Service Plan. When you are playing with less then 50 devices my experience is that this can be done very well.

Maybe add another ARM template for a low cost solution is a quick solution to this problem?

from azure-iot-remote-monitoring.

@BeatriceOltean It is all about my ability to develop a demo to prove the concept (which is what this product is all about isn't it?). What is the point of an MSDN subscription with Azure credit, if it is unable to run 1 single product continuously throughout a billing cycle. so either the pricing model of the IoT resources need to be changed, the pricing tier of the solution needs to be more appropriate (shouldn't these things be scaled up rather than down anyway) or the monthly azure credit allowance should be increased?!

from azure-iot-remote-monitoring.