The limit has indeed been raised to 20. We’re interested to learn about scenarios that require more than 20 modules.
Thanks for the 20, we'll need more :-) The simplest designs separate coupling and concerns. At best, we would have simple modules (containers) in the IoT-Edge for each device type that is installed in a factory floor or hospital region. This can be well over 20 device types (classes or categories of different device types) of course.
If we take this separation-of-concerns thought further and say that we'd like to have even simpler code and better separation of concerns, then each edge module could handle and individual instance of a device. Then, our code would not even have to do multiplexing and multi-device-instance (of a device type/class) management. This instance-variant would be closer to functions as a service though, which is already available on the Edge if I am correct -- as long as it is production-ready...
This is a must-do for the IoT-Hub and IoT-Edge. Announce it now, or lose serious ground. Sincerly.
we will consider this request.
Apologies for the confusion on our part.
This is currently not on our roadmap. However, we will review this item in the future as we prioritize future releases.
Thanks for your suggestion.
A GraphQl service like graphcool and https://cloudacademy.com/blog/aws-appsync-graphql-as-a-service/ as an Azure AppService would be preferable ... I think there is a feedback.azure.com suggestion regarding this already.
Hi Richard, item #3 has been addressed with the public preview of extended offline feature work. You can find out more about it at the blog post below. The rest of the issues you raise will take longer for us to add to the product.
While we like this idea, it’s not something that is specific to Functions, and not something we have a schedule for. If you’d like to know more about using Functions with GraphQL, check out this workshop:
We’ve put out a new version of the sign in policy called sign in v2. This is available through the new portal experience and we have rebranded policies as user flows. Please give this a try and give us feedback through this link: https://microsoft.qualtrics.com/jfe/form/SV_0Gu45RkBy2YR1kh
As long as it is brandable and customizable (like Auth0's lock.js) then this is fine.