API Access to Dynamics 365

[@owenbscott]

I REALLY need to update this video .. and I will! Apologies to those that are trying to follow it and not finding certain things. Will update ASAP!

[@Ks-oj6tc]

Very valuable information

[@johningram2153]

Great video, thanks. Right to the point, step by step of what you need to do to create and use API credentials.

[@eshop668]

Thanks Sir. May I know you mentioned "Application User in Microsoft Dynamics 365 Customer Engagement" as above, is this under Dynamic365 CRM? How can we get it in Dynamic365 ERP Finance & Operation?

[@blackfincloudservices2844]

Thanks E-Shop - Dynamics ERP F&O is a completely different system, not part of the so-called "DataVerse". I am by no means an expert or even a casual user of Finance and Operations, but my understanding is that you would use an App Registration in Azure to connect to that system in a similar manner that this video explains. At least the app registration part of it is the same. How it is applied specifically to F&O, someone with that experience would know, or maybe you can find it by specific searches.

[@aseelwajieh4695]

am not getting the application users tab, am using 2 different accounts for azure and dynamics 365, is that the issue?

[@rdhaundiyal1]

thanks, clear and concise

[@jamesT008]

Great...can you show how to fetch data with python and update data to D365 as well.... Precise i am looking to fetch data in odoo and update D365 and vice versa

[@blackfincloudservices2844]

Hi James - I think a good resource/starting point for this would be the GitHub repository from Dangoscomb - github.com/dangoscomb/pydynamics

[@MultiSaunak]

Please can you let me know how we push dynamics crm 365 auditing logs to any external SIEM. Although we have managed to forward logs but in the logs how can we identify that what the auditing event is as there is no info on event code or id

[@blackfincloudservices2844]

Thanks - have you had a look at this - this is an improvement over what it was earlier - and there are some unique identifiers there that may help contextually - docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/reference/audit?view=dataverse-latest

[@karunkrishna1111]

Excellent, only tutorial that explained enabling the app on the CRM side. Are you able to include an example of access the opportunity endpoint using postname? I am still getting 401 when making request. I am not able to get Auth Token, it mentions that admin needs to enable approval

[@blackfincloudservices2844]

Thanks, Karun - sorry for the delay - if you are attaching to an On-Prem instance, this might help - docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/webapi/setup-postman-environment?view=op-9-1. If you are attaching to an online version, you might find this helpful: docs.microsoft.com/en-us/power-apps/developer/data-platform/webapi/setup-postman-environment#connect-with-your-common-data-service-environment

[@MarkChristopherAquinoBlog]

hello sir, how come i cannot find the Appliciation User after clicking User? i didnt able to reach the application form. please help. thank you

[@blackfincloudservices2844]

Thanks for your question, Mark! Yes, since this video was created, Microsoft has moved the Application User feature/concept to make.powerapps.com be sure to switch to the right Environment). Couple of new things - visit make.powerapps.com to find those users, and also you will now see that all Service Principal User Names (of which App Registration is one) are now is prepended with a # sign. Please let me know if you cannot see those users at make.powerapps.com.

[@farrukhmohammed5471]

@@blackfincloudservices2844 hi Mark, thanks for this video. It is super helpful. I did try to look up the application users in powerapps and it does'nt exists. Is this the new view that one need to create? There is Administrative Access Users, Full Access Users, Schedulable Users, My connections etc.

[@blackfincloudservices2844]

@@farrukhmohammed5471 Yes, they removed that view. However, now that the application account (AKA Service Principal) accounts are pre-pended with a "#" sign, one thing you can do is create a simple view like "All Users where Full Name begins with #". That should do it.

[@richardcollins9862]

Great video. Clear and straight to the point. But how do you use it? Nothing about endpoints or am I missing something?

[@blackfincloudservices2844]

Thanks, Richard, for responding. Yes, I should definitely create another video about a few of the many ways in which you would use this method of connecting. I can think of three right off the bat: 1) With a console application written in C# with something like Visual Studio, consuming the Web API for Microsoft Dynamics Customer Engagement, where you use this App ID and Secret to authenticate for the console app (this is not to be confused with a Plugin, which you compile in Visual Studio and then upload using the Plugin Registration Tool, which does not require authentication because it's server-side.) 2) A third-party application, like ClickDimensions, where you are asked to enter an Application User ID plus a Secret to manage your ClickDimensions integration and 3) Creating integrations using something like Azure Data Factory, where it's allowed to use an Application User instead of a named user to read and write data to CRM. I hope that helps a bit. I do owe my channel some new videos, and this may be one of them. Thanks again ... Owen

[@muhammadshuja2012]

Great video. Thanks. I have one question, will this work for on-premises version as well?

[@blackfincloudservices2844]

Hi Muhammad - no, this is for online versions. For on-premises, you need to use the Web API - and of course that depends on the version of the on-premise environment. Hopefully you are using at least version 8.0 .... Here is some documentation for On-Premises version 9.1: docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/webapi/authenticate-web-api?view=op-9-1. 8.0 is out there - slightly harder to find, but it's there.

[@wachhagottoday]

Sorry but I struggled understanding the context of this. If you could use a scenario to paint it. Unless this is a technical thing and only for developers and i mean high code developers.

[@blackfincloudservices2844]

Thanks for getting through it, even though it wasn't clear about what it was about! The reason for this video, which is still valid, is that for a long time it was difficult to gain access to the API for Microsoft Dynamics 365 (on-premise, mostly), and now it's much simpler. This new(ish) method involves "Registering" an "Application" in Azure and then apply that application registration as a special type of user in Microsoft Dynamics and Power Apps. This simplifies the method by which we can gain API access to the back-end. You might say that this is mainly for developers, as you mention, but I would contend that you don't have to be a serious developer to make use of this information. Since Power Apps and Dynamics CE are low-code systems, we have a lot of people who are not developers creating Apps. Those people would find this useful as well. The scenario would be that a low-code/zero-code integration between some other system and Microsoft Dynamics/Power Apps needs to be created and Azure Data Factory is used (another low-code system) to connect these two systems. Well, an Application would be registered with a Secret that would then be applied to the connection you set up in Azure Data Factory. That's one scenario. There are many others.