From the Microsoft Power Platform blogs: Multilingual copilots; Register, authenticate toward Azure app: Embed image in email; Synchronize Microsoft shifts

In this week’s Power Platform blog roundup:

• Create multilingual copilots with the Power Platform CLI and Microsoft Copilot Studio
• Register and authenticate towards Azure app with Power Automate
• Three ways Power Automate can embed an image in email
• Synchronize Microsoft shifts with Outlook calendars in Power Automate the 2024 way

Create multilingual copilots with the Power Platform CLI and Microsoft Copilot Studio

Writing on the Microsoft Power Platform developer blog, Daniel Laskewitz stated that a while ago, it became possible for users to create multilingual copilots in Microsoft Copilot Studio. He pointed out that it's easy to enable the setting and have multiple languages in your Copilot.

In his blog post, Laskewitz explained how to translate your Copilot into a different language.

First, Laskewitz wrote about how to create a Copilot by using the creation dialogue. He stated that he would use the conversational boosting capabilities, although it's not necessary for this scenario.

What is important is the language you will select; in my example it’s set to English. This will be the primary language. You can add multiple other languages to your copilot if needed, but the primary language will not change.

Laskewitz then provided information on how to add a secondary language and switch to that language. Finally, he described how to work with the translations in Visual Studio code.

Register and authenticate towards Azure app with Power Automate

On the Let's Power Automate blog, Tom Riha wrote that in addition to many actions with a specific functionalities, Power Automate also gives you some generic actions – HTTP requests.

Riha noted that unlike the standard actions, where you might encounter some limitations, HTTP requests give you much more control as the limitation is moved to the other side to the endpoint of the application you’re trying to access. He stated that one example is the Graph API. He also noted that a lot of predefined actions interact with this API, hiding it in the background.

Riha wrote that since not all functionality can be predefined, you sometimes need to access a different endpoint in Graph. To call an endpoint directly, Riha stated that you should first try one of the predefined HTTP request actions. He then explained how to do that.

However, Riha noted that these actions don’t support all the available endpoints. As such, if you need more than they offer, you’ll need an Azure application. He then explained how to register an application in Azure and how to authenticate toward the application.

Three ways Power Automate can embed an image in email