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.
-
Continuous Deployment of runbooks
I have runbooks that are stored in source control which then get deployed to Azure Automation. The process of deploying them is rather cumbersome (basically a bunch of hand crafted Powershell scripts that call the Azure Automation cmdlets). It seems to me that there are going to be lots of people crafting the same kind of scripts - that's a lot of wheel-reinvention going on.
I'd like to see some features introduced that support quick and easy Continuous Deployment of runbooks (i.e. I check them into source control and they automatically get deployed to Azure Automation).Some ideas:
-Support Continuous…56 votesThank you for the feedback. The product team has noted this suggestion and will consider it if resourcing allows.
-
Start-AzAutomationSourceControlSyncJob Add SyncType parameter to invoke 'Incremental' syncs
The Start-AzAutomationSourceControlSyncJob function only triggers a FullSync from a connected Azure DevOps Repo, which can sometimes take a long time if you have lots of runbooks in a repo. Can we add a pramater to this to trigger an optional incremental sync?
Use Case
The Azure Automation account has this option as a feature toggle but not something that can be triggered ad-hoc after a full sync outside of Azure Automation. We don't want to use the AutoSync feature as we want to control the upload of runbooks via Azure DevOps pipelines with approvals etc. then trigger a sync job…40 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This 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
-
Git (Stash) Source Control Support or TFS On-Prem
Would be good if we could connect to our Stash server rather than having to use GitHub. Alternatively we have an on-prem TFS setup that we could also use. Data sovereignty issues prevent the use of GitHub/VSO at this time.
28 votesThanks for your feedback on this! We are definitively interested in private/on-prem scenarios for source control.
As we start to do more development in this area, our team will follow up to get more details about your specific needs. -
authenticate source control fails
We use VSTS + Git for change control. When asked to authenticate there is a failure with 0 additional information. Our source control is part of the same AD tenant.
26 votes -
Sync in both directions
I find that a possibility to sync to repos would be useful as that would enable creation of already existing runbook files in the repo, also the graphical runbooks (if any) could be exported that way.
23 votes -
Setup DevOps SourceControl sync as a AzureADApp service principle
I would like to list two issues and possibly can be addressed by one implementation.
Would like to setup sync between Azure Automation Account and DevOps as an Azure AD APP service principle and/or managed identity of automation account, rather than a person or on-prem service account.
Would like to access files from DevOps Repository (e.g latest ARM templates) as a REST call using managed identity/service principle.
Above is very important as people leave organisations and can leave broken process behind and the worst is, the organisations would not know until something drastic happens.
Please see the issues below in…
21 votes -
Github checkin for modules and configurationdata needed
right now, while I can connect to github, the only thing I'm able to check-in or out are runbooks. This needs to be extended to both modules, configurations, and configuration data in order to provide functional DSC support.
Tracking configurations is critical to a proper dev-ops model, and in the current PowerShell implementation of DSC, that means BOTH configuration scripts as well as composite configurations stored as modules.
To take it further, company specific modules need to have the same ease of check-in/out, especially with the removal of versioning from the zip.
21 votesThanks for this feedback. This is something that has been in our backlog, and having your input helps us to prioritize this.
You can currently write your own runbook to use to check in other artifacts as a workaround. You may want to take a look at http://blogs.technet.com/b/privatecloud/archive/2014/05/08/automation-mvp-spotlight-series-tfs-and-service-management-automation-better-together.aspx to see how this was done with TFS and convert to modules.
-
export /import run book into VSTS
While working on Azure run books we would like to export the the scripts into VSTS and put them under version control. Therefore we have one single source for all code. This is usefully we can keep in sync version of scripts with the current version of code including environment requirements
20 votes -
Add GitHub Enterprise Source Control Support
Currently Azure Automation only supports connecting to public GitHub, it would be helpful if we could use our GitHub Enterprise instance for source control.
19 votes -
Source Control integration - preserve logging settings
I've noticed that every time Azure Automation syncs up a new version of the runbook (PowerShell script pulled from an Azure DevOps repo) it resets the Logging\Tracing configuration. Is it possible to preserve these settings during sync?
3 votesThanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This 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.
-
Ability to force synchronization for Azure Automation Source Control
Please provide an ability to force a synchronization of all content in the source control system into the Azure automation runbook. This is particularly useful when you set up a connector to say github for source control and then you want it to update the existing runbooks.
It seems the only way to force it is to make a code change.
2 votes -
Source Control for Modules
I setup source control but it only supports runbooks. can you add module support for our custom modules?
2 votes -
Search does not seem to work for VSTS repository.
We have a large number of projects, some of which have 100s of repositories. The list that shows up is random, probably selecting some max # of repos as returned by the API. But when I type search, I do not find my repository. It always returns the same list, never the thing I was searching for. I am in the Administrator group for the project I am looking for.
1 vote -
Azure DevOps Collection Selector
As we have multiple different Azure DevOps Collections, I would like to see an additional drop to select which collection I want to connect to. I am unsure how it is picking the collection right now, but it is not the connection I need and I don't see a way to change it.
1 vote -
Multiple directories - only repositories from first one are visible
Having same user in multiple directories (in my case, it is my private repository and another one for startup) - I see repositories only from first directory (private) and cannot select others.
1 vote -
certificate
Windows does not let you export a private key certificate without a password, but there does not seem to be any way to specify a password when using ARM. I'm not sure why the ARM resource requires a base64 string--it would make much more sense to just reference a certificate in an existing Key Vault, like the Compute team does.
1 voteThanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This 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.
-
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 votesThanks 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.
- Don't see your idea?