How to monitor the status of Azure API Connections (Part I)
Nov 12, 2021
Sometimes I like to use my friends to have a different point of view on things, which is one of these cases I have been discussing with Mike Stephenson and
Logic Apps: CI/CD Part 3- Building your Azure Pipeline
Nov 11, 2021
In the previous posts of this series, we've talked about how to build and prepare your Logic App for CI/CD In this last post, I'll show you how to build your
BizTalk Server BAM Tools Error: Database ‘BAMAnalysis’ has compatibility level. Tabul...
Nov 8, 2021
Completing the enormous saga, aka nightmare, to install BAM in one of my latest BizTalk Server installations, and once I thought I solved all the issues BAM
BizTalk Server 2020 BAM Configuration: Could not load file or assembly Microsoft.SqlServer.SQLTask
Nov 7, 2021
I recently published a blog post about BizTalk Server 2020 BAM Configuration: Microsoft SQL Server Integration Services (SSIS) is not installed on the local
Azure Breakthroughs: Finding the Azure VM administrator username
Nov 4, 2021
I usually use a range of different usernames to define as the administrator of my Azure Virtual Machines, and I have others that clients shared with me So,
BizTalk Server WCF-WebHTTP Receive Location: 413 Request Entity Too Large
Oct 29, 2021
We published a REST web service in BizTalk Server a long time ago that exposes a BizTalk Server Orchestration Basically, we receive a JSON payload, convert it
Logic Apps: CI/CD Part 2- Preparing for CI/CD
Oct 27, 2021
In the previous post, we built a Logic App from scratch and shared a few changes required to prepare it for CI/CD In this article, we explain how to
BizTalk Server 2020 EDI/AS2 Runtime Configuration: Failed to deploy BAM activity definitions. Pl...
Oct 22, 2021
And yes, let's continue one of my previous insane experiences installing a brand new BizTalk Server 2020 production environment In one of my earlier blog
BizTalk Server 2020 BAM Configuration: Microsoft SQL Server Integration Services (SSIS) is not in...
Oct 21, 2021
This could be a valid error message if it weren't for the simple little detail that we are dealing with a High-availability multi-server BizTalk Server



