Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Mark Nash

My feedback

  1. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Update Management » General  ·  Flag idea as inappropriate…  ·  Admin →

    Update Management solution of Azure Automation is a free tool to allow basic patch management by triggering the machine’s OS to install updates as per provided configuration at stated time.

    Hence there are two ways to achieve your scenario “exactly same updates” in test & then prod, by either manipulating the OS behavior or tweaking the AUM config:

    1. - Host the updates locally using Microsoft WSUS [https://docs.microsoft.com/azure/automation/automation-configure-windows-update#make-wsus-configuration-settings] or Reposync utility from RedHat [https://access.redhat.com/solutions/23016]or Ubuntu Landscape [https://docs.ubuntu.com/landscape/], etc. And the configure the update service or package manager of all your machines to use the local update source. In this way the updates installed when using Update Management will only be what is available in your local patch server which is running (say) WSUS or RH Reposync. And if the patch server remain unchanged in 2-3 weeks when you start update schedule for Prod, they will also…
    An error occurred while saving the comment
    Mark Nash commented  · 

    The idea would be that you define the pipeline as : (Dev) -> (Test) -> (Prod)

    Example Scenario:

    There are 3 available patches at start of Monday

    Monday:
    Dev gets patched with all 3 successfully

    Tuesday:
    2 new patches are released on patch Tuesday

    Wednesday:
    Test deploys Dev's 3 successful patches but then fails 1

    Thursday:
    Prod deploys Test's 2 successful patches

    Next Monday:
    Dev gets the 2 new patches deployed, and successfully completes both

    Next Tuesday:
    No new patches released

    Next Weds:
    Test successfully installs the 2 new patches and the patch it previously failed

    Next Thurs:
    Prod patches with the 3 patches that succeded on Test

    Mark Nash shared this idea  · 
  2. 572 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →

    This is not currently planned for the normal SQL DB since the databases within a logical server are not hosted within a single server like in SQL Server – they have multiple replicas that are independently placed on different servers due to the high availability architecture in SQL Azure. However, SQL Azure Managed Instance supports use database as a command because all of the databases in that model are on the same SQL instance – just like SQL Server. It is therefore recommended that you consider Managed Instance for migrations from on-premises SQL Server where you can not/do not wish to modify behavior to fit within a single SQL Azure DB.

    Topic left open for comments and voting, but please note that some of the comments left do not seem to recognize that SQL Managed Instance is available and recommended by Microsoft for many of the use cases listed. We…

    Mark Nash supported this idea  · 
  3. 94 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Site Recovery  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Nash shared this idea  · 
  4. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Nash supported this idea  · 
  5. 17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Automation » User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Nash supported this idea  · 
  6. 689 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Networking » Load Balancer  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Nash supported this idea  · 
    An error occurred while saving the comment
    Mark Nash commented  · 

    Is there any Update to this as it has been almost half a year since It became under review?

    We are looking to implement a way to easily update load balenced servers without taking sites down and this may be the update to Azure that we require.

  7. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Nash shared this idea  · 
  8. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Portal » Create + deployments  ·  Flag idea as inappropriate…  ·  Admin →
    Mark Nash shared this idea  · 

Feedback and Knowledge Base