Thank you for your suggestion. We understand it is super important to whitelist specific IP list for ADF as part of firewall rules and avoid opening network access to all. We are working on this with high priority. Once this is ready, we will also add ADF to the list of “Trusted Azure service” for Azure Storage and Azure SQL DB/DW.
Thank you for your great suggestion. We included this in our planning.
we always place network related services in a dedicated Resource Group, as they generally have a different lifecycle and RBAC requirements
278 votesplanned · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
This is still coming. The work is being completed now and we will be able to expose it in a few months.
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.
Azure Portal Team
When you attempt to move VMs created from a marketplace image (EG SQL Cluster) it fails with this error message: "Resource move is not supported for resources that have plan"
Is this going to be addressed?
I was then asked to raise a subsequent case [REG:116081714555243], upon which i was asked to post on here. This is the response from paid Premier Support!
"I pulled information about one of the VM from your subscription and it has more than 80 characters
Can you submit product enhancement request on the following link
Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature list and also gives us insight into the potential impact of implementing the suggested feature
Please please please please please add interactive console access as many here ask (surely for good reasons!???) Network appliances such as barracudas are prime examples where connectivity loss may not be fixed by simply seeing the screen, or resetting ssh access. There are steps related to routing which if misconfigured mean not only do you lose access to the VM, but also have to request the license again. Equally, the diagnostics are not on by default and so when you need it, it's not switched on and on every occasion I've tried to enable it on a troubled VM, it's failed. We need the last resort available to us- we need to be able to connect to console! You don't need it often, but when you need it, you NEED it!
We are working to understand the requirements of this feature and deliver it. If you have any scenarios or examples that might help us take a decision kindly give a detailed comment below.
The first part of your request is under discussion – it’s something we hear frequently and are thinking about quite a bit!
For domain join, please see https://github.com/Azure/azure-quickstart-templates/tree/master/201-vm-domain-join
If you’re having issues with DSC or custom script extensions working as expected, please open an item in the Virtual Machines section – the right folks will see it there :)
We’ve moved this ask to the backlog due to technical challenges in reserving Public IP addresses during stop state.
I agree, this is a considerable hidden cost, and it seems daft that you pay more for a router than you do for a server. If you have a network with multiple segments, the costs rack up.