Latest blog articles

I am now proudly welcoming Rachel to the team, who will join as Marketing Manager. She will leverage her expertise and vast experience for our new Digital Marketing Services and manage our partnerships.

Standard mode Logic Apps behave quite differently when deploying resources. It took much research to find a stable way to deploy workflows and, especially, workflow connections. Here is a walkthrough of the deployment steps.

Most companies have systems on on-premises servers that need to interact with the cloud components. Let's look at some options and their design implications.

Storing secrets inside configuration files is bad practice. In this example, we encrypt these values using the server machine key.

As a consultant, I have spent most of my time over the last 10 years on the road. However, the COVID pandemic changed my work situation overnight. Maybe my travel routine was wrong all these years? Maybe the digital nomad…

Previously, we looked into deploying Azure resources uing infrastructure-as-code using Pulumi. In this post, I am walking you through creating the C# (or TypeScript etc) code from manual prototyping and proof-of-concept deployments in Azure to making them using Pulumi.

When swapping between debugging using a workbench and deploying to a SharePoint developer tenant, we need to toggle the –ship flags. Also, we need to chain the Gulp commands. Just running gulp package-solution –ship does not perform the entire chain.

To handle Infrastructure-as-Code workflows, I use a product called Pulumi. It is built on top of the open-source platform Terraform. Pulumi handles versioning and recreation of cloud resources, handles state and shows a preview of what changes will occur.

Example using Altova MapForce to generate an XLST 2.0 mapping function and deploying this into an Azure logic app for use in an integration service.