Thanks for your feedback here.
Indeed the current user experience is very poor. Not only it is not possible to make bulk updates but the UI is misleading as nothing indicates to the user that such action is not permitted.
You could end up manually adding 10+ IP addresses with their own unique name only to realize you need to do it all over again upon trying to save.
If allowing bulk edit is not possible then a quick fix would be to at least prevent the user from adding/editing more than one IP.
We are more focused around data synchronization than schema synchronization at the moment. We may revisit the priority of this in the future.
We will consider this in the future.
We really need this too. It is literally a show stopper.... Would be great if Microsoft could give us a (rough) ETA on this so we can plan accordingly... Thanks!
Thanks for the feedback. It’s not in our planned scope yet but we’d like to see how many customers need this. – Linda Wang
I echo the need for this. We operate a LOB where users records results of an inspection in a web page (transactional database) and can then generate SSRS report (hosted in Azure VM) that retrieve data from the reporting database. This 5 mins latency requires him to wait 5 minutes after saving his last inspection before he can generate the result of his inspection.
398 votesunder review · 7 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →