Power CUT #5 – Can’t create an API permission for the Power Apps runtime service on an app in Azure AD

In this very short and simple PowerCUT post, I’m going to give you an answer to a simple problem I came across recently. Do you ever have a need to interact with the Power Apps runtime service, one of the APIs you can add… READ MORE [https://lewisdoes.dev/blog/power-cut-5-cant-create-an-api-perm
close up shot of keyboard buttons
Photo by Miguel Á. Padriñán on Pexels.com
In: Low Code Lewis Content 🚀

In this very short and simple PowerCUT post, I’m going to give you an answer to a simple problem I came across recently.

Do you ever have a need to interact with the Power Apps runtime service, one of the APIs you can add permissions for to an Azure AD app registration?

I had to do some testing in my own tenant for a project recently where I don’t have premium Power Apps licensing available but do have the developer plan environments.

So let’s see how this went…

The error

So when I tried to grant admin consent for the tenant for the Power Apps Runtime Service API permission which basically gives access to CDS/Dataverse, I encountered the following error.

Resolution – What does this mean?

Now it’s unlikely that you’ll come across this because the whole purpose of this is that you try to access Dataverse. But if you’re working in developer environments where you are able to use Dataverse but don’t actually have a premium license in place you may experience this.

This error appears when you don’t have an active subscription in your organisation to use Microsoft Dataverse or a Power Apps premium license or perhaps a Power Automate premium license.

To resolve this, you’ll need to purchase a premium license for the Power Platform that includes access to using Microsoft Dataverse.

Written by
Lewis Baybutt
Microsoft Business Applications MVP • Power Platform Consultant • Blogger • Community Contributor • #CommunityRocks • #SharingIsCaring
Great! You’ve successfully signed up.
Welcome back! You've successfully signed in.
You've successfully subscribed to LewisDoesDev.
Your link has expired.
Success! Check your email for magic link to sign-in.
Success! Your billing info has been updated.
Your billing was not updated.