How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
We have provided collection of Powershell Runbooks and Modules for Microsoft Azure Automation and Operations Management Suite, to demonstrate integration with the Hornbill Collaboration platform and Service Manager application.
Please see the description within each Runbook and/or Module for more information about functionality, input parameters, and the APIs that they use.
Open Source
The Microsoft Azure and OMS Hornbill Integration is provided open source under the Hornbill Community License and can be found on the PowerShell Gallery and GitHub.
Modules
IMPORTANT! Both the HornbillAPI and HornbillHelpers PowerShell Modules are required to be added to the Azure Automation account prior to making use of the Hornbill Runbooks. See the .psm1 Module files within the Modules for more information on the input and output parameters for each CMDLET.
HornbillAPI : This module contains the required CMDLETs to build and fire API calls from Azure Runbooks to your Hornbill instance:
- Set-HB-Instance : MANDATORY - Allows your Powershell script to define the Hornbill instance to connect to, the zone in which it resides, and the API key to use for session generation.
- Add-HB-Param : Add a parameter to the XMLMC request
- Clear-HB-Params : Clears any existing XMLMC parameters that have been added
- Open-HB-Element : Allows for the building of complex XML
- Close-HB-Element : Allows for the building of complex XML
- Invoke-HB-XMLMC : Invokes your API call
- ConvertTo-HB-B64Decode : Returns a UTF8 string from a given Base64 encoded string
- ConvertTo-HB-B64Encode : Returns a Base64 encoded string from a given UTF8 string
- Get-HB-Params : Returns XML string of parameters that have been added by Add-HB-Params, Open-HB-Element and Close-HB-Element
HornbillHelpers : This module contains a number of helper CMDLETs to carry out common requests within Hornbill Runbooks:
- Get-HB-CatalogID : Provide a Catalog Item Name, and this CMDLET will search your Hornbill instance for a matching record, returning the Primary Key
- Get-HB-OrganisationID : Provide a Organization Name, and this CMDLET will search your Hornbill instance for a matching record, returning the Primary Key
- Get-HB-PriorityID : Provide a Priority Name, and this CMDLET will search your Hornbill instance for a matching record, returning the Primary Key
- Get-HB-Request : Retrieves details about a Request
- Get-HB-ServiceID : Provide a Service Name, and this CMDLET will search your Hornbill instance for a matching record, returning the Primary Key
- Get-HB-SiteID : Provide a Site Name, and this CMDLET will search your Hornbill instance for a matching record, returning the Primary Key
- Get-HB-WorkspaceID : Provide a Workspace Name, and this CMDLET will search your Hornbill instance for a matching record, returning the Activity Stream ID
Module Installation
Install via the Module Gallery
- Open Microsoft Azure in your browser and navigate to your Automation Account
- Click on
Modules GalleryunderShared Resources - Search the Modules for
Hornbill - Click in to each Hornbill module in turn, and click the
Importbutton - On the list of Modules, wait for the Module Status to become
Availablebefore attempting to run any Runbooks that use them.
Install from the PowerShell Gallery
- Download the Modules from the PowerShell Gallery, and place on your local machine
- Open Microsoft Azure in your browser and navigate to your Automation Account
- Click on
ModulesunderShared Resources - Click the
Add a modulebutton - Use the
Upload Filecontrol to find and select your Module, then click theOKbutton - On the list of Modules, wait for the Module Status to become
Availablebefore attempting to run any Runbooks that use them.
Runbooks
We’re provided a number of example Powershell Runbooks to allow your Azure Automation Account (and therefore the Microsoft Operations Management Suite) to interact with your Hornbill instance. Please see the Runbooks themselves for more detailed information regarding input parameters etc:
- HornbillAzureIntuneAssetImport : Allows the import of asset records from Intune into Hornbill
- HornbillContactArchiveWorkflow : Archives a Contact
- HornbillContactCreate : Creates a Contact
- HornbillLogChangeRequest : Logs a Change Request within Service Manager - this is a Powershell Workflow, and can be called from other Azure Workflow Runbooks (Powershell or Graphical)
- HornbillLogChangeRequestWebhook : Logs a Change Request within Service Manager - this should be called with an Azure Webhook, and is useful when setting up Alerts in Operations Management Suite
- HornbillLogIncident : Logs an Incident within Service Manager - this is a Powershell Workflow, and can be called from other Azure Workflow Runbooks (Powershell or Graphical)
- HornbillLogIncidentWebhook : Logs an Incident within Service Manager - this should be called with an Azure Webhook, and is useful when setting up Alerts in Operations Management Suite
- HornbillLogServiceRequest : Logs a Service Request within Service Manager - this is a Powershell Workflow, and can be called from other Azure Workflow Runbooks (Powershell or Graphical)
- HornbillLogServiceRequestWebhook : Logs a Service Request within Service Manager - this should be called with an Azure Webhook, and is useful when setting up Alerts in Operations Management Suite
- HornbillRequestClose : Closes a Service Manager Request
- HornbillRequestResolve : Resolved a Service Manager Request
- HornbillRequestUpdateDetails : Updates the details of a Service Manager Request
- HornbillRequestUpdateTimeline : Updates the timeline of a Service Manager Request
- HornbillUserAddGroup : Adds a Hornbill User to a Hornbill Group
- HornbillUserAddRoles : Adds one or more Roles to a Hornbill User
- HornbillUserAddWorkspace : Adds a Hornbill User to a Hornbill Collaboration Workspace
- HornbillUserArchive : Archives a Hornbill User account
- HornbillUserCreate : Creates a Hornbill User account
- HornbillUserDelete : Deletes a Hornbill User account
- HornbillWorkspaceCreate : Creates a Hornbill Collaboration Workspace
- HornbillWorkspacePost : Adds a Post to a Hornbill Collaboration Workspace - this is a Powershell Workflow, and can be called from other Azure Workflow Runbooks (Powershell or Graphical)
- HornbillWorkspacePostWebhook : Adds a Post to a Hornbill Collaboration Workspace - this should be called with an Azure Webhook, and is useful when setting up Alerts in Operations Management Suite
- HornbillWorkspacePostComment : Adds a Comment to an existing Post on a Hornbill Collaboration Workspace
Runbook Installation
Install via the Runbook Gallery
-
Open Microsoft Azure in your browser and navigate to your Automation Account
-
Click on
Runbooks GalleryunderShared Resources -
Search the
PowerShell GalleryforHornbill -
Click in to each Hornbill Runbook that you want to install in turn, and click the
Importbutton -
The Runbook will then be available for use/edit/publishing in your list of Automation Runbooks
-
Download the relevant Runbook Powershell scripts from the PowerShell Gallery, and place on your local machine
-
Open Microsoft Azure in your browser and navigate to your Automation Account
-
Click on
RunbooksunderProcess Automation -
Click the
Add a runbookbutton -
Click
Import an existing runbook -
Use the
Runbook Filecontrol to find and select your Runbook, then click theOKbutton -
Give the Runbook a description should you so wish, then click the
Createbutton to add the Runbook to your Runbook library
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}