(UPDATED) Guide to configuring Microsoft Teams with the Oracle Digital Assistant

The App Studio is no longer supported, hence we need to use the Developer Portal to configure MS Teams to configure the ODA connectivity.

Check the original post here.

Microsoft Teams (MS) is one of the most widely used communication channels and is very popular among Oracle Digital Assistant (ODA) customers. The initial setup was not easy as my personal hotmail.com account was not enough. My work email also did not work as I do not have admin privileges for the oracle domain (obviously)

So I ended up creating a developer account valid for 90 days. This account gives all the necessary permissions that a full corporate MS account has, without the need to depend on admins 🙂

I followed the ODA Documentation for MS as a channel available here. There are 3 possibilities to create an MS Bot. I followed the Developer Portal Channels Registration.

Add a bot with the Developer Portal

This is the main difference when comparing it with the older post. AppStudio is deprecated: “App Studio has reached its end-of-life. Use the new Developer Portal to manage your apps now.”

Go to https://dev.teams.microsoft.com/

To set up a bot through the Teams Developer Portal, you create the following:

  • A Microsoft Teams app. This app is the container for the bot that you create and is how you access the bot in Teams.
  • A bot. This is the artifact within the app that communicates with Oracle Digital Assistant
https://docs.oracle.com/en/cloud/paas/digital-assistant/use-chatbot/microsoft-teams.html#GUID-F8C284DB-5EB1-415C-9A6E-6D97B58992B3

Fill in all the fields, except App Id (that is generated), and press Save at the bottom.

Choose the menu App Features. Press Bot.

We will create a new Bot.

Give it a name and open the newly created bot.

Go to Client secrets and add a new client secret.

Press the Azure link. This will redirect you to the azure portal where we have a bit more details on our newly created bot.

Select your bot and go to Certificates & Secrets

Create a client secret – give it a name and choose expiration time.

Copy the value of the generated client secret and save it in a safe place on your system

Ok, now back to ODA.

Create ODA Channel

As with every channel configuration, we need to create the ODA Channel definitions.

Important: Use the Bot Id and the Password created previously. Not the App Id, we need the Bot Id.

Save the Webhook URL generated by the ODA Channel.

Configure the Webhook URL for Microsoft Teams

Save the previous Webhook URL in the Bot endpoint address as seen below, under your bot Configure option.

Now we are ready to test the app and the bot. Press Preview in Teams.

Press Add and then you can test it!

And here we have our Skill working in MS Teams!

And another example, this time making use of MS Teams Adaptive Cards!

PS: Some extra steps might be required when it comes to policies, users, and permissions, especially in a corporate setting. This developer instance has very few restrictions.