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
Related
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/
Is it possible to access the SQL server database of a Dynamics 365 business central directly or can I access it only via APIs?
I advise you to review the link below, maybe it can help;
https://demiliani.com/2020/05/15/read-scale-out-with-azure-sql-and-dynamics-365-business-central/
Ugur
There's no way to get direct access to SQL from BC cloud. You would need to use the native connector to Business Central. Alternatively you could consider the Web Services page in Business Central or the API.
We are trying to send NServiceBus messages from a Microsoft Dynamics CRM plugin and running into issues like this:
Attempt by security transparent method [Our_Namespace].GetStandardBus(System.String)' to access security critical type 'NServiceBus.IBus' failed at [Our_Namespace].GetStandardBus(String endpointName)
The CRM plugins are running in the sandbox which means they are running as partial trust in IIS and we really want to keep it that way.
So my question is, is it possible to access NServiceBus from an IIS partial trust application?
Thanks,
Mark
Check out the Dynamics Adapter for NServiceBus:
https://github.com/ParticularLabs/NServiceBus.DynamicsAdapter
... contains an example application that demonstrates bi-directional integration between cloud hosted Dynamics 365 2016 and an on-premises NServiceBus system using Azure Service Bus Queues.
I am curious to know why we always need to register our CRM online instance on an Azure Active Directory in order to authenticate the Web API while accessing from outside CRM domain.
That is, for example, if I need to access CRM online instance through another website using CRM's Web API endpoint, then I must register my CRM instance to Azure Active Directory.
Though I am aware that, its a very nominal charge to create an Azure Active Directory, still I would need to subscribe to Azure even if I just want to perform some general research for CRM connectivity through Web API.
Why this is must? Are there any security considerations behind this?
Why can't we use the same authentication mechanism as we used to do with Organization service?
Any details on this will be much appreciated.
The CRM WebAPI uses OAuth2 and Azure AD is the only currently supported authentication platform to provide this (Windows Server 2016 will support OAuth2 for on-premise).
The Organisation service is a WCF service and as such uses SOAP for authentication and authorization. This is an entirely different technology stack that brings it's own set of problems, many of which the OAuth2 protocol tries to solve in this scenario.
Although you manage your CRM Online users through the Office 365 portal the underlying technology for these accounts is also Azure AD. Check if you can use this existing AD tenant created as part of your subscription rather than having to create another.
If you are using CRM online you already have aan Azure Active Directory. If you haven't already done so, you can signup for an Azure subscription and import the underlying AAD into your Azure subscription. You will need a credit card, but as far is I know using the Azure AD is free.
I need to be able to extend CRM 2011 which is running in the cloud. I need to be able to perform CRUD operations from a completely separate internet web site. What options do I have? I have zero experience with CRM. I just found out that the OOB web services can only be accessed within the context of CRM.
I just found out that the OOB web services can only be accessed within the context of CRM.
This is only true for the REST endpoint. Not for the other endpoints. You can access the IOrganizationService if you use .NET as basis or you could access the web services via SOAP.
Use the WSDL Endpoint
http://blogs.msdn.com/b/girishr/archive/2011/03/22/crm-online-2011-web-services-soap-sample-now-ready-for-emea-amp-asia.aspx
CRM 2011 exposes webservices through oData and SOAP endpoints. If you are using CRM 2011 Online you can hit these endpoints over the internet. If hosting CRM yourself, you can set it up for IFD (Internet Facing Deploy). I would suggest taking a look at the CRM 2011 SDK for oData and SOAP examples.