Create a Custom Connector For Power Automate & Power Apps

July 15, 2024 priyeshwagh777 Azure Functions, Customizations, Microsoft Azure, Microsoft PowerApps, Power Automate, Power Platform azure, custom connector, Dynamics 365, Microsoft Azure, power apps, Power Automate, Power Platform

One of the most important qualities of extending capabilities of any platform is being able to add Custom code and make it available to wider use cases.

In this case, it’s a custom code that is encompassed in a Custom Connector in Power Platform and made available to Power Automate or Power Platform.

Use Case

The purpose of my custom connector is to call my hosted custom code in Power Automate or Power Apps.

For this example, I’ve created a simple Azure Function that just returns a value – just to test the working of the Custom Connector. Of course, your use case is to be able to connect to the hosted app, expect it to process the business logic which you intend to do and return back the results.
So, in my case – my Azure Function will simply greet the name passed to it.

See the Postman test below –

Now, let’s make a Custom Connector that will execute this Azure Function in your Power Automate.

Create Custom Connector in Power Apps / Power Automate

You can either make the Custom Connector from the Power Automate portal or the Power Apps Maker portal, both are the same things. Let’s see this example from Power Apps portal –

In this use case, I’m in a Solution in Power Apps / Power Automate. Open the one in your case since you can’t create a Custom Connector from outside a Solution any longer.
Now you can drop down from New and see in Automation menu that you can create a Custom Connector
Now, you’ll be required to enter the name of the Connector itself and other details like a PNG icon for it, Description etc.
Now, below is the info that I filled in. I’m calling it Data Transporter and have selected an Icon which should make me easy to recognize my connector in Power Automate and Power Apps and enter enter the details of my hosted Azure Function which is authenticated using an API Key.
So, here’s what my info looks like –
Now, when I click on Security after filling all the info, the type of Authentication I used in this case if API Key, yours could be different depending on what your custom application is configured to work with –
It’ll ask you to fill in the information so that it appears as parameters to fill in for the Custom Connector when the end user will work on their Flows/Apps.
The info I’m choosing to fill is this – I’m giving a name to the parameter to indicate what info is required. The actual parameter name required by the Azure Function, in this case – it’s ‘code’ and since I need to pass the API key in Query string, I’ve selected Query instead of Header.
When you go to the next part, i.e. Definition, make sure you also give a Name to the Custom Connector already. Before your lose the info you’ve already entered. Make sure you also click on Create Connector

Once you click on Create connector, it’ll create it in a few moments.
Now, since you are aware of Triggers and Actions from using Power Automate – in this use case, my Custom Connector is designed to be an Action i.e. when called/used in Power Automate, it’ll simply perform the operation it’s designed to do.
Hence, I’m selecting an Action here.
When I select New Action from the left hand pane, it’ll open up information for me to fill out to describe the Action.
Now, since this will appear as a listed item in Actions in my Power Automate connector, I’m filling in this info (and we can check later how it appears).

Next, I’ll click on + Import from sample as it’ll give me a place to enter a sample for the request to call my hosted Azure Function.
Next, I’ll pass these values as I did in Postman to create the sample. Once done, I can click on Import.
When I import, I’ll the request parameters set in the Custom Connector based on the sample I entered.
Next, I’ll scroll down to ensure that all validations are perfect and I needn’t fix anything.
Next, I’ll skip AI Plugins step and also the Code step since I want to keep this example concise and to the scope of the hosted Azure Function only.

And this is skipped too –
Now, the final step is to Test the Custom Connector. The Editor will ask you to Update connector before you can Test. Then, in order to begin testing – you’ll need to first create a Connection using New Connection button as shown below.
When you click on New Connection, you’ll be taken to a new tab to enter the API key which you created as parameter in the initial setup of this Connector. See #7 above. Enter the API key you have which works for this hosted app and then click Create connection.
Next, in case the Connection doesn’t appear, click Refresh button once.
Once you refresh, you should see your Connection come up and selected.
Now, next step is to test the Custom Connector itself. Enter the values that you wish to test for and click Test operation.
You’ll see the test results based on what the hosted code is supposed to perform.
In my case, it was easy as it just greets the name entered.

