Blog
Error - How to fix the "This app isn't opening correctly" / "InsufficientActivePlanForApp" message
May 16. 2023
If users receive the "This app isn't opening correctly" / InsufficentActivePlanForApp error, here are some steps you can take to resolve this issue.
An issue that app builders often report is this. When running an app, the following error appears:
{
"error": {
"code": "InsufficientActivePlanForApp",
"message": "The user with object identifier in tenant does not have an active plan with sufficient policies to use this app.",
"details": [
{
"code": "InsufficientPlanForPremiumApis",
"message": "The user with object identifier in tenant does not have a plan with sufficient policies to use premium APIs. Premium API"
}
]
}
}
The cause of this type of error is fairly self explanatory. The user doesn't have a sufficient license - eg, a per app or per user license. The cause of this will be because premium connectors have been used in the app.
At this point, there are 2 ways to resolve this issue:
- Purchase and assign a premium license to the user
- Edit the app and remove any functionality that refers to premium connectors
Let's say we choose to remove references to the premium connectors in our app. The behaviour that can confuse app builders is this.
After re-publishing the app, the error still occurs. From the app details pane in the Maker Portal, it isn't obvious what connection causes the 'premium' designation of the app.
In such situations, the common thing that makes an app 'premium' is that it calls a Power Automate Flow that uses a premium connector. Therefore, the next step is to investigate the Flows that are called by the app and to remove them from the app if required.
A typical thing that happens is that app builders call a Flow that uses the Word Online connector to create PDF documents. Because this is premium connector, this is thing that causes an app to become 'premium' in many cases (HTTP request actions in Flow are another common culprit).
Conclusion
If a user receives the InsufficientActivePlanForApp error, the reason is because premium connectors have been used in the app. We can either assign a appropriate license to the user or we can remove the premium connectors from an app. App builders often struggle to understand why an app has been designated 'premium' and in most cases, it's because the app calls a Flow that includes a premium license.
- Categories:
- licensing
Related posts
- SQL Server - Grandfathered licensing model to end on October 1, 2024
- How to fix licensing error when registering for the Power Apps developer plan
- Licensing - Microsoft 365 licensing price set to increase in March 2022
- Microsoft announces cheaper Power Apps licensing from October 2021
- Why is Microsoft 365 licensing so confusing?
- Licensing - What license do I have?