Mike

My feedback

  1. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike commented  · 

    Just had a similar issue and the error was the same with no description. turns out it was a permissions issue in case anyone else sees this and comes across it. The suggestion here should be to make the error message less cryptic when there's a permission issue.

  2. 30 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Mike commented  · 

    I'm not sure I agree with this line of thinking for all devices. In a connected world, devices are prone to getting hacked at any time, regardless of if it was lost. Also, forcing a device to be reauthorized once every 60 days ensures that a device has not unknowingly been lost. I found this post looking for a way to lower the 60 day limit for certain high level accounts.

  4. 52 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Mike commented  · 

    I just read up on security defaults and I wanted to post this somewhere, 'Well done!' on making this a standard for all accounts. At one point in order to get MFA you had purchase an AD Premium and I remember posting some feedback that you should never have to pay for security. So, bravo on making this move to make it simple and effective for all accounts to be protected and not charging for it. I agree too that setting up one account to exclude for emergency access would be nice. I know that I can go through the process of setting up in conditional access but the exception account would make it convenient to not have to go through that process, or to be concerned that I might not set it up right since I don't do that every day.

    Mike supported this idea  · 
  5. 38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Logic Apps  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  6. 402 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  7. 728 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  127 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  8. 1,099 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  86 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  9. 67 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Cost Management » Budgets  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike commented  · 

    One more scenario: For the Azure services that have 'serverless' options those can go from a daily low $ to maxing out your credit card without knowing about it. At least being clued into that as quickly as possible would help.

    An error occurred while saving the comment
    Mike commented  · 

    I just went looking for a way to set a daily alert, let me give you the scenario. Sometimes I might be testing something to see how it's going to price out for me or a customer. Having an alert that resets daily really helps me to test it and not forget to turn it off. You might be wondering, 'why not just use a monthly alert and set it really low.' That might works but if I'm playing with the settings trying to get down to a budget then I have to keep remembering to go in and resetting the alert.

    Another scenario: By setting a daily budget amount at 99% of the norm, I get a much quicker notice when something is running hotter (dollar-wise) than expected. Like for example maybe a team member changed a setting and didn't know the price consequences. That quicker insight helps me to manage something I'm spending on that I don't use and don't need.

    Mike supported this idea  · 
  10. 40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike commented  · 

    I hope this has always been planned to roll out in-memory OLTP for lower tiers and was started at the higher tiers to work out the technicalities. Otherwise it kind of defeats the purpose of what cloud is touted for, i.e. the ability to start small and scale up as needed. By offering In-Memory OLTP only on the upper tiers it doesn't give the same advantages to the smaller guys who don't have the big budgets. We're running standard and the price jump to premium or vcores would be an unjustifiable gross overallocation of resources for our needs just to get In-Memory OLTP. So because of that our caching and temp tables are consuming a vast amount of unnecessary DTUs. Either way we're wasting money. Cloud should be helping the little guys so they can become big guys.

    If as the OP says the difference is because of version number of sql server, and it's easier to make a new Standard v2 tier to be able to phase out the older sql, that would work for us at this time, we'd take the time to convert.

    Mike supported this idea  · 
  11. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Signup and Billing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike commented  · 
    Mike supported this idea  · 
  12. 111 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Web Apps  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Mike commented  · 

    I think you can mark this one as done now right? I read a blog post a while back that this behavior was changed and according to this documentation this setting is not swapped between slots: https://docs.microsoft.com/en-us/azure/app-service/deploy-staging-slots

    I updated my sites months ago to have the staging slot settings for 'Always On' to OFF and it hasn't been an issue any more. I've also just now tested it one more time and it's working well!

    Nicely done and thanks!

    An error occurred while saving the comment
    Mike commented  · 

    15 votes in only 6 weeks, that's not bad. Any updates on this? I guess this is harder than it seems?

    An error occurred while saving the comment
    Mike commented  · 

    Any updates on this? This continues to be a pain point for me.

    An error occurred while saving the comment
    Mike commented  · 

    Thanks for the updates Oded and Ruslan. As a workaround for now, does anyone know if I set Always On=false and use something like uptime robot to ping the site is that sufficient to keep it always on? I read somewhere that it won't work for free accounts, but obviously in this case i'm thinking about using it as a workaround on standard or premium tier.

    Mike shared this idea  · 
  13. 53 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Azure Active Directory » B2B  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  14. 103 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    triaged  ·  9 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  15. 1,121 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    74 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →

    Hey Folks,

    We have made some great progress on this idea and most of our services today do support move resources across groups.

    We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.

    Please file individual asks on each service category present in uservoice and vote for it.

    Thanks,
    Azure Portal Team

    Mike supported this idea  · 
  16. 266 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Additional Services  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  17. 69 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  18. 108 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  10 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  19. 166 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  14 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
  20. 249 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    unplanned  ·  7 comments  ·  Azure Resource Manager  ·  Flag idea as inappropriate…  ·  Admin →
    Mike supported this idea  · 
← Previous 1

Feedback and Knowledge Base