Posts

Showing posts from 2018

Headless-Daemon calling AAD secured API

Image
In AAD series of articles, we will see how to call the AAD protected secure API from a headless (or) console application and its authentication flows and scenarios. In the previous article, we have seen how to register an app in aad . I recommend you to read to get familiar with the app registration concept. How to call the AAD protected secure API from a headless (or) console application For these types of non-interactive clients, we can use 2 types of authentication flows for different scenarios.    - client_credentials_grant    - username/password The above grant types allow clients to authenticate silently without any user interaction. oAuth 2.0  client_credentials_grant Authentication is done bas ed on the valid "Client Secret" used, so this is available only for the "WebApp Type" app registrations. and copy the below information from the respective app registration for later use.      - ClientID: Client App's ...

Step-By-Step Azure AD App Registration

Image
Enterprise developers and software-as-a-service (SaaS) providers can develop commercial cloud services or line-of-business applications, that can be integrated with Azure Active Directory (Azure AD) to provide secure sign-in and authorization for their services. To integrate an application or service with Azure AD, a developer must first register the application with Azure AD. Any application that wants to use the capabilities of Azure AD must first be registered in an Azure AD tenant. This registration process involves giving Azure AD details about your application, such as the URL where it’s located, the URL to send replies after a user is authenticated, the URI that identifies the app, and so on.  In the upcoming series of articles will see different 'grant_type' and which one to use for what scenario? how to use in Daemon-Headless-App calling secure WebAPI - client_credentials/password_credentials how to use in Windows-Forms-App calling secure WebAPI - cod...

Approval and auto escalation with time out in Microsoft Flow

Image
Let's see how to create an Approval workflow with timeout and escalation. I have used Office 365 Custom List "item created or modified" as my trigger. Create "Supervisor Approval" Create "Escalation Approval" Specify duration in ISO 8601 format. refer here for more time-out formatting. "Escalation Approval" would trigger only after the "Supervisor Approval timeout" Final Flow -Ratsub

Cognitive reports in Power BI with R-script

Image
As a continuation of my previous  Sentiment & Phrase analysis using Cognitive Services via MSFlow  will see the report creation part in PowerBI with r-script analytical capability. About PowerBI Power BI is a business analytics solution that lets you visualize your data and share insights across your organization, or embed them in your app or website. Connect to hundreds of data sources and bring your data to life with live dashboards and reports. - PowerBI About R-Script R is a free software environment for statistical computing and graphics. R is an integrated suite of software facilities for data manipulation, calculation and graphical display. - R-project Let get started, Open PowerBI  Now, design the form based on your requirement.  Then, add master lookup filter "Product Name" Configure it further Adding Measure a.k.a DAX To know more about measures and Data Analysis Expressions Now, let's bre...

Sentiment & Phrase analysis using Cognitive Services via MSFlow

Image
In this  digital transformation  era i mplementing AI and Cognitive services into any of our service and application where ever possible plays one of crucial role improving end-user/customer/business decision and overall experience. Let's us see a scenario for Ratsub Tech (A Fictional company) is B2B & B2C e-commerce retailer who is interested to understand "UserVoice" e-Mail by tracking its mailbox to understand user experience/sentiment towards their purchases. Create a form to capture User recent purchase and provide a placeholder to fill their thoughts or you can also use adaptive forms will see about this later. At this point assume there is an interface for end-user to fill and send back there 'UserVoice'.  Setup an e-Mail rule and move these emails(i.e. To:uservoice@ratsubtech.com) to "Support" folder. //Sample e-mail template for this usecase From: rathanavel@live.in To: uservoice@ratsubtech.com Subject: CustomerID^639~Product...