When consuming messages from an Azure service bus the order may not be guaranteed due to the brokered based messaging scheme where multiple consumers can consume messages from the bus. Sure you can force the Logic App to execute as a single instance but then you sacrifice performance and scalability. You can also use ReceiveAndDelete but then you loose the transactional nature of the bus. Ultimately to ensure a message is consumed in the correct order using the transactional nature of the bus you would add a sequence number to each message and use this to enforce the ordering.

To achieve ordered delivery using Logic Apps, you would need to ensure all related messages are consumed by the same Logic App instance and for this we use the session Id property on the service bus. Below is the full workflow process to force ordered delivery using Logic Apps and session…

One of the many great features of Azure API Management is the fact that it has a built in Git repository for storing the current configuration as well as publishing new configurations.

This allows you to push updated Azure API Management configurations to this internal Git repository as a new branch and then Deploy the configuration to API Management.

The internal Git repository in Azure API Management is not intended to be used for a normal development workflow. You’ll still want to develop and store your Azure API management configuration in an external Git repository such as GitHub or TFS/VSTS and then copy configuration updates to the internal Git repository in Azure API Management using some sort of automated process (e.g. Continuous Integration/Continuous Delivery could be adopted for this).

The Internal Git Repository

To access the Internal Git Repository requires short lived (30 days maximum) Git credentials to…

Recently, I’ve created an audition video to become a Pluralsight author.  I wanted to share this video, as it might be interesting for you.  The video gives an introduction to Azure Logic Apps and finishes with a great demo about Saleforce integration (at 5:43).

Enjoy!

In the early days of Microsoft Azure, back in 2010 when it was called Windows Azure, Microsoft had announced plans to make the Azure services available to be run / hosted in on-premises datacenter. Shortly after the announcement they released Azure Pack which wasn’t quite what we had all hoped for. Then about 2 years ago, Microsoft started talking about “Azure in your datacenter” again! The started talking about this new product offering called Azure Stack. We’ve seen a couple technical previews of Azure Stack so far, but not much in the way of a GA (Generally Available) release. That is until now. This week, Microsoft announced that in coordination with hardware OEMs you can now order Azure Stack integrated system hardware, with the first systems beginning to ship in September. There is also some pricing information, and an Azure Stack Development Kit (ASDK) being made available.

This is an…

Hello!

A few days ago I was asked about an easy way to create audio files to be used as datasets in Custom Speech Service (CRIS). As I mentioned in a previous post, the audio files must have special features, so it is important to create them correctly.

Note: the files are WAVs files, mono and another pair of details makes it not easy to create them in a single step.

Although there are several ways to create these files, this is the one I use and it works.

• To record the audio I use an app that comes by default in Windows: Voice Recorder

• I guess I don’t need to explain how the app works. Just press the microphone button. Nor do we expect many options in the Settings section.

• Once we have recorded a session, we can access the list of recordings. If we see the record path…

DocumentDB has been around for awhile now in Microsoft Azure. It’s a Document based, NoSQL database in the cloud. There’s been tons of advancements to the service over time, including MongoDB API support so you can use it in place of MongoDB for existing code bases. It’s always been called “DocumentDB” since initial release of the service, but for a time it was labeled as “NoSQL (DocumentDB)” in the Azure Portal. It seems there was some indication that Microsoft wasn’t happy with the name they first chose.

Today, we wake up in the morning to updates that have been made to the Azure Portal where DocumentDB is no longer there. Well, it actually is there, but has undergone renaming / rebranding. From this day forward, DocumentDB will no longer be called DocumentDB. Instead we will call this NoSQL, Document based database service….. Azure Cosmos DB.

From this day forward, DocumentDB…

Azure Storage Queues provide an easy to implement messaging communication mechanism for reliably passing messages to/from different components of a single application or multiple applications. Storage Queues have an HTTP/HTTPS API to allow for support of any development platform; however, Microsoft does provide a .NET SDK to make it even easier to implement from C# or other .NET languages.