Olivier Bloch

@Mark:You are spot on! The use of the MXChip board is just meant to illustrate the use case and the Chirp SDK is usable on other hardware

@Barrett: you can find all the service client samples (including code that shows how to add a device to the registry) in the Python SDK repo: https://github.com/Azure/azure-iot-sdk-python/tree/master/service/samples

@Steven McNeese: this is a great question. It's a bit of a chicken and egg question as a device won't have any sort of access to the cloud if it doesn't have an actual network connection. And for this reason, the Azure IoT platform itself cannot provide such a feature. 

As you might have noticed on most consumer IoT devices connecting to the Web, the user has to setup the Wifi connection at first use. This is one way to do this. Another way is to flash Wifi credentials on devices at production time, but this means you have to know where the devices will go.

Hi @DimaKan!

Actually a colleague of mine has been playing with the Movidius USB Stick and had it working with IoT Edge. We might be able to have this published on GitHub if he has some time to clean it up.

@MhAlan: instructions are in the github repo linked in the description. Let us know if you can't find what you need to repro the demo. 

@Scott: That's weird. I do have sound here and double checked the video directly and all seems fine. can you confirm you still have the issue after trying different browsers/machines and or rebooting? Thanks

@Dixon: The best way to address developers needs is to put our shoes in theirs and there happens to be a lot of IoT developers out there working on Macs.

Hey @Aaadil

You always have something that needs to be flashed on the device (firmware, bootstrap) that will have the code to connect to the DPS service. But this code will be the exact same on all devices coming out of the production line. When we say zero-touch provisioning in the device management space, that means that you don't need to have manual intervention on every single device to provision them with unique credentials and code.

You will ask "but how will DPS identify and differentiate devices from one another if they all have the same code running on them?". Well, this is where HSMs solutions like TPM are used. HSMs usually have unique secret seeds flashed in factory by chip makers which  are used by our bootstrap code to authenticate when connecting to DPS. in the case of the MXChip devkit, there is an ST-Safe chip in there. Check out this sample that shows how to provision an MXChip devkit with DPS: https://microsoft.github.io/azure-iot-developer-kit/docs/projects/dps/

@xLANxDIx: The dev in me had a good laugh reading your comment... the CEO as well! :D

@Aaadil: The Remote Monitoring preconfigured solution already offers simulators out of the box, but if you want to test at scale (more than a few devices), you can use the Device Simulation service that comes in the form of separate preconfigured solution on azureiotsuite.com

@Aaadil: This is a legit question. Here is the difference:

- IoT Central is a SaaS solution that is managed by Microsoft in terms of scaling, multi-tenancy,...). With IoT Central you can customize the type of devices and the dashboard as well as some rules, all of that form the IoT Central portal itself. You won't have to host the services on an Azure subscription (you actually don't need an Azure subscription to try IoT Central :)) 

- The IoT Suite Remote Monitoring Preconfigured solution is a solution that deploys on your Azure Subscription and that you can then configure (down to the PaaS services and micro services) at will. Think of it as a template for building your IoT solution

Going one way or another very much depends on the level of customization you need/want.

Hope that clarifies things

Olivier

@Ian2: the short answer to your question is no, this is not something that I am able to tell you today as there is very little that is public about the next version of Windows Phone as of today. However, considering  the popularity of PhoneGap and the fact that this is a community open source framework, you should expect it to support future popular mobile platforms once they are out there.