Code is as-is, no warranties, etc.
The script automates the provisioning of a new Azure hybrid connection including —
- Creation of a service bus relay namespace and hybrid connection.
- Configuration of an existing Azure web app to use the newly created connection.
- Navigate to the Azure portal.
- Open the cloud shell.
- When prompted, be sure to select Bash, not Powershell.
- Clone this repository within the cloud shell.
git clone https://github.com/caseywatson/AutomatedHcmSetup.git
- Navigate to the cloned repository's directory.
cd AutomatedHcmSetup
- Allow the script to be executed.
chmod +x ./create-hc.sh
- Run the script. Refer to the table below for more information on using script parameters.
./create-hc.sh -g <resource group name> -w <web app name> -n <connection name> -e <connection endpoint>
| Parameter | Flag | Description |
|---|---|---|
| Resource group name | -g |
The name of the resource group in which the relay and connection will be deployed. This must be the same resource group that the web app (-w) is deployed to. |
| Web app name | -w |
The name of the Azure web app that the hybrid connection should be assigned to. This web app must already exist in the resource group provided through the resource group name (-g) parameter. |
| Connection name | -n |
The name of the hybrid connection. All related resources created by this script will be prefixed with this identifier. |
| Connection endpoint | -e |
The hybrid connection endpoint (including host name and port) as defined in this article. |
Tip: Want to run this script as part of an automated pipeline? Include the
-qflag to run this script quietly. The only script output will be the HCM connection string which can be redirected to a file or collected as part of an automated deployment tool like Azure Pipelines. Happy Holidays, Manish. 🎁😉