• Instantly respond to high-need warnings or messages. 
• Capture, track, and catch up with new sales clients. 
• Copy all email attachments to your OneDrive Business account. 
• Collect data about your business and share that data information to your team. 
• Automate an approval workflow.

• Navigate to the Azure portal. Click Create a resource link on the top-left corner of the portal page, choose Compute > Function App.

• Pass Function App settings as mentioned below and click on Create to provision and create a new Function App.

• After creating Function App, access Notification icon in the top-right corner of the portal and verify Deployment succeeded message.

• Click Go to resource button shown in the above image to navigate to your newly created Function App. You can also choose Pin to dashboard to quickly access the Function App from your Azure portal dashboard.

• Time (in hours) estimation for turbine repair or maintenance.
• Capacity (in kilowatts) of the turbine.

• In your function app, click + icon next to Functions. Select In-portal and then Continue at the bottom.

• Choose More Templates… and then Finish and view templates.

• .Choose HTTP Trigger.

• Provide function Name as “TurbineRepair” and select Authorization level as “Function”. Click the Create.

• Replace the default code inside run.csx script with the below code.

run.csx
#r "Newtonsoft.Json"

using System.Net;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Primitives;
using Newtonsoft.Json;

const double revenuePerkW = 0.12;
const double technicianCost = 250;
const double turbineCost = 100;

public static async Task Run(HttpRequest req, ILogger log)
{
    // Get query strings if they exist
    int tempVal;
    int? hours = Int32.TryParse(req.Query["hours"], out tempVal) ? tempVal : (int?)null;
    int? capacity = Int32.TryParse(req.Query["capacity"], out tempVal) ? tempVal : (int?)null;

    // Get request body
    string requestBody = await new StreamReader(req.Body).ReadToEndAsync();
    dynamic data = JsonConvert.DeserializeObject(requestBody);

    // Use request body if a query was not sent
    capacity = capacity ?? data?.capacity;
    hours = hours ?? data?.hours;

     // Return bad request if capacity or hours are not passed in
    if (capacity == null || hours == null){
        return new BadRequestObjectResult("Please pass capacity and hours on the query string or in the request body");
    }
    // Formulas to calculate revenue and cost
    double? revenueOpportunity = capacity * revenuePerkW * 24;  
    double? costToFix = (hours * technicianCost) +  turbineCost;
    string repairTurbine;

    if (revenueOpportunity > costToFix){
        repairTurbine = "Yes";
    }
    else {
        repairTurbine = "No";
    };

    return (ActionResult)new OkObjectResult(new{
        message = repairTurbine,
        revenueOpportunity = "$"+ revenueOpportunity,
        costToFix = "$"+ costToFix
    });
}

• Click the Save button.

• Expend test tab at the far right of the function app and select Test to verify the function. Pass below value inside the Request body, and then select Run.

run.csx -> Test -> Request body
{
    "hours": "6",
    "capacity": "2500"
}

• You can see below the value returned inside response body Output.

Output JSON
{"message":"Yes","revenueOpportunity":"$7200","costToFix":"$1600"}

• In your function app, under Platform features, select API Management.

• Click Create new link on API Management page.

• Pass API Management service settings as mentioned in the below table. Click Create to generate the API Management instance.

• Select Enable Application Insights to view logs inside the function application, accept the defaults and then click Link API.

• Click Select on Import Azure Functions dialog, where TurbineRepair function is highlighted.

• Accept the defaults on the Create from Function App page and click Create to register API for the function.

• Click POST operation on the Test tab of “turbineCostMgmt” function.

• Provide values for hours and capacity in JSON format. Click Send.

JSON Request body
{
    "hours": "6",
    "capacity": "2500"
}

• Observe the HTTP response.

• Click Download OpenAPI definition at the top of API Management page.

• Observe OpenAPI definition in the downloaded JSON file.

