Dirk Boer

My feedback

  1. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Cache » Azure Redis Cache  ·  Flag idea as inappropriate…  ·  Admin →
    Dirk Boer shared this idea  · 
  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Dirk Boer supported this idea  · 
  3. 415 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Dirk Boer commented  · 

    This is a really big blocker for SAAS applications with no simple workaround. According to this stackexchange https://serverfault.com/questions/104160/wildcard-ssl-certificate-for-second-level-subdomain it is actually working on modern browsers.

    Any update on an ETA? Could this be months or years?

    Dirk Boer 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

    0 comments  ·  Azure Active Directory » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Dirk Boer supported this idea  · 
  5. 228 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Dirk Boer supported this idea  · 
  6. 2,737 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    166 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)

    Dirk Boer commented  · 

    Yeah, please copy paste this somewhere in your codebase:

    if ( CurrentBill >= Account.SpendingLimit )
    {
    Account.Suspend(); Account.SendNotificationMail()
    }

    The lack of this feature is absolutely ridiculous. Usually I'm a big Microsoft and Azure fan, but this is completely unsellable. I can't get rid of the feeling that this was a deliberate trap to make some extra money by companies that are paying less attention.

    Dirk Boer supported this idea  · 

Feedback and Knowledge Base