Azure Actions

Added a new action system use called 'Azure Action', allowing for the ability to create Users in Azure and assign them to groups via system actions.

In this guide we will cover:

- How to Utilise Azure Actions in Halo

Azure Actions allow you to create users in an Azure tenant and assign a user to an Azure group from Halo. 

Pre-requisites:

• You have successfully configured the Entra ID integration
• You have successfully configured the Microsoft CSP integration 

Ensure you have used the Entra ID or CSP integration to connect the Entra tenant that you would like to carry out the actions in. 

How to Utilise Azure Actions in Halo#

An action with the system use 'Azure Action' is available. 

Fig 1. Action with system use to complete an Azure Action

When this option is selected, a new "Azure Action" tab will show on the action configuration. Here you can select which Azure action you would like to perform, and which Azure connection you would like to use for the action. Connections setup in the Azure Active Directory Integration and also the Microsoft CSP Integration (HaloPSA) will show here. Ensure you choose the connection that authenticates access to the tenant you would like the action to be carried out in. 

If the connection you have chosen does not yet contain the necessary permissions to complete your selected Azure action, the required permissions will be listed on the action configuration page and the rest of the configuration will not be available. You must first add these permissions to your application in Azure and re-authorize the connection before the rest of the configuration options are made available. Different permissions are required depending on which Azure action you are completing, be sure to check the action configuration for the exact permissions your connection needs to have. 

Note: Permissions will show dynamically on the page based on the Azure connection you have selected.

Fig 2. Permissions required for Action to Assign User to Group

Fig 3. Permissions required to Create User

Once your connection has the required permissions, you can configure input and output mappings. Input mappings allow you to map Halo Ticket/Action fields to Azure fields for the corresponding action:

Fig 4. Field Mappings

The Azure Action will be performed against the first Azure tenant which has been mapped to the Ticket's assigned Client. If you have multiple Azure tenants mapped to one Client, you can override which tenant the Action is performed against by creating an input mapping for the Azure Tenant field

Output mappings are only available when using the Create User Azure action, which allow you to map the ID of the created user to a ticket custom field. 

Fig 5. Output Mappings

By creating an output mapping for the id field, you can then use this in subsequent Azure actions. For example, an automation workflow can be created that first creates the Azure user, and then assigns them to a group.

Fig 6. Automation Workflow to create a user then assign them to a group

For use of more Azure actions make use of custom integration runbooks.