turbinecostmgmt.json
{
  "swagger": "2.0",
  "info": {
    "title": "turbineCostMgmt",
    "version": "1.0",
    "description": "Import from \"turbineCostMgmt\" Function App"
  },
  "host": "your_apim_service_name.azure-api.net",
  "basePath": "/turbineCostMgmt",
  "schemes": [
    "https"
  ],
  "securityDefinitions": {
    "apiKeyHeader": {
      "type": "apiKey",
      "name": "Ocp-Apim-Subscription-Key",
      "in": "header"
    },
    "apiKeyQuery": {
      "type": "apiKey",
      "name": "subscription-key",
      "in": "query"
    }
  },
  "security": [
    {
      "apiKeyHeader": []
    },
    {
      "apiKeyQuery": []
    }
  ],
  "paths": {
    "/TurbineRepair": {
      "get": {
        "operationId": "get-turbinerepair",
        "summary": "TurbineRepair",
        "responses": {}
      },
      "post": {
        "operationId": "post-turbinerepair",
        "summary": "TurbineRepair",
        "responses": {}
      }
    }
  },
  "tags": []
}

• Microsoft Flow account having same authentication credentials as Azure account.
• Consumption Plan, as it requires limited utilization of resources and only pay for the time the function is executed.

• SharePoint, to be used as a data source.

• Under TurbineRepair function, click </> Get function URL link.

• Copy function URL which is displayed by clicking Copy link.

• Browse to https://flow.microsoft.com, select My flows and click New > Instant-from blank

• Add When an item is created SharePoint trigger. Select Site Address as your SharePoint site name and required List Name as “Turbines” that contains the turbine data.

• Specify a condition to execute the next set of actions. Insert a new step and add a new Condition control, which will add two branches: If yes and If no.

• You can specify a condition to match a criterion and add steps/actions to one or both the branches based on the condition. Select the first box on the Condition card and choose ServiceRequired under Dynamic Content dialog returned through When an item is created trigger.

• Add true for the condition i.e triggerBody()?[‘ServiceRequired’] is equal to true.

• Click Add an action in the If yes branch and add a step (action) – HTTP-HTTP. Rename the action to Calculate costs.

• Change Method to "POST" and add Function URL copied earlier as URI to call the Turbine Repair Azure function. Add Body as shown below. You can also select a Dynamic Content dialog box to pass the Estimated Effort (for hours) and MaxOutput (for capacity) list item values.

Action: Calculate costs -> Body
{
      "hours": "triggerBody()?['EstimatedEffort']",
      "capacity": "triggerBody()?['MaxOutput']"
}

• Provide flow name as Turbine Repair Approval and Save the flow.

• At this point of time, check the Flow run by adding a new item or row in the Turbines list.

• Navigate to Turbine Repair Approval flow and click on the Flow start date. You can observe that the flow is succeeded.

• You can observe the output Body that the flow action returns: message > “Yes”, as well as revenueOpportunity (potential revenue) > “$7200” and costToFix (cost of repair) > “$2600” values from TurbineRepair Azure function it calls.

• Add a Compose action at the bottom of If yes branch to the store value of Message returned from Calculate costs action.

Compose -> Inputs 
body('Calculate_costs')['Message']

• Add another condition at the bottom of If yes branch below Compose operation.

• Select the first box in Condition 2 card and add Output of Compose operation under Dynamic content tab.

• Add Yes for the condition i.e outputs(‘Compose’) is equal to Yes. The flow executes next If yes or If no branch based on if Message value returned by Azure function is yes (repair required) or no (repair not recommended).

• Add two Compose operations, one each to store repair cost and potential revenue returned by Calculate Costs action. We will be using these values later while sending an email.

Compose 2 -> Inputs
body('Calculate_costs')['costToFix']

Compose 3 -> Inputs
body('Calculate_costs')['revenueOpportunity']

• Add an action Office 365 Outlook – Send an email at the bottom of If yes branch of the second condition to notify respective person regarding turbine repair as well as costs and potential revenue.

• Pass a valid email address of the user in your organization in To field, add email Subject and compose email inside Body. Fetch the value of Title token for SharePoint list under Dynamic content tab and CostToFix and RevenueOpportunity from the above Compose 2 and Compose 3 operations respectively.

Send an email -> Subject
Recommended repair for triggerBody()?['Title']

Send an email -> Body
Based on our calculations, the cost to fix triggerBody()?['Title'] is outputs('Compose_2') and the revenue opportunity is outputs('Compose_3'). Please arrange for the repair to be made.

• Save the flow. The completed flow should look like the one below:

• Once flow configuration is completed, add a new item or row inside the Turbines list.

• Adding a new item triggers the Turbine Repair Approval flow. On the flow page, check the Flow run.

• If your flow ran successfully, you can observe flow operations by expanding various actions.

• Verify the email account (Outlook) inbox for the person you passed in the To field of Send email action. The received email should look like the one below.

Conclusion