Bill McCrary

My feedback

  1. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary supported this idea  · 
  2. 114 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  5 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary supported this idea  · 
  3. 58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  API Management » Policies  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary shared this idea  · 
  4. 37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary commented  · 

    Not really - take the dev/test/production example, production will sort before test. We'd like a nice UI with sort indices or draggable layouts, etc.

    To take this to the next level - also offering more than 1 template would be nice. For example a template like Azure pricing uses @ https://azure.microsoft.com/en-us/pricing/details/api-management/

    Table = product group
    Cols = product tier
    rows = product tier meta data (rate, limits, etc)

    Numerous other templates would work but you get the idea.

    Bill McCrary shared this idea  · 
  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary shared this idea  · 
  6. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  API Management » API management experience  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary commented  · 

    It looks like we can delete issues from the publisher portal - but still no concept of "private", we need to have issues marked private by default.

    Bill McCrary commented  · 

    +3 - at a minimum, give us options to sort-by-api. There is an API selection option in the main "New Issues" view, but when I try to see the list, that bit is missing. There also needs to be some moderation or way to remove abusive comments. Right now there is really no way to lock this down...

    Bill McCrary supported this idea  · 
  7. 359 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  39 comments  ·  API Management » Developer portal  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary commented  · 

    +3 - I just tested this, most things seem to sync but not widget markup. For example I simply added a logo to the header widget, backed up to git, clone/copy to 2nd instance repo, push and deploy, but the logo was missing. APIs, products, etc synced but not the widget markup.

    Bill McCrary supported this idea  · 
  8. 23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Web Apps » CLI/Powershell  ·  Flag idea as inappropriate…  ·  Admin →

    This is currently not supported with Set-AzureWebsite or Set-AzureRmWebApp commands, we are currently looking into ways to add the support to the new Azure Resource Manager PowerShell cmdlets
    http://aka.ms/webapp-powershell

    For now you can use something like the following:

    Define the following function:
    Function SetWebApp($ResourceGroupName, $SiteName, $ConfigObject)
    {
    Set-AzureRmResource -ResourceGroupName $ResourceGroupName -ResourceType Microsoft.Web/sites -Name $SiteName -PropertyObject $ConfigObject -ApiVersion $WebAppApiVersion -Force
    }

    And call it like this:
    SetWebApp $ResourceGroupName $SiteName @{ “alwaysOn” = $true }

    Ahmed, Azure App Service Team

    Bill McCrary shared this idea  · 
  9. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  1 comment  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary shared this idea  · 
  10. 19 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    10 comments  ·  Application Insights » SDK  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary shared this idea  · 
  11. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Data Sync  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary shared this idea  · 
  12. 127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Azure Search » Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Bill McCrary commented  · 

    Exactly this - we have to have some way to monitor this backend stuff. Indexers are a no-brainer for our use case, but now I have to manually monitor this job until the platform can do that for me.

    I hope these alerts also include things to help us monitor scale, like QPS/response time analytics, possibly a query analyzer like SQL offers to help people identify query improvements.

    Bill McCrary supported this idea  · 
  13. 197 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Storage » Files  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. We plan to support Shared Access Signature in Azure Files via REST API to allow anonymous public access to data in the file share. However we do not have a specific timeline to share yet.

    Bill McCrary commented  · 

    Please implement this. We want to replace S3 with Azure file storage, but we cannot until there is a simple way to allow public GETs against the file system rest API.

    Bill McCrary supported this idea  · 
  14. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Diagnostics and Monitoring  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Nir Mashkowski responded

    We currently put an entry in the Operation Log whenever there is a Success or Failure in autoscaling. We also send an email on the Failure, but not success of autoscale. The reason for this is it would be extremely noisy – we do many thousands of scale actions in a day.

    We may potentially add this as an opt-in only feature in the future, but it’s not on the immediate roadmap.

    Bill McCrary commented  · 

    Seconded - noisy or not, let the customer handle that with an option in the portal's scale settings or email rules or whatever. The resource alerts help here, but until the settings options for alerts are exactly like the scaling rules, we're not going to get perfect correlation. We'd like the auto scale action to give us the option to receive alerts.

  15. 2,711 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    163 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)

    Bill McCrary commented  · 

    More dirty business from marketing. Every time I hear someone from MS speak about this feature, it all boils down to one load of bull: they CAN cap whatever they want, they just are NOT ALLOWING us to cap the accounts we want.

    Just look at the most recent update to this thread:

    @Chaitanya – We do have offerings for Educational institutions through the Microsoft Educator Grant Program, which implement a form of this feature.

    Just another obvious example of MS selectively capping what THEY want to cap, but playing dirty with our enterprise dollars.

    Our company is considering spending a very nice chunk of change in Azure in the following years, but maybe Amazon deserves those dollars more than MS...

    Bill McCrary commented  · 

    This appears to be a major problem for lots of people. 1,300+ user voice votes, but this is not even in the “planned” phase?

    I also think this is a really bad business practice to be able to cap “free” accounts, but not able to cap accounts tied to real $$$. I mean, my MSDN account is capped at $100/month, and you better bet the minute I use that last penny, my account is SHUT DOWN until those credits renew the next month. So, they CAN cap accounts, but are not ALLOWING us to cap an EA account, essentially giving Microsoft a blank check if we experience malicious activity?

    If Microsoft has zero options for us, I’m going to have to reconsider some things.

    Bill McCrary supported this idea  · 

Feedback and Knowledge Base