Chris Pietschmann
My feedback
-
2 votes
-
1 vote
Running IoT Edge on an Azure Sphere device would be interesting; however it’s not planned at the moment. I’m not sure how powerful the NXP chips are; however you are correct that we would need a more powerful Azure Sphere chip than are available today. Additionally there may be some other issues we need to address in terms of authenticating with the Azure Sphere Security Service.
The first step for integration with Azure Sphere will be allowing them to gracefully connect to an Azure IoT Edge device.
Chris Pietschmann
shared this idea
·
-
3 votesunder review · 1 comment · Azure IoT Edge » Installing IoT Edge runtime · Flag idea as inappropriate… · Admin →Chris Pietschmann
commented
Azure IoT Edge runtime support for Windows 10 IoT Core on a Raspberry Pi or other device would be really great. Hopefully, Windows IoT Core is updated with support for Raspberry Pi 4 soon too.
Chris Pietschmann
supported this idea
·
-
1 voteChris Pietschmann
shared this idea
·
-
3 votesChris Pietschmann
commented
With the Azure Sphere OS kernel being Linux, and many parts being released as Open Source, I'm assuming the cryptographic functions already are open source.
A note to the product team, could you point us to the code that does the cryptographic functions? Also, a GitHub project for the open source components of Azure Sphere would probably help with this "fear" of trusting the code; rather than only making the code downloadable from Microsoft.
-
2 votesChris Pietschmann
supported this idea
·
-
1 voteChris Pietschmann
commented
I think the NXP chips should support this once they are released. It looks like the NXP chips are targeting more processing power from what was announced.
-
1 voteChris Pietschmann
shared this idea
·
-
17 votesChris Pietschmann
supported this idea
·
-
28 votesChris Pietschmann
supported this idea
·
-
59 votesChris Pietschmann
commented
It would also be really useful if during development/testing we could use the Azure Sphere device with a specific Tenant, and then move it to a different Tenant when we move the device to production. I know, you'd think, generally a test device wouldn't get put into production, but we all know that actually does a happen at times. It'd be really nice if we could use a command like "azsphere device unclaim" to let a device go from the Tenant, so that it'd be free for another tenant to claim again.
Chris Pietschmann
commented
Being able to unclaim a device and re-claim it on another Azure Subscription and AS3 (Azure Sphere Security Service) tenant would be really nice to have. There are scenarios for production devices to change custody as described in the description of this feature request. However, another really useful scenario would be during development of a POC. Once a device is claimed, it's currently not possible to give that device to another developer to build POC's with unless they are able to access the same Azure Subscription and AS3 tenant. I understand the production implications to device trust if you're able to unclaim and re-claim devices, but to be able to do this with at least the development kit devices would be really great.
Chris Pietschmann
supported this idea
·
-
1 voteChris Pietschmann
shared this idea
·
-
5 votes
We are working on enabling this functionality on the functions Premium Plan.
Thanks for the feedback!
Alex
Azure Functions teamChris Pietschmann
supported this idea
·
-
9 votes
We have just announced the imminent release for .NET Core 3.0. See the following reference:
https://github.com/Azure/app-service-announcements/issues/200Thanks,
OdedChris Pietschmann
supported this idea
·
-
14 votes
This continues to be unplanned, but it’s a great item. Please keep the votes coming!
- Matthew
Chris Pietschmann
supported this idea
·
-
20 votes
We have just released integration with API management as there is a consumption plan. Please review https://docs.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition to see if this meets your needs.
Chris Pietschmann
supported this idea
·
-
23 votes
This makes a ton of sense. We don’t have this work fully designed or scheduled, so marking as “unplanned” for now, but we will be looking to tackle this.
- Matthew
Chris Pietschmann
supported this idea
·
-
317 votes
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.
Chris Pietschmann
supported this idea
·
-
1,797 votes
Just a quick update. Work on this feature continues but is taking longer than expected.
We have recently published guidance how how users who can run Windows in a VM whether on Parallels or Virtual Box with a Mac or Linux host can use the Cosmos emulator. Please feel free to use this as a workaround.
https://docs.microsoft.com/en-us/azure/cosmos-db/local-emulator#running-on-mac-or-linuxWhen this feature is complete we will update here.
Thank you.
Chris Pietschmann
supported this idea
·
-
85 votes
We want to add this as well.
Chris Pietschmann
commented
The new Azure Portal redesign changes that were just launched does have contextual help information and easier navigation builtin. This request is from over 3 years ago, and I would consider that this item has been completed. Thanks for all the Azure Portal improvements!
Lol Thanks for including my Azure Portal + Clippy mockup from my article about an Azure personal assistant (https://build5nines.com/personal-assistants-in-the-cloud-and-clippys-comeback/). :)
Chris Pietschmann
supported this idea
·
Chris Pietschmann
commented
A personal assistance would be great within the Azure Portal. Perhaps, clippy should be brought back and added to the Azure Portal to help us manage our cloud resources even easier. Maybe you could also rename Cortana to Clippy and give it a happier more helpful voice and personality as well.
Do you mean you want to add a Desktop UI to Azure Sphere? That goes against the entire point of Azure Sphere being a microcontroller, and not a microcomputer.