Dave Medvitz
My feedback
-
62 votes
Thanks for your feedback
We’ll review this feature to include it on our roadmap.
-
10 votesDave Medvitz
supported this idea
·
-
309 votes
We understand the need for this capability and are looking at ways to solve this. At this time we do not have any timelines to share however but your comments help raise the priority for getting it done.
- Altaf TDave Medvitz
commented
Not having this causes a lot of issues with VNet based azure services. DevTest Labs can't use artifacts, Service Fabric (configured for internal only) doesn't install properly, making both less than useful. Manually putting in a DNS suffix does the trick, allowing those machines to get to our internal WPAD file, but we shouldn't need to do this.
Dave Medvitz
supported this idea
·
-
52 votes
Currently working to understand the requirements for scenarios. Will update the thread soon.
Dave Medvitz
supported this idea
·
-
77 votes
Hi,
Thanks for the feedback. We do plan to improve the performance and scale of Azure VPN gateways. We will provide more updates once we have concrete plans and measurements.
Thanks,
Yushun [MSFT]Dave Medvitz
commented
Increasing the number of VNet Peers would be helpful, as well.
-
8 votesDave Medvitz
shared this idea
·
-
4 votesunder review · 0 comments · Azure portal » Create + deployments · Flag idea as inappropriate… · Admin →Dave Medvitz
supported this idea
·
-
35 votes
We’ve added some custom configurable tiles such as; ‘markdown’ (allows custom markdown), ‘armData’ (will display data from a defined arm GET), and ‘armActions’ (creates a button which will create a user defined arm POST call)
Dave Medvitz
supported this idea
·
This would be especially useful for the default AllowVNet[IN|Out]bound rules. In our organization, we have a hub/spoke network setup, where we have to set our default route to a NVA in the hub. This sets the VirtualNetwork tag to '0.0.0.0/0' and gives us a default NSG rule to *allow all traffic*. While this is the documented behavior, it is not intuitive (you have to go to where the service tags are documented, and even there I don't believe its clear). It also easy to miss-configure, and hard to fix.