all Technical posts

Finished Azure Integration Account Functionality and Other Cool Features in Arcus Scripting v0.6

Recently, we released Arcus Scripting v0.6. The scripting library was quiet for a while, without any updates, so let's see what's new in this run-down post on the upcoming functionalities

For more information on all things Azure Integration Account, see our documentation page, where all the available PowerShell functions are described.

Add Azure App Service application settings with ease

Azure App Services can have common application settings. Just like local application settings, these should not contain any sensitive or secret information but are particularly useful when passing-in dynamic configuration values that can manipulate the application. Setting such application settings has to be done via the Azure portal. With Arcus Scripting v0.6, you don’t have to make that trip to the portal anymore.

Installing the new library Arcus.Scripting.AppService gives you access to the Azure App Service functionality:

PS> Install-Module -Name Arcus.Scripting.AppService

Setting Azure App Service application settings was never so easy:

For more information on this module, see our documentation page.

Extend ARM template content injection with absolute file paths

One of the new features in v0.6 is entirely written by a contributor. It’s great to see our library expanding with features that were missing. All these additions grow from the usage of the library and the healthy reflex to contribute the missing pieces. In this case, the ARM template functionality to inject content into the template was missing something. We allowed relative value files to be injected into the ARM template, but didn’t have support for absolute external file paths. The way it was updated made sure that we stay backward-compatible with relative file paths, making this a very flexible piece of functionality.

All ARM functionality is located in the Arcus.Scripting.ARM powershell module:

PS> Install-Module -Name Arcus.Scripting.ARM

When using the following ARM template example, we can now use an absolute file path for the FileToInject value:

The injection then can be done with a simple command:

Inject-ArmContent -Path deploy\arm-template.json

For more information on the different features of the ARM module, see our documentation page.


This new version of Arcus Scripting has received the most contributions so far! It’s amazing how our contributors are helping us to improve the library, and go from better logging, to easier understandable documentation, to fully working features. This proves that this library really helps people in their daily work.

The Arcus Scripting release has a lot more to offer. Come take a look at our documentation page for a list of all the available functionality. If you have any questions, remarks, comments, or just want to discuss something, feel free to contact us.

Thanks for reading!
-Arcus team

Subscribe to our RSS feed

Hi there,
how can we help?

Got a project in mind?

Connect with us

Let's talk

Let's talk

Thanks, we'll be in touch soon!

Call us

Thanks, we've sent the link to your inbox

Invalid email address


Your download should start shortly!

Stay in Touch - Subscribe to Our Newsletter

Keep up to date with industry trends, events and the latest customer stories

Invalid email address


Great you’re on the list!