IT planing for CRM impact

Dynamics Telephony policy is to have as little impact on your CRM as possible. Here are the impacts you need to consider.

As part of or submission to the Microsoft AppSource Store, install and basic tests were carried out by Microsoft Engineers.

Admin Level User will be required during the install phase. This is to allow for the installation of the entities described later. This user needs to be allowed install a solution in your CRM.

Authentication. Dynamics Telephony supports all authentication methods supported by CRM online or on-premises. When users use Dynamics Telephony, they simply logon to CRM as normal.

HTTPS and HTTP are both supported. The certificate for HTTPS needs to be trusted by Internet Explorer.

Install procedure is described HERE

Entities Installed by Dynamics Telephony are listed HERE. The entities are all standalone with no dependency in your standard entities on the Dynamics Telephony entities. They are installed as a solution that you can request to inspect. They can be uninstalled with no impact on your CRM.

Entities written by dynamics Telephony:
– Dynamics Telephony entity records.
Phonecall due to click-to-dial or incoming calls.
Note due to click-to-dial or incoming calls.
– (optional) create contact for unknown caller.
These records are written using the logged-on user. See relationships below:

entities for click to dial