Has anyone integrated SN with MS Adaptive Cards?

[Austen Harriso2]

Current investigating the possibilities for an integration between ServiceNow and Microsoft's Adaptive Cards. Checking to see if anyone has any experience with either sending an Adaptive Card JSON body from ServiceNow to any target application (specifically hoping for experience with Outlook here) or in rendering cards in the platform. 

I'd appreciate any info on the topic. Let me know if you've implemented this feature or if you scoped the feature and were unable to implement.

Thank you!

[Laszlo Balla]

Hi Steve,

Could you please elaborate on this? Which property did you have to update to get it working? I'm still struggling getting this thing to work, even though we are using a @service-now email address in our sub-prod instance too... I must be missing something.

[Steve Kelly]

Hi,

So the system property sn_ms_oam.outlookactionable.originator is populated with the default @service-now.com Microsoft Provider ID for Outlook Actionable Messages. Having a registered Provider ID with Microsoft is a necessity for OAM to work with emails from a particular domain. The ServiceNow documentation says OAM should work with any @service-now.com emails, but it wasn't working for us.

So we ended up registering our own email domain with Microsoft, per the ServiceNow documentation, and then updating the system property above with that new Provider ID we got when we registered. And voila, it worked!

As far as I can tell, we were not doing anything wrong in the setup as its pretty basic. So I'm not sure why the default Provider ID was not working with the @service-now.com domain emails. But if you plan on using this with your own email domain, you will need to register anyway.

Let me know if this clears things up.

Thanks,

Steve

[Laszlo Balla]

Thanks Steve, it certainly helps. This is indeed very strange that the OOTB provider ID is not working. I am (was?) not planning using a non-SN domain. I have logged a case with HI in the meantime, so I'll see what they find... I'll let you guys know.

[Duodecimal]

"our own email domain" - Could you elaborate? I'm still getting 401s. 

This is how I'm filling out the provider info in Outlook:

Other than setting the scope of submission being just my mailbox, I'm not sure what else I need to do. 

Since this is a sub-prod instance, the email is being sent to our developer inbox account, but the source code still says that I'm the expected originator, which makes me think that this isn't the problem. 

{"$schema":"http://adaptivecards.io/schemas/adaptive-card.json",
"type":"AdaptiveCard",
"version":"1.0",
"hideOriginalBody":false,
"expectedActors":["abongiovanni@***.***"],
"style":"emphasis",
"originator":"***",
...

[Steve Kelly]

Yep, so our own email domain being our university email domain, which is a .edu domain. We added the multiple email addresses for our .edu domain that we use with ServiceNow.

I don't think you can register a @service-now.com email account since SN has already registered their own domain with Microsoft. I believe that is what is supposed to work default out of the box, but didn't for us and doesn't appear to be for others (if I am understanding the documentation correctly).

When we registered our own domain with Microsoft as a provider, got a new provider ID and updated the system property specified in the documentation, it started to work.

If you use @service-now.com accounts for your ServiceNow email notifications, I'd suggest maybe opening a ticket with HI if it is not working out of box and as expected when you activated the plugin and added the mail scripts. 

The other thing to note is, when you're testing make sure you are the approver of the test record, as it seemed when we were testing that you will only see the adaptive card in Outlook if you are the approver and intended email recipient.