And your Custom Connector is now ready to be used!

Consuming Custom Connector

Now, let’s see how you can use the Customer Connector in Power Automate in order to perform the operation in your Flows –

Once in Power Automate, look for the Custom tab in the Action selector.
Then, you can see the Action you defined in your Connector Definition steps above.
Since you need to authenticate using the API key you have, the create Connection step will ask you this info and you can give the name of the Connection.
Pass the value you want to pass as data.
Finally, you can just save and test the Flow itself and look for your Outputs.

And that’s how you can have a Custom Connector for your custom app/service your have created. I’ll soon write about other aspects of Custom Connector which I wasn’t able to cover in this blog.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

HTTP Trigger Azure Function Authorization Types simplified

July 14, 2024July 14, 2024 priyeshwagh777 Azure Functions, Microsoft Azure azure, cloud, power apps, Power Automate, Power Platform

Now, many of you must be wondering how the Authorization types for Azure Functions using HTTP Triggers work and where to look for information while using these different types. Hopefully, this post helps simplify each of those for you.

Now, when you create a new Azure Function from Visual Studio or from the Azure Portal, you’ll be asked about Authorization where you’ll find the selection to either be 1 of the below –

Anonymous
Function
Admin
System

Anonymous

This type of Authotization let’s you use the Azure Function without needing for any key and anyone with the URL alone can access it. Of course, this is not recommended for any production use –

Now, if you notice your Visual Studio, when you write your first Azure Function, it comes with pre-defined method ready for you to continue to write your own code. But right away, you’ll see that the Authorization method is pre-defined considering you must’ve selected Anonymous while starting the Project.
Also, since the Azure Function is understood to be Published already on the Azure Portal, you’ll see in the Function’s settings that the same has been reflected as well.
Now, if you test this using Postman, the code will be able to run directly just using the URL without any API key. Either you pass in the body – and you’ll get a 200 OK with the result that the Azure Function is supposed to result.

Or using query parameters – the result will be the same.

This simply explains Anonymous authorization. Without any check on who’s supposed to access the Azure Function.

Function

In this type of Authentication, only the Function and resources associated to it will be accessible. This needs the caller to have a key [or code] to be passed while calling Azure Function –

Let’s look at the code, and see that the type is not set to Function for Authorization.
And when you Publish the code, the same will be reflected in the Settings too.
And when you want to access the Azure Function from Postman, you’ll need the Function Keys defined in the Function Keys area of the Function itself – a Default Key is given already but you can choose to add your own keys and using any of them would do.
Now, here’s what the Key looks like when you click on Show [there’s a button on the far right to expose the key’s value]
Now, when you go to Postman, you need to can pass this as a query parameter –

Now, let’s look at the Admin Type of Authorization.

Admin

In this type of Authorization, you get access to Functions’ Runtime APIs. The way to use the Admin key is similar to the Function Keys, just that they are available from the Function App itself than the Function –

Now, when the Authorization is set to Admin
You’ll see this reflected in the portal once Published.
Now, in the Function App itself – you can navigate to the App keys under Functions [as of the portal’s layout in mid-2024]
You can expose to see this value and share it to the clients who are going to consume this Function App. They key required here is the _master
Now, you can test this using Postman

Remember, this type of Authorization is to be used when the calling client needs to also access Functions Runtime API.
Finally, Let’s look at the System type.

System

This type of key is managed by Function runtime and is used when the calling client when there’s a need for granular access to function runtime features.

Now, you can set this from the code and publish it.
And it’ll appear in the settings of the Function [In case when the Function wants to access granular function runtime features].
And this is present in the App keys area under System Keys section.
And when you test the same, they work just like any other key from the Function app when called.

Hope this was useful!

Here are some Power Automate posts you want to check out –

Create your first custom Copilot for Customer Service Hub – Part 2 | Authentication

July 10, 2024 priyeshwagh777 microsoft copilot ai, copilot, custom copilot, customer service, Dynamics 365, microsoft, microsoft copilot, Power Platform

