Yep, this is needed. This is a security issue, imo.
Thank you for the feedback. We are working on prereqs to make this possible. Not in scope for CY2019.
This just bit me. I migrated a Public IP from classic to ARM and couldn't use it in the LB.. now we're stuck. Please fix this!
23 votesplanned · 8 comments · Azure Active Directory » Domain Services · Flag idea as inappropriate… · Admin →
Thank you for reaching out! We definitely want to support Azure Cloud Germany. Please vote this feature up to help us prioritize it.
Thank you for your feedback!
We are still waiting to see how many people might find this feature useful.
I don't think this needs to be a feature request. It's far too obvious that it should "just work". Two tables with same name, different schema (e.g. dbo.users and dba.users) shouldn't collide (as they obviously don't in the database).
394 votesunder review · 7 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
Good feedback. Let us take a look. Please vote this up if others would like this support.
What's the latest with this? It's a horrible experience to not be able to precompile the site before the LB starts sending traffic. There needs to be some direction here.
3 votesdmarlow shared this idea ·
This would be pretty neat. I just ran into a scenario where something caused a big spike. I'd love to see being able to set the DTU limit when setting up a connection (like via the connection string).
Just to confirm, your primary goal here is to be able to update just a single role in a deployment instead of having to update the entire deployment when you update just one role. Correct?
Yes, that is correct. Whether that be a single role, or a specific instance of a role.
Yes, I'm talking about exposure control. It may not always be ideal to use this if there are breaking changes being rolled out. However, if it's more functional or mostly UI based, it may be possible to deploy to a single instance.