Download presentation
Presentation is loading. Please wait.
1
Office 365 Actionable Messages with Connectors and Email
Shivakumar Seetharaman Principal Program Manager
2
Agenda Introduction Demo Architecture Sample Markup
Security considerations
3
Actionable Messages (Preview)
Allows users to easily complete simple tasks right from Outlook Supported with Office 365 Connectors s Built using the same rich, elegant and consistent layout capabilities of connector cards
4
Trello: Office 365 Connector with actions
MS Flow: with actions
5
Architecture for Actionable Messages with Emails
Register for sending marked-up s 1 LoB Systems Expense System HR Mgmt System CRM System Accounting System SMTP endpoint Outlook Client Send with Markup 2 Markup gets stamped as a property and Outlook renders the markup with actions 3 URL provided in the markup is invoked 5 User clicks on the action 4
6
Architecture For Actionable Messages with Connectors
Register for sending connector message 1 2 User configures connector Cloud Service Providers Outlook Client Webhook URL endpoint HTTP POST Connector message w/ actions 3 Markup gets stamped as a property and Outlook renders the markup with actions 4 URL provided in the markup is invoked 6 User clicks on the action 5
7
Markup example Email message
<html> <head> <script type="application/ld+json"> [ { " "MessageCard", "hideOrignalBody": "true", "sections": [ "title": "Expense report is pending your approval" "facts": [ "name": "Amount", "value": " " }, "name": "Purpose", "value": "Meeting with Summit Ski" } ], "potentialAction": [ "HttpPost", "name": "Approve", "target": "<url>" “OpenURI", "name": "View in MS Approvals", ] </script> </head> <body> <!-- The body goes here. --> </body> </html> Supports 2 types of action primitives: httpPOST openURI
8
Markup example Connector card
{ "summary": "This is the summary property", "title": "This is the title property", "sections": [ { "title": "This is the **section's title** property", "activityTitle": "This is the section's activityTitle", ..., "facts": [{ "name": "This is a fact name", "value": "This is a fact value" }, ... ], "potentialAction": [ "ActionCard", "name": "Comment", "inputs": [ "TextInput", "id": "comment", "isMultiline": true, "title": "Input's title property" } "actions": [ "HttpPOST", "name": "Submit", "target": " ] "name": "Favorite", "OpenUri", "name": "View in app", "targets": [ { "os": "default", "uri":" } }], }] Markup example Connector card Types of Input controls supported: Text input Multichoice input Date input
9
Security Considerations Developer requirements
Send phase Use SPF or DKIM for Office365 to verify the sender domain (for actionable s only) Your service must be registered with Microsoft Action URL must support HTTPS Action processing phase Bearer Token Signed by Microsoft Includes subject, sender claims and target URL (audience) (Recommended) Limited Purpose Token Correlate service URL with intended request & user Include as part of target URL
10
Call To Action Try out Actionable Messages preview
Your existing connectors support actions Asana, Bitbucket, Github, Trello, Twitter and Zendesk Add Actionable Message support to s from your internal LoB applications Hook up your service to Actionable Messages Use aka.ms/gotActions to sign up, and we’ll be in touch! Questions before your sign up?
11
Resources Developer Documentation Messagecard playground tool
Messagecard playground tool Channel9 video introducing Actionable Messages (for end- users/IT admins)
12
11/17/2018 4:37 PM © 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Similar presentations
