dmarlow

My feedback

  1. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow commented  · 

    Yep, this is needed. This is a security issue, imo.

    dmarlow supported this idea  · 
  2. 564 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Networking » IP addresses  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow commented  · 

    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!

  3. 19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    planned  ·  6 comments  ·  Azure Active Directory » Domain Services  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow supported this idea  · 
  4. 11 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure mobile app  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow supported this idea  · 
  5. 36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Data Sync  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow commented  · 

    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).

  6. 394 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  7 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow commented  · 

    Bueller

    dmarlow supported this idea  · 
  7. 355 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow commented  · 

    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.

  8. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow shared this idea  · 
  9. 68 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    dmarlow commented  · 

    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).

  10. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Cloud Services (Web and Worker Role)  ·  Flag idea as inappropriate…  ·  Admin →

    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?

    dmarlow commented  · 

    Yes, that is correct. Whether that be a single role, or a specific instance of a role.

    dmarlow commented  · 

    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.

Feedback and Knowledge Base