Follow my blog for more interesting topics on Dynamics 365, Portals and Power Platform. For training and consulting, write to us at info@xrmforyou.com
I have been conducting a lot of PowerApps portal training lately and more often than not, I get this question – “Who can provision a portal?“. “What are the required privileges required to provision a portal?”
Well, you can find information in bits and pieces everywhere. However there are access checkpoints need to cross check so that you do not get an error during portal provisioning.
In this blog I will explain in detail the various checkpoints to remember when you provision a portal. Let’s go through all of them. Click here to know how to configure a PowerApps portal for your CDS environment, in case you are not aware of it.
- Check if the user have the required role – If a user is complaining that they are not able to provision a portal, this is probably the first step that you need to check. Make sure the user have the system administrator role in Common data service (CDS) or Dynamics 365. Access mode should be set to Read-Write under Client Access License (CAL) information in the user record.
To verify this setting is correct or not, in your CDS or Dynamics 365 environment, navigate to Advanced Settings -> Security -> Users. Open the user record in question.
Click on Manage roles to open the security role for the user and make sure the user have System Administrator role.
- You don’t have required permissions to create Azure Active Directory applications
Even though you may have system administrator privilege in CDS or your Dynamics 365 instance, you may receive this error. This is because when you provision a portal, a new application is registered in Azure active directory. And if the user does not have the privilege to create an app in Azure active directory, they will get this error during portal provisioning.
To resolve this issue you must contact your tenant administrator to provide you with app creation privilege in Azure AD tenant. You can find more details here.
- I’m getting an error that portal creation is blocked in this tenant by global administrator
The error is because your global administrator has blocked creating a portal in this tenant. For that you need to enable portal creation in your tenant.
You basically need to run a powershell command to enable portal creating in your tenant.
Set-TenantSettings -RequestBody @{ "disablePortalsCreationByNonAdminUsers" = $false }
These are the usual errors that you usually face while configuring a PowerApps portal. Once these are fixed, you should be good with the portal creation
You will also like the below posts
Hope this helps!
Debajit Dutta
(Business Solutions MVP)