Prevent Authentication Prompts in Power Apps and Power Automate for Custom Connectors

You have authored a Custom Connector and created a Flow associated with a Power Apps which you have then shared with your team or organization. However, when the end users started using the APP they get an authentication prompt, requiring them to enter their credentials or API key which is not ideal as this means setting up a separate, or shared account, for each user in each connector, very inconvenient. In this post, I will explain how we can work around the problem by Sharing the connection of your Custom connector with specific user or the entire organization.

Creating Power Automate / OpenAPI Extensions for Azure Functions (Fusion Development)

So, what is this "Fusion Development" you ask? Fusion development allows your business to build better applications, faster, by bringing together professional developers with amateur or hobbyist developers. If you're not familiar with fusion development, have a look at the Microsoft Learning Path  - Transform your business applications with fusion development. In this post, we … Continue reading Creating Power Automate / OpenAPI Extensions for Azure Functions (Fusion Development)

Decouple the Flow from The Power App to prevent end-user Authentication Using a Child Flow

In my previous blog, we worked around for Power Apps prompts for credential during deployment problem by decoupling the Conversion logic of flow from the Power App by writing to SharePoint from the App. We then used the full version of Power Automate to attach the Flow, which does all the work, to the SharePoint list or library. In a this post I will explain how to apply the same principle without using SharePoint as an intermediate using the Child Flow.