What is the most performant and secure method to call an on-premise API (integrated to on-premise systems not related to CRM) from a Dynamics 365 plugin in Azure?
Why do you want to user Dynamics API when you are already in Plugin for Azure.
Why not user native SDK for Dynamics on-prem .net4.6.2
Connect to Dynamics in Plugin using connection tool and use it.
Here is an example to do so, once connected you can perform CURD operation against dynamics.
https://crm365blog.wordpress.com/2018/05/27/connecting-to-crm-2013-2015-2016-and-dynamics-365-in-c/
one more article
https://rawishblog.wordpress.com/2018/07/16/how-to-connect-to-dynamics-crm-onpremises-ad-ifd-from-a-windows-form-application/
We just received an update to Dynamics CRM 9.0, but it seems like a get a unresolved reference when I try to programmatically access the Organization Service Endpoint.
The Uri I am using for this CRM online instance is https://xxxxxxxxxxxxxtest.api.crm.dynamics.com/XRMServices/2011/Organization.svc?wsdl&sdkversion=9'.
Please let me know if anything has changed that I cannot use this endpoint anymore?
Please check if the following blog article helps you. There are several different possibilities why this is happening, but with version 9, so are easily fixed:
https://community.dynamics.com/crm/b/nishantranaweblog/archive/2018/01/31/metadata-contains-a-reference-that-cannot-be-resolved-https-orgname-crm8-dynamics-com-xrmservices-2011-organization-svc-wsdl-amp-sdkversion-9-error-in-dynamics-365
Hope this helps.
The OData URL is
https://[ORGNAME].crm.dynamics.com/XRMServices/2011/OrganizationData.svc/[EntitySet]
The Organization URL is
https://[ORGNAME].api.crm.dynamics.com/XRMServices/2011/Organization.svc
(Double check the info by going under Settings -> Customizations -> Developer Resources)
2011 aka soap endpoints are deprecated, which means will be retired anytime. So you don’t have much time, earlier is better to convert to Web Api.
Beginning with the Dynamics 365 (8.0) release, a new OData 4 endpoint was added to the Dynamics 365 application stack. This endpoint is known as the Web API. The Web API provides a development experience that can be used across a wide variety of programming languages, platforms, and devices. The Web API is intended to replace the CRM 2011 endpoint, also known as the SOAP endpoint, for accessing the Dynamics 365 organization web service and other provided web services.
As of the release of Microsoft Dynamics CRM Online 2016 Update 1 and Microsoft Dynamics CRM 2016 Service Pack 1 (8.1.0), the CRM 2011 endpoint has been deprecated. The 2011 endpoint will be removed some time after the release of Dynamics 365 version 9. We plan to provide updates to the Dynamics 365 SDK assemblies and tools over the next several minor releases, retargeting them to use the Web API instead of the 2011 endpoint.
Till then check if TLS 1.2 is the issue like discussed here.
Check, please, that option "Don't use proxy server for local (intranet) address" off on Proxy tab in Network settings
I have an Azure Logic app that needs to connect to an on-premise Dynamics CRM instance.
I'd like to use the "Dynamics 365" connector so I had a look at this article
Connect to data sources on premises from logic apps with on-premises data gateway
But I can't see CRM as part of the supported data source.
For the moment, I plan to connect directly to CRM Sql Server database (available from the data gateway) but I am wondering if there is any workaround to use "Dynamics 365" connector to connect to an on-premise Dynamics CRM instance?
At the moment, the CRM connector does not support the on-prem data gateway. Another option is to use Custom Connectors and wrap your CRM Soap endpoints with it.
Custom Connectors support the on-prem data gateway, thus you can wrap your CRM Soap Endpoints with the Custom Connector and use either SOAP to REST or SOAP pass-through.
This is still in preview and the team are still working on the documentation, but it works :)
HTH
I am working on MS Dynamics and using CRM SDK to access the entities of dynamics. Code is running fine when I enter the credentials of Dynamics CRM online. I am stuck in a case in which other organization has desktop version of Dynamics CRM ie. 3.0 and they have let me to access their CRM via VPN because they have installed Dynamics CRM on their local network. I want to access the data as I need to import the data in other database as per requirement. but code is not authenticating the credentials . May be something is going wrong when there creates a discovery URL or something else.
How can I resolve it ?
we have an in-house exchange server and we would like to integrate that with our Online Dynamics CRM application at /CompanyName/.crm.dynamics.com
We do not have any online exchange account with Microsoft yet and do not plan to add that. I went to server profiles interface within the Email Settings and tried adding both exchange and POP3-SMTP. But nothing helped. Way the settings are, I don' think Microsoft even allows setting up on premise exchange server with Online Dynamics CRM.
Is that so or am I doing something wrong
Any clue where should I start.
CRM Online only supports Exchange Online so I don't think what you want to do is possible.
Supported email service configurations for server-side synchronization