Archive
Power Apps | Custom connector | User does not have an entitlement to use PowerApps
From the Dynamics trial instance, while registering a Custom Connector, encountered following issue.

Reason:
- Error message states clearly, that the User who is trying to register ‘Custom Connector’ does not have ‘Power Apps’ license.
- By default when you subscribe for trial , Dynamics only grants the ‘Dynamics 365 Customer Engagement Applications’ license which does not have ‘Power Apps’ option.
- To check the User license, connect to Microsoft 365 Admin Center
- Go to user’s ‘Manage product licenses’ tab.

Fix:
- Grant the user Power Apps license to the user.
- One option is by subscribing for the ‘Dynamics 365 Customer Engagement Plan‘ license by following below steps.
- Connect to Microsoft 365 Admin Center
- Go to ‘Billing -> Purchasing Services’.
- Select ‘Dynamics 365 Customer Engagement Plan Trial’ and click on ‘Get free trial’.

- You would get following confirmation page up on procurement.

- Now open the User, and grant the ‘Dynamics 365 Customer Engagement Plan’ license.
- Make sure ‘PowerApps for Dynamics 365’ is enabled.

- You should be able to configure Custom Connector now.
- Refer Power Apps license guide for more details.
đ
ADX Portals – Cannot register for ‘OnSendingHeaders’ event
Other day, while configuring portal on a new CRM instance, portal shown error page, up on clicking the ‘Apply’ button.
There were no details on error screen to deduce the reason. So we had to go to the server where our portal website hosted.
When checked the ‘Event Viewer’ logs in Portal server, there was this following exception:
Exception type: InvalidOperationException
Exception message: Cannot register for ‘OnSendingHeaders’ event after response headers have been sent.
Reason & Fix:
- CRM instance was missing ‘Adxstudio License Key’ record.
- Post CRM connection, ADX would first check for the valid ‘License Key’. Since there was no ‘License Key’ record, Portal thrown error.
- To fix this, add the ‘License Key’ by going to ‘Advanced Find -> ADXStudio License Keys‘, add a key.
đ
Dynamics 365 â Different types of User Accounts and License consumption
Other day I was asked a question âWhat are the options to create/migrate users in Dynamics 365 application with no license consumptionâ
The options are
- Create a User of type âStub Userâ which does not consume license
- Sync a User from O365 to Dynamics 365 and remove the license later. This approach deactivates the User in D365 and free up the license.
- Create an Application User
- Create an Administrative User account
- Create a Non-Interactive User account
To know different options is crucial, especially, when you are migrating the Users from legacy systems and the Users are not expected to access the D365 application which should not cost any licenses.
In this article, I am going explain the different type of Users and how they consume the licenses.
Administrative User Account:
- An Administrative user is a user, who has access to the Settings and Administration features but has no access to any of the customer engagement functionality.
- Since the administrative user does not have access to customer data and any of the customer engagement functionalities, it does not require a Dynamics 365 (online) license.
- To create an âAdministrative Userâ
- Create a User in Office 365; (Admin Center -> Users -> Active users -> Add a user)
- Assign a Dynamics 365 license under ‘Product licenses’ tab.
- Go to D365 application and open the User record
- On the User form, under âAdministrationâ tab, âClient Access License (CAL) Informationâ section and select âAdministrativeâ for Access Mode.
- Final step is, remove the Dynamics 365 license of the User from Office 365, so that you can free the license and still the User can login to the application as ‘Administrative’
Non-interactive User Account:
- Non-interactive user is not a physical User and It is used for programmatic access to push or pull the data to/from Dynamics 365 applications.
- Non-interactive user let applications (i.e., Consoles, SSIS packages or ERP connector etc.) authenticate and access Dynamics 365 (online), without requiring a Dynamics 365 (online) license.
- Creation of Non-interactive user account is same as Administrative User Account, except setting the Access Mode to âNon-interactiveâ
- There is a limit of five non-interactive user accounts
Application User Account:
- âApplication Userâ is used while establishing server-to-server (S2S) authentication
- âApplication Userâ with conjunction of Azure Active Directory (Azure AD) will establish S2S authentication.
- âApplication Userâ does not consume license.
- Application users are created with a non-interactive user account, however they are not counted towards the 5 non-interactive user accounts limit.
Stub User:
- Stub user cannot log in, cannot be enabled, and cannot be synchronized to Office 365 and will not consume license.
- Stub Users are designed for records that have been imported that refer to this user but the user does not exist in Dynamics 365 (online).
- Stub users are user records that are created in Dynamics 365 using Data Import or using the Create or Create Requests methods of the SDK.
Licensed User:
- Licensed user is an User whom gets created in O365 with license and synced to D365.
- Licensed users must be assigned at least one Dynamics 365 security role to access Dynamics 365 (online).
- The service does not allow access to users who do not have at least one security role.
- Removing all security roles from the user prevents the user from signing into and accessing Dynamics 365 (online). However, it doesnât remove the license from the user.
Refer article for more details.
Notes:
Following are points to consider before Importing Users
- Imported Users will be in Disabled state in CRM. You have to run a follow up logic to enable Users or you can Bulk Enable users.
- Users’s Business Unit cannot be set during the import. Users will be assigned to the root business unit.
- âSalespersonâ will be the default role for all imported users. Import will fail if ‘Salesperson’ role is either deleted or renamed.
đ