Now, you must have created your own Copilot to be deployed for the Customer Service Hub. If not, here’s the link to Part 1 of this blog – Create your first custom Copilot for Customer Service Hub – Part 1

Configure User Authentication with Microsoft Entra ID

Here’s how you can configure the User Authentication with Microsoft’s Entra ID for your Copilot to be authenticated with –

Go to the Azure Portal [https://portal.azure.com/], then given the appropriate permissions your might have, you should be able to create an App Registration
Now, create on New Registration –
Now, give it a suitable name so that you can identify that the purpose of this App Registration is for Copilot. Select multi-tenant, leave Redirect URI blank and click on Register.
Once ready, go to Authentication and then click to add Platform.
In the platform selection, click on Web.
Now, enter the URIs – First, enter the first URI, make sure to select Access tokens and ID tokens in Implicit grant and hybrid flows section and then click Configure.

https://token.botframework.com/.auth/web/redirect https://europe.token.botframework.com/.auth/web/redirect
Then, go ahead and add the Second URI from the main screen itself. Then, click Save and refresh the page once.
Now that both the URIs are added, click on the configuration link to consider both the links for configuration.
Now, you’ll be taken to this pane where you can click
Now, both the URIs will appear here.
Next, generate Client ID and Client Secret as you’ll need these details too –

Set Copilot Authentication to use Custom Authentication

Going back to the Copilot itself, set the Authentication you just created in the Azure Portal –

Go to Settings on the Copilot to use the Custom Authentication.
Go to Security section and then select Authentication.
Select Authenticate manually and then enter the details as shown below. Enter the Client ID and Secret which you must’ve saved before.
Next, come back to Copilot Settings and in Security, go to Settings and then look for Web channel security.
Once you open it, you’ll find that the Secured Access is disabled. Go ahead and enable it.
It takes up to 2 hours for it to take effect. Till then, old settings apply.
Finally, in Channels, select Customer Service Hub so that you can connect to the Customer Service Hub.
On the right hand side pane which opens up, you’ll see that this is not connected. Click the Connect button.
It connects to Customer Service Omnichannel in a few moments.

Part 1: Create your first custom Copilot for Customer Service Hub – Part 1

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Create your first custom Copilot for Customer Service Hub – Part 1 | Create Copilot

July 8, 2024July 10, 2024 priyeshwagh777 Dynamics 365 CE, microsoft copilot ai, artificial-intelligence, copilot, custom copilot, dynamics 365 custom copilot, microsoft, Power Platform

Now, if you already have Copilot Studio in your Organization or have created a trail [Start your Copilot Studio Trial], you might be looking to build your first Copilot. Here’s how you can do it –

In this example, I’m creating a Copilot to help new Customer Service Reps at the organization to search and seek help about the organization itself quicker.

Create your Copilot

Here’s how you can start building your first custom Copilot –

In your Copilot Studio environment, you must be seeing this New Copilot button in Copilot section. Click that.
Here’s you need to start describing the Copilot you are looking to create. This is optional but recommended to do so as first step. It’ll ask you some questions on the context of the Copilot which you are looking to create.
After it gathers some information from you, it’ll summarize what the Copilot is aimed to do.
Now, once done you can click Skip to Configure to go to the next step.
Further, you can name the Copilot and then start adding Knowledge by adding sources where the Copilot will source information from.
Some of the most common ways for the Copilot to source knowledge from is from website and SharePoint data itself.
In this example, I’m sourcing some information about whitepapers from thecompany’s website itself.
Now, once this is ready, I’ll further proceed to Create the Copilot itself once relevant Knowledge links have been added as required. Once done, click Create.
Now, once the Copilot is created – it’s ready to be configured further or even ready to be Published if nothing else is to be added at this point.
You can scroll down in the details section and find that the Copilot is ready to be Published.
Note that based on the Copilot settings for Channel, it’s only available to Teams at first – but you need to configure for other channels – like Customer Service Hub [in this case]
Now that this is published. –
Your Copilot is now ready!