Automation

Azure Automation allows you to automate the creation, monitoring, deployment, and maintenance of resources in your Azure environment using a highly-available workflow execution engine. Orchestrate time-consuming, error-prone, and frequently repeated tasks against Azure and third party systems to decrease time to value for your cloud operations.

Visit the Automation page to learn more about Automation and how to get started.

How can we improve Azure Automation service?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Please modify the DSC Installation Scripts for linux to not run things out of /tmp

    CIS hardening techniques suggests to mark /tmp with noexec. If one does this, then they cannot register the VM with Azure Automation DSC as the python install scripts look to be running things out of /tmp.

    The error that is produced in the logs is misleading as well.

    2019/05/30 19:34:24 ERROR:Checking for ctypes python module...Error: Python does not support ctypes on this system. Please install the ctypes module for Python or upgrade to a newer version of python that comes with the ctypes module.

    ctypes isn't the issue here, noexec being placed on /tmp is.

    Thanks!

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  2. Increase 1MB Size Limit for DSC Node Configurations (MOF files)

    Azure DSC node configuration (MOF files) are currently limited to 1 MB in size. This limitation does not allow for significantly detailed or complex configurations.

    In my specific scenario, we have several IIS websites in a our web farm and we've hit the limit of how many unique websites we can configure per server because the MOF file is larger than 1 MB. The resulting error is that the MOF cannot be encrypted by Azure DSC Automation.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Provide Ansible configuration

    I would like to use to Linux configuration by Ansible.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Apply DSC sequentially in Availability Groups and Zones

    Say you have a configuration that applies to two servers behind a load balancer and it includes the installation of some software.
    You now want to upgrade that software so you update the product ID and link to MSI.
    Once the servers pick up the change and attempt to apply it, they could both do it simultaneously causing a system outage.

    Having DSC respect Availability Groups and Zones would prevent this happening and allow the use of DSC for automatic upgrades.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Please allow for versioned configurations in Azure Automation

    It would be great to have multiple versions of DSC configurations compiled into Azure Automation, simultaneously.

    Currently, a server, or other resource, could be provisioned with one version of a configuration, but if an updated version is compiled during pipeline transitions, they could receive a different configuration than tested in a lower environment, invalidating their tests.

    This would allow someone to target a v1.1.0 configuration, even though the latest is v1.1.3 in Azure Automation, for example.

    It would be doubly nice if this could be derived from Git tags or other versioning mechanism in TFS/VSTS, as well.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow VMs to communicate with DSC without public Internet connection

    Can we allow Azure VMs to somehow communicate with Automation Accounts in the same subscription in order to implement DSC without requiring the VM to have an Internet connection? Since the IP address of the automation account changes so readily, I cannot create a specific NSG rule for automation accounts, though I would love to be able to use Azure DSC for our VMs. Today, I cannot due to the inabaility for me to lock down generic Internet traffic on internal-only VMs.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  7. During DSC compilation failure, show full error and line number within the DSC script

    During DSC compilation failure, show full error and line number within the DSC script.

    Currently, you get the line number in the script that is calling and parsing the output of Start-AzureRmAutomationDscCompilationJob. This isn't useful.

    Checking the portal, it gives you the same (not truncated) error message, but no line number. Not useful either.

    Show the full error and line number both in portal and on the exception passed back to the API.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow arbitrary naming of DSC nodes

    If I have multiple VM's in multiple regions and the VM name is duplicated, there's no easy way to know which is which. Can we have some control of the name used when registering the VM? Or can we have some mechanism to apply and view tags?

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow DSC Reports to include ResourcesNotInDesiredState that were corrected during a consistency check

    Currently if a node is set to ApplyAndAutoCorrect, when the report is sent back to the report server, there is no reference to any resources that were non-compliant at the time of the consistency check. DSC will auto correct without reporting what it did. For compliance reasons, we would like to be able to query the report server to see if any resources had to be put back into desired state. We would like DSC to report non-compliance like it does when using ApplyandMonitor mode prior to auto correct.

    Here is the link to the same request on the PowerShell…

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Create an IP to report on DSC drifts / compliance

    PowerShell DSC is currently poor in reporting on configuration drifts and compliance levels. Collect this data in Ops Insight to answer questions like:
    - which systems are experiencing a configuration drifts and for which DSC policies?
    - which is the compliance level for this specific DSC policy / setting?

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base