Azure FunctionsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMEZ1bmN0aW9ucyUyMiU3RA==

Log in to the Azure portal, and navigate to Deploy custom template.
On the Custom Deployment page, click the Process your own template in the editor option.
On the Edit Template page, click Load File.
Upload the azure_functions.json file.
Click Save.
The Custom Deployment page is loaded with parameters required for deployment.
Here, enter the details as:

Parameter	Description
Subscription	Your account subscription.
Subscription Resource group	Enter the name of your resource group. The resource group is a collection of resources that share the same lifecycle, permissions, and policies.
Region	Choose the Azure region that's right for you and your customers. Not every resource is available in every region.
Managed Identity Name	Enter the name of User-Managed Identity to be attached with all Kyvos VMs.
Managed Identity Resource Group Name	The Name of Resource Group in which Managed Identity is deployed.
Kyvos Work Dir	Enter the path for the Kyvos work directory.
Additional Tags	Enter the additional tags to put on all resources. Use the syntax as: {"Key1": "Value1", "Key2" : "Value2"}
Storage Account Name	Enter the name of the Storage Account to be used for Kyvos.
Storage Account Container Name	Enter the name of the Container in Storage Account which will be used for Kyvos.
Storage Account Resource Group	Enter the name of the Resource Group in which the Storage Account is deployed.
Azure Function Crontab	Crontab entry to call Azure functions for use with cluster scheduling.

Click Review and create.
The Outputs page will display the Function name. Copy it and keep it handy for deployment.

Azure Secured FunctionsJTdCJTIydGl0bGUlMjIlM0ElMjJBenVyZSUyMFNlY3VyZWQlMjBGdW5jdGlvbnMlMjIlN0Q=

Log in to the Azure portal, and navigate to Deploy custom template.
On the Custom Deployment page, click the Process your own template in the editor option.
On the Edit Template page, click Load File.
Upload the azure_functions_secure.json file.
Click Save.
The Custom Deployment page is loaded with parameters required for deployment.
Here, enter the details as:

Parameter	Description
Subscription	Your account subscription.
Subscription Resource group	Enter the name of your resource group. The resource group is a collection of resources that share the same lifecycle, permissions, and policies.
Region	Choose the Azure region that's right for you and your customers. Not every resource is available in every region.
Azure Function Subnet Name	Name of the Subnet in which the Azure function will be deployed.
Kyvos Instance Subnet	Name of the Subnet in which the Kyvos cluster is deployed.
Managed Identity Name	Enter the name of User-Managed Identity to be attached with all Kyvos VMs.
Managed Identity Resource Group Name	The Name of Resource Group in which Managed Identity is deployed.
Kyvos Work Dir	Enter the path for the Kyvos work directory.
Additional Tags	Enter the additional tags to put on all resources. Use the syntax as: {"Key1": "Value1", "Key2" : "Value2"}
Storage Account Name	Enter the name of the Storage Account to be used for Kyvos.
Storage Account Container Name	Enter the name of Container in Storage Account which will be used for Kyvos.
Storage Account Resource Group	Enter the name of the Resource Group in which the Storage Account is deployed.
Azure Function Crontab	Crontab entry to call Azure functions for use with cluster scheduling.

Click Review and create.
The Outputs page will display the Function name. Copy it and keep it handy for deployment.

Post Deployment steps JTdCJTIydGl0bGUlMjIlM0ElMjJQb3N0JTIwRGVwbG95bWVudCUyMHN0ZXBzJTIwJTIyJTdE

Once you have deployed the cluster with externally created Secured Functions, you need to perform the following steps after deployment.

Go to the Key Vault created in Azure Deployment.
Navigate to Networking.
Click on Selected Network > Add existing Virtual Networks.
Choose the Virtual network, then select the same Subnet where you have launched your secured Functions.
You can find the subnet in the inputs of Deployment of Azure Function. Look for the value of the AzureFunctionSubnetName parameter.
Similarly, go to Storage Account associated with Kyvos deployment and perform steps 2 to 5 for the storage account.

Browser not supported