web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Azure API Management C...
Power Apps
Unanswered

Azure API Management Custom Connector in Dataverse for Teams (D4T) Environment

(0) ShareShare
ReportReport
Posted on by 186

Hi All

 

We've created a custom connector using Azure API Management as outlined in this blog post. The custom connector then gets exported to our Development (full Dataverse environment, this connector is called BusinessCentral) and the Dataverse for Teams environment (this one is called BusinessCentralTeams - more on that later). The big benefit of this is that users without a per-app or per-user can use the connector within Microsoft Teams.

 

The development of the app is done in a full Dataverse environment and then deployed downstream as a managed solution. At this point the BusinessCentral custom connector is part of the managed solution. When importing into the Dataverse for Teams environment, non-licensed users get a 'You require a premium license' error when opening the app. This is despite the fact that when opening the canvas app in the editor, the connection is not marked as premium.

 

lkaspar_2-1653458103040.png

 

The current workaround is to create an unmanaged layer in the Dataverse for Teams environment and do the following in the app:

 

1. Remove the BusinessCentral connection (when searching for it, it's marked premium)

2. Add the BusinessCentralTeams connector

3. Re-publish the app

 

lkaspar_3-1653458354182.png

 

 

This will remove the message for users and allow them to use the app.

 

The biggest downside is that it makes the deployment process complex and error-prone:

 

1. Import Managed Solution

2. Remove unmanaged layer

3. Edit the app and switch connections

4. Re-publish

 

Users also need to re-consent to the custom connector every time after completing this process (I think this can be solved by switching to oAuth).

 

The two connectors are obviously identical. The only difference is that one got deployed to a full Dataverse environment and then deployed as a managed solution. The other was directly deployed to a Dataverse for Teams environment from Azure API Management.

 

Question for the community/Microsoft:

 

How can we avoid having to create the unmanaged layer? Is there something I can configure in our Development environment prior to deployment? 

 

Any advise would be most welcome.

 

@mods - please move if this post should be in a different board

Categories:
I have the same question (0)
  • lukas.schauffele Profile Picture
    186 on at

    Anyone?

  • Peragin Profile Picture
    160 on at

    Hi @LKS ,

     

    Did you ever find a resolution for this?

  • lukas.schauffele Profile Picture
    186 on at

    Hi @KH_2437 

     

    Yes, I did. The trick is to export the custom connector from APIM into the Dataverse for Teams environment. You then export the custom connector as part of an unmanaged solution and import it into your full Dataverse environment.

     

    Note: you won’t be able to add the custom connector to the solution directly. Instead, create a flow with the custom connector action and add it to the solution. Then right click on the flow and select ‘add required components’. This will add the custom connector. 

     

    I’m currently on leave but can add more detailed steps when I get back.

  • Peragin Profile Picture
    160 on at

    Thanks @LKS ,

     

    I would appreciate that.

     

    Regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 739 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 343 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard