Runbook and module galleries for Azure Automation
Rather than creating your own runbooks and modules in Azure Automation, you can access a variety of scenarios that have already been built by Microsoft and the community. You can either use these scenarios without modification or you can use them as a starting point and edit them for your specific requirements.
You can get runbooks from the Runbook Gallery and modules from the PowerShell Gallery. You can also contribute to the community by sharing scenarios that you develop, see Adding a runbook to the gallery
Runbooks in Runbook Gallery
The Runbook Gallery provides a variety of runbooks from Microsoft and the community that you can import into Azure Automation. You can either download a runbook from the gallery, which is hosted in the TechNet Script Center, or you can directly import runbooks from the gallery in the Azure portal.
You can only import directly from the Runbook Gallery using the Azure portal. You cannot perform this function using Windows PowerShell.
You should validate the contents of any runbooks that you get from the Runbook Gallery and use extreme caution in installing and running them in a production environment.
To import a runbook from the Runbook Gallery with the Azure portal
- In the Azure portal, open your Automation account.
- Under Process Automation, click on Runbooks gallery
Locate the gallery item you want and select it to view its details. On the left you can enter additional search parameters for the publisher and type.
- Click on View source project to view the item in the TechNet Script Center.
To import an item, click on it to view its details and then click the Import button.
- Optionally, change the name of the runbook and then click OK to import the runbook.
- The runbook appears on the Runbooks tab for the Automation Account.
Adding a runbook to the runbook gallery
Microsoft encourages you to add runbooks to the Runbook Gallery that you think would be useful to other customers. You can add a runbook by uploading it to the Script Center taking into account the following details.
- You must specify Windows Azure for the Category and Automation for the Subcategory for the runbook to be displayed in the wizard.
- The upload must be a single .ps1 or .graphrunbook file. If the runbook requires any modules, child runbooks, or assets, then you should list those in the description of the submission and in the comments section of the runbook. If you have a scenario requiring multiple runbooks, then upload each separately and list the names of the related runbooks in each of their descriptions. Make sure that you use the same tags so that they show up in the same category. A user will have to read the description to know that other runbooks are required the scenario to work.
- Add the tag "GraphicalPS" if you are publishing a Graphical runbook (not a Graphical Workflow).
- Insert either a PowerShell or PowerShell Workflow code snippet into the description using Insert code section icon.
- The Summary for the upload is displayed in the Runbook Gallery results so you should provide detailed information that helps a user identify the functionality of the runbook.
You should assign one to three of the following Tags to the upload. The runbook is listed in the wizard under the categories that match its tags. Any tags not on this list are ignored by the wizard. If you don’t specify any matching tags, the runbook is listed under the Other category.
- Capacity Management
- Change Control
- Dev / Test Environments
- Disaster Recovery
- VM Lifecycle Management
- Automation updates the Gallery once an hour, so you won’t see your contributions immediately.
Modules in PowerShell Gallery
PowerShell modules contain cmdlets that you can use in your runbooks, and existing modules that you can install in Azure Automation are available in the PowerShell Gallery. You can launch this gallery from the Azure portal and install them directly into Azure Automation or you can download them and install them manually.
To import a module from the Automation Module Gallery with the Azure portal
- In the Azure portal, open your Automation account.
- Select Modules under Shared Resources to open the list of modules.
Click Browse gallery from the top of the page.
On the Browse gallery page, you can search by the following fields:
- Module Name
- Cmdlet/DSC resource name
Locate a module that you're interested in and select it to view its details.
When you drill into a specific module, you can view more information about the module, including a link back to the PowerShell Gallery, any required dependencies, and all of the cmdlets and/or DSC resources that the module contains.
- To install the module directly into Azure Automation, click the Import button.
- When you click the Import button, on the Import pane, you see the module name that you are about to import. If all the dependencies are installed, the OK button is activated. If you are missing dependencies, you need to import those before you can import this module.
- On the Import page, click OK to import the module. While Azure Automation imports a module to your account, it extracts metadata about the module and the cmdlets. This may take a couple of minutes since each activity needs to be extracted.
- You receive an initial notification that the module is being deployed and another notification when it has completed.
- After the module is imported, you can see the available activities, and you can use its resources in your runbooks and Desired State Configuration.
Modules that only support PowerShell core are not supported in Azure Automation and are unable to be imported in the Azure portal, or deployed directly from the PowerShell Gallery.
Python Runbooks are available in the Script Center gallery. You can contribute Python runbooks to the Script Center gallery. When you do, ensure that you add the tag Python when uploading your contribution.
Requesting a runbook or module
- To get started with runbooks, see Creating or importing a runbook in Azure Automation
- To understand the differences between PowerShell and PowerShell Workflow with runbooks, see Learning PowerShell workflow