<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Philip Howard on Medium]]></title>
        <description><![CDATA[Stories by Philip Howard on Medium]]></description>
        <link>https://medium.com/@philip.howard?source=rss-da9910d2fdb6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*v5u-C9uf3D_nwQeZogompA.jpeg</url>
            <title>Stories by Philip Howard on Medium</title>
            <link>https://medium.com/@philip.howard?source=rss-da9910d2fdb6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:50:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@philip.howard/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What A Robot And A Strong Upper Body Can Teach You About Real-Time Data Analytics]]></title>
            <link>https://medium.com/aptitive/what-a-robot-and-a-strong-upper-body-can-teach-you-about-real-time-data-analytics-c06db47f4fbb?source=rss-da9910d2fdb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c06db47f4fbb</guid>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[analytics]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Philip Howard]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 13:12:16 GMT</pubDate>
            <atom:updated>2018-07-06T18:47:46.431Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7TYUErMQDwM2lntX" /></figure><p>The Aptitive team just recently hosted its very first (data) Science Fair — a data-science twist on the science fairs of yore where students would stand in the local school gym with the mysteries of the universe printed onto cardboard trifolds, only instead of baking soda volcanoes and tennis ball solar systems, we saw demos for <strong>data warehousing</strong>, <strong>integration tools</strong>, <strong>predictive analytics</strong>, <strong>real-time data analytics</strong>, and some impressive <strong>data visualization tools</strong> (I’m looking your way, Looker. That VR demo was pretty cool).</p><p>For my team’s demo, we linked <a href="https://azure.microsoft.com/en-us/">Microsoft Azure</a>’s IoT suite to a <a href="https://www.raspberrypi.org/">Raspberry Pi</a> controlled robot and hosted our very own Robot Race.</p><h3>The Project</h3><p>We connected an Android phone to Azure IoT Hub and streamed its accelerometer data to the cloud every half-second. That data was read by an Azure function that converted the acceleration value to a percent of the robot’s max power and stored the result in an Azure Queue Store. The Raspberry Pi acting as the brain of our robot would read from the queue and run it’s four little motors accordingly. The harder you shook the phone, the faster the robot would go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*OqqWIFHcTJyHlnQP7r8Rfg.gif" /><figcaption>Yes. You’re picturing it correctly</figcaption></figure><p>If you’re not the type of person who is immediately overcome with joy at the thought of controlling robots via frantic arm-flailing and would rather we just scienced some data, we didn’t forget you.</p><p>We also performed real-time ETL on the acceleration data for data warehousing and visualization using Azure Stream Analytics. If you’re unfamiliar, Stream Analytics is a Platform as a Service tool designed to query, transform and load streaming data using a Microsoft brand of SQL that contains support for temporal logic. The robot may have been shiny, but the Azure powered real-time data analytics were the real star of the show.</p><p>While we were collecting two messages per second in IoT Hub, Stream Analytics was executing a series of saved queries on that data that averaged the acceleration values and sent the results to Azure Blob Storage and Microsoft PowerBI simultaneously. While participants were shaking their arms into a knotted mess, we were watching their acceleration dance up and down on a PowerBI dashboard while it was also being stored away for integration into a data warehouse (which, in fact, our data team was doing using a combination of <a href="https://www.alooma.com/">Alooma</a> and <a href="https://www.snowflake.net/">Snowflake</a>).</p><h3>The Business Application</h3><p>Connecting to a single source of data and passing it on is just scratching the surface of what Stream Analytics is capable of. Combine a stream of how fast your delivery trucks are eating diesel with your maintenance records and now you have real-time data analytics reports of when you need to bring the next one into the shop. Add in your mileage reports and expected costs of maintenance and now you have a live feed of the profit margin you’re earning for each truck per mile.</p><p>Whether this is relevant to you is entirely dependent on your business needs, but this is by no means the only possible scenario; finding that sweet spot where the dreams of business users meet technology is exactly where real-time ETL shines. In a world where IoT is becoming commonplace and data is collected in massive volumes, being able to transform your data for analysis on the spot is the next step in knowing what’s happening in your business the moment it happens.</p><p>You can also control robots with it too. So there’s that.</p><p>Click <a href="https://www.aptitive.com/data-science-fair">here</a> to learn more about the (data) Science Fair and see more photos from the event.</p><p><a href="https://www.aptitive.com/robot-strong-upper-body-can-teach-real-time-data-analytics/"><em>This blog</em></a><em> originally appeared on the Aptitive website.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c06db47f4fbb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/what-a-robot-and-a-strong-upper-body-can-teach-you-about-real-time-data-analytics-c06db47f4fbb">What A Robot And A Strong Upper Body Can Teach You About Real-Time Data Analytics</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Query Streamed Data In Real-Time With Azure Stream Analytics]]></title>
            <link>https://medium.com/aptitive/query-streamed-data-in-real-time-with-azure-stream-analytics-e88513494195?source=rss-da9910d2fdb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/e88513494195</guid>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[10daysofiot]]></category>
            <category><![CDATA[stream-analytics]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Philip Howard]]></dc:creator>
            <pubDate>Tue, 10 Oct 2017 13:34:37 GMT</pubDate>
            <atom:updated>2017-10-10T13:34:37.923Z</atom:updated>
            <content:encoded><![CDATA[<p>So I’ve had my head in Azure’s cloud services for a little while now, and I continue to find new things that are fun to set up. With the ease of development and the pay-as-you-go paradigm, tailored cloud solutions for your business are attainable and relatively low-risk, giving you the freedom to try new ideas, and Microsoft has some great walkthroughs for becoming familiar with each item in the Azure toolbox.</p><p>Most recently, I’ve been playing around with the services available in Azure’s IoT suite, and I wanted to combine a couple of the Microsoft walkthroughs together for you, along with a few notes of my own to make the process a little easier.</p><p>You will need an Azure and a Power Bi account to complete this demo. If you don’t have one, you can register for free trial accounts <a href="https://azure.microsoft.com/en-us/free/"><strong>here</strong></a><strong> </strong>and <a href="https://powerbi.microsoft.com/en-us/get-started/"><strong>here</strong></a>.</p><p>Here’s a link to the original Microsoft <a href="https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-real-time-fraud-detection"><strong>walkthrough</strong></a> if you wanted to check with it as you followed along.</p><p>Finally, if watching suits you a little more than reading, I have a video of the whole process <a href="https://youtu.be/TKDzVu8ZNzg"><strong>here</strong></a>.</p><p>So let’s get started.</p><h3>The Scenario:</h3><p>A telecommunications company wants to identify caller fraud in real-time by querying call records as they’re made so that the users can be identified and the accounts suspended.</p><p>For this demo, we’ll be consuming data with and Azure Event Hub, identifying the fraudulent calls by querying the data stream with Azure Stream Analytics, and then visualizing the fraudulent calls with Power BI.</p><h3>Create and Configure an Azure Event Hub</h3><p>The event hub is the first point of contact for your data. It’s where data is ingested and where your Stream Analytics Job queries from. It is unidirectional, which means that data only flows in the direction of device to event hub, making it a staging area for your data to wait until it is processed (bidirectional data flow is supported by Azure IoT Hub, if back-and-forth communication is required).</p><h4>Create an Event Hub Namespace</h4><ol><li>Log into the Azure portal and click <strong>New</strong> &gt; <strong>Internet of Things</strong> &gt; <strong>Event Hubs</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*fTVrlPqMmrLEO7LO8j0P1w.png" /></figure><p>2. In the <strong>Create Namespace </strong>blade, enter an Azure-unique name (the namespace will be a fully qualified URL), select your subscription and create a new resource group.</p><p>3. Copy the name you assigned your namespace and paste it into a text editor (Trust me. It’ll save you time later).</p><p>4. Leave the remaining default options (it should look similar to the picture below) and click <strong>Create</strong>. The namespace will take a few minutes to deploy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/478/1*ixYNqVhVigCxNNyyE1bOSA.png" /></figure><h4><strong>Add an Event Hub</strong></h4><ol><li>After the namespace has finished deploying, open <strong>Resource Groups</strong>, select your newly created resource group, and select your event hub namespace.</li><li>In the top left of the namespace blade, click <strong>+ Event Hub</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/1*I9Rt_6C3eBwTBzTNuMrPPg.png" /></figure><p>3. Provide a name for the event hub and accept the remaining default values, and click <strong>Create</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/522/1*MWQUfkmZLNba9qKf6UuLZA.png" /></figure><p>4. Copy the event hub name and paste it into a text editor for later.</p><h4>Create a Shared Access Policy</h4><ol><li>After the event hub has finished deploying, return to the event hub namespace blade, select <strong>Event Hubs</strong>, open your new event hub, and then select <strong>Shared access policies</strong>.</li><li>In the top left of the shared access policy blade, click <strong>+ Add</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/665/1*mZpn8yiT6BZM30t9bZdo2Q.png" /></figure><p>3. Enter a policy name, select <strong>Manage</strong> (send and listen will automatically be selected), and click <strong>Create</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/319/1*RGmqmAmDc-04VJVj-6fPWw.png" /></figure><p>4. Copy the shared access key name and paste it into a text editor for later.</p><p>5. After the shared access policy has been created, open it an copy <strong>Connection string-primary key</strong> (click the blue icon to copy).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jo9JR4SH_8hVM7zHQBzcHg.png" /></figure><p>6. Paste the connection string into your text editor for later.</p><h3>Begin Streaming Data To the Event Hub</h3><p>Now that we’ve prepared our Data Hub, we can begin sending data. For this demo, Microsoft provided a data simulator that you will need to download in order to follow along.</p><h4>Configure the TelcoDatagen App</h4><ol><li>Download the <a href="http://download.microsoft.com/download/8/B/D/8BD50991-8D54-4F59-AB83-3354B69C8A7E/TelcoGenerator.zip">TelcoGenerator.zip</a> file and unzip it to c:\telcodatagen (an another equally easy-to-find directory of your choosing).</li><li>Navigate to your unzipped folder and open the <strong>telcodatagen.exe.config </strong>file in a text editor.</li></ol><p>The connection string you pasted into your text editor should look something like this (<em>carriage returns are added for readability</em>):</p><pre>Endpoint=sb://myneweventhub.servicebus.windows.net/;<br>SharedAccessKeyName=eh-sas-frauddetection;<br>SharedAccessKey=URiYTBMWeW5KTHMsou0jP1daA5HvCcsCbqOSzYa/Cjc=;<br>EntityPath=eh-aptitiveiotdemo</pre><p>In order for us to configure the app correctly, we’ll have to paste the connection string in two parts. I’ll highlight everything that needs to be copied for each step.</p><p>3. Copy the value for <strong>EntityPath</strong>:</p><pre>Endpoint=sb://myneweventhub.servicebus.windows.net/;<br>SharedAccessKeyName=eh-sas-frauddetection;<br>SharedAccessKey=URiYTBMWeW5KTHMsou0jP1daA5HvCcsCbqOSzYa/Cjc=;<br>EntityPath=<strong>eh-aptitiveiotdemo</strong></pre><p>and paste it into the value for “<strong>EventHubName” </strong>in the config file (make sure to paste inside the quotes):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*_FOulSLBur1xYMwAiLLeYg.png" /></figure><p>4. Copy the remaining connection string, ignoring the entity path and the preceding semicolon:</p><pre><strong>Endpoint=sb://myneweventhub.servicebus.windows.net/;<br>SharedAccessKeyName=eh-sas-frauddetection;<br>SharedAccessKey=URiYTBMWeW5KTHMsou0jP1daA5HvCcsCbqOSzYa/Cjc=</strong>;<br>EntityPath=eh-aptitiveiotdemo</pre><p>and paste it into the value for “<strong>Microsoft.Service.Bus.ConnectionString</strong>”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/657/1*u3TFHYb0aWJ-jTTwUEz19w.png" /></figure><p>5. Save and exit the config file.</p><h4>Start the TelcoDatagen App</h4><ol><li>Open a command window, navigate to the directory that contains the TelcoDatagen App, and enter <strong>Telcodatagen.exe 1000 0.2 2</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/408/1*YfHezGA7KXZFECgBsFEFnQ.png" /></figure><p>The first parameter is the total number of simulated calls to send, the second parameter is the percent/probability that the call sent is fraudulent, and the third is the total number of hours the app will run.</p><p>If everything was configured correctly, you should start seeing rows printed in your console window.</p><p>2. Minimize your console window (do not exit the application).</p><h3>Create and Configure the Azure Stream Analytics Job</h3><p>So now you’ve created an event hub to accept data and you’re streaming simulated call records to it. Great. Now we can finally manipulate our data and gain some meaningful insights from it. This is where Stream Analytics comes in.</p><p>Azure Stream Analytics is a service that allows us to ingest, query and output data in real time to a variety of sources for analysis and/or storage. For this demo, we’ll be sending our selected data to PowerBi.</p><h4>Create a Stream Analytics Job</h4><ol><li>In the Azure portal, click <strong>New </strong>&gt;<strong> Internet of Things </strong>&gt;<strong> Stream Analytics Job</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/1*4B5YKyPnAuKJ8kS045cu6A.png" /></figure><p>2. In the <strong>New Stream Analytics Job</strong> blade, enter a job name and select the same resource group we created our event hub in:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*rKUuTpouwgX7Ow-zgn4Hwg.png" /></figure><p>3. Click <strong>Create</strong>.</p><h4>Add an Input Dataset</h4><ol><li>After deployment is complete, open your resource group and select your new stream analytics job.</li><li>In the <strong>Job Topology </strong>section, click the <strong>Inputs</strong> box:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*Z7g3x3jv-uqNpVIvGgvfJA.png" /></figure><p>3. Select <strong>+Add</strong></p><p>4. In the <strong>New Input</strong> blade, enter an input alias, select <strong>Data stream </strong>for Source Type, and select <strong>Event hub </strong>for the source.</p><p>For import option, the easiest method is to select <strong>Use event hub from current subscription</strong>, but I’ve found that Azure may take a few minutes to recognize any new event hubs you’ve created. If you’re trying to use this option and the service bus namespace field is empty, you may have to change your import option to <strong>Provide event hub settings manually</strong>.</p><p>If you’re required to manually provide the event hub settings, return to your text editor with your pasted values and perform the following:</p><ul><li>Copy your <strong>Event Hub Namespace</strong> name and paste it into <strong>Service bus namespace</strong>.</li><li>Copy your <strong>Event Hub</strong> name and paste it into <strong>Event hub name</strong>.</li><li>In your connection string, copy the values for <strong>SharedAccessKeyName</strong> and <strong>SharedAccessKey </strong>(do not include the semicolons) and paste them into <strong>Event hub policy name </strong>and <strong>Event hub policy key</strong>, respectively.</li></ul><pre>Endpoint=sb://myneweventhub.servicebus.windows.net/;<br>SharedAccessKeyName=<strong>eh-sas-frauddetection</strong>;<br>SharedAccessKey=<strong>URiYTBMWeW5KTHMsou0jP1daA5HvCcsCbqOSzYa/Cjc=</strong>;<br>EntityPath=eh-aptitiveiotdemo</pre><p>5. Accept the remaining default values and click <strong>Create</strong>.</p><h4>Add an Output Dataset</h4><ol><li>After the input has been created, exit the input blade and, in the <strong>Job Topology</strong> section of the stream analytics job, click the <strong>Output</strong> box:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*MKNtKMRWbyWtzpyLwh_uPQ.png" /></figure><p>2. Click <strong>+Add</strong>.</p><p>3. In the <strong>New output</strong> blade, enter an output alias and select <strong>Power BI</strong> for the sink (if you don’t yet have a Power BI account, you will have to sign up for one before completing this step). Click the <strong>Authorize</strong> button and enter your Power BI credentials.</p><p>4. After your connection to Power BI has been authorized, enter names for Dataset Name and Table Name (they will be automatically created in Power BI, so it’s better if they don’t already exist), leave the remaining default values, and click <strong>Create</strong>.</p><h4>Create and Save a Query</h4><p>We’ve come a long way since we’ve started, and now we can finally get to the purpose of why we’re ingesting this data in the first place: identifying caller fraud.</p><p>We accomplish this by filtering our data with a query that will join the data stream on itself and select only calls made from the same unique device ID within 5 seconds of each other, but from different countries.</p><ol><li>After the output has been created, exit the output blade and, in the <strong>Job Topology</strong> section of the stream analytics job, click the <strong>Query</strong> box:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*3a_TR1--A8gHYHPBRL-T_g.png" /></figure><p>2. In the query window, enter the following query:</p><pre>SELECT System.Timestamp AS WindowEnd, CS1.SwitchNum as Country, COUNT(*) AS FraudulentCalls<br>INTO &quot;CallStream-PowerBI&quot;<br>FROM &quot;CallStream&quot; CS1 TIMESTAMP BY CallRecTime<br>JOIN &quot;CallStream&quot; CS2 TIMESTAMP BY CallRecTime<br>ON CS1.CallingIMSI = CS2.CallingIMSI<br>AND DATEDIFF(ss, CS1, CS2) BETWEEN 1 AND 5<br>WHERE CS1.SwitchNum != CS2.SwitchNum<br>GROUP BY TumblingWindow(Duration(second, 1)), CS1.SwitchNum</pre><p>Let me take a second and point out a few important things about this query:</p><ul><li><strong>CallStream-PowerBI </strong>and <strong>CallStream</strong> are our output and input datasets. If you named them differently, you will have to adjust the query accordingly.</li><li>In order to select calls made within 5 seconds of each other, we have to perform two actions. First, we need to timestamp our data. We do this by using selecting <strong>System.Timestamp</strong> and declaring which field we’re timestamping by using the <strong>TIMESTAMP</strong> declaration when calling our “table.” In this case, we’re timestamping by <strong>CallRecTime</strong> (the time the call was made). Second, we need to implement the <strong>DATEDIFF BETWEEN</strong> commands to selectively join rows between 1 and 5 seconds apart. This functions differently than the DATEDIFF command in SQL, and the data sources must be timestamped in order for it to function correctly.</li><li>Finally, PowerBI can can be overwhelmed if we send too much data at once. We use the <strong>TumblingWindow </strong>command to reduce the size of the data sent into manageable chunks.</li></ul><p>3. Click <strong>Save</strong> and exit the query window.</p><h4>Start the Stream Analytics Job</h4><p>Now that we’ve configured our input, output and query, we can begin streaming our data to Power BI.</p><ol><li>In the top left of the stream analytics job, click <strong>Start. </strong>Starting the job will take a few minutes.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*6XenZ3Z1ZhKOz0n2ZyhECQ.png" /></figure><p>You’re done! Now we can navigate to Power BI and begin configuring our dashboard.</p><h3>Create a Dashboard in PowerBI</h3><p>This post isn’t meant to be a breakdown of the visuals you can create in Power Bi, but I’d be remiss if I didn’t show you at least one or two ways for you to see your data update in real-time. Microsoft provided some basic ideas that are quick to set up, and I’ll show you them here.</p><h4>Create an Incident Counter</h4><ol><li>Go to Powerbi.com and log into your account.</li><li>In your workspace, click <strong>+Create </strong>(if this is your first time logging into Power BI, you may have to click <strong>skip</strong> in your workspace in order to see the “+create” option).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*7bxUvBFmNNdnEyeollvJ3A.png" /></figure><p>3. Create a new dashboard and name it <strong>Detected Incidents</strong></p><p>4. At the top of the window, click <strong>Add Tile.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7uXMFZWyA5jDD_hWfULj3w.png" /></figure><p>5. Select <strong>CUSTOM STREAMING DATA</strong>, and click <strong>Next.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*onjo6-WXhi4pWTTr0EuX2g.png" /></figure><p>6. Under <strong>YOUR DATASETS</strong>, select your dataset and click <strong>Next </strong>(if you don’t see your dataset, try refreshing your browser. If this doesn’t fix the issue, you may have made a mistake when configuring you stream analytics job).</p><p>7. Under <strong>Visualization Type</strong>, select <strong>Card</strong>, and then in the <strong>Fields </strong>list, select <strong>fraudulentcalls</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/1*ouLEB9gAXKLuiVJU5iB8pg.png" /></figure><p>8. Click <strong>Next</strong>.</p><p>9. Add a title for the card and click <strong>Save</strong>.</p><p>You should now see a counter on your dashboard showing you the current number of fraudulent calls approximately every second. You can follow the same instructions as above to create line and bar charts as well, which will update at the same frequency.</p><p>Seeing your data graphed in front of you in real-time may be fun, but this is really only scratching the surface of the possible applications (and let’s be honest. Saving time and money is a whole lot more fun). Azure comes with a full list of services that allow you to connect your applications and keep you and your customers in the know. If we were to flesh out this example a little further, we could, for example:</p><ul><li>Configure a series of logic apps that automatically notify users of the fraudulent activity via SMS and disable their account to minimize any damage.</li><li>Create a blob storage output and an Azure function that automatically parses the data and inserts it into a SQL database.</li></ul><p>Creative solutions tailored to your business needs really only require a little imagination and a little know-how, and, true to the cloud services paradigm, you’re paying only for what you use. Development costs in time and expensive hardware are no longer barriers to getting hands-on experience or trying new solutions, so don’t be afraid to roll up your sleeves and have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e88513494195" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/query-streamed-data-in-real-time-with-azure-stream-analytics-e88513494195">Query Streamed Data In Real-Time With Azure Stream Analytics</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Making Meetings Not Suck Via The Magic of Dynamics 365 APIs]]></title>
            <link>https://medium.com/aptitive/making-meetings-not-suck-via-the-magic-of-dynamics-365-apis-8611bfb3cdf3?source=rss-da9910d2fdb6------2</link>
            <guid isPermaLink="false">https://medium.com/p/8611bfb3cdf3</guid>
            <category><![CDATA[crm]]></category>
            <category><![CDATA[dynamics-365]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[sales]]></category>
            <dc:creator><![CDATA[Philip Howard]]></dc:creator>
            <pubDate>Tue, 13 Jun 2017 22:05:36 GMT</pubDate>
            <atom:updated>2017-09-06T14:54:06.039Z</atom:updated>
            <content:encoded><![CDATA[<p>Why should you use Dynamics 365 APIs? I’ll give you one good reason: meetings, meetings, meetings.</p><p>Meetings are those special moments in the day where all work stops so that people-in-the-know can disseminate important business information to people-in-the-don’t-know in the hopes that, afterward, everyone knows enough to be able to do their job properly.</p><p>Naturally, not all meetings are created equal: white-boarding solutions with a client and collaborative problem solving are where the rubber meets the road in the world of innovative ideas. Status updates to your employees on your business’s sales opportunities, though? Not so much. Not only are you presenting data considered stale by today’s standard of instantaneous information, but you just lost an hour of company time focused inward when you could have been doing literally anything else (and let’s be real here. How often have you come from a meeting and said, “that was great, but it really could have used a few more PowerPoint slides?”).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*C7qqsyX0VxObdq5WwSPpqw.gif" /><figcaption>Never. The correct answer was “never.”</figcaption></figure><p>This is where I start talking about Microsoft Dynamics CRM.</p><p>Dynamics CRM is a powerful tool for maintaining customer relationships and making sure you’re keeping your thumb on the sales cycle so that if you miss an opportunity, it wasn’t because of poorly managed data.</p><p>As a rule, though, you’re not going to be giving access to your CRM account to every employee in your business, even though it’s critical for your team to have an accurate idea of what opportunities are in the pipeline. So, meetings…</p><p>Or not.</p><p>Dynamics 365 comes with a suite of APIs that provide another avenue of approach to your sales data. If you’re not too shy about writing a few lines of code, you can build customized solutions that supply on-demand access to need-to-know information without exposing sensitive data you’d rather keep locked away.</p><p>An Azure AD account is required to create the credentials necessary for Dynamics’ OAuth 2.0 authentication, and obtaining the auth token for accessing your data can be a process in its own right, but the developer community has come through in fine style with helper libraries and tutorials galore (I’ll be following this post up with one of my own, in fact).</p><p>Once you have access, though, the sky is the limit. Extract your data for analysis with Python. Build a web application that automatically alerts your sales teams when a lead needs immediate action. My team and I even built a Chrome extension that gives an “at a glance” look at what opportunities are on the horizon; one click and now our consultants know everything they need to know to begin preparing possible solutions for our clients <em>before </em>they get to the meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*cjzwcTCJvgm2KDxnd_Uk4w.jpeg" /><figcaption>A novel idea, I know.</figcaption></figure><p>The point is, accurate information is critical to success, but data these days turns faster than overripe fruit. Stop wasting time making sure your people have the information they need when they need it and let computers do what they do best: handling tedium; that way, the next time you call a meeting, you can hit the ground running.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8611bfb3cdf3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/aptitive/making-meetings-not-suck-via-the-magic-of-dynamics-365-apis-8611bfb3cdf3">Making Meetings Not Suck Via The Magic of Dynamics 365 APIs</a> was originally published in <a href="https://medium.com/aptitive">Aptitive</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>