Mike Webber

My feedback

  1. 64 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber supported this idea  · 
  2. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  3. 9 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  4. 68 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Automation » Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    You can currently add multiple schedules to a single runbook and use different parameter values with the different schedules.

    Would this work for you or do you need the ability to add the same schedule to the runbook, but with different parameters values? Or are you hoping to use entirely different parameters for each schedule?

    I’m trying to better understand your use case to help us prioritize this feedback.

    Thanks,
    Beth

    Mike Webber commented  · 

    Having the ability to add the same runbook to the same schedule multiple times with different parameters would be ideal. An example scenario would be a runbook that performs standard database maintenance tasks. The runbook parameters include the database to execute against. The runbook needs to run against many databases at the same time. To handle this scenario currently, a duplicate schedule needs to be created for each database. Having the ability to add the same runbook to a single schedule with different parameters, would allow a significant reduction in the number of schedules required. This would make it easier to manage.

    Mike Webber supported this idea  · 
  5. 50 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  6 comments  ·  Networking » Load Balancing  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  6. 26 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Networking » Speed/Bandwidth  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber commented  · 

    Best practices for a virtual data center recommend having a hub and spoke vnet architecture. Ingress and egress controls are placed in the hub and traffic from and to the spokes is forced through the hub. This results in a large amount of data transiting the peered vnets. $.02 per GB for traffic that is not leaving the data center is not acceptable.

    Mike Webber supported this idea  · 
  7. 174 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Mike Webber supported this idea  · 
  8. 38 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Key Vault » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  9. 2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Active Directory » Domain Services  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber supported this idea  · 
  10. 16 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  11. 36 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  12. 48 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber commented  · 

    Use case 2 is similar to ours. We would like the ability to have VSTS perform the ARM deployment to create the database resource. Then create a contained database user for the service principal used in the VSTS service endpoint. Then VSTS would be able to deploy the SQL scripts in a subsequent task without requiring VSTS to have or use the SA credentials. This is very important when sharing the same logical server across multiple applications and teams.

    Mike Webber supported this idea  · 
  13. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Log Analytics » Azure Resource Management  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  14. 2 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  15. 12 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Application Insights » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  16. 64 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Service Bus  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber supported this idea  · 
  17. 3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  18. 433 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    25 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber shared this idea  · 
  19. 336 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Networking » Application Gateway  ·  Flag idea as inappropriate…  ·  Admin →

    We have raised the limit to 100 recently. We are regularly reviewing the limits and will continue to look for opportunities to raise the limits even further. If you have scenarios requiring limits higher than what is supported, please add your scenario details here (if you are comfortable with that) or raise an issue with Azure support and we will get back to you.

    Mike Webber supported this idea  · 
  20. 859 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  Data Factory  ·  Flag idea as inappropriate…  ·  Admin →
    Mike Webber commented  · 

    It's not reasonable to expect enterprises who are trying to secure their data in an Azure SQL Database to open the firewall to allow all of Azure to connect. Until this feature is available, Data Factory is not a viable option.

    Mike Webber supported this idea  · 
← Previous 1

Feedback and Knowledge Base