Chris Pietschmann
My feedback
-
1,004 votes
Hey Folks,
We have made some great progress on this idea and most of our services today do support move resources across groups.
We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.
Please file individual asks on each service category present in uservoice and vote for it.
Thanks,
Azure Portal TeamChris Pietschmann supported this idea ·
-
1,157 votes
Hey Folks,
We have made some great progress on this idea and most of our services today do support move resources across groups.
We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.
Please file individual asks on each service category present in uservoice and vote for it.
Thanks,
Azure Portal TeamChris Pietschmann supported this idea ·
-
21 votes
Chris Pietschmann supported this idea ·
An error occurred while saving the comment -
70 votes
An error occurred while saving the comment Chris Pietschmann commented
Specifically support for writing Azure Sphere apps with C# and .NET Core 3 would be nice for .NET developers. However, most IoT developers are probably already most comfortable with C. Supporting C# would add the benefits of .NET to Azure Sphere, although with a more limited memory space, it may be more difficult to fit .NET based apps on the Azure Sphere devices.
Chris Pietschmann supported this idea ·
-
50 votes
Chris Pietschmann supported this idea ·
-
384 votes
Thanks for the suggestion, we are looking into the feature request
Ahmed
Azure App Service TeamChris Pietschmann supported this idea ·
-
37 votes
Thank you for taking the time to vote for this item.
We are looking to options to address this scenario.
Chris Pietschmann supported this idea ·
-
70 votes
Hi Magnus. This is currently unplanned by us for our road map. Some context and feedback for you on this.
First, to do the replication itself to the secondary region you need RU/s sufficient to support the request rates for the primary region itself. Replication and writing to the secondary region itself is not free so there needs to be sufficient throughput provisioned to do that.
Second, for the secondary region to be able to function as the primary should a fail over occur, the replica region itself needs sufficient throughput to function as the primary.
Thanks again for your suggestion. Will mark as unplanned for now in case circumstances ever do change.
Chris Pietschmann supported this idea ·
-
12 votes
We are working on this but do not have an ETA for this yet. Will update here as we get closer to releasing.
Thank you for your suggestion.
Chris Pietschmann supported this idea ·
-
147 votes
An error occurred while saving the comment Chris Pietschmann commented
So often you are required to open multiple browser tabs to various different services and blades within the Azure Portal at the same time. it would be nice if the Azure Portal supported tabs more natively.
Here's 2 suggestions on how tab support could work:
- Add ability to open links within the Azure Portal in a new browser tab when desired.
- Add mutli-tab support to the Azure Portal UI / UX itself so you can have multiple blade views open simultaniously.The reason for this request:
When managing production workloads it's often the case where you need to monitor multiple services, and/or make configuration changes in multiple places. It's extremely cumbersome to keep navigating around the Portal between resources, especially when you need to go back and forth between multiple resources.There are many times when you need to keep, for instance, an App Insights Live View open, while making database queries to an Azure SQL Database, and checking the trigger status of Azure Functions when monitoring and troubleshooting.
Chris Pietschmann supported this idea ·
-
22 votes
An error occurred while saving the comment Chris Pietschmann commented
This would be more a limitation of the Solidity language, and not Azure Blockchain Workbench itself. And Solidity does support enums and structs.
-
31 votes
Chris Pietschmann supported this idea ·
-
5 votes
Chris Pietschmann shared this idea ·
-
17 votes
Chris Pietschmann supported this idea ·
-
5 votes
In September 2014, Microsoft announced plans to deliver Azure from datacenters in India. You can read more here: https://www.microsoft.com/india/datacenter/
An error occurred while saving the comment Chris Pietschmann commented
Isn't this one already completed?
-
128 votes
Hi, we are currently reviewing this feature for implementation.
Chris Pietschmann supported this idea ·
-
445 votes
Thank you for your feedback. Would a display name type of label for resources address your renaming scenario?
Chris Pietschmann supported this idea ·
-
262 votes
We are very excited to announce the Public Preview of Azure Resource Mover https://aka.ms/resource-mover-preview
Azure Resource Mover is a new free service that greatly reduces customer time and effort needed to move resources across regions by providing a built-in dependency analysis, planning, and testing that ensures the resources are prepared to move and then successfully moved to the desired region.
Currently, using this capability, customers can easily move their
Virtual machines with managed disks,
Networking components (NIC, VNET, NSG, Load Balancer, Public IP)
and SQL Azure resources (Database and Elastic pool)from one Azure region to another. The service is available through the Azure portal, PowerShell, and SDKs with any Azure subscription and you can move resources from any public region to any other public region.
We will be improving the resource support coverage in the coming months.
Support for moving customer production workloads is now…
Chris Pietschmann supported this idea ·
-
10 votes
An error occurred while saving the comment Chris Pietschmann commented
Do you mean like here: https://stackoverflow.com/questions/tagged/azure
-
625 votes
SSL only requires multiple IPs when the client is on Windows XP, using an older version of Internet Explorer. Most modern browsers support SNI (Server Name Indication) and thus don’t require multiple IPs.
Support for multiple IPs is under review in the team.
Chris Pietschmann supported this idea ·
The Azure Sphere OS code is already Open Source and licensed under GPL2. It's available for download here: https://3rdpartysource.microsoft.com/ However, it's not OSS like we've grown accustomed to. It would be great if the project were hosted on GitHub and accepted PR's. I understand that in Preview, it's rapidly changing, but once it reached Production it'd be nice to have a "standard" Open Source project for the Azure Sphere OS code over on GitHub.
For now, in case anyone is interested, I've put together a repo to make it easier for myself to look at the source code and see changes between Preview version releases. You can access it here: https://github.com/crpietschmann/AzureSphereOS Keep in mind this repo is not supported by Microsoft, and just something I'm doing to grok the code more easily.