Run Azure Stream Analytics job from UWP app


Working with the newest technologies is great and frustrating. I can create solutions I’ve never made before while complaining about the outdated/incomplete documentation.

I had one of those feelings while working with Azure Stream Analytics (ASA). My solution worked but there was one ‘elementary and simple’ thing I wanted: Start the ASA-jobs within my C#-code. That shouldn’t be hard and there’s some documentation. But no, I needed to combine several opposed solutions to a new one to make it possible.

In this post I shortly explain how you can start ASA-jobs within your C# UWP application:

  • I explain which components you have in the authentication process and which parameters you need.
  • Example code is provided. You only need to enter your parameter values.



The following diagram shows how the authentication works, corresponding to the steps below.



Step 1: Create App for accessing Azure Resources

You will create an application in your Azure Active Directory and assign a role to this application.

This is described well in the following post:

Follow these steps. You might change some settings depending on your exact needs. A few choices I made:

  • Paragraph ‘Configure multi-tenant application’ I did not enable multi-tenancy. Because it was not the case for my solution.
  • Paragraph ‘Assign application to role’ I selected the role Contributor to make sure my application can also start a ASA-job.

Important id’s/keys you created in this steps and need later on:

  • Client ID of the application (See paragraph ‘Get client id and authentication key’)
  • Key of the application (See paragraph ‘Get client id and authentication key’)
  • TenantID (See paragraph ‘Get tenant id’)

Step 2: Get all the information you need

When running ASA jobs you’ll need some ID’s, keys and names. Below, you see a list of properties you need. The first 3 you created in the previous step. The other values are already available because you have an ASA job, which belongs to a ResourceGroup which is part of an Azure Subscription.

  • Client Id from the application
  • Key of the application
  • Tenant id of the application
  • Id of the subscription where the ASA is part off
  • Name of the Resourcegroup where the ASA belongs to
  • Name of the ASA job

You will use a few references. See the list below:

  • System.Threading.Tasks
  • Windows.UI.Xaml
  • Microsoft.Azure.Management.StreamAnalytics
  • Microsoft.Azure.Management.StreamAnalytics.Models
  • Microsoft.Azure
  • Microsoft.IdentityModel.Clients.ActiveDirectory

Step 3: Request AccessToken

Now you request your new application for an AccessToken. To get this you sent the clientId and key of the application to your Active Directory.

The response message containts an AccessToken for this application. This AccessToken and your SubscriptionId (from the Subscription which contains your ASA-job) is your Token Cloud Credential.

Step 4: Start Azure Stream Analytics job

You use this Token Cloud Credential to create a new Stream Analytics Client. This client is used to run your ASA job. You can set job parameters like the JobStartTime. Besides the parameters you’ll need the name of the ResourceGroup where your ASA job belongs to and – of course – the name of the ASA job.

When the call is made, it will take about 2 minutes before the job is started. During these 2 minutes:

  • Steps 4-A are processed at the back. This will check if the AccessToken you send has the valid permissions.
  • The ASA-job is started (which takes most of the time)


Useful links:

Hylke Peek is a Data Solution consultant and is currently working for The Backbone. His focus is on BI, Analytics, IoT and Cloud. He is also a speaker, teacher and blogger. Mainly he is working with the Microsoft stack (MCSA Data Platform and MCT). Always trying out the new stuff!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Next ArticleBuilding the Poor Man's IoT Presentation (+ inspiration for new posts)