Brandon

My feedback

  1. 26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
  2. 521 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  76 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  3. 313 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Upvotes: 249

    <=-=Oct 4 2016 2:15PM=-=>

    This is similar to my feedback located here: https://connect.microsoft.com/SQLServer/feedback/details/2769130/sql-2016-temporal-tables-with-triggers. The solution I suggest is similar to this, and could be used in many different cases developing using SQL server.

    <=-=Jan 10 2017 9:43AM=-=>

    I would love this too. The issue is that many/most applications don’t use Windows Auth in the connection to SQL Server (connection pooling issues, etc), so SQL can’t get the User information

    <=-=Jan 10 2017 9:51AM=-=>

    @Sanford

    Just to clarify, I am not asking for an “automatically store user name” feature. I’m asking for “automatically store whatever I want, based on whatever expression I provide.” So the fact that the user name may or may not be available is not really relevant.

    That said, there are plenty of workarounds for various situations. I imagine that if you’re using a shared connection, you can get some notion of “user” some other…

    Brandon supported this idea  · 
  4. 435 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  5. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Signup and Billing » Bugs  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the feedback. There are two issues here, and we’re working on both:

    1. There’s a delay between when usage occurs and when the event reaches the billing system. We’re working on reducing the latency in the pipeline so that we can build projections on better data.
    2. We currently employ a simple linear extrapolation. We’re working on improving our forecasting algorithm as well.

    Brandon supported this idea  · 
  6. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Cost Management » Cost analysis  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon shared this idea  · 
  7. 1,231 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Folks,

    Thanks for the questions and suggestions. And apologies for not sharing any update on this thread for so long. We’ve been working on this problem and have announced changes on our official team blog (see here: https://cloudblogs.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-microsoft-account-overlap/).

    First, we are acutely aware of the UX pain this is causing and we are sorry for this. We are trying to undo a decade and a half of systems divergence. There are literally hundreds of different engineering teams across Microsoft involved in this effort. So this is taking time.

    Second, we can’t easily “merge” two accounts, or allow IT to “take over” personal Microsoft accounts. There are two main hurdles: (1) The terms of service are fundamentally different for the two account types and (2) they are based on different technologies with different stacks (different identifiers, SDKs, token formats, etc.). We’re working to converge the two stacks but again this…

    Brandon supported this idea  · 
  8. 262 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  16 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
    Brandon commented  · 

    I would also like to see this implemented. It is odd that my cycle is billed from the 27th to the 26th, but my invoices aren't generated until the 17th of the following month, and the credit card gets charged on the 27th, a full month after the cycle ended.

  9. 165 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  12 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  10. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Marketplace » Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  11. 2,842 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    173 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →

    Quick update,

    We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.

    After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.

    We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.

    Thanks for your continued feedback,

    -Adam (Azure Billing Team)

    Brandon supported this idea  · 
  12. 360 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  37 comments  ·  Azure portal » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  13. 420 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  51 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  14. 1,145 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 
  15. 1,538 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    159 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon supported this idea  · 

Feedback and Knowledge Base