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.

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Display Name for Custom Connection Type Properties

    With the current Connection Type extensibility, giving 'friendly' names to the properties within the type is not possible, resulting in unfriendly names displayed to the user when creating a new Connection. Supporting Text Hints would also be nice, though less necessary.

    ie:
    {
    "ConnectionFields": [
    {
    "IsEncrypted": false,
    "IsOptional": false,
    "Name": "ServiceBusNamespaceURL",
    "DisplayName": "Service Bus Namespace URL",
    "Hint": "ie: https://[namespace].servicebus.windows.net",
    "TypeName": "System.String"
    },

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow Advanced source Control Sync to Github and VSTS

    provide an option to allow users to unhide the runbooks that sync AA and Github to allow users to modify the process, with their custom process.

    Use case would be adding an email notification or integrating with a ticketing system so their is a record of who preformed the sync and when in other system than the Azure Audit log.

    0 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  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for posting this! You can actually overwrite these scripts with your own content today just by importing a runbook with the same name as the script (just like global modules, these are global runbooks). So for example, you can name a script Sync-MicrosoftAzureAutomationAccountFromGithubV1 and your script will run when you click the “Sync” button.

    In order for us to make these scripts public, we need to remove some proprietary code so this isn’t just as simple as releasing them. I’ll discuss with the team to see what we can do though.

  3. Graphical Runbook: Input that had a default but afterwards is set to mandatory still have default value in tester

    Steps

    1. Create input at set a default value
    2. Set the input to be mandatory, which hides the default value textbox.
    3. test the runbook in the tester, and the default value will still be inserted in to the input textbox
    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  2 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
1 2 24 25 26 28 Next →
  • Don't see your idea?

Feedback and Knowledge Base